My posting declined a bit around the start of the new year, but that has been because I have been pretty busy doing some things.. Those things are ...
For further actions, you may consider blocking this person and/or reporting abuse
Cool! I think this is a reasonably safe bet and a good time to get in.
JAMstack is not going to replace everything, but it is clearly a trend.
Thanks! I totally agree! : )
Signed up on jamestack.courses :)
Looking forward to it~
Awesome! Hopefully I’ll have some stuff in the coming weeks.
Bet your software engineering career on practices & principles instead of specific tech :)
I would argue that JAMstack is a practice and not a specific tech. This isn't "Betting my career on Gatsby"
Sorry, it's just a bundle of tech that will eventually get partially replaced (even though there will be legacy apps to stay).
I'm talking about:
Phone me when they replace JavaScript friendo.
Not sure what you’re getting at. Betting career on a single language or framework seems weird to me, even if it’s not going to go away.
I do JS/TS on the front-end side of my day-to-day work, and I also do Go/Ruby/Python for CLIs, Kotlin/Ruby/Go/Python for back-ends, and I do Kotlin/Swift for mobile apps. And I did in the past things like Clojure, Scala, and Haskell on production applications (both backend and frontend).
Also, within bounds of each language, I’m proficient at using at least 2-3 frameworks and a considerable amount of libraries.
What’s the point of betting a career on a single stack or language? I mean, what does it even mean?
Let’s tackle the meaning of the concept of
betting:Betting is very similar to gambling and in general any risk-taking.
That means that if JAMStack is no more, or not HOT, your career would be over, or would sustain serious damage that’ll take years to recover.
Is this true for what you’ve meant by “betting on JAMStack?”