13 ms·
I had a similar brilliant engineer with odd working hours at one point. I also had the same problem with other engineers requesting the same odd hours, with equ
by PragmaticPulp 7y ago
I had a similar brilliant engineer with odd working hours at one point. I also had the same problem with other engineers requesting the same odd hours, with equally negative results.
In my case, I eventually learned that the odd hours weren't the key to his perceived success. Instead, he used the odd hours to force us to give him only work that could be accomplished alone. We were lulled into letting him make key architecture decisions in isolation, because no one else was awake or online at the same time to discuss them.
Eventually he became the architect by virtue of operating in isolation, where we couldn't discuss his decisions. Everyone else was forced to work around his code. If he refactored the codebase in the middle of the night to make his job easier, the other team members were all forced to work around his refactor and waste time updating their PRs to match his work.
Worse yet, having someone like that on the team drives away other great employees. Eventually everyone else will get sick of accommodating the architects isolated schedule. If they have other opportunities, they'll leave.
> I often think about how I could have better allowed his brilliance while not alienating the rest of his team, but in the end I failed.
It's not on you. Brilliance and individual productivity aren't everything in a team setting. If your project must scale past a single person, you need everyone operating on the same page. It's painful in the short term to lose the quirky rockstars, but it makes for a healthier team in the long run.
- fizx 7y agoYou're both right :) You want the "quirky rockstars" as your prototypers, not your architects. Then everyone can thrive.
- rch 7y agoIt seems like all these comments assume everyone is working on roughly the same class of problem. That's probably a mistake.
- heyflyguy 7y agoThis is a super strong, on point message.
- oh-4-fucks-sake 7y agoI feel like I'm currently living in a gray area between those two alternatives. I'm US as the lead architect for this project. I've written much of the code, made most of the architectural decisions, and all PRs go through me. The curveball in my situation is that all of my engineer teammates are offshore of varying levels of quality. I don't really have a choice to cut all the fat because I work at a consulting firm but on a unique project where it's a joint ownership between my consulting firm and a client. The project behaves more like long-term internal project work but its the client paying us and our bills. We're incentivized to keep these green offshore guys on the payroll even though their contributions are pretty small. For whatever reason, even though the client knows they submit low-quality work, the client still wants them on the project. We've tried over and over to push the devs critical thinking skills to the level where they can take a prototype and not royally fuck it up, but they just can't seem to meaningfully push through and take ownership of a prototype. It's weird, because I do end up architecting and developing in isolation (which is sweet, honestly) but stakeholders are somehow happy enough with our throughput that they won't shell out for more US senior engineers. I guess the upshot here is that a team is only as flexible and scalable enough as the average level of talent on the team.
- ticmasta 7y agoRands in Repose (Michael Lopp) talks about this in his book "Managing Humans" as volatiles and stables, the former being largely analogous to rockstars. He (I believe accurately) describes how volatiles ignite the fire that leads to big change, then become stable around the new solution (or leave) and get disrupted by new volatiles. It's very similar to Clayton Christensen's work on disruptors. If you're a manager, the math of having true rockstars on your team rarely works. They take more effort to manage yet produce fractional more output (they might be 10x better than a terrible developer but they're not multiples of solid devs). So I'm way further ahead if I can focus my efforts on improving broad-based productivity 5-10% than if I cater to my rare unicorns that are 30-50% better than my average team. Something I think ICs often overlook is a focus on leverage and scale to drive big improvements.
- westoncb 7y ago> Something I think ICs often overlook is a focus on leverage and scale to drive big improvements. Mind expanding on "leverage and scale" in this context?
- nogabebop23 7y agoI think what they mean is scale = repeatability; you can't really say "clone rockstars" but you can do something n-times with a pool of good developers, and leverage = the scaling action; ex: a senior dev could increase their output by 10% or you could introduce some knowledge sharing/mentorship/coaching program where the individual's capacity falls by 10% but they increase an entire team's production by 5%. In a small org where you probably shouldn't have dedicated dev. managers stick with the former; in growing companies the isolated rockstar is still rare and you're trying to move the needle with 50, 100, or more software devs.
- kraigie 7y agoWas this Google's entire point of 10% time? An outlet for unicorns that keeps them away from the company bread & butter and unicorns.
- proverbialbunny 7y agoAs someone who has built prototypes and has worked with others who do the same, I couldn't agree more. The problem is there aren't many prototype gigs out there, so it's not a great specialty.
- Legogris 7y agoIsn’t there? Academia, R&D divisions, early-stage small startups... Most greenfield projects require a prototype.
- proverbialbunny 7y agoI've worked at mostly early-stage startups. I haven't seen R&D Divisions at companies, but I'm sure something exists.
- tilolebo 7y agoClearly, odd working hours doesn't mean communication has to stop. It should be possible to set up asynchronous communication channels, like a collaborative document-editing service (Google Docs, Dropbox Paper, etc).
- marcinzm 7y agoThe problem is response delay. If you need 10 rounds of back and forth to communicate something then your total time is 10*delay. Moreover, at some point people start to forget the context so the total time goes up even more and quality of responses goes down. If it takes 6 hours for a response then you can spend days waiting for a relatively simple point to be hashed out. Especially if there's multiple people whose input you need who are all working at different schedules.
- tilolebo 7y agoClearly, having 0 work hours in common with the rest if the team is a problem. But what if you have at least 2-3 hours per day? You can already discuss a lot of things during that time. I get that asynchronous does not always work, but it has some benefits, especially for tasks such as architecturing an app. I'd be worried if such discussions would happen only in an oral fashion, or in chat channels.
- spease 7y agoI find this often boils down to people being unwilling to read/write very much. If people insist on reading and writing no more than a single sentence at a time, async communication will be very difficult. If they’re willing to provide full answers to the question, it’s not so bad. Good documentation is also invaluable, and good documentation being 1:N is often more valuable than a 1:1 synchronous discussion for certain things.
- Cthulhu_ 7y agoThat's assuming people bring up the patience to wait for a response - a rockstar developer type is inclined to go "screw that, I can whip this out in a couple hours", so by the time others have a chance to think about it it's already done. Not too late to challenge it, but it'll feel like wasted effort then.
- dheera 7y ago> you need everyone operating on the same page You're right that people need to be on the same page, but being on the same page should not be 5 scattered 15-minute meetings in a day on top of "Hey did you see my e-mail" and "Hey check this out" and "Hey where is that site you mentioned yesterday". Real work gets done when people work undisturbed in blocks of time. Meetings should be scheduled such that engineers have large blocks of continuous time. Meetings should be focused on generating action items and establishing the prerequisites for those action items so that further ad hoc requests are minimized. For example, you might find that 1pm is a good time for meetings because it accommodates all (early/late-shifted) commute schedules, is right after lunch which people need to take a break for anyway, and leaves a continuous block of work time after the meeting until the end of the day. The timing may differ in your work place but you should figure out what works best. Asking your engineers is a good first step.
- Consultant32452 7y agoMy team has offshore and onshore developers. We get all the downsides of a quirky rockstar who architects things in the middle of the night without any of the benefits of lots of work getting done.
- protonimitate 7y ago> Brilliance and individual productivity aren't everything in a team setting. If your project must scale past a single person, you need everyone operating on the same page. It's painful in the short term to lose the quirky rockstars, but it makes for a healthier team in the long run. I think this is a self-inflicting ailment in the tech world. Many who are ICs fancies themselves one of these mythical "rockstars" who can code the business saving solution in 24 hour benders. Management/hiring/culture in general put too much emphasis on the brilliance of a single person on the team. But as you said, there's a time and place for the brilliant IC, and that's usually the very very early stages of a business. I've seen this sort of situation play out at my current job. We had a "rockstar" who was with us from the beginning. He was able to ship solutions extremely fast, was a fantastic eng, but loved to do things on his own schedule. He was the backbone of the eng side of the business... until he decided to take an offer somewhere else. He pulled off a crazy last 48 hour bender to wrap things up he was working on, but in his haste left behind a half-finished total rework of the back end which nobody other than him had a vision for. We spent the next 6 months trying to understand and finish where he was going with this rework. The manager who enabled this from the beginning also left, so we were left with a bigger mess than when we started. Sure, this particular eng got a metric ton of features shipped in our early days, but in the end ended up costing almost as much to clean up his mess as the value we got from him in the first place. There's a way to make these situations work, but blindly enabling the whims of the rockstar is not it.
- hanniabu 7y ago> there's a time and place for the brilliant IC, and that's usually the very very early stages of a business I definitely agree with this with a slight alteration....early stages of a project
- cgrealy 7y agoEhhh... everyone is brilliant in the early stages of a project. Coming up with a fantastic green fields design isn't hard and represents a fraction of a percentage of the overall work. Give me a solid engineer who can deal with all the legacy cruft and still produce a maintainable piece of software.
- beat 7y agoThis is the sort of thing that gets me ranting about how 10x programmers are actually vampires, sucking their life out of the rest of the team with their loose-cannon behavior.
- oarabbus_ 7y agoWould love to hear some examples/experiences especially since 10x programmers are so deified
- cheez 7y agoIt's like classic school. My kids complain that they are forced to slow down to keep pace with the rest of the class. Same idea here.
- beat 7y agoI've worked with a lot of them over the years. Big/breaking codebase changes without consulting anyone, not waiting for requirements to work out, not playing well with others, not being willing to mentor less experienced team members... the list goes on and on and on and on. I do not like working with 10x programmers. They're the engineering equivalent of putting your bills on a credit card. You have to pay it eventually, with interest.
- reggieband 7y agoYour description sounds so familiar to a situation I was in over a decade ago I almost wonder if it is the same! In my case the "brilliant" engineer wasn't really that brilliant although he did have grand intentions. He ended up building an XML based configuration systems so wildly over-complicated it retarded development for everyone else involved. He'd come in overnight and make massive change that would require everyone to spend their entire day re-doing their work. He was also extremely toxic from a personality standpoint, often getting into angry exchanges with his piers. He was the type of engineer who tried to dominate technical discussions by insulting and dismissing others rather than by demonstrating the merit of his ideas. Most engineers would just avoid the confrontation and this allowed him to railroad bad ideas through. Eventually, after I left, he bypassed all dissent entirely by working overnight so that no one could even challenge him. I was on contract so I just left. No way was I going to deal with that environment. I lost all respect for the technical management there too. The director in charge of the project seemed to be confusing arrogance and belligerence for ability. Rather than reign in a clearly toxic employee he actually encouraged everyone to work around him and touted the benefits of the crazy XML system he was building. These benefits, of course, were no more than empty promises from the employee himself. But they were politically expedient ... the director could claim the team was building some advanced system that could potentially be reused. It gave him some cover to explain why things were taking so long to deliver. IMO, this is the worst environment possible for development. You have directors favouring empty promises for incredibly complex systems to give them good talking points. You have toxic developers who make any dissent to their bad ideas so unpleasant that they gain control. This creates a feedback loop where good engineers see bad ideas and bad behaviour get rewarded with special treatment.
- chasd00 7y agothat person doesn't sound brilliant at all. What earned him the badge "brilliant"?
- JohnBooty 7y agoWhen dealing with complicated systems (PARTICULARLY fragile, over-complicated ones) the engineers are often (unfairly) seen as "brilliant" because they're the only ones that understand the mess. It's ironic, right? The more fragile and over-complicated the system, the more the engineers who created the mess in the first are considered "brilliant." I've seen this countless times. (In defense of such engineers, it's often not their fault. They built one thing, and then management and business needs dictated a plethora of changes and technical debt against their wishes. I have been one of these engineers on occasion)
- JohnBooty 7y agoOuch. I used to work with a guy like this. Generally speaking, this is an occurrance that is exceedingly common and extremely under-recognized in our industry. Instead, he used the odd hours to force us to give him only work that could be accomplished alone. We were lulled into letting him make key architecture decisions in isolation Our guy accomplished this via different means but the end result was the same: because of various factors, he became "architect" and essentially was able to make decisions alone. Then we had to live with them. Eventually he became the architect by virtue of operating in isolation, where we couldn't discuss his decisions. Everyone else was forced to work around his code. Yyyyeeeeeeep. Our guy was genuinely, I think, the best engineer on a team of pretty good engineers. But in terms of sheer talent he was not a "10x" coder in terms of raw talent. Call him perhaps a "1.2x" or "1.5x" in terms of raw talent. However, he was essentially able to operate as something like a "10x" talent because he got to do a lot of greenfield work, make sweeping architecture changes and decisions, and so forth. Meanwhile we were all left to deal with his fallout. Whether or not you believe there are legitimate "10x" engineers (we'll set that debate aside for a moment) I think it is very, very obvious that we have misidentified the talent level of many engineers. Your actual output level as an engineer, be it 1x or 100x, is always a product of many factors and your actual talent level is only one of those factors. Worse yet, having someone like that on the team drives away other great employees. Yes. Two big reasons. 1. It's not a good way to make software, obviously. Great employees want to make great software and will be frustrated. 2. It's career fucking suicide to work under somebody like that. It's impossible to shine when working under somebody like that. You can't clean up a mess as quickly as other people can create a mess. You just can't. With very rare exceptions you simply cannot mop a floor well enough to be seen as something other than a janitor.
- fjabre 7y agoTo play devils advocate: If he was as brilliant as you imply perhaps he SHOULD have been the one making the key decisions under his purview anyway. This almost sounds like bitterness coming from the other side of the team. Not everything is a team decision and nor should it be. Often times brilliant engineers, in order to express that brilliance, need to be left alone by over zealous managers and jealous teammates that would rather argue than get work done.
- xmalloccc 7y agoYeah, this is a general problem with these threads here. If there are 5% brilliant engineers, the other 95% will answer here how horrible the 5% really are. Never mind that the 5% do most of the work and the other 95% attach themselves to a project, criticize and obstruct the 5% and take the credit for the project.
- derf_ 7y agoHello, fellow brilliant engineer here. In my experience, it is not as often as you might think. The key issue comes down to brilliance coupled with selfishness. If you look for it, you can see some common themes in these comments: "...the other team members were all forced to work around his refactor and waste time updating their PRs to match his work," or "Meanwhile we were all left to deal with his fallout," or "...this particular eng ... ended up costing almost as much to clean up his mess as the value we got from him in the first place." We have all had to work with that guy. In the early part of my career, I have been that guy. People are not arguing because they don't understand your brilliance and are jealous of your productivity. It is because you are making their lives harder. That is what makes people bitter. Turn the problem around: instead of asking "how can I get all of these over-zealous, jealous people to leave me alone", ask, "how can I apply my brilliance to make their lives easier instead of harder?" Unless you are doing something basically trivial, there is usually too much work for any one person to do it all by themselves, no matter how brilliant. You need those people. So help them out. You will have a much better time. And so will they.
- PragmaticPulp 7y ago> To play devils advocate: If he was as brilliant as you imply perhaps he SHOULD have been the one making the key decisions under his purview anyway. I think you missed the point. It's easy to operate in a vacuum. If you maneuver yourself into a position where you can only ever operate in a vacuum, you avoid the real difficult work: Coordination, communication, cooperation. That work doesn't just disappear, though. The rest of the team has to pick up the slack, fix the leftover bugs, work around the lone wolf's quirks, and so on. If a project requires more than a single person to scale, then those people need to work together as peers. If you let one person run away with the fun work and leave everyone else to clean up the bugs and pick up the scraps, it's not a sustainable situation.
- toraobo 7y ago> We were lulled into letting him make key architecture decisions in isolation, because no one else was awake or online at the same time to discuss them. That sounds like a process rather than schedule issues: important architectural decisions shouldn't be performed "on the spot" but only after some sort of discussion. Preferably in writing. > If he refactored the codebase in the middle of the night to make his job easier, the other team members were all forced to work around his refactor. Don't you do code review? People shouldn't be able to push code without another person looking over it. These issues would also apply to remote or off-shore workers.
- Aeolun 7y agoIf you are the lead you generally have permission to push directly to master. This isn’t always something you do, but it’s occassionally helpful to clean up the last mess before a release.
- yjftsjthsd-h 7y agoSure. Not ideal in theory, but in practice that's generally reasonable. But if it's a regular thing, it should get called out and addressed one way or another (i.e., even ignoring the pathology that this conversation covers, if there's always a mess to fix right before release, then your process needs to be revisited).
- gregmac 7y agoThere's a world of difference between "clean up" and "refactored the codebase in the middle of the night ... [and] other team members were all forced to work around his refactor and waste time updating their PRs to match his work". "Clean up" would be things like fixing typos/docs, bumping version numbers, fixing a build script because some path/version/etc of some external dependency changed, and sure -- mostly that's fine. If you're doing proper CI, there should be little to no surprises like this in your master branch, because you shouldn't be merging branches that break the build, and the "final release" build is really no different from any other build, other than you label it "release" (or "GA" or "RTM" or whatever) after the fact. Refactors and any thing that could be classified as an "architectural change" really must go through code review. If someone thinks their skill is so great that reviews are pointless -- I absolutely guarantee in 100% of cases that they're gravely mistaken. If the rest of the team can't understand the changes, well, they're bad changes, full stop. This is the team working on the code base, they are the ones that have to be able to understand it. This can be fixed of course, by firing everyone and getting a better team (just kidding), helping raise the skill level of the team, or by simplifying the changes. In my experience though, if no one understands it's usually a sign of overly-complex and/or under-documented code. Code reviews are a two-way street, and learning is not just for the reviewee -- it's a great opportunity for the reviewers to learn, too. They get to see how someone else solved a particular problem, with rationale, the opportunity to ask questions (and 80%+ of the time, a question about how/why is usually an indicator a comment in the code is missing), and "current context" (eg: it's a change that's probably been discussed in the days/weeks before). If the changes really are good, and it's a good PR (eg, not a massive, surprise major refactor that touches thousands of lines of code) then the PR will pass easily. And seriously, if you need to do a massive change like this in a rush right before a release, then the team probably missed something major and the release simply isn't (and was never) ready. Major refactors means brand new code, and putting brand new code into a release with no testing (not even dev testing!) is a terrible idea.
- shados 7y ago> Instead, he used the odd hours to force us to give him only work that could be accomplished alone Ding ding ding. We have a winner! A big problem with people like that is that at the end of the day, writing code or building stuff is the easy part. Communication, coordination, mentoring, onboarding, figuring shit out, etc, is the hard part. People who hide for large parts of the day or multiple days are usually just dumping the hard part on others. Since the industry is often stuck thinking that line of codes === worth, these people seem more productive. Often, it's the polar opposite. They're freagin useless and anyone else in their situation would do the same or better. Everyone else is slower because of the increased burden (who's answering questions when Mr "I work from 5pm to midnight" isn't around?
- spease 7y agoIf people are regularly interrupting their development work to answer questions, then it suggests that documentation isn’t a priority and/or the team isn’t being very productive. Async communication often works fine as long as people are willing to read and write in detail. And you can often work faster if the code is better organized and self-documenting than if you have to spend an hour meeting with another dev to understand it.
- nbanks 7y agoThere is a compromise. I have a tendency to work odd hours because it's much easier to get actual work done if there's less distractions. On the other hand, I do feel it's important to have at least 1-2 hours overlap with other people's schedule to ensure that there's buy-in for any major changes in the code base.
- hinkley 7y agoI've gone from loving Flow state early in my career, to being cautious about it, to watching with suspicion and dread the behavior of my coworkers to see if they are making decisions based on opportunities to engage in it instead of rational thought. For some it seems like a form of thrill seeking. When you are in flow state you are producing a lot of output but aren't asking any questions. That turns into big, solid chunks of the system with no oversight, no consensus, no introspection, no empathy. And when someone does ask questions - because who wouldn't? - we aren't questioning a small isolated part of the architecture, we're questioning a very big piece. One that the author feels very warm feelings about because they had An Experience while writing it. Flow state is useful, possibly great for refactoring. It's occasionally a waking nightmare for new code, and not a great experience for everyone else the rest of the time.
- banannaise 7y agoFlow state is where I build trash that works, so that later I can refactor it into elegant code that doesn't.
- jacobsenscott 7y agoThis is where mandatory code reviews really help. He can't merge that crap and mess everyone else up without someone approving the changes. Also, to be frank, if his code is reverberating all over the code base like that, causing merge conflicts and re-write all over the place, he is a terrible engineer - not a brilliant engineer. He clearly had no knowledge of the basic SOLID principles, modularization, encapsulation, etc. He was a rookie blasting experiments all over the code base.
- spease 7y agoWell, or the code base had no organization to begin with and he’s moving in that direction. Sometimes individual people can be very focused on their particular assignment and greatly resent somebody forcing them to make even small changes. Even if those are to make a global API smaller and more consistent.
- AlanYx 7y ago>In my case, I eventually learned that the odd hours weren't the key to his perceived success. Instead, he used the odd hours to force us to give him only work that could be accomplished alone. We were lulled into letting him make key architecture decisions in isolation, because no one else was awake or online at the same time to discuss them. Eventually he became the architect by virtue of operating in isolation, where we couldn't discuss his decisions. McCarthy's 1995 book "Dynamics of Software Development" has a chapter devoted to this phenomenon.
- Roark66 7y ago>Eventually he became the architect by virtue of operating in isolation, where we couldn't discuss his decisions. I had opportunity to see some projects that went in the wrong direction by bad architectural decisions resulting from an opposite behaviour. Every architectural decision would be made based on everyone's input where most junior people's opinions would weight the same as most experienced. In the end decisions were made primarily based on how simple the solution appears and not based on its suitability for performance, future extensibility, maintainability etc.