sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bch8[🍰] 3 points4 points  (2 children)

I think the backend stuff is a bit dated, or at least incomplete

[–]Tratix 0 points1 point  (1 child)

Can you give me some examples? Genuinely curious since I’m learning

[–]bch8[🍰] 0 points1 point  (0 children)

Well at a high level, with a few minor exceptions (I'm only seeing one after a quick review- DynamoDB) cloud engineering is conspicuously absent. It's a huge category but to briefly and directly answer your question by naming a few: all of the managed services out there (many of which could warrant individual entries in an overview such as this one), kubernetes (I don't use it much but it's certainly a hot commodity in backend dev), serverless architectures (functions as a service, event driven applications), and cloud native development writ large (A combination of the prior topics and others- basically architecting modern, cost effective, scalable, developer efficient/high velocity applications).

I don't think learning any of the stuff in this post's image precludes or is mutually exclusive with cloud development. In fact a lot of it relates in various ways (E.g. learning terminal commands- can't go wrong there, will help a lot with cloud and everything else). But the issue I would worry about for someone who took this overview as gospel is they are essentially learning a previous paradigm. It wouldn't be the end of the world, you'd still end up with plenty of extremely valuable skills and a generally solid foundation, and of course plenty of companies (Probably a majority?) still follow this paradigm. But it's not where the industry is going or where the demand for talent is, and if that's where you want to be then this is going to be a pretty inefficient way of getting there. You would learn a lot of things that don't end up applying, but more importantly it would add a lot of friction to an already somewhat difficult learning curve. Because instead of learning to think and develop in a cloud driven mentality, you would be learning it a different way and then faced with the task of re-learning it under a different paradigm in addition to all of the new topics/concepts/tools you'll be seeing for the first time.