4 ms·
> I think 10x developers, like world-class athletes, musicians, and authors, absolutely do exist. You’re just not going to find them with a coding test. I can
by ChrisMarshallNY 4y ago
> I think 10x developers, like world-class athletes, musicians, and authors, absolutely do exist. You’re just not going to find them with a coding test.
I can confirm.
I have no idea, whether or not I'm a "10X" programmer, but I do tend to work quickly. So quickly, in fact, that I often piss off the people I'm working with, because the job is done, before they have had a chance to interfere with^h^h^h^h^h^h^h^h^h^h^h^h^h^h^h contribute to the project.
- Consultant32452 4y agoI consciously reduce my output to be at about the 70th percentile of whatever team I'm on, with short bursts of max productivity when I subjectively feel like it will help the team get out of a pinch. People like me a lot more this way.
- shapefrog 4y agoBeing seen to be labouring away also becomes important. Punching out 3x others, while working regular hours against visibly "harder working" people - leads to a reputation of being lazy.
- Consultant32452 4y agoOnly accepting remote work positions has fixed this problem for me.
- TheRealDunkirk 4y agoI concur. I've demonstrated that I'm a 10x+ full-stack programmer several times in my career, but I've met at least a few people who could bang out code better than me. I can design complicated systems with many moving parts to solve difficult business problems, and hand them off to someone else to manage with minimal maintenance. I've done it many times. However, I worked with one young guy who understood Ruby better at age 25 than I ever will. But then it came time to log into the server and do something, and he didn't even know how to open a terminal and SSH into the box! So, no, I don't believe a simple coding test will find people who are "10x" in software development. There's a lot more to it than just writing lines of code.
- jason-phillips 4y ago> he didn't even know how to open a terminal and SSH into the box! You just described something which is trivial to learn in less than one minute. This lack of experience does not directly speak to their skills or abilities. Extending your example to illustrate its irrelevance, were I to have spent 60 seconds with this engineer alone just before your little ssh test, he would still appear to be a 10x engineer to you. Focus more on ability and less on what one has or hasn't seen just yet in their careers. I could easily find the limits to your knowledge in seconds and I'm quite sure you could return the favor. I'd gladly hire someone who demonstrates the ability to become a wizard in X and not care in the slightest if they've seen Y and Z yet. I can teach Y and Z to someone like that very easily.
- hcayless 4y agoYes, but: a programmer who has made it to age 25 without learning how to ssh into a server where their code will end up running is to me demonstrating that they are remarkably incurious about the larger ecosystem within which they’re working. One sign of a better developer is that their horizons are broader.
- scarface74 4y agoSeeing that I write code everyday now that will end up running on Linux Firecracker MicroVMs that I will never have SSH access to… The “ecosystem” of development is very large. I’m sure there are parts of the ecosystem that others would know that you wouldn’t.
- geraldwhen 4y agoOr they’ve only worked at BigCo with defined production pipelines and connecting to individual EC2 instances isn’t possible without jumping through incredible month-long hoops, and not available for production at all. I am not able to ssh into any production instance I’ve deployed. I know how I would but it’s just not organizationally allowed.
- TheRealDunkirk 4y ago
- snozolli 4y agobecause the job is done, before they have had a chance to interfere I would say I've been a .1x (uninteresting drudgery, poorly defined goals, toxic workplace) to 5x developer. The single biggest factor in the 5x instances was a lack of interference. In one particular case, I completely ignored my manager, much to his dismay, and built the system I wanted to. He stopped complaining when integration of new hardware went from weeks to less than an hour. I don't understand why people demand experience and skills during interviews and then seem to do everything they can to ignore said experience and undermine their workers.
- distortionfield 4y agoGod damn dude. Maybe you piss them off because you call their contributions “interference”. Honestly this is one of the most dickish things I could imagine saying about a colleague’s work.
- ChrisMarshallNY 4y agoWow. That was pretty nasty. I thought we didn't make comments like that, here. I can see that we probably won't be working together, so I don't see why you felt the need to make that comment. In fact, I'm a pretty easy person to get along with, but you'll never know, now, will you? You've already decided how our relationship will go. I didn't call you any names. I've also worked in high-functioning teams since before a lot of folks on this site were born. In most cases, I was not the top dog, and there's a good chance that someone else was annoyed by my "contributions." There's also a tiny, tiny chance that I may have had some positive experiences, along the way. And isn't there a saying, somewhere, about "walking a mile in someone's shoes," or something?
- distortionfield 4y agoSo you can't handle someone suggesting that what you said is (honestly and objectively) dickish and maybe the real source of your problem, but you can outright call others' hard work "interference" and it's all gravy and not at all unprofessional or rude? You've got a skewed idea of "nasty". Have a good rest of your day.
- ChrisMarshallNY 4y agoBut I didn't call someone else's "hard work" "interference." That was your interpretation. I have just had the very common experience of having my work destroyed by people that really had no qualifications, but did have the right, to mess it up. I have been working on a project with a bunch of folks, for the last couple of years, that has had its ups and downs, but hasn't had any of that nastiness that was so depressing, in my work life. I now know that it can be better. It's no longer just "wishful thinking." I now have proof. I had to go through a pretty rough patch, to get here, and I don't recommend the process to anyone. I was sharing that. For me, it's a good thing. And your post definitely was "nasty," and I was supposed to understand it as a personal attack. It was delivered as such, and was received as such. Have a great day.