Being the wise, old, programming sage that I am (hahahahahaha!), I’ve built up a set of practices that I use in my development work. Such information has been gleaned from those old things with pages in, er, books, that’s it, and some from forums, and some from official guidelines and other official guidelines (it’s always good to have a choice of standards).
Anyway, I was thinking of collating them into a book, but then realised it would be more of a pamphlet, no-one would buy it, hard work and effort is meant to be free these days (thanks to the internet), etc.
I still might tho’, as I have a lot of real-world, pragmatic experience on how software development usually happens (badly in most places), and if you are able to introduce your own rules to your own work, it gives the illusion of control. It would be more of a tips book, with things like “Specs? Hahahaha!” and “Tab spacing is your friend”.
Well, it might help junior developers
Anyway, it’s more like a series of blog posts, so I’ll probably go with that, and then tweet the post URLs accordingly – stay tuned!
