
Dynamics of software development
by McCarthy, Jim · first published 1995
63% recommend38% neutral
Why HN recommends it
Practical, experience-based look at the human and team dynamics of building software, useful for working engineers and managers; valued for its frank, philosophical take on project management and developer behavior.
Summarised by Claude from recommending comments
"McCarthy has distilled a veteran's hard-won know-how into 54 memorable, pragmatic maxims - short essays on defining, building, shipping, and marketing software successfully, whether commercially or in-house. With a grown-up wit that's by turns homespun and sophisticated, McCarthy tells you how to maintain your cool ("Don't Flip the Bozo Bit"), organize a crack team ("Get Their Heads into the Game"), analyze the customer and the competition ("Alone? A Market Without a Competitor Ain't"), handle uncertainty and schedule slips ("When You Slip, Don't Fall"), make commitments with integrity ("Be l
Affiliate links. As an Amazon Associate I earn from qualifying purchases.






…longer > having to worry about the problem for the duration of the > project and (b) having a convenient scapegoat to blame if > the promise is broken. > Jim McCarthy, in his excellent book, Dynamics of Software > Development, suggests that the project manager needs to > confront this head-on and persuade the customers and/or > senior management that they need to share some of the > burden of uncertainty [around schedule,…
on “All late projects are the same (2011) [pdf]” ↗…couldn't see the 10000 ft view if you hit him on the head with it because ... ooh, look, shiny! He had to be micromanaged because his own steering mechanism was faulty. May I recommend that you read Dynamics of Software Development? Because it sounds a lot like you want to flip the bozo bit over there. http://www.amazon.com/Dynamics-Software-Development-Jim-McCa...
on “Ask HN: How do you cope with incompetent team members?” ↗The Analysis of Art by Dewitt Parker. This was referenced in Dynamics of software development by Jim McCarthy. They're both pretty good but the Parker book is kinda rare. Propaganda and Information Warfare in the Twenty-First Century by Scot MacDonald, it's purely academic but also a fantastic…
on “Ask HN: What are the best unknown books you have read?” ↗"Dynamics of Software Development" by Jim McCarthy
on “Ask HN: What language-agnostic programming books should I read?” ↗Dynamics of Software Development, by McCarthy.
on “Ask HN: Best book / resources on leadership, especially for tech teams?” ↗$10 or so spent on the dynamics of software development by jim mccarthy.
on “Ask HN: What is the best money you have spent on professional development?” ↗…developers you work with. The Mythical Mammoth doesn't have any of these problems, and is a great book, and one worth reading simply so you can have a sense of what building software actually entails (Dynamics of Software Development is another older book that has aged somewhat well --- as have all of Joel Spolsky's posts on Joel on Software; in fact, I'd probably start there). But while this stuff will help you understand the work…
on “Ask HN: Best resources for non-technical founders to understand hacker mindset?” ↗These are old, but I got a lot this year out of 'Dynamics of Software Development', McCarthy and 'Working Effectively with Legacy Software', Feathers.
on “Ask HN: Best book you read in 2010 and briefly why” ↗…format, which I listen to on my commute and when walking the dog. Personally, I would love to see more "philosophical" programming books in audio format such as "Pragmatic Thinking and Learning", or "Dynamics of Software Development".
on “The Hacker Shelf: Collection of free books for the intellectually curious” ↗…no one else was awake or online at the same time to discuss them. Eventually he became the architect by virtue of operating in isolation, where we couldn't discuss his decisions. McCarthy's 1995 book "Dynamics of Software Development" has a chapter devoted to this phenomenon.
on “Makers, Don't Let Yourself Be Forced into the 'Manager Schedule'” ↗No, please, instead of pointing out everything that is wrong in your reasoning: Please read a referent book about managing software development teams. For example "Peopleware", or "Dynamics of Software Development". Both a bit older, but valuable classics. The second one actually written by a relatively less technical author, a product manager at Microsoft. Maybe then you'll understand a bit more. By the way -…
on “The Worst Programmer I Know (2023)” ↗Nice reference to being seen as a bozo, presumably a la "Don't flip the bozo bit" from Jim McCarthy’s rule No. 4 in Dynamics of Software Development, explained well here: https://www.forbes.com/sites/forbestechcouncil/2018/08/13/th...
on “The secret of academic success, or fun filled failure if you prefer” ↗…book, although Weinberg talks frequently about "egoless programming", I can't see any (isolated) principles or guidelines, much less a list of commandments. I can't find an online version of McCarthy's Dynamics of Software Development to check what's in that. [0] https://www.techrepublic.com/article/the-ten-commandments-of...
on “Dad and the ten commandments of egoless programming (2012)” ↗…walls and involve everyone intellectually. This is real, if people aren't involved with the product, you are going to get crappy result. I am saying nothing new, but what already Jim McCarthy said in Dynamics of software development. But this is more true for projects, where your team is spread across different geographical locations. 3. Iterate. Short iterations, deliver, continuous integration and continuous deployment. Do not…
on “10% unemployment yet every startup in NYC struggling to hire” ↗…doing that process. You can even ask them why they have one. For instance I've got a copy of the 1926 text The Analysis of Art by Dewitt Parker because of Jim McCarthy's praise for the text in his book Dynamics of Software Development.
on “Does Your Office Have a Library?” ↗