In software development, we have philosophies, expressed in methodologies. One is to plan extensively, before a line of code is written and committed, to see and foresee every angle, to analyze and gather information, and step confidently forth with the knowledge youve accounted for all of the variables that might be involved (this is a small exaggeration, but then, so will be its comparative). Another is a rush, gathering information in every step, making trials and tests and stabs, and iterating until you get it right - or right enough. The unknowns are met iteratively, creatively, without a net, but tight rules enforcing no rules at all. Both have their strengths, and their flaws. To follow their letter, expressed in these methodologies, whether Waterfall, Prototype, Agile, Scrum, and so on, is, on observation, both undesirable and impossible, and yet, the advocates of one approach above another argue endlessly, and argue the strengths of even the most similar, and can be as easily as passionate as denominations of a belief system. Ive experienced many of these methodologies, on projects, some (most) successful, others failing for different reasons - none ideal. And so, Ive developed a philosophy of my own over the last fifteen years, and I find it similar to the philosophies I evolve in life. And yeah, I sweep for logical fallacy and confirmation bias like a submarine in enemy territory checks its six. There are no perfect solutions, no unflawed philosophies, no methodologies without vice. You evolve and adapt to the problems at hand, and shape your solutions to not only what you know, but what the people working with you do, bringing your strengths, your flaws, and harnessing their strengths and flaws with your own. You demonstrate your methods, your knowledge and vision, the summa of your experience, and when you inevitably fail in some aspect, you seek the wisdom of others often similar, and some who are sometimes very different and inscrutable. And if a tenet or two broken results in a stronger solution, you own the philosophy and methodology that emerge. Until the next iteration. :)
Posted on: Sat, 12 Apr 2014 03:08:49 +0000