Just because something doesn't have a name and isn't written down anywhere doesn't mean it doesn't exist. If you don't like agile, it doesn't mean you have no process. It just means you are following another process. Assuming you have a project that actually involves interacting with multiple programmers, your ability to interact with them is a key part of getting the job done.
If you're a lone cowboy doing it all alone, then good for you, but please state that upfront in your blog posts about how the software world is doing it wrong so we know you are evaluating things from a very unusual position.
If you aren't a sole programmer, then you've got a process. Maybe it's better than agile processes. If so, please, tell us what that process it.
This whole article reads like a racecar driver dismissing automotive technology because the only thing that matters is the skill of the driver.
If you're a lone cowboy doing it all alone, then good for you, but please state that upfront in your blog posts about how the software world is doing it wrong so we know you are evaluating things from a very unusual position.
If you aren't a sole programmer, then you've got a process. Maybe it's better than agile processes. If so, please, tell us what that process it.
This whole article reads like a racecar driver dismissing automotive technology because the only thing that matters is the skill of the driver.