3 ms·

I had 15 years experience writing JS in the corporate world when I was laid off last year. Reflecting upon that here is what you need to have a stellar JS caree

I had 15 years experience writing JS in the corporate world when I was laid off last year. Reflecting upon that here is what you need to have a stellar JS career. * Be 10x at administration. Learn to communicate with precision and get your work done on time. This is what will get you promoted in comparison with your peers. * Be average at writing software. Be as average as possible. If you are interested in solving real problems, innovating, or any kind of engineering you are in the wrong line of work and should immediately look for something unrelated. Your peers are only interested in the framework of the moment and the vanity of code style. If you over achieve beyond that you only lower your career mobility and desirability in the marketplace. You are hired to jiggle user events and put text on screen, so don’t over think what goes into the actual work with a bunch of delusions. Be average. If you want to continue writing JS/TS for a living those two bullet points will dictate where you need to focus.

thiago_fm 3y ago
That isn't entirely true about the average part. Being average is fine (and great!), but plenty of people aren't real geniuses and work on really complex problems(like search, complex solutions with high-scale), or non-CRUD work. You can specialize in that, being average, given that you are lucky to find a job there. The only downside is that it's highly specialized and has fewer companies willing to hire for it, but as those positions are rarer, there are also rarely people with the correct skillset. Other engineers will look at yourself as being a genius, when in reality you are also average like them that got to specialize in a problem that isn't common. It isn't that good if your intentions are to become a manager and has a more corporate profile. Then the best path is to do whatever else is doing (frameworks/tools/kool-aid)

thiago_fm 3y ago

That isn't entirely true about the average part. Being average is fine (and great!), but plenty of people aren't real geniuses and work on really complex problems(like search, complex solutions with high-scale), or non-CRUD work. You can specialize in that, being average, given that you are lucky to find a job there. The only downside is that it's highly specialized and has fewer companies willing to hire for it, but as those positions are rarer, there are also rarely people with the correct skillset. Other engineers will look at yourself as being a genius, when in reality you are also average like them that got to specialize in a problem that isn't common. It isn't that good if your intentions are to become a manager and has a more corporate profile. Then the best path is to do whatever else is doing (frameworks/tools/kool-aid)