Is Design Dead? (Commentary)

Reckless programming is a hobby of every high schooler with interests in computer sciences, or any computer sciences freshman.

We tend to think that if we know some of the quirks of the given programming language, we do not have to think too much about what goes into developing, because we are not entirely sure about how the program is gonna look like either functionally, or in code, we just do what sounds right for us.

Apparently, "reckless programming" shares its main philosophy with the more official sounding (official-ish) "extreme programming", when it comes to complete and utter disregard of design and/or planning. We know what our code's goal is, we'll know if it accomplishes it, we do not really care about how each module or part of the code works towards this goal, or how such modules will change, but we may know how we want them to change towards the goal.

Here's the thing, though, disregard for rules, although fun, also carries the stigma of messy and unmaintainable code. If no planning is done for the development, we cannot expect to have plans for when everything finally fails.

On top of this, if refactoring is not considered, well, we are gonna have to start all over.