3 ms·
Personally I think this is great but I would spend less time on certain things and more time on others. I think what people who are trying to train themselves
by ilaksh 7y ago
Personally I think this is great but I would spend less time on certain things and more time on others.
I think what people who are trying to train themselves for programming jobs need most is topics in software engineering. And in particular I have my own view of the most important parts of software engineering.
So I would put more emphasis on modern tooling, practical requirements analysis, hammer home the importance of iteration and closed feedback loops such as end-to-end testing and observing/interacting with users. Emphasize iterative requirements analysis and verification -- it's very easy to get on to the wrong path early on in a project and waste a lot of time. And for most projects the programmer is the person who is best equipped to really understand and steer requirements and this means they need to be assertive which is quite a challenging aspect that requires practice.
Also modules and components can be critical so they need to get beyond objects or functions to that level. And also they need to understand and have experience with package managers and registries. These are examples where things have changed over the years. In the past it might have been more important to, for example, have experience with assembly language, or something. But these days, for building new software or integrating existing, selecting and combining components is critical to leverage the massive amount of available code and systems and avoid reinventing the wheel. People disparage that as "glue" or "plumbing" etc. but it is a high-level skill that needs to be developed and I think in most cases a much more advanced approach than building everything from scratch. Also it takes practice to know which parts should be components and which parts should be custom.