Coding development philosophy

This is an off the wall question, inspired by the Jordan Greenhall interview on DAOStack, when he mentions the rare ability of the DAOStack team to resolve the problem of anti-rivalrous via both theory and practice, while mostly today’s code is happening at an incremental view with a focus on speed/deadline as if it was the only measuring stick, while the capacity or actual ability to not just think incrementally and instead to think about the architecture of the solution should be another measuring stick.

To put it in more simple terms, there’s a tendency in code development to solely focus on speed and deliverable (x-axis) without ever thinking about the architectural design of a solution (y-axis)

I believe that it is partly because the x-axis is easily measurable, hence controllable, namely by measuring time.

So I was wondering if anyone has any idea on that topic, and if so, how would you go about measuring the y-axis, namely the quality of the design. And maybe even how the DAOStack team feels about framing their solution in that fashion? Does that fit an existing philosophy or method practices at DAOStack?

1 Like