13 ms·
The Worst Programmer I Know (2023)
- franktankbank 2y agoSounds like Tim was the manager. What exactly was the paid for manager doing?
- bluGill 2y agoThere are different types of managers. I'd use the term technical lead for tim. Someone needs to maneage product delivery. Someone needs to manage the backlog. Someone needs to manage the training of everyone. Someone needs to ensure people are getting setup for their next job. Someone needs to ensure everyone is paid right. Someone needs to handle it when two people don't get along. The above is a small subset of the full list - I don't know everything on the full list.
- franktankbank 2y agoNot to be a total fucking asshole... but: > Someone needs to manage product delivery: You mean the 2-week delivery cycle into an automated CI/CD? Good lord I hope they don't have a useless scrum master too. > Someone needs to manage the backlog: I'm curious what input the manager has into this besides reading through a list of engineer curated items. > Someone needs to manage the training of everyone: Tim seems to be handling that. > Someone needs to ensure people are getting setup for their next job: Tim seems to be handling that. > Someone needs to ensure everyone is paid right: HR has but one fuckin job as far as I can tell. > Someone needs to handle it when two people don't get along: Hey Tim can you id the asshole? How comfortable are you hiring/firing? Obviously IME non-technical management has done nothing but played politics and prevented firing of shitheads who were wrongly hired.
- throwanem 2y ago> HR has but one fuckin job as far as I can tell. Yes. Protecting the company. As long as anyone's paycheck doesn't have a slur actually written on it, that's roughly where HR's interest ends in the matter. Don't feel too called out. If I thought you were wrong on anything else here, I would say so.
- bluGill 2y agoHR generally gets a secondary job of checking with other companies are paying someone for similar work. The primary job is protecting the company as you noted. (though paying someone a competitive wage protects the company from people leaving for too little, or the from paying more than they must)
- dahart 2y agoDo you have experience being a tech lead and/or a manager? Tech leads and people managers are two explicitly different roles in many organizations, for good reasons, including, but not limited to them being both full time jobs. It certainly depends on the company and the size of the team and other things, but many many tech leads are not at all comfortable hiring & firing, nor with interviewing and prioritizing work and product managing and meeting with management and approving time off requests and dealing with complaints and deciding raises and promotions and dealing with equipment and managing budgets… the degree to which you’re downplaying these roles is what leads me to have to assume you might not know what’s really involved.
- franktankbank 2y agoMan that is a whole lot of fluff to differentiate between being able to hire and fire. I wonder what Tim would do.
- dahart 2y agoSo your mind is made up that someone fictional who is not described in a blog post does not contribute to an org you know nothing about? Is your point that all management is useless? Or something else? And why are you certain, what is your experience running a team or a company? Maybe the sarcasm isn’t communicating your point effectively?
- franktankbank 2y ago[flagged]
- bluGill 2y ago> You mean the 2-week delivery cycle into an automated CI/CD? Good lord I hope they don't have a useless scrum master too. If you can automation that job good for you. However some people work in a regulated industry where not getting FDA/FAA and their equivalent for every other country in the world before shipping software means someone will go to prison. > I'm curious what input the manager has into this besides reading through a list of engineer curated items. They better have a lot. You might call it product owner (in scrumm), or some other title. Every project I've never worked on has more great ideas than they can invest in today and so you need to figure out what the priority is. It better not be only engineering that has input to this - marketing (a very different skill from engineering) needs to have input, as does finance... > Tim seems to be handling that. [training] It is normal to handle more than one management task. I doubt Tim is handling harassment training. This is the main job of HR (not making sure people are paid as you seem to think) > Hey Tim can you id the asshole? How comfortable are you hiring/firing? probably not. As one manager of mine told me, he always knew long before the team if someone would work out. The team is close, knows that person is nice (most people are nice), and seems to be smart. If you are the first to notice someone isn't getting up to speed quick enough you are the "asshole" that needs to be removed from the team, an outside manager will be much quicker because they are removed from personal contact with the person in question.
- simonw 2y agoInstead he would spend his day pairing with different teammates. With less experienced developers he would patiently let them drive whilst nudging them towards a solution. That's not a management activity - that's the kind of coaching you would expect from a senior IC ("Individual Contributor" - I still hate that term.) Generally I would expect a "manager" to have authority over other people in the company: run performance reviews, handle promotions and hiring and firing. I think it's important for companies to provide a career structure that allows for influence, decision making and leadership roles that don't also require taking on those management tasks. Management tasks are extremely time consuming and require a substantially different set of skills from being a great team coach or force multiplier like Tim in the story.
- jprosevear 2y agoI would agree, but the manager probably should be in touch enough that they could see the teaming behaviour themselves.
- llamaboy 2y agoThey did… that’s the whole premise of the article
- Izkata 2y agoA lot of people seem to have zeroed in on "the manager's decision" and completely missed that it referred to the department manager, not the team manager, and the story is told from the perspective of the team manager.
- dilyevsky 2y agoNot sure the story is even real but apparently that was going on long enough without his manager knowledge that the manager was dead set on making tims exit preparations
- franktankbank 2y agoI can't quite tell what the manager in this story should have been doing though. Where is their value add? If its just MBA fluff playing psycho games with metrics then I'd argue they can get fucked.
- spiderfarmer 2y agoClearly performing another under appreciated task: to act as a buffer for Tim, allowing the team to flourish even when they don’t adhere to company policy. And all other managerial stuff apart from coaching.
- sehyun 2y agoDiscussion 2 years ago: https://news.ycombinator.com/item?id=37361947 https://news.ycombinator.com/item?id=37361947
- AGorilla 2y ago[dead]
- deleted 2y ago[deleted]
- croes 2y agoSo the real metric is the manager who knows their team and what each member brings in.
- peterldowns 2y agoYes, absolutely — and can effectively communicate that to their manager.
- JohnMakin 2y agoUsed to be bitten by stuff like this until I figured out something Tim and this author apparently didn’t - the problem is trivially fixed by management by attaching tim’s name to any tickets he may have helped out on. he can ask his teammates to do this and they gladly will, or, nice teammates will usually throw a “figured this out with the help of @Tim” in the ticket. goes a long way to keep “tim” on your team against obtuse velocity metrics like this. productivity metrics aren’t entirely worthless. if I come into a team, for instance, and I see they have 1 PR mapped to roughly every 1 jira ticket, and I see a guy on a 3 person team that’s got 70% of the PR’s in a year, that isn’t a clueless piece of info. he’s probably the lead. not always, and people game stuff like this, but it is a data point you can make note of.
- Clubber 2y agoYou're absolutely right, but some people just refuse to play silly games. It's odd that the manager isn't ever in the room with the team and doesn't understand his team's dynamics. Giving the benefit of the doubt, he must have been new, but any manager worth his salt will ask people on their team what the team dynamics are.
- BigGreenJorts 2y agoMy understanding is that metricizing like this is a tangible way for managers to defend "underperforming" team members to upper management. Your manager can always say you're a valuable member of the team and that will certainly go quite a way, but it's even more powerful if your manager can say, XYZ is an I valuable team member, if you need evidence of that, they provide a lot of value in supportive roles like on these tickets. [Listing tickets].
- throwaway7783 2y agoAgree on silly games, but this is simply acknowledging others' contributions. I think this should be encouraged in general, metrics or not
- Clubber 2y ago
- eckesicle 2y agoThese sort of stories seem to be dime a dozen and weirdly celebrated around HN and the software engineering community. We’re told of the hero, who goes against their managers and executives and doesn’t deliver any stories as agreed in sprints. We’re told of the engineer who isn’t hired by Google because he can’t invert a binary tree. Everyone else piles on and decree that, yes indeed, you cannot measure developer efficiency with a Leetcode or whiteboard problem. We’re too good for that. Another engineer chimes in: “I don’t test my candidates. The best people I worked with were hired over a beer and a chat at the local pub” We’re told of the MBAs who destroy the organisation, by introducing evil metrics, and how that the work we do are immeasurable and that the PHBs don’t understand how great we are. 10x engineers aren’t a real thing, everyone is equally productive in our digital utopia. Meanwhile in the real world, hordes of awful engineers deliver no story points, because they in fact, do nothing and only waste time and lowers morale. Meanwhile in the real world, each job opportunity has thousands of applicants who can barely write a for loop. Leetcode and whiteboards filter these people out effectively every day. Meanwhile in the real world, metrics on delivery, features and bugs drive company growth and success for those companies that employ them. To me, all these heroes, and above process people, just strike me as difficult to work with narcissists who are poor at communication. We are not special, and we do not sit above every other department in our organisation.
- mjburgess 2y agoPeople of a revolutionary (or "innovative") temperament are those who are going to say, "this system doesnt work, these processes are broken, the wrong outcomes arise" and ignore them. In doing so they just "do the right thing" in their judgement, and in so doing, develop the next iteration on the processes that others will follow. If these innovators are operating in a niche where innovation is required, they are solving different problems than most others and have different self-defined standards ("narcissism"), and so on. Probably many people who visit HN have this temperament, and a significant number are in niches which need to evolve this way (eg., this applies to all startups). HN is a small sample of engineers: most don't go to websites to conceptualise their own activity, reflect, etc. These are indications of people with a desire to innovate, or to solve novel problems in their profession. If you are in a highly stable environment, with effective processes, etc. then people of this temperament can be trouble if left entirely to their own devices: good managmenet would place them in projects/areas where there is some unknown unknowns to figure out. In many cases however, people without this temperament (say, "it works, dont break it, conservatives") find this behaviour unsettling, arrogant, disruptive, isolating -- because it is. There isn't any thing to "communicate" when you havent figured out what the solution is -- you can air your thought process every day, but that will just unsettle more people when they see how much it changes (in response to more thkning, information, etc.). And the values by which this change takes place are not conservative, they're radical and imposed by a person who sees a route out of a predicament and so on. It's quite arrogant to place yourself in that position, or think it's yours by some invisible duty that no one else has. In any case, if you operate in this niche, esp. eg., if you're in a start up environment -- then you arent going to care a jot about this "real world". They are acting against the real world, to improve it.
- bsindcatr 2y agoSome things that don’t measure whether a developer is “good”: - # LoC added, changed, removed - number of points earned in a sprint, when those points aren’t quantitatively indicative of business value, and they never are - number of on or off-the-clock hours schmoozing with others to solidify relationships with the business and “play the game” - number of times they “sound like good developers / intelligent people” in meetings or presentations - number of weeks they spent on really complex problems they worked to solve when they could have provided more incremental value earlier much more quickly - number of solutions they provided the company quickly while leaving many times more LoC to maintain - number of hours they spent honing code, formatting, updating to the latest versions but doing so for their own edification and preferences rather than focusing on the team and the business and what would help them and so many more...
- khazhoux 2y ago> Some things that don’t measure whether a developer is “good”: > # LoC added, changed, removed Everyone loves to say this, and yet at every company I've worked at, the top developers just cranked out code. High quality, performant code. And at every company I've worked at, the lowest performers would take a week to write 100 lines of basic python. "Oh, but khazhoux, those 100 lines were really very complex!" No, not actually. "But won't people just pad their code with comments to increase their LOC?" 1) I've never seen anyone bother, 2) I'm not saying "managers should count LOC"... I'm saying managers should look to see how much code each developer is actually committing to the codebase. If someone isn't committing much code, but talks like they're writing a lot of code, then you may have a problem. Honestly, somewhere along the way people seem to forget that software is made from code. I would never suggest a manager stack-rank their team by LOC, but the notion that the code people write means nothing, is preposterous.
- bsindcatr 2y agoYou can make massive LoC changes by reformatting everything or just adding superfluous code or changes. You can rip out a lot of code rewriting it to simplify and then losing a ton of business functionality that was used, or causing the need for a lot of business changes in process that might not be for the business’s benefit. You can, on your own or with AI, write many LoC, and maybe it provides business value, which seems to align with being a “good developer”, but someone has to maintain those LoC, so then you have to weigh the business value to the end user and the team. Is it ok to the team to have all the extra LoC to maintain? How often will those changes eventually result in valid further changes to get that code to work? Will other devs just rewrite it and are their changes good? So in the end, no, LoC added/changed/removed is not a good indicator of added overall business value when weighing both the business value to the user and the ongoing maintenance time that ensues, even though “good developers” along with “average developers” and even “bad developers” may have high LoC added/changed/removed counts. During what some come to think as their peak years, they still don’t think of things this way. But as we get older and more experienced, we realize that sometimes new or old crappy code is ok, sometimes we should do a better job if it makes sense for the business and team, that many can contribute in their own way if those are the people and resources we have, things may change, and overall there is a limited amount that humans can do. If you base performance on LoC and alter the team accordingly, you may lose great developers. You may also introduce volatility and risk later having a codebase that is higher cost to the business. But embracing change and working fast and loose may also be important, so it depends.
- mjburgess 2y agoI've had some thoughts on programming practice somewhat related to Tim's role, and some on language design this morning. I write code for others to read a lot, to explicitly teach them how to do something. This code has always been overly verbose, "decompressed" and teaches people the thought process behind a solution above being a "neat" solution. I was dragged a little reluctantly into this style, by being forced to anticipate all the ways the code may be misunderstood ahead of time -- by all the ways it was misunderstood previously. Its much less work for me to be verbose up-front, than fix misunderstandings later. After watching and looking at some of the best systems programming code/coders -- I've come to think this is just the best way to program in general. The latest program I wrote this way, and the quality of code is vastly higher. No abbreviations, any unusual coding practice (eg., conditional imports, using classes as namespaces rather than object templates, etc.) I noted briefly in comments to highlight it's unexpected. Any functions which are domain/app-specific have execessively long names which fully describe that step/asepct of the solution. Extensive design comments where my thinking is noted. etc. Programs which teach their readers how to think about the solution, rather than how to understand the code -- and teach it to a "smart junior" rather than to an expert. I think this is different than literate programming, and of the maxim "code is read more than written" -- it's a specific "educational ethic": code isnt clean, or literate, or readable -- its educational. If this is the best way for "programming in the large", then a property of programming languages follows: languages which enable the programmer to "decompress" their thoughts over many lines are preferable to ones which hinder this. This I think then explains something about the uptake of functional languages -- which resist this decompression of thoughts over lines of code. They are often sold on their conciseness -- as if a 200 line C++ ought be reduced to a 10 line F# program. This trades the wrong sort of productivity: long-lived large programs require programmers to build mental models of them far more often than they require them to add to them at-scale. A programmer self-teaches the code base more often than they write it: this isnt about reading. This goes somewhat to the role of Tim in OP. Perhaps the right software engineering programming practice is to write code as-if you are pairing with a new programmer in the future. To verbalise everything Tim would say, already, in the code.
- catlover76 2y agoInteresting, cool insight > any unusual coding practice (eg., conditional imports, using classes as namespaces rather than object templates, etc.) Why ever do that kind of stuff though ;__;
- failrate 2y agoThe worst programmer I know literally could not go a day without either checking in code that did not compile or saying something creepy and sexual in a large open plan office, and we all worked together to get them fired.
- SJC_Hacker 2y agoThe first problem can be fixed by CI/CD, and proper branching strategies. Each IC should have their own branch, then PR into appropriate branch Have no idea on the second, other than a visit from HR.
- failrate 2y agoI was the ci/cd guy. I am not exaggerating when I say this person's code just would not compile and they would not test locally.
- SJC_Hacker 2y agoAn intermediate state on their own branch maybe not such a big deal. But did they regularly initiate pull requests on on broken branch ?
- failrate 2y agoP4, not git.
- SJC_Hacker 2y agoI've never used perforce but it seems git can this problem at least
- SJC_Hacker 2y agoMean to say git can fix this problem
- decGetAc 2y agoHow did the manager not know Tim didn't have tickets slated for him ? How did Tim not even pick up some (at a lower capacity) and then still helped with the remaining time ? I guess as someone who does a lot of the same that Tim is doing,and I bet others can resonate, I still "have to" pick up tickets and I think that's always the expectation in any job I've had as an IC. Is Tim managing his time well ?
- gravy 2y agoIt never occurred to me that a rebuttal to "not using lines of code or bugs solved because it can be gamed" is just to point out productivity is literally always gamed
- readthenotes1 2y agoThey even have a fancy title, "measurement dysfunction", and a smug "if you know you know" nickname, Goodhart's Law
- NalNezumi 2y agoGlad to hear that Tim stayed and author managed to steer the entire process towards the right direction. Which requires a listening manager. I experienced the "bad ending" of this productivity metric trickle down: OKR. This startup wanted not just team-based 3-month review Objective Key Result but also individual one, and on top of it, tied stock option to OKR. It was a robotics startup so very cross-domain teams (Software, Hardware, Embedded, DevOps, HW design, HW testing, HW maintenance etc etc). The result? Developers became lonely islands. There were no "Tim" anymore. When I (Software Integrator) encountered an issue, that I just couldn't figure out but had a hunch it must be a deep-rooted issue, went to the expert (control/kinematics) for feedback. The answer I got was "I'm sorry I really want to help you but my OKR deadline is very close, and I simply don't have time". He could've probably fixed it in a day or less, but it ended up taking 2 weeks. The problem turned out to be quite deep: inside layer upon layer of C++ mega monorepo, I found that boost library and a custom kinematics library had implicit struct copy and the different libraries (more than two) used different order for representing translation & rotation (xyz, rpy, Euler, Quaternion) and all of the ordering of each components were different. Somehow over 2 years of operation nobody got troubled by this until our new team had to use it. Afaik I reported it to the Software team, but again, because OKR, nothing was done about it.
- jrs235 2y ago100% this. Want to sacrifice team output? Have team members be concerned about individual goals. Team alignment and synchronization will be off affecting the efficiency and effectiveness of that team's performance.
- bipson 2y agoI think just because this startup botched OKRs they still make a lot of sense. Intel and Google apparently relied on them heavily in their formative years. But: - they should be cascading (so conflicting OKRs between departments should not happen) - you should never, ever tie them to individual performance results/compensation/rewards
- YZF 2y agoMy sense was OKRs came later for both Intel and Google. Do you know around what year/size they started? I worked with some ex-Google person who tried to get us to use OKRs. That totally didn't work. Larger company. Like many things I don't think they're necessarily a bad idea it's just that good ideas always lose to culture. With the right culture/leadership it's not the process that matters. I.e. OKRs aren't going to fix an organization that isn't aligned and conversely there are infinite other ways to align an organization with the right culture and leadership. So in practice, like other things, it just ends up making things worse because it's never a real fix.
- lapcat 2y agoWas Tim hired as a teacher or trainer? What I find strange is that it sounds like Tim was not doing any individual work. As a very experienced programmer, I'm sure that I could increase the productivity of other programmers by pairing with them all day. However, is that actually the best and most productive use of my time? In my estimation, I think that overall team productivity would be maximized if I spent approximately 20% of my time pairing with others and 80% on individual contributions. (That's a rough estimate; it could be 25/75 or 30/70.) The article said that Tim was "patient", but perhaps he was too patient, wasting a lot of his time that could be spent accomplishing other things.
- motorest 2y ago> Was Tim hired as a teacher or trainer? Do you think that's any relevant? Software development engineers in general are hired to work on projects as part of small teams, and their goal is to deliver projects. It's not story points, it's not burn down charts, it's not PRs, it's not LoCs touched. It's how many projects are delivered, and keep everything and everyone problem free. This means that if you are struggling, your team will struggle as well until you unblock yourself. If you can unblock yourself by having a team member sit besides you and walk through a problem, that team member will be helping the team.
- infinghxsg 2y agoYes, obviously it’s relevant you have a fundamental misunderstanding about what software engineers do. We don’t “build systems” we diffuse risk for the managers. If someone is “helping build something” they can spend their own money doing that. This is business, the less work you do the more money you make.
- lapcat 2y ago> If you can unblock yourself by having a team member sit besides you and walk through a problem, that team member will be helping the team. I don't dispute that; hence the 20-30% pairing. But if it's the case that all day, every day there's at least one person on the team who is blocked, then you don't need a "Tim", what you really need is a new team, because that's an unacceptable level of blockage.
- readthenotes1 2y agoKinda concerned the author thinks story points correlates with biz value....
- RKFADU_UOFCCLEL 2y agoVery good article, managers just want short summaries of what's going on and sometimes these summaries come in the form of bad metrics.
- _fat_santa 2y agoHonest Question: Are there any metrics around developer productivity that actually work? Reading stories like this and others over the years I've come to the conclusion that you simply can't measure developers productivity on a granular level, it's just about the final product. However, I would love to be proven wrong.
- tpmoney 2y agoI don't think there are realistically any good "individual" productivity measures that work across a broad spectrum of employees, even when all of those employees are in the same role. Every team I've ever been a part of, even before being a developer has been made up of people that all contributed to the overall project in different ways. Imagine trying to measure all workers on a car assembly line by the number of screws they insert per day, or the number of welds they make per day. Anyone who's primary job on the line isn't inserting screws or making spot welds is instantly a low performer by this metric, and yet you can't assemble a complete car with only screws and welds. And it's worse I think in something like software development, where the specific way a team member contributes might be more nebulous. Very rarely do you hire someone just for their code review skills or the design capabilities. The team member that somehow always manages to recall the tiniest of details about the system that no-one else recalls from the feature work done 5 years ago is not exactly a skill you can find on a resume or even one you could build a good metric for even if you had hand tailored metrics for all employees. And it's a hard problem to solve. I don't envy the job of anyone in management trying to figure out how to determine who (if any) of your employees is a drag on the team. Sometimes it's obvious and there are concrete problems, but other times it's just someone "everyone knows" is a drag, but without hard metrics, you're left with awful things like having employees stack rank each other.
- johnnyanmac 2y agoIt's prone to its own biases, but I always figured the best metric was simply to ask how others on the team (or coworkers you need to work with) think of you. Your lead obviously has a bigger sway on this, but overall the idea is that you're generally doing a good job if the people around you overall see you as productive and feel more productive when working with you. I can only really see an exception for some gnarly Principal who's off deep into some very specific problem where this evaluation would fall apart. But such an individual problably isn't one you're worried about productivity with.
- dosinga 2y agoTim would do well in these times of LLMs. They can write code faster than anybody but also need more guiding and coaching than anybody. They don't learn anything no matter how much we call it machine learning. These days what we most need is a Tim of Tims - somebody who coaches software engineers into becoming Tim.
- darthrupert 2y agoDamn. Now that I read this I realize why my current team feels like nothing gets done and the reason is the team has no Tim.
- ibash 2y agoThat’s not a good excuse
- darthrupert 2y agoIt's not even an excuse.
- easyThrowaway 2y agoI mean, I've worked on some companies where management would've seen what Tim was actually doing and nonetheless reply with "We're not paying him to hang out with other developers, we pay him to sit at his desk and code!" Vox Jira, Vox Dei. Make sure you're not working in a company with such kindergarden-like approach at managing people before attempting anything like that.
- Beijinger 2y agoThis reminds me of the chicken problem: https://medium.com/heroicpresence/the-super-chicken-study-part-1-why-collaboration-is-the-new-competition-effb70b111a7 https://medium.com/heroicpresence/the-super-chicken-study-pa...
- Waterluvian 2y agoWhen you look at damage per second graphs and conclude that all your healers need to be kicked from the raid. It’s so difficult to quantify the value of “support” but they’re indispensable. I have yet to really find a sensible way to quantify it. It’s ultimately just something that you need to trust leaders to get right.
- pipes 2y agoI've never worked on a team where story points aren't translated into time. I've found story points to be a completely useless level of indirection. Genuine question, has anyone here ever found them useful?
- cornel_io 2y agoThere are a couple important things to also keep in mind: First: just like there can be individuals who lift up an entire team but are not ticking off tasks themselves, there can be apparently individually productive team members who slow the entire team down for any of a number of reasons. In my experience it's usually either that they are a) fast but terrible, b) have really weird coding styles that might not be bad but are very difficult for others to work with (architecture astronauts and people who barely speak the language often fall here), or c) are process bullies who try to set up the entire review system to enforce their preferences in a hardline way that suits them but delays everyone but them. Each needs to be dealt with very differently, to varying degrees of success, but my honest opinion at this stage is that no matter how productive these people seem by themselves it's mostly harmful to have them on a team. Behavioral issues in senior people tend to be really tough to adjust, and take a lot of energy from a manager that is better spent helping your top performers excel; that said, if you can get them to adjust sometimes it's worth the effort. Second: pair programming works great for some people, but it is terrible for others. I've measured this on teams by trial and error over fairly long periods, and unfortunately it's also the case that people don't segment neatly based on their preferences, so the obvious "let them choose" method isn't ideal. There are pairs of people who really love pair programming and desperately want to do it all the time who are almost fully 2x as productive when split apart instead (yes, including downstream bugs and follow-ons, meaning that they really are just having two people do the job of one), and there are people who hate pairing who see similar multiples by being forced into it even though they hate it. My rough intuition is that there are two independent variables here, a social factor that measures how much you enjoy pairing, and a style factor that determines how much benefit you derive from it, with the two not correlating much at all. There might even be a slight anticorrelation, because the more social people who love it have already naturally done as much knowledge sharing as is helpful, and the people who hate it are underinvested there and could use some more focus on the fact that they're part of a team.
- karaterobot 2y ago> You see, the reason that Tim’s productivity score was zero, was that he never signed up for any stories. Instead he would spend his day pairing with different teammates. I'm very glad this essay turned out to take this position, because when I read the first couple paragraphs, I was ramping up to write a mean internet comment about how stupid measuring developer productivity through story points is. A friend of mine is exactly like this Tim guy he talks abou: he spends time helping other people fix their problems, or takes extra time doing things the right way. His personal velocity suffers, but the team and the code base is greatly improved on net. He was put on a Performance Improvement Plan at one company, and told his job was at stake at another as a result. No question it's kept him at a Senior level when he should be higher at this point in his career. I sort of take it personally, because I worked with him at the company that gave him the PIP, and both he and I quit as a result. When I see companies trying to measure developer productivity (and tying it to employment and advancement) I think about Seeing Like a State by James Scott, and the concept of legibility: imposing by force a set of rules on a complex, messy system to make it easier to steer from some office far away. Makes it very convenient to managers, and often leads to disaster.
- noqc 2y agoGoodhart's law is not a joke. There is no standin for value.
- dmoy 2y agoYea the best teams I've ever been on have always had someone like Tim. The best best teams I've been on, Tim's helpfulness osmoses onto other people, and instead of Tim always being the one, the process goes like this: 1. Dev gets stuck 2. Dev attempts to unstick self for appropriate amount of time given problem and probability of self-unsticking given resources (e.g. some stuff is easier to search for internally, or dismantle and go piece by piece) 3. Dev announces "hey I'm blocked on XYZ thing" 4. Whoever knows the most about that topic (not always Tim, but often Tim) puts that as like their highest priority thing, and almost always jumps in right away to help (unless they're like ignoring chat cus they're in the zone) Works great especially if you do #4 at some break time (like say lunch or standup), and everyone has enough things to work on that they can do their own internal CPU pipelining and work on other stuff until someone has time to help unstick them
- Atotalnoob 2y agoProblem on a lot of teams is people skip over #2 in my experience. Good devs always do #2, bad devs skip it.
- ChrisGammell 2y agoExtra points for the ones that sit down at step 4 and lay out all the things they've already tried so the context on the problem is clear
- nedt 2y agoThat's easy to solve. When they ask me it might take an hour or two until I come back to them. If they were just trying to us me as a rubber duck the problem will have been solved by then. And it's not only devs. Also PMs have this behaviour. Sitting it out before asking what they need makes most question vanish.
- morsecodist 2y agoThe idea of measuring individual developer productivity is kind of absurd to me. I'm not saying that what we do is magic, there are just so many variables. Measuring story points or lines of code is kind of the opposite of productivity. This encourages developers to do as much meaningless work as possible. I'd want a developer to make a task simpler or use an existing tool which means less time writing code. The value of them saving that work from knowing another way is high but hard to measure. What you want is measuring business outcomes but those are hard to attribute to a particular developer. I think unfortunately we're left with our subjective judgement here. I think we'd do better admitting to ourselves that we can't measure this than to pretend we have some sort of science here.
- mrbadguy 2y agoWell said. There’s a noticeable lack of judgement in many places these days; people think they can abdicate it to metrics and data but this is mistaken.
- jckahn 2y agoI don’t think it’s that we _can’t_ accurately measure developer value/productivity, it’s that doing so isn’t feasible with any methodology we currently have. As you said, we’re not doing magic, therefore our value is measurable. Measuring just requires an impractical degree of time and energy.
- suzzer99 2y agoDev productivity is like quantum mechanics. The second you try to measure it, the wave function collapses, and you've fundamentally altered the thing you were trying to measure. That said, at every place I've worked you could get a starting point idea of who the top devs were by looking at overall code commits. This Tim sensei situation may be more common than I think, but I've never run into it.
- elevatedastalt 2y agoThanks to Goodhart's law, it's true for any measure that becomes a target.
- markus_zhang 2y agoA much easier solution is just assign a team improvement ticket to him and call it a day. I doubt he never worked on any tasks though, so maybe something for him once for a while.
- ChrisMarshallNY 2y agoI think this was posted here a year or so ago. I love this story.
- PartiallyTyped 2y agoWhat i like the most is how it describes the more senior engineers in my team.
- ewalk153 2y agoI love a good pairing ladder. While there is no absolute good measure of productivity, a suite of thoughts observation can provide at least tripwires. One major problem with tools that ask crafters to do data entry to show their value is that best people are most likely to refuse. You really need to focus on tooling to help capture what’s going on without toil. For example, if your folks are remote and they use software to aid in pairing (eg Tuple), script the system to log the tuple sessions and perhaps even capture the pairing in the commits made together. This can be used as an input to bring visible to be best leaders in your org.
- tasn 2y agoI get the point that they are trying to make, but Tim should try to find a way to ship things. It sounds like he could ship a lot and make the codebase better for everyone if he did.
- wwarner 2y agoHm. In the agile world, non-coders don't typically sign up for stories. So maybe this person shouldn't have been expected to land stories, or possibly there wasn't room in the budget for someone to be just a peer coder. I personally like the story paradigm as a way of working out (and then sticking to) priorities, and I love it when managers and principals work on stories like everyone else. Also, in the remote work context, everyone has to work harder on figuring out the right thing to work on, and stories are a decent way to achieve that.
- deleted 2y ago[deleted]
- ibash 2y agoMaybe. There’s also folks that pair because they’re a crutch for one or two other engineers. The other engineers never improve or are let go, but softly slow down the team. There’s also the folks that pair because their code doesn’t make sense on its own. Or they have some config files they’ve refused to check into the repo, etc. Pairing makes them feel valuable.
- gavmor 2y ago> There’s... folks that pair because they’re a crutch for one or two other engineers [who] never improve. I can imagine this happening if neither pair is all that good a communicator, and if the seniormost never employs a little Socratic dialog every now and then.
- hansmayer 2y agoI think a lot of this idiotic thinking about measuring productivity through "stories" is to pin on the "Agile" industry overselling their low value "methodologies" to the MBA-type managers, which are now unfortunately just about everywhere. Hence you have some clueless person deciding who has to go, based on how many tickets get moved on the board. As Joel Spolsky once said, no software company can succeed unless a programmer is at the helm.
- andix 2y agoThe title should be: Why measuring developer productivity by story points is bad. I was once part of a team that had a zero-storypoints developer too, let's call him Zero. He always refused to get any stories assigned during planning, his goal was always zero. He felt responsible for delivering all the planned stories and helped the people who struggled. He often came to me and told me to help someone on a specific task, because it was too much for him to help everyone. This was well understood by management though. Zero took a 4-6 week vacation every year, and management always pushed important releases back if Zero was not there. The team could've done it without him, and it might've been better for the team not to have Zero around for all important releases. But management was scared something could go terribly wrong without him.
- snapetom 2y agoWouldn't Zero be a hero in disguise, then? When I hear stories about Tim or Zero, it makes sense... with the caveat of whether they are actually transferring knowledge to teammates, and whether the other team members are capable of taking over the function of Tim/Zero. If not, then Zero is just covering for low performers, and your bus factor is still a liability.
- johnnyanmac 2y agoIn Zero's case, it sounds more like there is knowledge transfer but there's this cult of personality from management's perspective. Almost the opposite of Tim. It can be scary, but you gotta pass the torch at some point and accept there will be turbulence compared to Zero smoothing out the landing. That's how you get future Zeros/Tims who very likely had their own turbulence to handle.
- aaws11 2y agopreviously on hacker news: https://news.ycombinator.com/item?id=37361947 https://news.ycombinator.com/item?id=37361947
- m463 2y agoReading this is similar... https://www.folklore.org/Negative_2000_Lines_Of_Code.html https://www.folklore.org/Negative_2000_Lines_Of_Code.html
- casey2 2y agoThis just seems like you performed a social engineering attack on your boss to keep someone on the team who was objectively performing poorly but happened to be doing something that is valued in western culture. In short you replaced one well defined metric with an adhoc one following your bias. You are a peon. For all you know your local improvement has a negative effect on the whole company. Listen to your boss and let the company fail fast if it has an unfit system.
- PartiallyTyped 2y agoThis is an awfully bad reply. The person described in the essay is basically an L6 and an L5 moving to L6 at AWS. Our L6s don't write code, they build PoCs, work on designs, estimates, and scale through others. They use their experience and knowledge to scale out, and the L5s and L4s do the work.
- slowtrek 2y agoMoral of the story: Anyone that looks for the metric to find the weakest link, is the weakest one at heart.
- iamleppert 2y agoCounterexample: Not everything needs to be a group activity or social. If a developer of average skill can't manage to deliver a feature without the constant help from a "Tim", it says something about your code, processes, team. I've worked at places where they used pairing as a signal the team was working well together, when the reality was the code was so brittle and full of hacks it took the combined help (usually moral support) of a Tim to help support through every little change. Every team is different, but software development needs the time and space for individual work just as much as group work. A small team who needs a dedicated person for pairing, who also doesn't (or won't) do any IC work, is a huge red flag.
- nijave 2y agoDon't forget about the type of software. Something really specialized or algorithm heavy (science or math heavy) might be harder to do solo than a CRUD app.
- YZF 2y agoMy experience is the opposite. Easy stuff is simpler to pair up. Really hard stuff is solo. E.g. I expect Ph.D. work to be mostly a solo project. Not that it's impossible to do hard work collaboratively but I think a lot of heavy thinking is solo (Einstein, Newton e.g.) and it's hard to keep other people synchronized.
- johnnyanmac 2y agoMost of us work in decade+ legacy code made from a lot of people who are no longer at the company. So most of the code is brittle by default. That's simply the trend that emerged from a workforce that stopped incetivizing retention. As such, I'd argue that 80+% of your problem solving for the first few years (AKA the only years before you hop or get laid off) is in fact asking other people what the quirks of the code-base are. Maybe that is bad, but it doesn't seem like the retention culture is shifting anytime soon.
- tzs 2y agoI had a sort of similar situation. I was one of two senior developers at a company making utility software for Windows and Mac in the late '90s and early 2000's. The other senior developer was the owner and CEO of the company and had to spend most of his time doing owner/CEO things so was only able to spend maybe one day a week developing. The way we organized most of our Windows programs is that I'd write a non-GUI core that implemented all the underlying system level stuff we needed, and then the junior developers would write a nice Windows GUI that used that core. If the product needed anything like a VxD, a filesystem hook, an LSP, or any other Windows kernel extension I'd write that too. We were profitable and there would be profit sharing bonuses quarterly (I think...might have been monthly but that doesn't significantly change what follows). The owner was always tinkering with how to decide how much profit sharing each person got. One scheme, which he was sure was going to be great, was to take the total amount available for profit sharing for a quarter and divide that by the number of employees. Call that amount "1 share". So if there were N employees there were N shares available. He wanted those shares to be allocated so that 25% of the employees got 2 shares, 50% got 1 share, and 25% got 0 shares. Who is in what group would be determined by a company wide vote. Ballots were distributed that listed all N employees in alphabetical order, and we were told to write a 2 next to N/4 names, a 1 next to N/2 names, and write a zero next to the remaining N/2 names. For each person their numbers from all the ballots were totaled, and the 1/4 with the highest totals got 2 shares, the 1/4 with the lowest totals got 0 shares, and everyone else got 1 share. In addition, the people with the 8 highest votes would be put on a committee that would advise the owner on the direction of the company. The owner's expectation when he launched this was that I would be the top vote getter nearly every time, and would always be in the top 8 so be on the committee of 8 which he was planning for me to run. I ended up not being in the the top 8. I wasn't even in the top 25%. I don't remember for sure, but it was either somewhere in the bottom half of the 1 share group or it was in the 0 share group. The reason was simple. Although I wrote the core functionality of all our products my role was not really visible to people other than other developers. It was the junior developers who wrote the GUIs. It was the junior developers who did most of the interaction with the testers. When a test found a bug they'd report it to the junior developer who was, to the testers, the face of the project. If the bug turned out to be in code the junior developer would let me know. So every developer put me down for 2 on their ballot, but to everyone else I was just some guy in development doing some unknown work so I didn't get many votes from anyone else. At least the owner immediately recognized that this profit sharing scheme was flawed and dropped it. Since he reacted so quickly I didn't gloat too much over the fact that this was exactly what I told him was going to happen when he first proposed this scheme. (Some gloating was necessary because the owner and I had been best friends since we met in college about 15 years earlier, and the obligation to rip on your best friend when they do something stupid after you told them it would not work is stronger than the rule that you shouldn't tell your boss "I told you so!").
- umvi 2y agoSo there wasn't a way to capture the fact that Tim was helping with so many JIRA stories in a way that makes Tim's work more visible? Like maybe pair programming stories that Tim owns and moves on the board (assuming Tim's time is best used in a mentorship capacity)? It kind of rubs me the wrong way that Tim can just fly under the radar and do whatever he wants without any paper trail or accountability while the rest of the team has to clearly convey what they are working on
- afro88 2y agoYou can put subtasks under stories, and Tim can have his own subtask that represents his contribution. You can also (with an extension) put time against subtasks if leadership/management want to get really pedantic. Each team member should have at least 1 assigned story/task/bug in each sprint, and Tim should have at least x hours logged against subtasks off stories in the sprint. Or you can, you know, trust your team to deliver the stories they said they could do in a time window, as a whole. Let them figure out the how at the team level.
- black_13 2y ago[dead]
- TZubiri 2y agoI don't think this demonstrates the whole system and premise was wrong, you can just adjust so that Tim gets some credit whenever he helps a teammate. Measuring stories/features/issues solved seems sensible to me
- crazygringo 2y agoI agree with a couple other comments here -- this is a bizarre model where one programmer does no individual work and does all the helping. A much healthier situation, to me, is one where Tim does stories like everybody else, and when people need help they ask the group and whoever is the best at that thing helps them -- or whoever hasn't helped in a while. Surely there are easier stories for those who need the most help, and Tim should be taking on the hardest stories by himself? Or if you really do have an insanely lopsided team where everyone is straight out of school with no experience, and a single super-senior dev, then... shouldn't they just be a special kind of team lead who is expected to mentor full-time and not be subject to metrics? The post here is not a good example at all of metrics failing to capture work. In reality, it is surfacing the fact that either Tim's job title and metric are totally wrong for him individually, or else that Tim is failing to contribute the hardest code, and the team is failing to distribute the "helping" workload. In both cases, the metric is working as intended, and it is surfacing something very important than needs to be fixed. (Remember, "fire Tim" is not the only possible action you can take because of a metric.)
- wavemode 2y ago> shouldn't they just be a special kind of team lead who is expected to mentor full-time and not be subject to metrics? It sounds like this was precisely the situation, and the author's company did indeed take this very action, in response to seeing the data. So, what is your complaint?
- crazygringo 2y agoNo they didn't. They dropped the metrics for everyone entirely, and Tim's job title is unchanged. The article is arguing metrics are bad and shouldn't be used; I'm arguing metrics are a valuable signal and Tim should have been given a different formal role of mentor.
- move-on-by 2y ago> when people need help they ask the group and whoever is the best at that thing helps them -- or whoever hasn't helped in a while. I agree this would be healthy for an organization, but I don’t think that is often possible. In this example, the organization is clearly NOT tracking mentor activity. So, anyone who helps someone else, is getting zero recognition for it. I work with a lot of people where ‘ruthless prioritization’ is considered a good quality. That means no one gets any help. All taking. No giving. Pure selfishness really. Back to the example. Tim is stepping up and filling in a major gap for the company. People need help. He has decided to go against the grain and help. However, instead of doing it with the help of leadership, he is just doing what needs to be done and it almost cost him his job. Frankly, I identify with Tim. I love helping people figure out problems. Be it build env issues, failing tests, or some design gap. I help people all the time on top of my other work. While my immediate manager knows that and is good with it, upper leadership doesn’t care and just wants everyone to act like what they are working on is more important then what their peers are working on. Ruthless prioritizing is a seed of toxicity. I got a bit off topic… How to encourage helping peers and juniors when helping isn’t tracked and isn’t rewarded or encouraged? How do you maintain a healthy culture despite all the metrics?
- nawfalak 2y agoeven though this post puts in a good word for tim, calling him out and putting his linkedin in a post with this title is crazy
- randomNumber7 2y agoTims job seems perfect for me. I like casually hanging around and telling people what they can do better. This usually results in me seeming unlikable, since I am so often pointing out mistakes.
- hardwaresofton 2y ago> This usually results in me seeming unlikable, since I am so often pointing out mistakes. "comms diff" as the kids say. Communicating is a skill, it is possible to get better at it and help people in a way that they enjoy your presence as well.
- EGreg 2y agoHmm, I wonder what Paul Erdos was doing in mathematics Was he the cross-pollinating bee of math?
- ArthurStacks 2y agoIn my company I would have told him to start doing some work and getting stories delivered or he's gone. Yes, he's being useful in assisting others but I can easily find someone who can do that and their own work at the same time. He doesnt need to be sat there with others the whole time. What is likely going on there is Tim is playing his boss, playing up his pairing role and its benefits in order to sit being idle watching others work while providing commentary.
- glouwbug 2y agoMight it be that he’s so good everyone comes to him first and not you?
- ArthurStacks 2y agoI would not hire him in my business regardless of how 'good' he thinks he is. I'm interested in people who can get work done.
- guappa 2y agoYou still employ developers? You said AI made them irrelevant.
- j-bos 2y agoReal bummer the dilbert link in the story is broken, so much lost history.
- Tewboo 2y agoIt's hard to believe, but this person's code is so convoluted, it makes my head hurt. I've seen a lot, but this takes the cake.
- CaffeineLD50 2y agoA nice write up. But our AI overlords will need metrics that they can use.
- dankwizard 2y agoThese articles are so predictable and always have a smug aura around them. "Reports showed me the absolute worst programmer on my team. Did I fire him? No. I actually gave him a 20% raise. Do you know why? He was the best programmer on my team (in disguise)."
- lmm 2y agoI would guess at least 80% of the people who look like this Tim are contributing zero if not negative. I think there are good odds the actual Tim in the story was too. I mean I'd certainly love to do just the fun part of my job and duck out of all the scut work, if I could find a team that let me.
- WuxiFingerHold 2y agoAgile methods are often applied wrong and then are a disservice. There is no one-size-fits-all method to manage people and teams. Leadership naturally buys into those method as they are promised an easier life, but there is no shortcut to management and leadership. It's always situational. At my (very large) company Scrum and SAFe is applied to all kind of projects. Even to manage organisations with highly heterogeneous responsibilities and workloads. Think of 2 people doing dev, 2 conceptional work for various larger projects, 3 are basically consultants for other orgs, 4 are data analysts and 1 is doing some spreadsheet work all day long. Now our manager had the great idea to manage us with Scrum.
- Jean-Papoulos 2y agoIt seems strange that there is zero commits from Tim. Does he do code review instead perhaps ?
- atoav 2y agoEvery metric bas unintended side effects. Sure capitalists tend to think the greatest stuff happens from competition, but for real competition you need redundancy -and pay multiple people for writing functionally the same code. Competition within teams selects for the people who invest most time into looking as if they produced worked punishes those who are good team players. On top of that, how do you compare a guy who produces 100k lines of unmaintainable boilerplate code versus a guy who in the same timeframe hunts down a particularly nasty and hard to fix race condition and changed 1 line in the end? Any programmer knows the latter is much more exhausting and provides lasting value, while the former might actively hurt the project down the line. If you manage software development either you trust your team or you have to understand the program yourself and micromanage them. Best would be to trust and understand the program and only inject yourself when it is really needed.
- PeterStuer 2y agoYou get what you measure. If your metric is claimed completed story points, you'll get people good at claiming story points. Every system can and will be gamed, either directly or indirectly through osmosis and attrition. The only way to win is not to play. Put people in charge that know how the pie is made, then trust them to make the right calls. This btw is one of the major reasons why non-technical founders/managers so often fail.
- Sparkyte 2y agoThere is a Tim for every successful team. Sounds like a solutions architect.
- hackburg 2y ago[dead]
- NightSquirrel 2y agoThere are 4 methods of determining developer quality: Empirical metrics which can be misleading, or gammed. Team consensus which can devolve into a popularity contest. Manager "impression" which can be manipulated with strong people skills and "impression management", or letting an AI algorithm decide who is the most productive. No evaluation system is perfect and most are very flawed which is why management is both an art and a science and those that can do it well are very rare and in very high demand and therefore often deserve the compensation they receive.
- kevincox 2y ago> an AI algorithm In reality this is just some secret combination of the above metrics (assuming there are no "bugs", which there surely are).
- rurp 2y agoI worked at a company with very similar performance metrics and it was as counter-productive as you would expect. The surprising thing is that the management wasn't that bad overall but they worshiped at the altar of data and metrics for everything. That works great for some things, but not everything. The Jira-focused performance metrics led to a lot of short term work and fixes since everyone was heavily incentivized to get the immediate task done as quickly as possible without much long term thinking. This created an increasingly large amount of tech debt and caused some real messes. But hey, we could loudly proclaim our love of iterative innovation and data driven decision making processes! I suppose one benefit was that it became pretty easy to get a stellar performance review since it was completely based on a few metrics that could be managed.
- tracker1 2y agoI was let go from a position in a similar situation... I was pressed to enter Jira tickets and get them over the line. Didn't matter I was working with my team, acting as an SMA with two other teams, participating in planning meetings 20+ hours a week. I wasn't getting enough points in Jira across the line and had to go. Aside: I wasn't actually fired, when I went under "review" status, whatever it was called, I lined up another job and left.
- hackburg 2y ago[dead]