Notice the problem with that little text. There are no fully developed individuals. There are always unfamiliar problems. Finding ways to solve these unfamiliar problems is something a developer has to do all through his career. It is only by getting new unfamiliar problems to solve that he can grow and add to a possibly already magnificent experience. As long as we don't get hit by dementia, we have the ability to learn new things until the day we die. In the real world, everyone is a student now and then. Hopefully also a teacher now and then. In a team where A knows how to solve a problem, an information transfer from A to B means the team suddenly have two skilled developers who knows how to solve the problem.

Haven't it hit you, that someone out there and just out of school could actually ask you why you want to use a 64kB part, when there is an alternative solution that would fit in just 32kB? Life isn't just about finding the coolest way to blink a LED. The customer wants feature X, but feature X can normally be realised in more than one way. Right now, feature X, Y, Z, ... are always implemented your way, because you are using a one-way approach. Trying "what do you think about implementing this like ..." can lead to a response "Yes, that would work. But what if we insted did it like this...". A project manager has to make the decisions, but the quality of the project can be greatly improved if the experienced developers - the "hired hands" - are allowed to make suggestions too, before the manager takes the decision.