3 ms·

> It's a huge ugly monster with dozens of keywords (buzzwords?). You spend 6 months passing an AWS exam, and all you have learnt is how AWS works. This was act

> It's a huge ugly monster with dozens of keywords (buzzwords?). You spend 6 months passing an AWS exam, and all you have learnt is how AWS works. This was actually the comment that stuck out most to me. Because it's an abstraction of the specialization that's going on in the industry that worries me. Sure, you can learn general computing skills as a side effect of pursuing this efforts, but increasingly, we are learning how to drive tools, rather than solve problems. The effort to grow proficient with increasingly complex tools and frameworks is greater now than the effort to grow proficient in a particular language (even some of the more complex ones).

peisenmann 5y ago
The thing is that AWS is an enormous cross-section of functionality and specializations across the entire software industry. You can make a career out of being good at AWS. As a software engineer with years of experience deploying web applications to AWS for multiple companies, I can't grasp why a programmer would take a 6 month course, take an exam, or go to any huge effort to learn how most of it works. In my opinion, when you're a single-person team, it's much the same as writing a novel in that you have to keep moving. Stagnation is the death of the project. You have to take a single task, learn what you need to get that one thing done, do it, then move on. You don't need to know everything about everything at the start. It's not really a problem unique to game programming. Plenty of software projects never get finished. You can find their corpses all across GitHub.