3 ms·
well, if it's a short term use and throw kind of project/tool then sure I can go with 1 "10X programmer", but if I were a stakeholder in a long term project I w
by robofanatic 4y ago
well, if it's a short term use and throw kind of project/tool then sure I can go with 1 "10X programmer", but if I were a stakeholder in a long term project I wouldn't put all my eggs in a one person team.
- MrOwnPut 4y agothe 10x designs the entire system. the 1x teams work in it after, in a controlled way. eventually the 1x teams understand the system and mimic the patterns. enough patterns created by the 10x it's hard for the 1x to fuck things up. yes you eventually won't have the 10x one day, but if you utilized them right, they made you a nice temple. 10x or not, if you have a team design a system you're doing it wrong. teams can work in it later, one person should design it.
- robofanatic 4y agofair enough. would love to see your work to really believe what you are saying.
- MrOwnPut 4y agounfortunately that would dox me and i love being a contrarian here apparently. feel free to shoot me a way to contact you if you want. but it's not really worthwhile for me to basically gather up a resume unless you have connections.
- robofanatic 4y agowait, you are a 10x programmer and don't have a public github profile?
- MrOwnPut 4y agoi have many profiles, including github, that would be part of the resume. a lot of the cool stuff in my later years is commercial. you could have just replied with your contact info if you were really interested in me. the only reason for me to try to prove anything to you would be if you were actually someone.
- deleted 4y ago[deleted]
- turtleyacht 4y agoReminds me of a software team having one surgeon and the others are support staff--in no way denigrating, but equally essential with their skillsets, to execute on the (skunkworks?) project. This idea of a surgeon team is also from Brooks.