This matrix is an interesting way to show many of the area's that are important to becoming a well balanced software developer. That said I don't agree with ma

This matrix is an interesting way to show many of the area's that are important to becoming a well balanced software developer. That said I don't agree with many of the criteria for the levels. And in general its a bit too theoretical rather then practical. The next thing that is important is how do these criteria map to your organizations needs? I do notice as someone who has built tools for just about everything imaginable I lack of awareness of UX and its subtleties. Also optimization, GPU, graphics in general. He has obviously never worked as a game developer. The "systems programming" section should be a section in and of itself. Having "code organization" a sibling of system programming is a joke. But its a start.