The Curious Engineer

All blogs / Engineering management / careers

Daniel Lebrero Berna Blog

danlebrero.com

Daniel Lebrero blog

Engineering management / careersSoftware / engineering practiceLisp / Clojure / Scheme

’16’17’18’19’20’21’22’23’24’25’26
Posts
135 from 17 Mar 2016 to 19 Aug 2025
Posting
now and then
Kind
personal blog
Feed
https://danlebrero.com/feed.rss

2025 1

  1. Book notes: Residues: Time, Uncertainty, and Change in Software Architecture

2024 11

  1. Book notes: Become an Effective Software Engineering Manager
  2. Book notes: The HP Way
  3. Book notes: Tidy First?
  4. Book notes: Unbundling the Enterprise
  5. Book notes: Who Does What By How Much?
  6. "do" for a small speed up of your REPL feedback
  7. Book notes: The Ascetic Programmer
  8. Book notes: Flow Engineering
  9. Book notes: Continuous Discovery Habits
  10. Book notes: The Staff Engineer's Path: A Guide for Individual Contributors Navigating Growth and Change
  11. Book notes: Deming's Journey to Profound Knowledge: How Deming Helped Win a War, Altered the Face of Industry, and Holds the Key to Our Future

2023 10

  1. Book notes: Wiring the Winning Organization
  2. Book notes: Code that fits in your head: Heuristics for Software Engineering
  3. Book notes: Wrong fit, Right fit: Why How We Work Matters More Than Ever
  4. Book notes: Never split the difference
  5. Book notes: Inspired: How to Create Tech Products Customers Love
  6. The Taxman notification: an IT horror story
  7. Book notes: High Output Management
  8. Client-side good practices when building third party API integrations
  9. Notes on book notes
  10. Book notes: Building Microservices - Second edition

2022 14

  1. Book notes: Investments Unlimited, a novel about devops, security, audit compliance, and thriving in the Digital Age
  2. Book notes: Remote Team Interactions Workbook: Using Team Topologies Patterns for Remote Working
  3. Book notes: An Elegant Puzzle: Systems of Engineering Management
  4. Application configuration good practices
  5. Schrödinger's functions: not the pure functions your are looking for
  6. Book notes: Design It!: From Programmer to Software Architect
  7. Are you asking too much from your team/tech lead?
  8. Book notes: Software Architecture: The Hard Parts
  9. But life had other plans ...
  10. CTO last day: reflections, mistakes, and some learnings
  11. Book notes: Staff Engineering: Leadership beyond the management track
  12. Book notes: Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
  13. The self-inflicted denial-of-service (DDoS) attack
  14. Book notes: Turn the Ship Around!

2021 25

  1. My personal path to Senior developer ... and beyond!
  2. Book notes: Sooner, safer, happier: Antipatterns and patterns for business agility.
  3. Book notes: Fundamentals of Software Architecture
  4. Implementing DORA key software delivery metrics
  5. Book notes: Grokking Simplicity
  6. Book notes: The Subtle Art of Not Giving a F*ck
  7. Book notes: Designing Data-Intensive Applications
  8. Book notes: Zen & the Art of Motorcycle Maintenance
  9. Book notes: Thinking in Systems.
  10. First ever resilience test
  11. CTO day 7: Lucky Lotto, chaos engineering but for teams
  12. Book notes: Shape Up: Stop Running in Circles and Ship Work that Matters.
  13. CTO day 6: Building bridges with a "Week of little things"
  14. Book notes: Unlearn: Let Go of Past Success to Achieve Extraordinary Results
  15. CTO day 5: Building bridges with "Adopt a developer"
  16. Book notes: 97 Things Every Engineering Manager Should Know
  17. Book notes: Value Stream Mapping
  18. The feeling of Trunk-Based Development
  19. Book notes: A Philosophy of Software Design
  20. CTO day 4: Team building with "I dare you" challenge
  21. Book notes: Project to Product
  22. Prometheus in a Clojure stack: Duct, Jetty, Compojure/Reitit and Hugsql
  23. Book notes: Team Topologies
  24. Book notes: Level Up Agile with Toyota Kata
  25. Continuous improvement with Toyota Kata

