Re:Things I have learnt as the software engineering lead of ...
by Spooky23 on Friday December 29, 2017 @08:00PM
(#16033128)
There is no dishonor in that grunt work. It’s just that your work product will have limited impact.
I have a friend who has been a mainframe systems programmer for 30 years. He’s a master of his craft, and has a tool in his bag of tricks for every problem that happens. Most of his work helping people integrate with his mainframe to eventually replace it.
He’s a great guy and loves the life he wants to live. The problem is, few things in tech will live that long, and guru knowledge of some forgotten mainframe makes your options limited.
Re:Things I have learnt as the software engineering lead of ...
by twblalock on Friday December 29, 2017 @10:08PM
(#16033622)
The downside to doing it, for the people who do it, is that they will have a hard time finding another job if they get laid off. Their skills are likely outdated if they have been doing unchallenging grunt work for years.
Now I'm going to play devils advocate. What's wrong with doing grunt work and not being challenged? I know people who have been at the same job for 20 years maintaining the same system and not being challenged. They work their 40 hours a week, love the familiarity and stability, and go home.
I would die a thousand deaths doing that but sometimes I wish I had the type of personality that could deal with that lifestyle.
Realistically though, couldn't people say the same about me? I'm about 10% below the top salary I can get without going into management in my market. I should hit my top salary in about two years, except for cost of living raises. I'm okay with vertical moves being a "Senior Developer", "Architect", "Team Lead", "Consultant", etc. Some people would say why don't I want to be a manager or start my own company.