{
  "id": 21017347,
  "title": "Build Better Engineers, Not Just Better Software",
  "url": "https://urgent.news/2026/11/21/build-better-engineers-not-just-better-software",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T08:06:08.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jarihaikonen/build-better-engineers-not-just-better-software-4oo6"
  },
  "original_language": "en",
  "account": "In a coding project I was once a junior developer, tasked with a fix. I worked on it and opened a pull request, eager to share my progress. But later, the pull request was taken over by another developer who made changes and merged it without any review. I felt frustrated, not knowing why my version was different or how to improve it. They likely meant well, but the experience taught me a crucial lesson: helping someone solve a problem and solving it for them are not the same. As a lead DevOps consultant with over 20 years of experience, I often work with junior engineers. The tech lead or lead engineer, who is still hands-on, plays a vital role in guiding and mentoring these junior developers. By examining situations like my own, I have come to appreciate the importance of psychological safety in teams. Creating an environment where team members feel comfortable speaking openly, taking risks, and learning from their mistakes is essential. A lead must set the technical direction and bring the best solution to the table, but the primary responsibility lies in helping build a team that becomes increasingly capable of solving problems independently. When faced with a pull request containing issues, the temptation to take it over and fix it immediately is strong. However, this approach denies the author the opportunity to learn and finish their own work. Instead, it is better to provide constructive feedback, explain the concerns, and encourage the author to make the necessary changes themselves. Asking questions, allowing the author to explain their thought process, and guiding them through their reasoning can foster learning and growth. It is crucial to remember that people learn by doing and making mistakes. Taking over every time there are problems disempowers the junior developer and hinders their development. While there are situations where taking over is appropriate, it should be an exception rather than the default response. Before criticizing someone's work, take the time to understand their approach and reasoning. This empathetic approach not only helps the junior developer but also strengthens the team as a whole.",
  "summary": "I once worked on a coding project where I was effectively the junior. I had picked up a fix, worked through it and opened a pull request. I was pumped about it. I knew I still had a lot to learn, and I was looking forward to the review, because that was where the learning would happen. Later, I noticed the pull request had been taken over. Someone else had made their own fixes to it and merged…",
  "key_points": [
    "Lead DevOps consultants guide junior engineers.",
    "Psychological safety crucial for team growth.",
    "Constructive feedback encourages independent problem-solving."
  ],
  "editors_take": "Prioritizing mentorship over immediate fixes transforms technical leadership from a task of mere problem-solving into a strategic effort to build long-term team autonomy and psychological safety.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}