You miss the whole point of the list. The idea is that experience of working on variety of projects makes you better developer in whatever field you are in. Th

You miss the whole point of the list. The idea is that experience of working on variety of projects makes you better developer in whatever field you are in. This assumes you will understand where to use and when not to use those techniques. The list gives examples of projects each with unique requirements. Each requiring you to think about the problem in a different way. I just gave two more examples that I personally found very illuminating, that also have unique requirements, different from other projects on the list. I may be working on some more mundane software atm but, for example, I know how specifying size of every buffer or any data structure is important for reliability of the service I am working on. In fact, the service had bad track record of reliability which was quickly fixed by specifying what it means to do stream processing (no unbound data structures in memory, etc.) and quickly verifying each component against this spec. I learned this and many others from MISRA which is standard to help write reliable software for automotive industry. I adopted it for my embedded app to help me work on complex app that had to be very reliable.