Top all-time · #3031
Daniel Lebrero
Personal blog · danlebrero.comprogrammingcareer
Daniel Lebrero's personal blog at danlebrero.com covers programming and career. Since 2017, 25 different Hacker News readers have linked it 32 times, most often “Lucky Lotto, chaos engineering but for teams”. It is still writing: the last post was on 2025-08-19, and you can follow it by feed.
Too few sampled comments (6) to say how often HN recommends it.?
Why HN links it
Daniel Lebrero's CTO diary posts on downsizing and team churn, plus a post on generating sequence diagrams from a running system with Clojure and PlantUML, are linked by HN readers.
Summarised by Claude from a sample of 6 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Daniel Lebrero blog
Most-linked posts?
- Lucky Lotto, chaos engineering but for teams3 people · 3 mentions · first linked 2021-07-01
- CTO day 2: downsizing the team2 people · 2 mentions · first linked 2021-01-10
- Documenting architecture: Wireshark, PlantUML and a REPL to glue them all (2017)2 people · 2 mentions · first linked 2018-06-19
- Book Notes: Zen and the art of motorcycle maintainence2 people · 2 mentions · first linked 2021-08-04
- But life had other plans2 people · 2 mentions · first linked 2022-03-23
What Hacker News says?
"We couldn't operate their business and continue collecting data from their customers, while continuing to meet our own high standards as a global company." My hunch as an outsider is that Smyte wasn't GDPR compliant. Their leadership knew it, they knew they couldn't easily become so (for instance, they may have been using Kafka in a way where compaction wouldn't help, and didn't want to build an encryption-based mo…
Comment linking /2018/04/11/kafka-gdpr-event-sourcing/
on “Twitter ‘smytes’ customers”Submitted But life had other plans as a story · 1718 points
HN discussionMy favourite Wireshark link: https://danlebrero.com/2017/04/06/documenting-your-architect... Generating a sequence diagram of a running system w a bit of Clojure code and PlantUML mixed in.
Comment linking /2017/04/06/documenting-your-architecture-wireshark-plantuml-and-a-repl/
on “How I use Wireshark”Submitted Documenting your architecture: Wireshark, PlantUML and a REPL to glue them all as a story · 309 points
HN discussionTake one full day every other week where you play around, learn and explore. If you have not been able to do this at least 5 times last quarter - why not? What can we do to allow for that to happen. This is an example of an actual goal I have for members of my team - it is Specific, Measurable, Attainable, Realistic/Relevant and Time-bound. It's also tangential to the OP's topic here in a couple of ways. Good things…
Comment linking /2021/06/30/cto-dairy-lucky-lotto-chaos-engineering-for-teams/
on “Ask HN: Why can't I learn anymore?”Submitted Kafka, GDPR and Event Sourcing as a story · 184 points
HN discussionSeems like this comment and this article: https://news.ycombinator.com/item?id=25713859 https://danlebrero.com/2020/12/02/cto-diary-downsizing-team-...
Comment linking /2020/12/02/cto-diary-downsizing-team-firing/
on “Microsoft has started layoffs today”Submitted Documenting architecture: Wireshark, PlantUML and a REPL to glue them all (2017) as a story · 141 points
HN discussionFriendships can transcend teams, personalities are not going to be modeled in software and 'personal situation' is a great way to accidentally make a bad situation worse, for instance: by deciding to keep someone who has a family in favor of someone who does not but who is instrumental to the company in non-obvious ways. So no, I don't see that particular part addressed well or even at all through those three sets o…
Comment linking /2020/06/10/you-dont-believe-in-clean-code/
on “CTO day 2: downsizing the team”Submitted Lucky Lotto, chaos engineering but for teams as a story · 139 points
HN discussionAt least one CTO has actually tried exactly that: https://danlebrero.com/2021/06/30/cto-dairy-lucky-lotto-chao...
Comment linking /2021/06/30/cto-dairy-lucky-lotto-chaos-engineering-for-teams/
on “Theory-building and why employee churn is lethal to software companies”Submitted CTO day 2: downsizing the team as a story · 94 points
HN discussionSubmitted Clojure's most important lesson as a story · 45 points
HN discussionSubmitted Team building with “I dare you” challenge as a story · 15 points
HN discussionSubmitted But life had other plans as a story · 5 points
HN discussionSubmitted How to Docker Compose a developer environment: an open source example as a story · 5 points
HN discussionSubmitted Delay: Clojure's forgotten concurrency primitive as a story · 5 points
HN discussionSubmitted CTO last day: reflections, mistakes, and some learnings as a story · 4 points
HN discussionSubmitted Book Notes: Zen and the art of motorcycle maintainence as a story · 3 points
HN discussionSubmitted You dont believe in clean code as a story · 3 points
HN discussionSubmitted Kerberos Explained in Pictures as a story · 3 points
HN discussionSubmitted Kubernetes explained in pictures: the theme park analogy as a story · 3 points
HN discussionSubmitted Atoms, delays and side effects: a resource management idiom for Clojure as a story · 3 points
HN discussionSubmitted Testing or Monitoring? MTBF or MTTR? Make Your Choice as a story · 3 points
HN discussionSubmitted Good tests, Bad tests as a story · 3 points
HN discussionSubmitted Zen and the Art of Motorcycle Maintenance as a story · 2 points
HN discussionSubmitted "The HP Way: How Bill Hewlett and I Built Our Company" by David Packard as a story · 2 points
HN discussionSubmitted Toyota Kata in Software Development as a story · 2 points
HN discussionSubmitted Other Reasons for TDD: Baby Steps, ROI, Evil Manager and Watching the Watchmen as a story · 2 points
HN discussionSubmitted Kerberos explained in pictures as a story · 2 points
HN discussion
