News for hackers. Stuff that matters.
Re:Why I Strive to be a 0.1x Engineer by aidanlister on Wednesday January 27, 2016 @05:14AM (#10979264)
One of the first mentions* I saw on HN about the elusive 10xer was an article about the exact types of gains the author of this article is talking about -- a 10xer knows where to apply their effort and as such is an order of magnitude faster in achieving the business outcome, not producing LOC.

I feel like the author has wrapped up some sensible expectations for any senior developer and then soiled the content with a clickbait title.

* something to do with using a sticker printed on a transparency instead of some computer vision project.

Re:Why I Strive to be a 0.1x Engineer by LoSboccacc on Wednesday January 27, 2016 @05:22AM (#10979288)
sadly it's precisely what business are not gonna doing. measuring developers by LOC instead of business outcome allows to detach their worth from their productivity, albeit the metric is flawed in many ways it's better to say 'you produced X LOC, here's a 100$ raise' than 'your solution saved us 100M$, here's a 100$ raise'
Re:Why I Strive to be a 0.1x Engineer by Tiquor on Wednesday January 27, 2016 @06:19AM (#10979468)
I've worked in multiple fortune 500 companies and startups at the entry and now management level and been involved in Web Development for 20 years. I've never seen a LOC report except when we run some games with the other devs to see # of changes in GIT or other source control.
Re:Why I Strive to be a 0.1x Engineer by jameshart on Wednesday January 27, 2016 @11:47AM (#10981064)
Likewise, in my experience across many different sizes of company I've never seen LOC used as a productivity metric.

The one time I've seen LOC taken seriously was when I've been asked to produce a LOC report as part of a due-diligence audit of a codebase prior to acquisition - that's largely because the line of code count of the codebase is indicative of what code IP auditing/security auditing/localization might ultimately wind up costing the acquiring company so they're using it to figure out entries in the liability column, not even valuing the codebase based on LOC count.

Re:Why I Strive to be a 0.1x Engineer by dotnetchris on Wednesday January 27, 2016 @03:32PM (#10983023)
The best line of code i've ever wrote is the three i didn't.
Re:Why I Strive to be a 0.1x Engineer by ones_and_zeros on Wednesday January 27, 2016 @08:43AM (#10979949)
Can you tell me which companies you've worked for that determined developer value by the effect on the bottom line? Because I'd like to send them my resume.
Re:Why I Strive to be a 0.1x Engineer by OpenDrapery on Wednesday January 27, 2016 @11:09AM (#10980784)
Yes. Just because we all recognize that LOC is a shitty metric, doesn't mean that the industry has figured out what a good metric is. Measuring developer productivity and impact remains an unsolved problem. It still amounts to gut feel, and mostly whether or not your manager likes you or not, i.e. how much of a thorn you are to him/her.
Re:Why I Strive to be a 0.1x Engineer by nfc on Wednesday January 27, 2016 @05:59PM (#10984276)
If you agree with not getting paid while you have no effect on the bottom line I'm hiring ;)
Re:Why I Strive to be a 0.1x Engineer by dreamfactory2 on Wednesday January 27, 2016 @08:32AM (#10979908)
Big SI offshore dev operations sometimes use LOC still. (This is a part of why corporate enterprise software is so poor.)
Re:Why I Strive to be a 0.1x Engineer by protomyth on Wednesday January 27, 2016 @11:11AM (#10980792)
Steve Ballmer at the 20:03 mark of https://www.youtube.com/watch?v=GqFYsvxHZOs describes it as an IBM religion which he is pretty critical of.
Re:Why I Strive to be a 0.1x Engineer by icebraining on Wednesday January 27, 2016 @02:33PM (#10982412)
Re:Why I Strive to be a 0.1x Engineer by vonmoltke on Wednesday January 27, 2016 @10:25AM (#10980470)
Come work in government contracting.
Re:Why I Strive to be a 0.1x Engineer by ryandrake on Wednesday January 27, 2016 @10:03AM (#10980303)
I'd be totally OK with a "lines of code" metric. If that was what my raise is going to be based on, let's do it! At least it's a metric and I know about it!

I've worked at my fair share of companies, and not one of them based raises/bonuses (for engineers) on any kind of quantifiable metric or KPI. It basically always comes down to whether your boss likes you, or how much self-promotion you're doing, or what phase the moon is currently in, or some other wizardry. It's never a concrete metric that you can track your progress against throughout the year and know if you're going to succeed or not.

One of the questions I ask in every interview is: Is my compensation entirely dependent on my job performance, and if so, what metrics are used to evaluate my performance. For some reason, nobody seems to have a good answer for that seemingly simple question. Sometimes they'll say "yea it's performance based", but when you press for what they're measuring, you won't get any information. So I'll take the job, and a year later annual review time comes, and lo and behold, it's "Here's your [good|bad|neutral] (it doesn't matter) performance review and your 1.5% cost-of-living increase!" Very demoralizing. Show me a place with clear, transparent, quantifiable performance metrics, and I'll beat a path to your door.

Re:Why I Strive to be a 0.1x Engineer by jdmichal on Wednesday January 27, 2016 @10:48AM (#10980628)
This, to me, is a common fairy tale technical people like to tell themselves to justify not getting involved in the social connections (aka politics) necessary to be fully successful. It doesn't matter what metrics you choose, because they will all be gamed. Just like the politics is gamed. And no matter what game is picked, certain people will just not like playing it, and will bemoan the choice and why couldn't they have picked X, some other random metric that will also be gamed. But at least they like that game so they'll play along and possibly even excel.
Re:Why I Strive to be a 0.1x Engineer by Moru on Wednesday January 27, 2016 @06:29AM (#10979495)
I have seen this in the contract in some industries in Sweden. The people that has an optimization idea that saves the company money gets a percentage of what the company earns on the optimization the first five years or similar. Have also seen a few court cases where the company didn't pay out but was forced to pay :-)
Re:Why I Strive to be a 0.1x Engineer by mstade on Wednesday January 27, 2016 @10:13AM (#10980378)
I wonder how well those bonuses are received when the payee realizes the tax hike on anything about 36k SEK / month, or whatever the limit is these days. Sweden's tax system isn't very bonus friendly, so unless the bonus is so significant that it's worth the tax cost it's just not that great an incentive. For example, a 10k SEK isn't that meaningful a bonus, since anything above the 432k SEK / year is taxed at ~50% – unless you're ok with that you'd probably want to look into other options.
Re:Why I Strive to be a 0.1x Engineer by walshemj on Wednesday January 27, 2016 @10:14AM (#10980382)
Lol I could have retired if I had had that in my contract at BT or Reed Elsevier.
Re:Why I Strive to be a 0.1x Engineer by paulddraper on Wednesday January 27, 2016 @02:34PM (#10982421)
Really, a lawsuit?

If that's not discouragement from listening to employee suggestions, I don't know what is.

Re:Why I Strive to be a 0.1x Engineer by awjr on Wednesday January 27, 2016 @07:52AM (#10979733)
I left a company because the code I'd written generated 600k in extra revenue (it hooked up their sales system to Amazon) and got a 2% pay rise "just like everyone else". When it came to the review, I did ask, what more I could have done to get recognised.
Re:Why I Strive to be a 0.1x Engineer by rebootthesystem on Wednesday January 27, 2016 @08:57AM (#10979997)
Wrong way to look at it. Start a company and gain an understanding of what it will take for you to be in a position to have someone write some code that increases your sales. Infrastructure, capital, product, systems, risk, positioning, reputation, marketing, etc. perhaps then you will understand.

I had a sales guy once tell me, as we got a new hardware product ready for manufacturing, that we'd figure out how to split the profits once we started shipping. He felt entitled, even though he'd only been with us for six months. He conveniently ignored the fact that this product had been in development for nearly ten years during which time I invested millions into R&D, marketing and building an infrastructure to support the product internationally. I let him go a few weeks after that comment. Wrong attitude and a complete lack of context.

I actually prefer to hire people who have had some entrepreneurial experience. They make far better employees. They are independent, hard working, no-bullshit on-mission because they get it. Pay them well and unleash them for great results.

Re:Why I Strive to be a 0.1x Engineer by skolor on Wednesday January 27, 2016 @09:33AM (#10980149)
The important part of the parent comment was "just like everyone else". For people who are employees, not stakeholders, recognition for success is important and the parent clearly felt they were not being recognized relative to their peers for what they were doing.
Re:Why I Strive to be a 0.1x Engineer by lifeisstillgood on Wednesday January 27, 2016 @11:39AM (#10980996)
There are two areas I would look at here

1. How much independence did the OP show creating the Amazon hookup? Was it his/her baby? Did they push forgot to happen? Or were they just rotated onto the project and it came with the next item off the backlog?

2. Was the OP the only one to add value that year? Was the value they added more than others or about the same.

Without these two it's hard to see if they should realise they are just an employee and have no leverage or if they did get shafted.

I think we all need to have more P&L responsibility in our jobs - software is about creative capital and should be highly leveraged.

Maybe we should all go back to the partnership model?

Re:Why I Strive to be a 0.1x Engineer by rebootthesystem on Wednesday January 27, 2016 @02:10PM (#10982259)
Right. Timeline and comtex is missing as well. Also, in general terms, I think it is a bad idea to go to management or a company owner amd battle for a out-of-band raise. This is particularly true if one lacks context or visibility into the other layers that make-up the organization. It can make someone look clueless, selfish and not a team player. Nobody wants needy problem employees.

To me context is very important. Most of the frustrating moments I've had with employees has been with sales people. They come at things from a very different perspective when compared to engimeers. Most business owners I know have the same "chills-down-my-back" reaction when asked about sales staff.

Anyhow, I had a sales guy demand commission for closing sales at the office. The problem is I was spending tens of thousands of dollars per month in marketing and hundreds of thousands per trade show to make that phone ring. The job of a sales person is to go turn over stones and find business. What he was doing was taking orders. You don't pay someone a salary and commission (in a small company) to sit idle while fish jump into the boat. You pay them to fish. Anyhow, that guy was gone too.

The best sales person I had was this 20-something girl who did not know the first thing about selling. I hired her to help at a tradeshow. I noticed she was great with customers and bery comfortable with technical material. I hired her as a sales person and trained her over several weeks. She easily made twice the salary of the best sales person I had up to that point. Changed her life and gained an absolute gem of a team member.

Perhaps the real point here is that that's what you want to become: so good that you cannot be ignored. Business owners or management love to throw money lavishly at things and people who produce results. Not one time "got lucky" results but consistent dedication to the cause.

Re:Why I Strive to be a 0.1x Engineer by rebootthesystem on Wednesday January 27, 2016 @05:22PM (#10984010)
I really truly hate typing on an iPad...the typing errors are a PITA.
Re:Why I Strive to be a 0.1x Engineer by lifeisstillgood on Thursday January 28, 2016 @04:26AM (#10987255)
I feel your pain

"push for it to happen" -> "push forgot to happen". It's like being whipped with a Markov chain.

My personal feeling is that anyone drawn to sales has a belief that they can magically make the world / other people / their mother do what they want simply by using the right words / form of persuasion. Its a belief in magic instead of science and it should not be a valuable skill in the 21C. Calling it a Reality Distortion Field is not improving the situation.

Re:Why I Strive to be a 0.1x Engineer by awjr on Thursday January 28, 2016 @10:56AM (#10988897)
OP here. The Amazon hookup was one of the big projects but was a huge undertaking with high visibility and I was left to deliver it on my own.

It was an intense time with me cutting holidays short and very long days. I wasn't expecting a "cut" of the profits but it was very much about being recognised for the hard work I put in and that it was a good piece of work.

I felt I had gone above and beyond for 3-4months. I wasn't bitter. I just realised that after the derisory pay-rise, that it was time to leave.

I still miss that place. It was full of good people (some are close friends) and I did some really cool stuff that made a massive difference to the operation of the company. Would I go back? Yes as a consultant/contractor but not as a permie. I know my worth.

After that I joined an immensely challenging start-up which unfortunately failed and am now consulting and looking to bootstrap an idea in the summer ;)

Re:Why I Strive to be a 0.1x Engineer by rebootthesystem on Saturday January 30, 2016 @12:29AM (#11000670)
I hope it is obvious that it is impossible for someone to grasp the entire dynamic of your experience based on a few short posts. This requires a long conversation where one would explore and try to understand the entire context. I can't fault your or praise you in any way, not enough data.

In general, though, I'd say business owners (and good managers) are hungry for good employees who "get it". And, if they are smart, they'll recognize these employees.

But you also don't want one-hit-wonders. What you are after are people dedicated to the long term mission. Anyone can bust ass for a few months, get a raise and then proceed to rest on their laurels.

Recognition for good people often comes in the way of raises and promotions over time. You might invest a few years at a company doing good work and contributing value yet not necessarily see much in the way of praise and adoration. And then, one day, you get a promotion. Because people are watching and paying attention. That's the way it works in some places.

Re:Why I Strive to be a 0.1x Engineer by marktangotango on Saturday January 30, 2016 @11:14AM (#11002370)
I once worked at job where a bug fix or 'feature' could directly result in sales landing a $1M+ deal. I was fortunate in that it was a growing company and my boss recognized what I was doing and promoted me accordingly. Subsequently when growth leveled off, there was no more recognition other than paltry annual bonus/raises. We lost some good people due to that situation.
Re:Why I Strive to be a 0.1x Engineer by dreamfactory2 on Wednesday January 27, 2016 @08:37AM (#10979923)
only way around this is to not be an employee
Re:Why I Strive to be a 0.1x Engineer by sliverstorm on Wednesday January 27, 2016 @10:39AM (#10980576)
Of course at 1% margin you got them an extra 6k in profit, of which your 2% raise may have eaten up a big chunk. Margin matters here.
Re:Why I Strive to be a 0.1x Engineer by maker1138 on Wednesday January 27, 2016 @09:26AM (#10980115)
If they had given you a bigger raise they would be creating income inequality /sarc
Re:Why I Strive to be a 0.1x Engineer by zwischenzug on Wednesday January 27, 2016 @05:58AM (#10979402)
Does this still happen? I've never seen anyone judged by this standard, and I've been in the industry for 15+ years.
Re:Why I Strive to be a 0.1x Engineer by LoSboccacc on Wednesday January 27, 2016 @06:04AM (#10979425)
me neither tbh, but it was a relatable sample. there still are plenty bullshit metrics out there at the same level of LOC, I used the worse to get the point out
Re:Why I Strive to be a 0.1x Engineer by sokoloff on Wednesday January 27, 2016 @06:34AM (#10979508)
I can confirm that I've seen "number of tickets closed" many times and "number of wiki edits" used in the wild in an evaluative/comparative context.
Re:Why I Strive to be a 0.1x Engineer by Consultant32452 on Wednesday January 27, 2016 @08:04AM (#10979780)
Number of tickets closed is a great example.
Re:Why I Strive to be a 0.1x Engineer by ck425 on Wednesday January 27, 2016 @08:22AM (#10979872)
I've been judged on this before. Me and a colleague were working on a system slightly different to others in our dept so the tickets got kicked around for ages after we'd done our bit. My manager kept pointing out how few tickets I'd closed. He eventually realised his error after both myself and said colleagues manager pointed out why but still occasionally referred to it in performance reviews. Moral of the story for me was: a) Figure out asap how a particular manager tracks your work. b) Get your own way to measure productivity so if/when it comes up you can say 'wait a minute I've done x'
Re:Why I Strive to be a 0.1x Engineer by ryandrake on Wednesday January 27, 2016 @09:49AM (#10980227)
or c) optimize your use of the tool to beat the metric. This doesn't necessarily require you to change how you're doing your job. The metric is "more tickets closed?" Great! Let's file more and more granular tickets for each and every sub-task, so that we can close hundreds of them a month.

Sales people know this. They might not even know algebra, but if you make their commission/bonus dependent on a KPI that depends on multiple variables with multiple weightings, they will turn into Einstein overnight to optimize their behavior in order to maximize their bonus. You get what you measure.

Re:Why I Strive to be a 0.1x Engineer by marktangotango on Saturday January 30, 2016 @11:19AM (#11002402)
>> they will turn into Einstein overnight

Coming back to read this thread and found this gem, perfect example of why I wade threw all the detritus as above. Thanks!

Re:Why I Strive to be a 0.1x Engineer by ck425 on Thursday January 28, 2016 @12:05PM (#10989419)
Unfortunately not an option in that case as the issue was tickets not gotten closed full stop due to a long process to complete them after my input.
Re:Why I Strive to be a 0.1x Engineer by dfyafla on Wednesday January 27, 2016 @07:56AM (#10979747)
sadly it's precisely what business are not gonna doing.

I've spent much of my career doing close to nothing, with pay increasing each year. Many businesses seem to recognize it and reward it. I've never had an employer who measured contributions by LoC (though unless you've proven yourself of course there is some measure of productivity, such as stories completed, etc. Everyone knows what everyone else did).

As stated in the root of this thread, this article completely misses the point of the 10x engineer, to the point of almost parody. The 10x engineer is the one who builds the tiny core of an app that makes everything else easily possible. Or who moves the whole team from one derlict, no longer useful technology to another. And so on. It has never, ever, been "the guy who spits out 10x the lines of code".

Re:Why I Strive to be a 0.1x Engineer by Cthulhu_ on Wednesday January 27, 2016 @06:00AM (#10979406)
The problem is that any nontrivial savings or profit is almost never done by one person or can be traced back to one person or one job; in established companies it's a large team of management, developers, testers, etc which all work together to create value. You could argue that you can pinpoint it in a startup, but that's why a lot give shares to its employees.
Re:Why I Strive to be a 0.1x Engineer by LoSboccacc on Wednesday January 27, 2016 @06:05AM (#10979429)
true, but team efforts can still trickle down and makes an easier framework where to bolt on individual contributions
Re:Why I Strive to be a 0.1x Engineer by patmcguire on Wednesday January 27, 2016 @06:39PM (#10984522)
There's this one, where instead of spending six months writing floating point in software he should have insisted on FPU on the chip.

http://yosefk.com/blog/10x-more-selective.html