4 ms·

What he says here is so true, and something I see many engineers get wrong. Don't glorify and build your career around a single language or methodology. I beli

by nvarsj 4y ago

What he says here is so true, and something I see many engineers get wrong. Don't glorify and build your career around a single language or methodology. I believe an engineer should learn to build things in the most pragmatic way possible using the best tool for the job. This requires breadth of experience across many areas, and a focus on delivery. The idea of "Java engineer", "Scala engineer", "Golang engineer", etc. is so absurd to me. If you want to build a long lived career that will outlast tech fashion, learn many different tools and how to build software in different ways. Be known as someone who delivers, not an expert in language x or tool y.

_-____-_ 4y ago
I agree with this. When I see ChatGPT output a perfect React program, I don't think "oh shit, it's going to replace me writing React programs." I think "thank goodness I'm not going to need to write that shit anymore." Instead of writing 40 lines of React, I can write two sentences to ChatGPT. It's the same two sentences I would "write" to myself (in my head) before writing the 40 lines of React, but now I save all the hassle of looking up the details or typing out the same drudgery over and over again.
sibit 4y ago
> The idea of "Java engineer", "Scala engineer", "Golang engineer", etc. is so absurd to me. I find the idea of being an expert in a language acceptable if it's been used for long enough. Almost all of my coworkers only know .NET and there are enough jobs needing people for new projects and legacy projects that they most likely won't have to learn anything else. > or tool y This is where the absurdity begins for me. I have a coworker who is 5 years into his career with the title of "senior react engineer". He started as a "junior react engineer" and at this point only knows how to solve problems with React. He has limited knowledge of the underlying language or general CS concepts. Every problem he encounters can and will be solved by installing NPM packages.

by nvarsj 4y ago

_-____-_ 4y ago

I agree with this. When I see ChatGPT output a perfect React program, I don't think "oh shit, it's going to replace me writing React programs." I think "thank goodness I'm not going to need to write that shit anymore." Instead of writing 40 lines of React, I can write two sentences to ChatGPT. It's the same two sentences I would "write" to myself (in my head) before writing the 40 lines of React, but now I save all the hassle of looking up the details or typing out the same drudgery over and over again.

sibit 4y ago

> The idea of "Java engineer", "Scala engineer", "Golang engineer", etc. is so absurd to me. I find the idea of being an expert in a language acceptable if it's been used for long enough. Almost all of my coworkers only know .NET and there are enough jobs needing people for new projects and legacy projects that they most likely won't have to learn anything else. > or tool y This is where the absurdity begins for me. I have a coworker who is 5 years into his career with the title of "senior react engineer". He started as a "junior react engineer" and at this point only knows how to solve problems with React. He has limited knowledge of the underlying language or general CS concepts. Every problem he encounters can and will be solved by installing NPM packages.