Part III. The Process Pillar
The process pillar was created in order to define the steps required to get code from the developer’s brain to the user’s browser. It encompasses each permutation the code goes through, from qualified idea to validated design to accepted commit to deployed code.
If you’ve been doing development for long enough, you’ll probably notice that our processes have evolved immensely in the past several years. My first experience in web development involved being asked to digest two months’ worth of email correspondence, determine what the client was asking for, and then FTP into their server and make the necessary changes.
Fortunately, for most of us, we’ve learned from these mistakes and are following much better practices these days. Instead of FTPing changes sent in an email, we now:
- Use issue tracking and user stories to properly track workflows and mark ...