If I had my druthers, which I never will, I would insist on one thing: that anyone who tries to insist that I use a fixed, formal process for developing software must first read the Tao Te Ching.
I have few if any Taoist leanings myself, mind. It's just that I don't trust a proponent of, well, anything to be running off of any logic beyond buzzwords and glossy pictures. If they can read the Tao Te Ching and still think that their process is a good idea, they're at least not likely to be running on appeal-to-authority.
I should admit: I do not work in large-scale software development. There are all of three programmers on the team, including me, and the application's primary users work in the same lab as we do, and this lends itself to what — were I given to buzzwords — I would refer to as a highly-adaptive iterative development process. (But I'm not, so I don't.)
I suppose my objections boil down to these:
1. The management of resource consumption consumes resources.
2. You cannot squeeze blood from a stone, nor quality from a poor programmer.
(TBC)
(Also I figured out exactly what I was trying to do yesterday. It's actually easily doable!)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment