<story><title>Professional Software Development</title><url>http://mixmastamyk.bitbucket.org/pro_soft_dev/</url></story><parent_chain></parent_chain><comment><author>dboreham</author><text>I like this book as a means to present the ways people describe how software is developed. However, as I read I&amp;#x27;m itching to annotate it with notes on &amp;quot;what really happens&amp;quot;. I&amp;#x27;ve worked in this business for a few decades now, in various locations and various sizes of companies, including a few that are household names. I have NEVER seen software built on the ground in exactly the ways one sees documented (documented anywhere, not just in this book).&lt;p&gt;A couple of things I don&amp;#x27;t see mentioned (apologies if they&amp;#x27;re in there, I haven&amp;#x27;t read every word):&lt;p&gt;1. Process does (and should) vary tremendously depending on factors including the organization size, organization maturity, market maturity, experience level of the people involved, budget, etc. The book seems to suggest that there&amp;#x27;s a one-process-to-rule-them-all.&lt;p&gt;2. Often there are significant unknowns about a project : unknown technologies, unknown market needs, unknown requirements. Being able to accommodate the unknowns, which can mean not expending effort trying to know something unknowable, is important. The book I think gives an impression of quite confident smooth progress toward project completion that I personally have never observed.&lt;p&gt;Also: The value of Rubber Chickens is not mentioned...</text></comment>
<story><title>Professional Software Development</title><url>http://mixmastamyk.bitbucket.org/pro_soft_dev/</url></story><parent_chain></parent_chain><comment><author>mixmastamyk</author><text>Author here, writing this book was one of the hardest things I&amp;#x27;ve ever done, and there is seemingly no end to the small issues I&amp;#x27;ve faced (both writing and technical).  Would appreciate some feedback to make it as good as it can be, AMA thanks.</text></comment>