5 ms·

Hell, I stopped carrying about new web frameworks when I was 25.

by pitaj 3y ago

zabzonk 3y ago
i have never cared about them
- sambapa 3y ago
  And I always despised them!
- spacecadet 3y ago
  same, complexity for complexity's sake.
  - vsareto 3y ago
    To be fair, some of those frameworks were compensating for JavaScript which had real issues as a quickly-becoming-popular language. SPAs were an answer to cross platform and device issues, given the web browser was the best cross platform piece of software used by the largest population. It made sense to try that vs making native apps on all the different platforms. The fundamental problem in the web space spawning all of these tools has always been JavaScript’s weaknesses though.
    - spacecadet 3y ago
      I was there friend. I didnt agree, but hey, I left and we to "apps" for 10 years...
  - onetokeoverthe 3y ago
    [dead]
lawkwok 3y ago
Genuine question, as someone who got exhausted and is out of the industry for the foreseeable future. How do you stay competitive or job hop when every post is looking for the latest web framework?
- googlryas 3y ago
  Stop looking for work in tech places. It may require you to take a pay cut and work in a place viewed as a cost center though.
  - danielvaughn 3y ago
    I'm honestly thinking about just picking up c++ or something and turning my attention to embedded systems. I'm sure there's a wealth of old tech sitting around that needs to be maintained.
    - Shikadi 3y ago
      I'm in embedded, there's also cutting edge stuff to work on. The nice thing is you can be mostly detached from annoying web apis and frameworks and databases. The not so nice stuff is dealing with crappy vendors, using crappy tool chains, and spending a ton of time setting up automated builds. Sometimes I think about switching to true embedded (I do embedded Linux) but that tends to pay less
- vijucat 3y ago
  Don't choose hamster-wheel career tracks in the first place. Try to find Lindy paths [1], [2]. For example, SQL experts and DBAs. The rise and (mostly) demise of NoSQL actually cemented SQL's reputation as an irreplaceable technology. The latest Web framework is by definition non-Lindy: it's the new kid in town who think they know it all. grep is lindy, Unix is lindy, the qwerty keyboard is lindy, C++ is lindy, Computer Science is lindy, algorithms and data structures are lindy. Knowledge of the real world, whether it be finance or shipping, is lindy. Sorry, verbose reply, but I hope it helps. 1. https://luca-dellanna.com/lindy/ https://luca-dellanna.com/lindy/ 2. https://en.wikipedia.org/wiki/Lindy_effect https://en.wikipedia.org/wiki/Lindy_effect
  - sph 3y ago
    Interestingly, I've been thinking it would be a good idea to brush up on my C skills, because while there are serious contestants to its throne, a gig based on Rust today often means being at the cutting edge of tech, and will probably come with a lot of buzzwords like GraphQL, React, Typescript, monorepo, AWS Lambda, daily standups — things giving me symptoms of burnout just writing down. Whereas a C gig today probably means embedded, or subsystem far away from the frontend churn. If I'm lucky they have unit tests. The Lindy path you were talking about.

Hell, I stopped carrying about new web frameworks when I was 25.

by pitaj 3y ago

Hell, I stopped carrying about new web frameworks when I was 25.

zabzonk 3y ago

i have never cared about them

sambapa 3y ago
And I always despised them!
spacecadet 3y ago
same, complexity for complexity's sake.
- vsareto 3y ago
  To be fair, some of those frameworks were compensating for JavaScript which had real issues as a quickly-becoming-popular language. SPAs were an answer to cross platform and device issues, given the web browser was the best cross platform piece of software used by the largest population. It made sense to try that vs making native apps on all the different platforms. The fundamental problem in the web space spawning all of these tools has always been JavaScript’s weaknesses though.
  - spacecadet 3y ago
    I was there friend. I didnt agree, but hey, I left and we to "apps" for 10 years...
- onetokeoverthe 3y ago
  [dead]

lawkwok 3y ago

Genuine question, as someone who got exhausted and is out of the industry for the foreseeable future. How do you stay competitive or job hop when every post is looking for the latest web framework?

googlryas 3y ago
Stop looking for work in tech places. It may require you to take a pay cut and work in a place viewed as a cost center though.
- danielvaughn 3y ago
  I'm honestly thinking about just picking up c++ or something and turning my attention to embedded systems. I'm sure there's a wealth of old tech sitting around that needs to be maintained.
  - Shikadi 3y ago
    I'm in embedded, there's also cutting edge stuff to work on. The nice thing is you can be mostly detached from annoying web apis and frameworks and databases. The not so nice stuff is dealing with crappy vendors, using crappy tool chains, and spending a ton of time setting up automated builds. Sometimes I think about switching to true embedded (I do embedded Linux) but that tends to pay less
vijucat 3y ago
Don't choose hamster-wheel career tracks in the first place. Try to find Lindy paths [1], [2]. For example, SQL experts and DBAs. The rise and (mostly) demise of NoSQL actually cemented SQL's reputation as an irreplaceable technology. The latest Web framework is by definition non-Lindy: it's the new kid in town who think they know it all. grep is lindy, Unix is lindy, the qwerty keyboard is lindy, C++ is lindy, Computer Science is lindy, algorithms and data structures are lindy. Knowledge of the real world, whether it be finance or shipping, is lindy. Sorry, verbose reply, but I hope it helps. 1. https://luca-dellanna.com/lindy/ https://luca-dellanna.com/lindy/ 2. https://en.wikipedia.org/wiki/Lindy_effect https://en.wikipedia.org/wiki/Lindy_effect
- sph 3y ago
  Interestingly, I've been thinking it would be a good idea to brush up on my C skills, because while there are serious contestants to its throne, a gig based on Rust today often means being at the cutting edge of tech, and will probably come with a lot of buzzwords like GraphQL, React, Typescript, monorepo, AWS Lambda, daily standups — things giving me symptoms of burnout just writing down. Whereas a C gig today probably means embedded, or subsystem far away from the frontend churn. If I'm lucky they have unit tests. The Lindy path you were talking about.