This is, IMO, a bit mislabeled: this is not a complete CS study plan to become a SW engineer, but a collection of information about basic algorithms. Probably u

This is, IMO, a bit mislabeled: this is not a complete CS study plan to become a SW engineer, but a collection of information about basic algorithms. Probably useful as one of a number such lists, but almost orthogonal to the stated goal. I think the article's stated goal is background for getting hired as SW engineer at a large company. If this is your goal, I would spend half of allocated time on getting the basics (and you do need to be able to understand algorithms quickly) and the other half on networking -- going to a few meetups or an open conference will likely generate as much value for getting hired as learning yet another method of balancing a particular tree. Once hired, though, it is critical to expand beyond just writing code. Dropping by sales / user groups / wherever and using end-to-end system, just as one of the end users, is likely to yield larger benefits, career-wise, than writing an extra few functions. Learning a few basics about company's financials and how your product fits can be an eye-opener and help you steer once you are inside. Just my 2c.