4 ms·
Maybe it’s just my own bias because I love prototyping… But I feel in software engineering there’s a fifth D that combines the first and last items on this spec
by pavlov 2y ago
Maybe it’s just my own bias because I love prototyping… But I feel in software engineering there’s a fifth D that combines the first and last items on this spectrum. (Sort of like magenta is a color that’s produced by the mix of wavelengths at the opposite ends of the visible spectrum.)
Designing by Doing can cut through a lot of wasted time. If a principal engineer builds a working prototype, it can immediately move the discussion past the “Is that even possible or realistic” stage where lots of ideas go to die.
Leading by doing is often a much better use of an experienced engineer’s time than promoting them to an architect role where they produce diagrams that nobody barely looks at. Design isn’t a panacea.
- vishnugupta 2y agoI agree 100% to this. I use analogy of Scout in Age of Empires game. Scout allows one to explore the terrain, mark areas of resources, enemies, their civilization type and hence strengths/weaknesses. Similarly prototyping enables simultaneous exploration of problem space and solution space. After prototyping one can propose a design/architecture which is rooted in ground reality. You are more clear about upstream/downstream dependencies. Might even uncover gaps in product specs.