There are many different schools of thought in the world of IT, software engineering, and architecture today.
The
pendulum has swung so far in the direction of "Continuous delivery of
throwing spaghetti against the wall - to see what sticks" - that many
have lost sight of the need (and value) of doing __any__ deep design
work.
That has an often predictable outcome: "Continuous Rework".
Which is neither agile, lean, efficient, or economical.
Consider this feat of engineering:
"This digital model was created for the project of the virtual exhibition 'Prague at the time of Charles IV' and shows how the construction of the Charles Bridge took place in the 14th century"
"construction began at 5:31am on 9 July 1357...[and] was completed 45 years later in 1402" https://en.wikipedia.org/wiki/Charles_Bridge
Analysis. Design. Architecture. Planning. Calculations. Engineering.
All went into this effort.
Much good would accrue - if we make a distinction between what is appropriate for trial-and-error engineering - and what benefits may accrue to valuing some judicious levels of investment in deep design work.
Flailing may create the appearance of a lot of activity (and perhaps may seem to imply progress) - but, it is not a very efficient operating model.
No comments:
Post a Comment