With jokes, puns, and a rigorous problem solving based approach. You can download all the code samples used in the book from here: http://www.robmiles.com/s/Yellow-Book...

    Emphasizes possible, realistic and "best practice" approaches for managers, technical leads and self-managed teams. The author emphasizes efficient development concepts with an examination of rapid development strategies and a study of classic mistakes, within the context of software-development fundamentals and risk management. Dissects the core issues of rapid development, lifecycle planning, estimation and scheduling. Contains very good and practical discussions of customer-oriented development, motivation and teamwork. Explains such fundamental requirements as team structure, feature-set control (the dreaded feature creep in every project), availability and use of productivity tools and project recovery options. Relevant case studies are analyzed and discussed within the context of specific software development problems. Over 200 pages in this publication are devoted to a summary of best practices, everything from the daily build and smoke test, through prototyping, model selection, measurement, reuse, and the top-10 risks list. This publication is definitely recommended and will become a classic in the field, just as the author's prior publication, "Code Complete" already is.

    To make sure you get the most value for money possible I've also included the FREE eBook: "How to Study: 20 Tips to Get the Best Grades". It contains my best best advice on time management, goal setting and how to get the best grades with the least effort. It's advice that also transfers brilliantly well to professionals and the self employed who want to get ahead of the competition.----------HOW TO SPEED READ: FREE EXCERPT BELOW----------TECHNIQUE TWO- SEE MORE, MOVE YOUR EYES LESSAnother barrier to higher reading speeds is, again, learnt as a child. We learn to read by looking at one word at a time. It is perhaps the only way we can learn to read, but it offers a second obstacle by asking our eyes to move their fixation again, and again: which is time consuming.The human vision is much more capable than being asked to merely look at specifically one word at a time. You don’t have to move your eyes onto every word to be able to read a sentence.A quick step to become aware of this is to focus your sight in the middle of a sentence and notice that as you do so, you can in fact read the words around the central word, indeed without moving your sight from the center you may be able to read the whole sentence with your eyes resting at just this one space. If this is difficult, or the sentence is simply too long, mark two points in the sentence, one a third of the way in, and one two thirds of the way in, and use those as points to rest your eyes on while you read each word of the line of text. Using your wider vision, and attempting to see more will further help you to improve the speed at which you read as you minimize time spent moving your eyes.A useful technique is to use the above method and draw two lines down the page you are reading, dissecting it into thirds. Now practice moving your eyes only between these two points and reading all the words without any further eye movement. If you are struggling to take in the all the words in the line, try and relax your eyes, make them feel slightly lazy so that they aren’t focused so narrowly. Let your gaze be weaker, and soon you will be able to see more than you had before.

    There are currently a significant number of books on creating, documenting, and implementing software architecture, but precious few resources have addressed how to build a software architecture that aligns with a customer's overall business goals. In this new book, Luke Hohmann borrows from his extensive experience managing successful enterprise software projects to provide practical wisdom on creating and sustaining winning software solutions. This book helps technologists grasp the business ramifications of their decisions, and provides business-oriented software professionals (e.g. sales people and marketers) with better knowledge of how robust software can be built and maintained.