3 ms·
Could be worse. I am regularly up at night in a cold sweat worrying about how if I suddenly find a technically fulfilling job, realizing I forgot everything ab
by pjerem 4y ago
Could be worse.
I am regularly up at night in a cold sweat worrying about how if I suddenly find a technically fulfilling job, realizing I forgot everything about computers after a decade on working on meaningless front end JavaScript framework.
- Existenceblinks 4y agoEven worse when backend is javascript framework too. Welcome to isomorphic thingy (don't even know what that really means). SSR today only means nodejs server. No, not ruby, go, rust, python, php, elixir, it's javascript. Island architecture, partial hydration, and the latest backend js framework is "Zero JavaScript Runtime" wow. One language to rule them all pipe dream is not dead yet.
- Aeolun 4y agoYeah, that’s a thing. When you’ve been fighting React for some years your mental pathways for anything else are completely eroded.
- quickthrower2 4y agoWhere is the job where you get to work on compilers. If it is not React it is probably the glorious back end, making some graphql endpoints talk to mongodb or suchlike. Or devops, fight k8s!
- bluGill 4y agoThere are a few thousand compiler jobs in the world. Maybe in the tens of thousands, i'm not sure. For everyone of them there are thousands (again I don't know how to measure, could be in the ten thousands) of programmers using the compiler.
- golergka 4y agoFeels pretty lined up to the amount of programmers who are skilled in writing compilers.
- bluGill 4y agoIf I got a job in writing compilers I could becomes skilled at it. However I have a job in a different area. I doubt few as as skilled at writing the type of code I write as me, but the world only needs a few handfuls of people who write the type in the niche I'm writing code in. The world needs lots of websites, and so the world needs lots of people skilled in writing them.
- quickthrower2 4y agoThis is what I call the graduate job paradox. What you do as your first job massively influences you career. I did .NET for years by the fluke that is what my first job did. If they did Java, I would be an expert in Java. If I worked somewhere they needed a compiler written in C++ I would have done it and may have a compiler career. The paradox is as a graduate you generally, unless very exceptional or well connected, or live in the (not "a") tech city, just need to get that first job. It is hard to get that breaking opportunity, and so that thing that will have echoes throughout your career, you don't have much control over! The reason it is hard to get the first job is because it needs interview experience, and you have very little proof yet. You are asking a company to take that leap of faith. Later side stepping is possible but very hard as you are competing with people who can be paid the same as a web dev with deep experience. Also as a young person back then, I had approximately zero confidence, both in myself and even that programming is a good thing to do. Getting into it was very weird, I was probably the only person at my high school of hundreds who geeked out on electronics and programming, for example. Nowadays with HN and other sites, there is an online community such that even in a country town you can get a sense of community and what is possible. With that any graduate now could hatch a decent plan for their career. They might take any job to pay the bills, but aim to get into a FAANG for example, knowing what it pays and how to go about it. 2020's are amazing.