Hey, do you have any recommendations for books I should have my non-technical cofounder read to help him understand how software development works.<p>Thanks
I don't understand "why" he must understand how software development works.<p>Is he making unrealistic requests?<p>Does he think you are wasting your whole day in notepad instead of doing real work?<p>When you tell him about a new cool rebase trick in git, he only stares without understanding a word?<p>Anyway, a book is too long. My recommendation is to try to find some nice post in the old blog of Joel Spolsky <a href="https://www.joelonsoftware.com/" rel="nofollow">https://www.joelonsoftware.com/</a>
Strong recommendation for The Pragmatic Programmer, Andy Hunt & Dave Thomas.<p>Agile Manifesto, which many "agile" techniques often forget as well: <a href="https://agilemanifesto.org/principles.html" rel="nofollow">https://agilemanifesto.org/principles.html</a><p>Test-Driven Development by Example, by Kent Beck. No other. Kent Beck doesn't even show up on the first page of Google anymore. The book is on page 6. But it's a human way to develop software, dealing with the human limits of the average programmer. The book is easier to read than most of the articles written about it.
The Mythical Man Month by Frederick Brooks. The examples are old, but the wisdom remains. Particularly the chapter (and CACM article) No Silver Bullet-- Essence and Accident in Software Engineering (1986).<p>Or just: <a href="https://xkcd.com/1425/" rel="nofollow">https://xkcd.com/1425/</a>