I’m interested in the same question. There isn’t a definitive text because the problem is infinitely broad. My approach is to build crud apps around the tech stack I’m interested in, currently Python with fastapi, arangodb, with some next and typescript for the front end. But you could swap out Python for Go and swagger. For security there is Keycloak. For scalability you could look at building your system as pods in open shift but that adds cost. Personally, I think unless you’re Netflix kubernetes is probably overkill. But the biggest problem is that today’s tech stack is replaced tomorrow by the next new shiny, and all of them are complex and will be entirely different for every team and every problem. A book for dev ops is almost impossible.

deleted by creator

Lapce is an interesting alternative to vs code too: https://lapce.dev/

For me, vim is nice to use because it’s ubiquitous across any system I log into. Any server will have vi at the least. It’s also light and can load a file instantly on any hardware, reducing dependency to zero. Once you have a comfortable config, you’re done for the rest of your life. Although, in reality vim config is a lifestyle and not a choice ;)

To flip this around, think of some projects you want to do. The languages are just tools and will be determined by what you want to do, and then each type of project has it’s best tool chain. Think of the problem(s) you want to solve first and the rest will follow.