The analytics-service is a Kotlin/Spring Boot gRPC service serving KPI, trends, and entity data from ClickHouse/PostgreSQL. The API is its primary consumer. While the architecture is well-documented (CLAUDE.md is excellent), there are significant code quality issues: a monolithic main class, pervasive cross-service duplication, and inconsistent patterns.
Current markdown file viewing requires toggling between "read" mode and "source text" mode, causing disorienting context loss. When editing a file, the view switches modes and scrolls to a different position.
Implement a live preview mode that displays rendered markdown while allowing inline editing, similar to Obsidian's live preview feature.
before:
/ # strace -e write -c ./fakedata -l 100000 noun > /dev/null
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
100.00 0.333190 16 19785 write
------ ----------- ----------- --------- --------- ----------------
100.00 0.333190 16 19785 total| package me.lucapette.ext.klogger | |
| import mu.KLogger | |
| import java.util.WeakHashMap | |
| data class TimeDelta(val sinceStart: Long, val sinceLast: Long) | |
| data class TimeLog(val start: Long, var current: Long) { | |
| fun since(): TimeDelta { | |
| val now = System.currentTimeMillis() |
-
https://www.tripadvisor.com/Restaurant_Review-g187785-d785643-Reviews-Da_Nennella-Naples_Province_of_Naples_Campania.html Traditional, cheap, super funny. Max 15 euro per person. If they have it, try "pasta e patate", it's incredible.
-
https://www.tripadvisor.com/Restaurant_Review-g187785-d1034513-Reviews-Sorbillo-Naples_Province_of_Naples_Campania.html Top pizza place (top 5 are all same level) in Napoli. Among the cheapest and my personal favourite. Best pizza: Nonna carolina. With pesto.
-
https://www.yelp.com/biz/antico-forno-attanasio-napoli Pastry place. They make "sfogliatella" which is very local (and super good). There's two kinds: "frolla" (my fav) and "riccia". I suggest you try both :D
| variable repositories { | |
| default = { | |
| "0" = "fakedata" | |
| "1" = "deloominator" | |
| } | |
| } | |
| resource "github_issue_label" "gardening-label" { | |
| count = "${length(var.repositories)}" | |
| repository = "${lookup(var.repositories, count.index)}" |
Twitter was failing me badly so I quickly wrote down a random list of reasons why I think (of course, that's just my opinion) code challenges hurt diversity:
- A lot of people performed badly at exams at uni (or any other form of exam). I can correlate to this very well as I was getting really nervous when taking an exam. I think it's kinda of normal to see code challenges as an exam. I know of people that wouldn't apply because of this reason. After seeing a lot of bad usages of this hiring tool, I wouldn't apply in most cases either.
- I think it's safe to assume code challenges acts as a filter. All our hiring techinques do and that's fine. My "problem" with this one is that it brings a lot of false negatives. The challenge may be badly written, the person may not have the time to commit to it. And junior developers can get really scared by this.
- Code challenges are generally meant to hire the bar of seniority and I find that highly counterintuitive. Based on my experience, the more senior a person is,
| [1] pry(main)> Date.today | |
| NoMethodError: undefined method `today' for Date:Class | |
| from (pry):1:in `__pry__' | |
| [2] pry(main)> require 'date' | |
| => true | |
| [3] pry(main)> Date.today | |
| => #<Date: 2015-03-05 ((2457087j,0s,0n),+0s,2299161j)> | |
| [4] pry(main)> |
| class Array | |
| def self.toy(n=10, &block) | |
| block_given? ? Array.new(n,&block) : Array.new(n) {|i| i+1} | |
| end | |
| end | |
| class Hash | |
| def self.toy(n=10) | |
| Hash[Array.toy(n).zip(Array.toy(n){|c| (96+(c+1)).chr})] | |
| end |
| #!/usr/bin/env ruby | |
| require 'rubygems' | |
| require 'anemone' | |
| require 'optparse' | |
| require 'ostruct' | |
| Anemone.crawl(ARGV[0], {:discard_page_bodies => true}) do |anemone| | |
| anemone.after_crawl do |pages| |