Clean Agile

What Hacker News says

1. jjiceAug 2023
   I wasn't a huge fan when I read it a year or two ago. It's fine, but I think that there are a lot of things that just aren't that clean (which is a subjective take). Uncle Bob in general though is a favorite of mine. Highly recommend Clean Architecture, Clean Agile, and The Clean Coder.
   thread
2. kap7Jun 2021
   Just read:

   - Clean Architecture - Design Patterns: Elements of Reusable Object-Oriented Software - Domain-Driven Design: Tackling Complexity in the Heart of Software - Clean Agile

   and forget the rest. Life is short and those books are more than enough.

   thread
3. typlMay 2020
   Bob Martin's new book "Clean Agile" covers this topic well. The problem isn't dates or deadlines, it's arbitrary dates or deadlines that are not backed up by data that indicates whether or not they are achievable. Often we create estimates with no prior knowledge of the team composition and particularly their ability to apply their skills to the problem at hand. The only way to make good estimates is to give them work, let them start doing it, and observe their progress. You then can manipulate the scope of your project to determine what you want done (the highest value things) and estimate when you can get those things. The alternative levers (add a bunch of people, sacrifice quality) end up not working in software projects and become the "value destroying mistakes."
   Show morethread
4. jjiceFeb 2025
   Lots of negative comments about Uncle Bob in this thread. I personally didn't like Clean Code and really enjoyed A Philosophy of Software Design, but I do think that some of his other books are really solid.

   I accept that non-fiction books on anything will oversell the value of their way, and try to take what I can at a more moderate level. Through that lens, Clean Code didn't give me much, but Clean Architecture did. The Clean Coder is also an interesting read on professionalism in software, and Clean Agile is an interesting read on Agile roots. I don't know anyone that practices "true" agile (nor do I care to do so myself), but there are some really solid ideas in there.

   I get that Clean Code kind of had a cult-like following in that people followed it blindly, but damn some of these comments are just rude about Uncle Bob. I still think he's a pretty good author and has given me some advice through his other books that helped me a lot as a fresh faced dev.

   Show morethread
5. whynotmaybeJul 2023
   From Wikipedia, Uncle Bob made a book in 2017 and one in 2019.

   Do you know which one you're referring to?

   2017. Clean Architecture: A Craftsman's Guide to Software Structure and Design. Prentice Hall. ISBN 978-0134494166.

   2019. Clean Agile: Back to Basics. Prentice Hall. ISBN 978-0135781869.

   thread
6. mihaigalosSep 2022
   I loved this article.

   Countless times I had to estimate Jira "tickets" (actually called issues in Jira terminology) in hours. To this day, I fail to understand why and I haven't gotten a pertinent answer other than "the business needs it for planning, they're paying us, so you do it."

   Yet this contradicts at least 2 Agile Manifesto pillars:

   1. People and interactions over processes and tools (fostering the estimation ceremony + booking time rather than actual interaction or developer happiness).

   2. Reacting to change over following a plan (plan-the-work and work-the-plan over reacting to change).

   How do you even "do" estimates?! Clean Agile (ISBN-13: 978-0135781869) says "Estimates are never commitments. They are guesses."

   So it seems the business is trying to get a commitment out of an estimation, at hour granularity.

   What are your thoughts here?

   Show morethread