The Gods That Ate the Engineers
The article discusses the disconnect in software engineering between compliance with established standards and the actual needs of a project. It highlights the lack of measurable outcomes in software quality, making it difficult to assess the effectiveness of engineering decisions. The author argues that this gap has led to reliance on authority and conventions, resulting in practices that may not address the underlying issues in software development.
- ▪Software engineering lacks the ability to measure quality in the same way other engineering disciplines can.
- ▪The only validation for software is whether it works, which leads to all approaches being seen as equally valid.
- ▪This absence of measurement has resulted in reliance on authority and established practices, referred to as 'demigods'.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3596884) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Leon Pennings Posted on May 27 The Gods That Ate the Engineers #java #architecture #softwaredevelopment #programming How software development mistook its tools for its craft — and what it is paying for that mistake There is a conversation that happens in software teams every day. Someone proposes a simpler approach. Someone else says "but we need this to scale." The first person asks what scale is actually required.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
