15 Workplace Barriers to Better Code

Meetings, clueless managers, and productivity metrics create a huge gap between you and the next great piece of software.

Yesterday we were forced to ship a product while users shouted about missing features; senior management warned that any delay could get us fired, leaving everyone feeling powerless.

Developers are expected to code at breakneck speed without proper resources—no extra staff, faster machines, or anything that lets programmers focus on writing code—much like a horse expected to run without being fed.

Below are the fifteen real‑world programming obstacles.

No.1: Meetings – Frequent, lengthy meetings interrupt developers’ flow, forcing them to switch from coding mode to discussion mode, often wasting an hour of productive work.

No.2: Answering All Emails – The endless stream of emails consumes time; developers resort to terse replies like “tl;dr,” and some teams try “no‑email days,” which can hurt communication.

No.3: Trying to Measure Productivity – Managers count commits, lines of code, or bug fixes, assuming numbers equal quality, but this encourages bloated code and overlooks unquantifiable aspects of good software.

No.4: Arrogant Developers – Some programmers dismiss previous generations’ code as inferior, leading to pride‑driven rewrites that slow projects.

No.5: “Fix Later” Mentality (Technical Debt) – Rushed shortcuts create patches and “technical debt” that accumulate and become larger problems over time.

No.6: Non‑Technical Managers – Managers without a programming background make decisions that hinder developers, often focusing on superficial metrics.

No.7: Developer‑Managers – Former star programmers turned managers may micromanage and obsess over low‑level details, neglecting the bigger picture.

No.8: Socially Skilled “Brogrammers” – Developers who rely on charisma over technical depth can cause friction, especially when team members have conflicting technical preferences.

No.9: Selfish or Cowboy Programmers – Neglecting error handling or writing untested, risky code forces others to spend time fixing avoidable bugs.

No.10: Poor Documentation – Writing documentation takes time, and when managers judge developers by code output, documentation quality suffers.

No.11: Becoming a Slave to Documentation – Excessive, outdated, or low‑value documentation can drown teams in paperwork, diverting focus from actual development.

No.12: Distracting Environments – Noisy, shared spaces, constant interruptions, and lack of quiet work areas make it hard for programmers to maintain concentration.

No.13: Cultural Fit – Teams that share similar work styles and values tend to work better; mismatched cultures lead to communication breakdowns.

No.14: Clinging to Legacy Technology – Defending old tech increases maintenance cost and hampers progress, as legacy code often requires costly translation and refactoring.

No.15: Desire for the Latest Tools – Chasing new frameworks or languages without solid justification forces developers to constantly rewrite code, incurring hidden costs.

Compiled from: http://www.infoworld.com/article/2611225/application-development/15-workplace-barriers-to-better-code.html Author: Peter Wayner Reposted by: CodeCEO (http://www.codeceo.com/article/15-barriers-to-better-code.html) Translator: Xiao Feng

Long press to recognize the QR code and open it in a browser.

Download the Dajiang Tang Online Courses app.

Supports Android and iOS.

Qunar’s latest and hottest video courses are all here!