Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Why Invisible Engineering Work Deserves More Recognition

Why do visible developers get more credit than those doing critical work? Explore the hidden costs of recognition in software engineering.

Why Invisible Engineering Work Deserves More Recognition

Invisible engineering work often goes unnoticed, but it is crucial to the success of many projects. By day, engineers build software that may never be seen by anyone except their own team. This includes fixing data import issues, executing smooth migrations, or adding review comments to prevent bad patterns from spreading. Evenings are spent writing in public, creating posts that reach more people in a day than their code alone might. However, the recognition for this work is often limited to a single achievement in search results.

Researchers have studied the importance of this "buried builder" work for decades. In manufacturing and product development, a 2001 MIT study found that organisations rewarded those who saved the day through heroic effort, rather than those who quietly prevented disasters. This led to a cycle where senior management increasingly consisted of individuals who had only saved the day, ignoring the work that prevented any disasters from occurring.

Healthcare has also grappled with similar issues, with patient safety traditionally measured by counting problems and fixing them. Researchers like Erik Hollnagel, Robert Wears, and Jeffrey Braithwaite advocate for a shift from "Safety-I" (preventing problems) to "Safety-II" (promoting safety). The message is clear: while we can measure failures, success is harder to quantify.

This is also true in software engineering, where we have incident dashboards but not for the countless ordinary days when everything runs smoothly due to careful work.

The knowledge and context that engineers carry is critical and often lives in the minds of individuals who rarely have time to explain it. Open source projects provide a stark example of this, with one maintainer maintaining critical libraries while having zero support. In 2014, the Heartbleed bug exposed a flaw in OpenSSL, maintained by one person with limited resources.

In 2022, a maintainer of the XZ Utils compression library faced similar struggles, ultimately leading to security breaches due to external pressure and mental health issues.

These are not isolated cases. In Tidelift's 2024 survey, 60% of maintainers reported not being paid for their work, and nearly 60% had quit or considered quitting. The measurement systems that celebrate visible achievements like conference talks and follower counts fail to capture the true value of this invisible work. Promotions, job offers, and reputations are often based on what can be seen and counted, overlooking the critical glue work that keeps teams functioning effectively.

This work includes onboarding, roadmap updates, and answering design questions, all of which are essential for a team's success.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at hackernoon.com →

Report a problem with this story

More in Tech

More from Friday 30 October →