Hello, world: why I am writing
What you'll find here: system design, Java/Spring, Go and a log of my study routine.
Published · Ler em português
- #Learning
- #meta
In this post
This is the first piece on the site. The idea is simple: learning in public. Each post is something I studied, broke, fixed or designed — written for the Danilo of six months from now and, with luck, useful to you too.
What’s coming#
- System design — real trade-offs: consistency, idempotency, queues, locks.
- Java & Spring — what happens underneath
@Transactional. - Go — concurrency without drama and idiomatic code.
- AI in engineering — agents, incident auto-remediation and LLMs in production.
- Learning — how I organize my routine, what worked and what didn’t.
A little taste#
In Go, a worker pool fits in a few lines:
func worker(jobs <-chan int, results chan<- int) { for j := range jobs { results <- j * 2 }}And in Java 21, virtual threads make blocking code cheap again:
try (var executor = Executors.newVirtualThreadPerTaskExecutor()) { IntStream.range(0, 10_000).forEach(i -> executor.submit(() -> Thread.sleep(Duration.ofSeconds(1))));}Comments are down below — feel free to use them.
Found a mistake? Let me know by e-mail