I don’t understand how this comment relates to my tweet. I agree with you that nobody knows how to do anything and won’t until they start. That’s why you really

I don’t understand how this comment relates to my tweet. I agree with you that nobody knows how to do anything and won’t until they start. That’s why you really want to spend some time working with highly experienced people, in whatever career you choose. I’m not talking about some vague concept of “leadership”. Most of the experienced engineers I worked with on Chrome weren’t even officially “leads”. They were individual contributors just like me. I’m talking about the nitty gritty day to day details of writing robust reliable software. Class or function here? How should I test this? How should we detangle this spaghetti code? What order should we conquer this bug list in? If you want to make a good software product it’s best to have people on your team who have made many software products before successfully.