✳flâneur — a map of the web's best reading

Software engineering is about thinking, not typing | Organizing Chaos

jordankaye.dev · 1,745 words · saved by 1 readers

Software engineering best practices emphasize and value the importance of iterative work. They encourage working in ways that give us opportunities to make decisions frequently and adapt to changing circumstances. These principles are nearly ubiquitous and seem necessary for successful engineering efforts at large scales, but the concept is sometimes taken to an extreme that can be unhelpful. While it’s almost always a good idea to maintain the ability to iterate quickly and change our minds, that doesn’t mean that one shouldn’t take time to think before they begin to act. When confronted with a problem, rather than jumping directly to thoughts of “how can I fix this with code”, it’s often more effective to first carefully consider the universe of potential solutions. By the time code begins flowing into an editor, there should be a good idea of an overall plan; what is it that is actually being built towards? What concepts are being programming against? Should new foundational concept

Software engineering is about thinking, not typing | Organizing Chaos Software engineering is about thinking, not typing Oct 11, 2023 · 1698 words · 8 minute read Weeks of coding can save you hours of planning Software engineering best practices emphasize and value the importance of iterative work. They encourage working in ways that give us opportunities to make decisions frequently and adapt to changing circumstances. These principles are nearly ubiquitous and seem necessary for successful engineering efforts at large scales, but the concept is sometimes taken to an extreme that can be unhel

Explore this link on the map →

related reading