#begin The next big topic of this chapter is called It’s all writing. This section will dive into the many kinds of documentation we will have to write as pragmatic programmers. Andrew and David mention that we should treat english, or which ever language you or your...

#begin Ok; so next up is yet another section on testing. David and Andrew say that most developers hate testing. And I agree, as Uncle Bob would say, testing after the fact is really, really boring. You already know the code works because you just wrote it and tested...

#begin   The next section of the chapter is all about automation. Well, we talked about that before but let’s see what else Andrew and David have to say about it. They mention that automation is a way to ensure guaranteed repeatability. Well that sounds pretty...

#begin   Andrew and David kick this chapter off with the idea of no broken windows. Do you remember what this was about? You don’t leave broken windows in a building because if there’s one broken window and nobody fixes it, people expect its fine and no one will...

#begin   The last section of the chapter is about circles and arrow, which effectively just means CASE tools, UML or diagramming. I think its funny since even though UML is a standard its still not widely used. I remember an interview with Simon Brown, the...

#begin   Earlier we mentioned we would take another look at over analyzing the requirements. The following section of the chapter is all about the specification trap. But first, what exactly is a specification. Well, David and Andrew say that a specification is a...

#begin The next section of the chapter we will discuss is about knowing when to start, and stop or maybe pause for a bit. David and Andrew say you should listen to your nagging doubts. As a developer you are constantly doing things that work, or don’t. All of this...

#begin   The next section of the chapter is about solving seemingly impossible requirements. I think we’ve all faced such requirements before. What do we do when we’re asked to implement a requirement that’s impossible to implement due to current software...

#begin   Lets discuss the first section called “The Requirements Pit”. If you have attended some formal computer science education, or maybe more specialized in regard to gamedev you might know that courses describe requirements engineering or elicitation as a...

#begin   Evil Wizards The next section starts of with a really great insight. David and Andrew say that:”There's no denying it—applications are getting harder and harder to write. User interfaces in particular are becoming increasingly sophisticated.” Hahaha this...

#begin     Code That’s Easy to Test David and Andrew start this new section of with a description of people comparing software to an integrated circuit. Software components should be combined just as such circuit and such components must be known to be...

#begin   Refactoring Refactoring, one of my favorite subjects since it always feels good to clean up the code. As your game evolves it will be necessary to clean up some junk you left behind. This is not necessarily about tech debt but simply has to do with the...

#begin   Algorithm Speed Now, as we talked about in the introduction we will also discuss the topic of algorithm speed. This mostly boils down to being able to estimate with some level of precision your algorithm’s resources. Pragmatic programmers should be able...

#begin   While You Are Coding David and Andrew start new this chapter (6) off with a very shitty and outdated way of thinking and I’ll quote: “Conventional wisdom says that once a project is in the coding phase, the work is mostly mechanical, transcribing the...