A Good Coder is Considered Lazy, But Is That Always the Case?
Written on
Chapter 1: The Debate on Laziness in Coding
In the realm of software development, the notion that "lazy coders are effective coders" is often discussed. Yet, this statement is not universally applicable. The interpretation of "lazy" plays a crucial role in this debate.
Section 1.1: Defining 'Lazy' in Coding Context
The Secret Developer draws on a classic exchange between Alice and Humpty Dumpty to illustrate how definitions can vary. When it comes to the term "lazy," it can signify a reluctance to work, which usually leads to poor coding outcomes. Conversely, some may perceive lazy coders as those who are adept at streamlining processes and producing high-quality code. The Secret Developer reflects on personal experiences with different types of lazy coders.
Subsection 1.1.1: The Case of 'Sleepy'
During a stint at a small tech firm in Asia, The Secret Developer met a Java programmer nicknamed "Sleepy." This developer frequently arrived late, often appearing exhausted due to juggling multiple jobs. While they contributed a significant amount of code, their fatigue often led to delays and inefficiencies.
Your verdict: Lazy or not?
Section 1.2: Motivational Factors
Another instance involved a tech lead who struggled with productivity in the absence of deadlines. Although their work quality was commendable, they tended to procrastinate until the last minute, resulting in long hours to meet project goals.
Your verdict: Lazy or not?
Chapter 2: Distraction and Knowledge Gaps
In a more recent case, The Secret Developer worked with a colleague who often faced distractions at home, including caring for a young child. This situation led to a noticeable drop in productivity, as they would often log off early and respond to feedback only the following day.
Your verdict: Lazy or not?
Section 2.1: The Knowledge Gap
Another developer encountered had years of experience but demonstrated a concerning lack of practical knowledge in their field. Tasks that should take minimal time were often delayed, leaving simple queries unanswered for hours.
Your verdict: Lazy or not?
Conclusion: Redefining 'Lazy' in Coding
The Secret Developer concludes that all the aforementioned developers could be labeled as lazy. However, this doesn't inherently correlate with their coding capabilities. It’s vital to distinguish between temporary setbacks and a permanent state of laziness.
We should not confuse efficiency with laziness; instead, we should recognize the value in developers who seek out existing solutions, utilize third-party libraries, and are willing to ask for assistance. These actions are far from lazy and are indicative of smart coding practices.
About The Author
The Secret Developer, a professional software engineer, shares insights on Twitter @TheSDeveloper and contributes regularly to Medium.com. Today, however, they find themselves not coding at all—embracing that so-called laziness.