a great article, we software engineers are impatient and we tend to job hop often. Being an effective engineer is about more than knowing how to build systems and code, it also requires deep domain knowledge into your company's business and existing systems and this knowledge takes years to cultivate at the same company. All the superstars at my current company have been here for a while.
We job hop for a number of reasons. The primary one being compensation when their current job isn’t keeping up with inflation. Another is lack of promotion when you went above and beyond (as you were coached to by your manager, for that promotion). Another reason (which is why I do) is that life for some of us isn’t as stable. I move. I’m forced to sometimes because of rent. Sometimes that means having to find a new,…
Senior engineers are living in the future
61–70 of 241 posts
Re: Senior engineers are living in the future
#62One of my classmates in college couldn't handle this. I'd glance at some awful Visual Studio compiler error and then point out a missing semicolon. He ended up feeling stupid, but I was trying to be encouraging because his code was pretty good aside from some missing punctuation, which will come with practice. He ended up switching majors.
If it were easy, everyone would do it and it wouldn't pay as much. It's supposed to be uncomfortable in the same way that exercising at the gym feels uncomfortable. Thinking is effort.
Re: Senior engineers are living in the future
#63Earlier quoted context omitted.
A 10 years Java/PHP developer doesn't know how to use Golang on the job in 3 days.
I'd give them 1 week. And measure again at starting of week 3, if they are still struggle, that's very likely they suck at learning.
- Y-yes...
- You are fire!
Note: Sorry for the cheap joke, I also make frequent grammatical errors in English.
Re: Senior engineers are living in the future
#64Senior means two things: - Have experience - Self learning though above experience. I met many experienced developers, but most of them failed at step 2. To me, they're still junior.
Re: Senior engineers are living in the future
#65a great article, we software engineers are impatient and we tend to job hop often. Being an effective engineer is about more than knowing how to build systems and code, it also requires deep domain knowledge into your company's business and existing systems and this knowledge takes years to cultivate at the same company. All the superstars at my current company have been here for a while.
We job hop for a number of reasons. The primary one being compensation when their current job isn’t keeping up with inflation. Another is lack of promotion when you went above and beyond (as you were coached to by your manager, for that promotion). Another reason (which is why I do) is that life for some of us isn’t as stable. I move. I’m forced to sometimes because of rent. Sometimes that means having to find a new,…
Often the superstars are just normal people who really knows the business well and therefore what makes sense to implement and what should be skipped.
When you earn enough money for a decent lifestyle, then I think this becomes the major reason for a lot of people to jump ship: you join a company but leave a manager. https://getlighthouse.com/blog/people-leave-managers-not-com...
Re: Senior engineers are living in the future
#66Earlier quoted context omitted.
Well, golang is a tough language. I am stuggling with helm/kubernetes and the new company's ecosystem where everybody is new in the team. We are expected to deliver according to a plan while we keep hunting for relevant info. I would say the second point is a lot more nuanced than stated.
> Well, golang is a tough language. This _could_ be true for some, but it directly conflicts with the stated goals of the language. Most people (that I've spoken to) would consider Go to be a simpler language, with fewer features, than other comparable languages.
Re: Senior engineers are living in the future
#67Earlier quoted context omitted.
A 10 years Java/PHP developer doesn't know how to use Golang on the job in 3 days.
Why is 3 days, likely with competing priorities, a reasonable timeframe to learn a new language well enough to contribute production code in your estimation?
Are you going to write elegant, idiomatic code in the first week? Of course not. But give the task "make the system do X", 90% of coding is knowing how computers work, and the other 10% is knowing how to search on stack overflow to be able to translate what you want to do into the desired syntax.
Re: Senior engineers are living in the future
#68Re: Senior engineers are living in the future
#69Earlier quoted context omitted.
Except that's not at all what the article is suggesting. Quite the opposite.
> it is literally effortless to accidentally cultivate the impression of being some kind of wizard