Exactly. That's the problem I've noticed: Do you really want to hire someone who takes 80 hours to accomplish something that takes 8 hours for someone else? I think we've all seen this happening. I was brought in to a parallel team one day because they were about to miss a deadline. Turns out 25 year old guy was trying to build a graph database from scratch. He didn't know that he was building a graph database, and wasn't really aware they existed. He just knew what he needed, and went about building it. He spent a huge amount of time building his own awful, non-performant implementation. I told the team lead to get Bob to help. Bob has kids who are in their mid 30's. Bob sat down, logged into the VM, and a few hours later had an instance of Neo4J running and hooked into the app.

But hey, he thinks foosball tables don't belong in offices, so why hire him at a startup?