11

It's utterly frustrating to work with someone who has been in the same job for five years but still hasn't bothered to learn the basic tools necessary to do their job effectively. It's like they're stuck in a time warp, refusing to adapt and improve their skills.

How can you possibly expect to be successful in your career if you're not willing to invest time and effort into learning the tools of your trade? It's not rocket science, and these tools are there to make your job easier, not harder.

And what's worse is when these same people complain about their workload, blaming the tools for their inefficiency. Well, guess what? If you took the time to learn how to use them properly, maybe you wouldn't be drowning in work right now.

It's not even about being tech-savvy or a quick learner. It's simply about taking some initiative and responsibility for your own professional development. It's about having the basic level of competency required for your job.

Not to mention that constantly asking for help and guidance on tasks you should be able to handle on your own is not only a waste of your colleagues' time but also reflects poorly on your work ethic and reliability.

So, please, if you've been in the same job for five years and still struggle with basic tools, do yourself and your team a favor and take the time to learn them. It will make everyone's lives easier and improve your chances of success in the long run. Don't stay stagnant and hold yourself back – embrace opportunities to learn and grow. Your career will thank you for it.

The tools in question is Kubernetes and it's directly related to the persons day-to-day work (SWE + SDET mainly), 5 years is more than enough time to learn and adapt to a new toolset, and yet this particular person refuses to invest time into it. It's frustrating, to say the least, but also a disservice to themselves as they are limiting their potential and hindering their own career growth.

Comments
  • 4
    Putting in the absolute minimum effort necessary to not get fired is somehow simultaneously based and cringe.
  • 0
    I agree. But I also try giving these people the benefit of the doubt unless they are anti-learning.

    Some devs need to be encouraged thar it's OK to take time off their "daily tasks" to go learn a new skill properly.

    This is something many of us do on our own without telling anyone but some old timers have the sense that they are being watched and need to deliver every hour of the day.

    I find that it helps when you have a strong dev team to pull these people along for a course or something. Tell the managers "We'll spend next Friday doing competence development" - it's often okayed. But not something an old timer might have thought was possible.
  • 2
    And as a side note: double check before you call someone as a slacker.

    I once joined a new team and was shocked to see a senior dev didn't know our deploy process

    But turned out they were learning so much other stuff and were involved in dozens of other niche things - that they had been told to leave build tooling to the rest of the team 😆 (They handled everything from our clientside build tooling, some databases, elasticSearch, some CMS tools, SEO-tools, performance tools, Analytics - and were learning 2 new languages)
Add Comment