Chapter 62. Everything Is Just Ones and Zeros
Lukas Ruebbelke
Programming is inherently complex because we are trying to capture and express a reality that is, by nature, very complex. To further complicate the issue, our exposure to the full nature of the complexities of our domain is constrained to a particular and limited context, which is heavily influenced by where we fall in the organizational chart. For instance, frontend developers are experts at building web applications, but rarely understand the infrastructure required to put those applications into the cloud. The immediate symptom of this condition is that we develop a myopic view of our world and establish causal relationships where none exist. The longer-term and ultimately more costly outcome is that we end up doing the same things over and over at every abstraction layer and calling them by different names.
As engineers, it is easy to get fixated on the ergonomics of a particular framework or technology and to project our frustrations onto the perceived deficiencies of whatever we are working with at the time. Though a reasonable reaction, it usually results in a causal association where there is a correlation at best. The most common example I see occurs when someone tries to explain why they do not have adequate test coverage in their project. The response usually goes something ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access