Clean Agile
by Robert C. Martin · first published 2019
50% recommend50% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2012–2026Clean Architecture
Robert C. Martin
Recommended by 47 · mentioned by 10447 recommend · 104 mention47 recommend · 10447 recommend
2010–2025The clean coder
Robert C. Martin
Recommended by 53 · mentioned by 8553 recommend · 85 mention53 recommend · 8553 recommend
2007–2026The Practice of Programming
Brian W. Kernighan
Recommended by 90 · mentioned by 12890 recommend · 128 mention90 recommend · 12890 recommend
2007–2026Domain-Driven Design
Eric Evans
Recommended by 104 · mentioned by 191104 recommend · 191 mention104 recommend · 191104 recommend
2008–2026Clean Code
Robert C. Martin
Recommended by 298 · mentioned by 739298 recommend · 739 mention298 recommend · 739298 recommend
2018–2026A Philosophy of Software Design
John K. Ousterhout
Recommended by 163 · mentioned by 232163 recommend · 232 mention163 recommend · 232163 recommend
2007–2026The Pragmatic Programmer
Andy Hunt, Dave Thomas
Recommended by 353 · mentioned by 589353 recommend · 589 mention353 recommend · 589353 recommend
2007–2026Code Complete
Steve McConnell
Recommended by 393 · mentioned by 669393 recommend · 669 mention393 recommend · 669393 recommend
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…
on “Driving engineers to an arbitrary date is a value destroying mistake” ↗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.
on “A curated list of books on Software Architecture” ↗…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.
on “Ask HN: What are some older programming books that still hold up today?” ↗…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…
on “Less is more agile” ↗…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.
on “The bigger the interface, the weaker the abstraction” ↗…quickly that you won't be able to make the deadline in 6 months. Uncle Bob talks about it in depth in one of his lectures here: https://youtu.be/SVRiktFlWxI https://youtu.be/qnq9syXUuFE And in his book Clean Agile: Back to basics.
on “Ask HN: Do you think Agile/Scrum is beneficial for software delivery?” ↗…won't be able to make the deadline in 6 months. Uncle Bob talks about it in depth in one of his lectures here: https://youtu.be/SVRiktFlWxI?t=1807 https://youtu.be/qnq9syXUuFE?t=3400 And in his book Clean Agile: Back to basics.
on “Ask HN: Do you think Agile/Scrum is beneficial for software delivery?” ↗…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…
on “Clean Code vs. A Philosophy Of Software Design” ↗