Programming career
The Fate of Engineers Who Gain Years Without Increasing Their Skills
I was shaking as I was writing this.
I’m currently working on a team with an engineer who is almost 60 years old. I’m now in the design phase, so I don’t have to write any particular code, but this old man has very little ability. He’s been away from implementation for a while, so I can understand why she’s having trouble programming. However, proper documentation was not created during the design and testing phases.
My own lack of ability does not defeat me, so I think I can say that this old engineer is very good. In other words, it’s almost equivalent to a 1st or 2nd year engineer. Have you never written a design document or test case? The quality is so low that I thought.
I will call this old man Mr. Y, but Mr. Y has been an engineer for a long time until this year, so I think he has no engineering aptitude. I can’t imagine if I’m like this now or if I could do more work when I was younger.
I think programming is something that people who haven’t done it for a while will forget unless they’ve gotten used to it, but I don’t think people forget things like design documents and test cases all that often…
- What does this design document describe?
- What perspective is this test case made from and what should it check?
It seems like you don’t understand the basics of this. In Mr. Y’s words, “I’m not good with details and don’t understand them, lol’’, but I think the above two points aren’t exceptionally detailed and are rather very general.
I have said this in no way to undermine Mr. Y (although I am writing this far). Mr. Y, who is very personable and has good attendance, is a very serious working person (engineer). Instead, isn’t this Mr. Y your future self? And he feels scared.
I didn’t have a chance to program this time, so I haven’t brought out my worst point (poor coding skills), but when it comes to programming, my words boomerang back to me and sting me. My coding skills are inferior to even first- or second-year engineers.
It’s not just about programming. I’ve entirely forgotten about SQL , and I’ve also forgotten about Linux commands. Even if you try to retrieve the DB from SQL Server Management Studio, you probably have completely forgotten how to do it. They can’t manage tasks like a PM, and they can’t manage schedules as a PMO. I can’t even use simple Excel functions.
This time, I was able to do a little bit of work during the design and testing phase. It’s a coincidence that I have enough time, my work pace is gentle, and I can go home without staying up all night. If you get used to the current situation, which is exceptionally dull, there is no doubt that you will become Mr. Y next time.
The title of this article is not a word referring to Mr. Y but a word directed at myself. I am still determining what kind of shape the IT industry will take in the future, but there is no doubt that it will become even more technical than it is now.
It is not enough to design a program, and in some cases, if you are not familiar with infrastructure and architecture, you may not be able to participate in the project due to your age. I was shaking as I was writing this.
Stackademic
Thank you for reading until the end. Before you go:
