↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Five things that are killing my productivity as a developer (and how to potentially fix them)

The author says his productivity varies more with the team and project conditions than with task difficulty or interest. He identifies five recurring problems that affect output: late code review changes, meetings without a clear agenda, broken project setups, frequent priority changes, and micromanagement.

He recommends judging review changes by their cost and deadline impact, keeping meetings short and agenda-driven, warning the team early about dependencies or setup problems, limiting priority switches to real emergencies, and replacing control with honest communication and feedback.

Reading notes
#

  • productivity changes appear tied to the team and the project rather than to task complexity or enjoyment
  • review suggestions should be weighed against implementation time and deadline impact
  • if a change is large and the benefit is small, a backlog ticket may be better
  • meetings need a clear agenda and should stay short
  • conversations that do not need the full group should be moved offline or to 1-1 meetings
  • broken setup or dependencies can waste a full day if the team is not warned early
  • teams should share dependency and data setup issues so people can work safely
  • constant priority switching is presented as a sign of poor planning
  • roadmap planning should leave room for unexpected work
  • micromanagement is described as control and mistrust, not just status checking
  • managers should ask what is happening when output seems off and keep feedback open both ways