Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Build Better Engineers, Not Just Better Software

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…

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.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

A trash cleanup that deleted records a day early, and how I tested it in 2 minutes

Twenty, the open-source CRM, keeps deleted records in the trash for 14 days before deleting them for good. At least, that's what it says.

  • CRM Twenty retains deleted records for 14 days before permanent deletion.
  • Bug caused record deleted at 23:59 UTC to be permanently deleted at 00:10 UTC.
  • ChronoStack allows testing of time-based features in two minutes.

Twitter/X API Rate Limits in 2026: The Complete Guide

The #1 Pain Point for Twitter API Developers If you've worked with the X (formerly Twitter) API for any length of time, you've hit a rate limit. It's practically a rite of passage.

  • Twitter/X API rate limits changed in February 2026 to a pay-per-use model.
  • New accounts receive a $20 credit and first auto-recharge match up to $50.
  • Responses include three rate limit headers: limit, remaining, and reset timestamps.

More from Saturday 21 November →