2020 21

  1. CTO day 3: Meeting "The Business"
  2. CTO day 2: downsizing the team
  3. Course notes: Time Management for Technical Leaders
  4. CTO day 1: first steps and hiring framework
  5. Where TDD falls short, find yourself a good REPL
  6. Book notes: Good Strategy, Bad Strategy
  7. Book notes: Elements of Clojure
  8. Book notes: The Manager's Path
  9. Book notes: The Pragmatic Programmer, 20th Anniversary Edition
  10. Book notes: Implementing Lean Software Development
  11. You dont believe in clean code
  12. In case of doubt, ask for clarification
  13. Book notes: No-Nonsense Leadership
  14. Virtual backgrounds for remote Software Developers
  15. Book notes: The Lean Mindset
  16. Authorization service handover talk
  17. Book notes: The Unicorn Project
  18. Expectations for GOTO Oslo conference
  19. Book notes: Accelerate, building and scaling high performing technology organizations
  20. Software development and LEGO blocks
  21. Should I introduce an API Gateway in my workplace?

2019 6

  1. Apache Http Client and Asynchronous HTTP client timeouts explained in pictures
  2. Book notes: Becoming a Technical Leader
  3. Java with a Clojure mindset
  4. Architecture decisions: the belligerent contrarian and the rule of three
  5. Other reasons for TDD: Baby steps, ROI, Evil Manager Syndrome and Watching the watchmen
  6. Kodsnack podcast: The immediate feedback loop

2018 19

  1. RocksDB range queries in KafkaStream: dealing with big results
  2. If I ever write a book ...
  3. REPL driven development: immediate feedback for you backend code
  4. How to do a Java/JVM heap dump in Kubernetes
  5. How to convince your company to use Clojure
  6. In KafkaStreams, when to choose between a KTable or a KStream?
  7. Kubernetes explained in pictures: StatefulSets, Persistent Volumes and Headless Services
  8. Kubernetes explained: the theme park analogy: auto scaling, taints and affinities
  9. Kubernetes explained in pictures: the theme park analogy
  10. Habits of efficient developers - WeAreDevelopers 2018
  11. A more efficient developer: Go and have a rest
  12. Per user rate limiting with OpenID connect and Istio in Kubernetes
  13. Habits of efficient developers - slides
  14. Did you read my email?
  15. Kafka, GDPR and Event Sourcing - Implementation details
  16. Kafka, GDPR and Event Sourcing
  17. Kafka, distributed coordination and the actor model
  18. Production data never lies
  19. Easing open source contributions with Docker

2017 18

  1. How to Docker Compose a developer environment: an open source example
  2. Swagger Search: Finding an endpoint in your microservice primordial soup
  3. Why to Docker Compose a calm environment
  4. A more efficient developer: write programs for yourself
  5. Applying stability patterns: a case study - Devoxx PL 2017
  6. A more efficient developer: master your IDE
  7. A more efficient developer: disable notifications
  8. Error budget: Google's solution for innovating at a sustainable pace
  9. Atoms, delays and side effects: a resource management idiom for Clojure
  10. Delay: Clojure's forgotten concurrency primitive
  11. Testing or Monitoring? MTBF or MTTR? Make your choice!
  12. Clojure's most important lesson
  13. Automating resilience testing with Docker and Property Based Testing - Devoxx UK 2017
  14. Joins on stateful stream processing using Kafka Streams' KTables and GlobalKTables
  15. Documenting your architecture: Wireshark, PlantUML and a REPL to glue them all.
  16. Kerberos explained in pictures
  17. Proof of concept using KafkaStreams and KTables - implementation notes, gotchas and Docker Compose example
  18. Proof of concept using KafkaStreams and KTables

2016 10

  1. Why Java? Why Clojure?
  2. Automating resilience testing with Clojure and Docker - EuroClojure 2016 video
  3. The boy who cried wolf, an IT tale
  4. Automating resilience testing with Clojure and Docker - EuroClojure 2016 slides
  5. Good tests, Bad tests
  6. REPL Driven Development - Voxxed Days Belgrade 2016 video
  7. The broken promise of static typing
  8. The tragedy of 100% code coverage
  9. Logging levels: the wrong abstraction.
  10. Lines of code actually matters.