- Tracer Bullets
- Aside from the awesome analogy between software development and guns, this method of development makes a lot of sense to me. Why spend valuable time calculating all the variables before taking a shot at the target when you can fire off "tracer rounds" along side your "real ammunition" in a live environment? When operating in an unknown environment with the high likely-hood of changes occurring, rather than spending lots of time specifying and calculating in order to create something we hope will work we, instead, code a basic structure with minimal functionality to establish a starting point for further improvements.
- I, especially, like this because it's a technique which you can use to take that first step in coding a project. Sometimes when you take a high-level view of your project, it can seem like a daunting task. By starting with basic functionality first, then making incremental improvements to increase it's functionality, it allows you to get to work quicker and to make progress. For someone like me who likes to get into a project quickly and make immediate progress, this seems like a great technique. This all assumes that you have planned the project well in advance.
- The concept of Orthogonality resonated strongly with me. This describes the concept where two or more things are said to be orthogonal when changes in one do not affect any of the others.
- I've been a part of many projects where software modules are highly dependent upon others. Having been only a part of the "rebuilding" team, making changes to one part of the non-orthogonal code required me to make changes in several other modules as well. Understandably, some code may need to be dependent upon other modules for functionality. However, if you can isolate modules so that they are not dependent upon others it makes changing and updating the code much easier and development time is reduced dramatically. In addition, changes to the code reduces risk.
- I like this concept and will try to apply it in all future projects. While I have always had it in my mind that your code should incorporate independent modules, I have never been able to pen those thoughts as well as it was written in the text.
Friday, September 28, 2012
The Pragmatic Programmer - Chapter 2: Here's What I Thought Was Good
In chapter 2 of The Pragmatic Programmer, we read about "tips and tricks that apply at all levels of software development". According to the text, these are virtually universal methods. Here is my opinion on what was good and informative about this chapter: