I have been working in the industry for 8 years and am now considered a senior developer, also as a team lead.

Three years ago, my first child was born, and a few months ago, a second one arrived. While I don’t regret my decision to have kids at all, I do feel bad about how the lack of free time affects my career and how my knowledge falls behind the industry.

Before having kids, I used to spend a few hours a week on never-ending personal projects to learn new things. However, now I neither have the time nor the energy for that.

The only way that has worked for me is to read some tech books, which are often not about coding, and to read some blogs or subs like this.

However, I feel like this approach is too passive and is not providing the best outcome that I would expect.

Any tips there, perhaps from someone who was is similar situation?

  • @aport
    link
    English
    171 year ago

    Keeping up with current tech is part of your job, so do it on the clock. Senior developers are absolutely expected to spend time on experiments and exploratory projects; it’s how they can safely and confidently propose and lead major refactors and improvements.

    Understanding the potential risks and complications with a project supports your ability to properly scope, staff, and mentor.

    • @prwnrOP
      link
      English
      21 year ago

      This is a very fair point, similar to what some other members wrote. The only thing I need is to organize my work time a way that will make this possible and still let me perform in a similar pace as I do now.

      • @cliffhanger407
        link
        English
        211 months ago

        One of the biggest things you can be learning during this time if you haven’t already (and it’s an intensely uncomfortable thing to learn) is how and what to delegate. My projects don’t take me less time when I’m effective in this, but they do free up mental load for doing only the important grind-y work, and separately thinking about the things that need to be thought about.

        Junior devs are scary, and giving them actual responsibility is scary, but it’s also how they get more competent and eventually do more good work than things that need adjustment or rework.