Not really relevant to OP. But I've seen parents distinction being made in companies more than once. They basically let the 'senior' programmers create new prod

Not really relevant to OP. But I've seen parents distinction being made in companies more than once. They basically let the 'senior' programmers create new products and features (type 1 work). They let the 'junior' programmers do the maintenance on the results (type 2 work). The biggest problem with this organisation is that there is no feedback loop for the 'senior' programmers. They can mass produce garbage code and not worry about the consequences at all. Often the 'senior' programmers even start looking down on the 'junior' programmers for being merely maintenance programmers. Which is obviously messed up. I treat anyone who claims he's a pure type 1 programmer with suspicion. I seriously question anyone can be good at the type 1 work and be bad at the type 2 work. There are a lot of programmers out there who hate doing the type 2 work though. On the other hand there are also a lot of people out there who really shouldn't be doing any programming at all. They usually end up getting stuck in type 2 work and maybe reinforce the idea that a distinction between type 1 and 2 programmers could be made. But the reality is they should probably choose another profession entirely.