18 ms·
The Honest Troubleshooting Code of Conduct
- h2odragon 6y agoIm not sure but i think the only place to have that "we're here to work, not play soap opera at work" environment may be open warfare.
- noir_lord 6y agoOpen warfare or enterprise development. Though at least the former has the Geneva Conventions.
- NateEag 6y agoIf The Illiad is to be trusted, open warfare still has plenty of soap opera. Humans are emotional creatures no matter the context. You can't change that - all you can do is accept it then learn how to work with emotions (both yours and those of other people). IMO, the "adults in the room" are usually the people who have deep technical knowledge and have also learned how to regulate their emotions. One without the other gets you nowhere.
- rodgerd 6y ago> If The Illiad is to be trusted, open warfare still has plenty of soap opera. During World War II, some Royal Navy battleships turned their anti-aircraft guns on their own torpedo bombers, because they were determined that carriers not get the credit for sinking the Bismark.
- sneak 6y agoI think every organization above a certain size necessarily ends up with informal (or sometimes formal) groups of "adults in the room" that handle important things in good faith, as a coordinated team. It's inherently discriminatory against a certain type of employee (one who would rather metagame the organization itself rather than address the market/customers/ops) but quite necessary.
- noir_lord 6y agoOne of the best things you can do when you join a new organisation is figure out who those people are. They often know where the bodies are buried (or that obscure document stored on a documentation system from two generations ago that was deprecated but never removed "just in case" that describes exactly the system you are currently looking at wondering "wtf"). In an idealised world it wouldn't happen but I've never managed to work anywhere close to that.
- hitekker 6y agoI've heard a strategy to start with asking "who do you respect the most in this org?" or "who is the most knowledgeable person in the org?". Keep repeating that across every 1:1 and you may eventually build an influence graph.
- hitekker 6y ago> one who would rather metagame the organization itself rather than address the market/customers/ops Saved for future reference. My company has an exploding number of metagamers with an ever shrinking number of "adults in the room". It's stagnating hard.
- disgruntledphd2 6y agoTypically, this is a problem of success. Success attracts metagamers, which leads to less success, so they leave. Repeat until insolvency/heat death of the universe.
- sneak 6y agojwz once put it when talking about netscape: people who want to go to work for a successful company instead of people who want to go to work for a company and make it successful.
- lazyant 6y agoProblem is (as it seems the case in the author's case) when this group (I really loathe the term "adults in the room", by exclusion the rest of people are children or to be treated as such) has people with power that are "well actually" people just there to pontificate from their inflated egos without letting others do their jobs.
- Kalium 6y agoMost of us in software engineering have, at some point, encountered someone who does not see a difference between technical criticisms of a system and personal attacks on its designers and authors. This is an understandable error in a junior engineer, an irritating bad habit in a mid-tier engineer, and a problem in a senior person. In all cases, the answer often winds up being finding a way around them, much as this describes. I've been places where such people have found their way to technical leadership. Finding ways to improve things can rapidly become exceptionally difficult. At this point my only way forward is to have a personal blocklist of people whose technical leadership decisions I refuse to ever be subject to again. It's a shame, because some of them are also brilliant engineers.
- cratermoon 6y agoI'm well into the senior years of my career, and I have certainly been all of these things. But a fellow engineer taking things personally is not as problematic as the behavior that often accompanies it: never admitting error. Years ago I heard the phrase "set to bozo bit" to describe what you're calling a personal blocklist. It was described as an anti-pattern, and setting the bozo bit as a poor choice in nearly every case. It combines the bad parts of an ad hominem attack with the bad parts of personal arrogance and negativity. Don't think your other teammates won't realize you've "blocked" a teammate. Some of them will react badly, and potentially see you as arrogant. I end with this quote from E.W. Dijkstra: We shall do a much better programming job, provided that we approach the task with a full appreciation of its tremendous difficulty, provided that we stick to modest and elegant programming languages, provided that we respect the intrinsic limitations of the human mind and approach the task as Very Humble Programmers. ACM Turing Lecture 1972, "The Humble Programmer"
- zxzax 6y ago>It combines the bad parts of an ad hominem attack with the bad parts of personal arrogance and negativity. Don't think your other teammates won't realize you've "blocked" a teammate. Some of them will react badly, and potentially see you as arrogant. You are saying this as a senior engineer who is in a better position to do something else about being on the receiving end of those personal attacks. I respect that and I hope you are able to keep doing it. But that isn't the case when the abuse is continuing over a long period of time, that means no other senior person stepped up to do anything about it, and the people on the receiving either have to quit, or risk getting fired for "insubordination" because they filed a complaint against a senior employee. Playing the office politics game and trying to avoid the abusive employee is not sustainable, as you've acknowledged.
- hn_throwaway_99 6y agoI obviously don't know all the details here, as this is, by definition, just one person's version of events. That said, I'm always highly skeptical of any account that essentially paints many/most others in the org as the source of the dysfunction, and if only they implemented my brilliant idea would things get fixed. All large organizations have varying degrees of dysfunction, some more than others. Sometimes that dysfunction is toxic, but other times it's just a result of people being human with different opinions of how best to do things. Coming in to a new organization and making an announcement that is some version of "you're doing it wrong", unless you're very high up in the org, is rarely successful.
- anonymousab 6y ago> if only they implemented my brilliant idea would things get fixed. That is not how "Did it work? Kinda" reads to me.
- ericbarrett 6y ago> I'm always highly skeptical of any account that essentially paints many/most others in the org as the source of the dysfunction, and if only they implemented my brilliant idea would things get fixed. I didn't get that take from the article at all; I've been a part of one of the orgs she's describing and had the same experience. Over a couple years we went from a raucous, rough-and-tumble culture of open debate on the technical merits to a "polite" "respectful" org where nobody dared pop their head over the trench and bad decisions were allowed to continue unchallenged until they were nigh-irreversible. Much of it was due to a single executive's behavior. He was a big bully, always had to be right, and you knew that if you ever expressed an opinion about anything in his domain, he'd come after you like a fucking pitbull and worry your flesh until you submitted, using the power of his office and his connection to the founder to ensure you bent the knee.
- autarch 6y ago> Over a couple years we went from a raucous, rough-and-tumble culture of open debate on the technical merits to a "polite" "respectful" org where nobody dared pop their head over the trench and bad decisions were allowed to continue unchallenged until they were nigh-irreversible. I don't think polite and respectful are in opposition to open debate. If someone can't make a point in a debate without being polite and respectful, I really don't want to work with them.
- annoyingnoob 6y agoSeems like there is missing context here. Part of doing your job is communicating changes and explaining your reasoning when needed, "Unbuntu is doomed" doesn't really cover the need for communications. From the story I have no idea why there would be a need to switch form Ubuntu to Fedora - seems like a personal preference choice and that might look like change for the sake of change and no meaningful benefit to someone in a another group. Feeling like there is another side to the story here.
- Certhas 6y agoIt seems to me that this is kind of irrelevant to the point of the post. Also, if you would like more context, there is a first sentence to this post that links the post that explains the context. Specifically: > What would happen is this: a couple of people would get to talking (on Slack, for that is what they used) about something technical. There might be a topic at hand, like "Ubuntu is doomed", and they'd be hashing it out, figuring out what that meant. Then, invariably, someone would pop in two or three hours later, hit the hated "start thread" button on one of the comments, and would start shitting all over them. > "OMG why are you hating on Canonical" "Ubuntu is NOT DOOMED" > And then the people involved would have to walk this person back and say, look friend, Ubuntu at this company is doomed, because the company has decided that everything is moving from flavor X to flavor Y, and all of the flavor Y images are built from Fedora (yeah, I know, ignore that for this story) instead of X's Ubuntu. So once we're done with the migration, Ubuntu at this company is a goner!
- wilsynet 6y agoAuthor is saying that the company already decided they are migrating from Ubuntu to Fedora. That’s not the controversy. In a Slack channel, someone said “Ubuntu is doomed”. Not because Ubuntu, as a distro, will soon reach end-of-life, but because at $COMPANY, Ubuntu will be replaced by Fedora. That is to say, “Ubuntu is doomed (at $COMPANY)”. What author is objecting to is people joining the conversation several hours later and expressing unhappiness that someone is predicting the end of Ubuntu everywhere. But that’s because the new person wasn’t in the conversation, lacks context, and maybe should start by assuming the best intent rather than the worst intent.
- offbyone 6y agoI have been fortunate enough to land in a part of my employer's technical culture governed -- roughly -- by this sort of idea, albeit not one that's written down anywhere. The people in the Slack channels (IRC, back in the day, but time marches on...) that I frequent are the ones who provide some of the backchannel cross-team communication and technical analysis that make our company work. I like this article a lot; if I were trying to replicate the community I've got now, I'd probably start with this.
- zabzonk 6y agoI honestly found this completely unreadable. For example (and there are many others), what does this even mean: > This place hadn't quite ascended to the level of giving outages notable names ("Call the Cops", "Silent Night", "A Tree Did It" being just a few from elsewhere), it remained just "1152" after an associated ticket in a bug tracking system.
- pjc50 6y agoJust as some vulnerabilities have names like "Heartbleed" or "Spectre", some incidents leave enough of a mark on the company culture that they are assigned names.
- eecc 6y agoI think she used the wrong conjunction, but the meaning is quite clear
- rachelbythebay 6y agoI definitely screwed that one up, and it's slightly different now. I was going for one of those voiceover-y "not having attained X, they went for Y instead" approaches and it fizzled. I think it's because it was too long and because it's text and not an actual voiceover. (If that makes sense.)
- eecc 6y agoI got it, and indeed if you read it at “talking speed” it works ok. By the way, I also appreciated the post. I’ve been in similar situations in several occasions and never quite figured out how to avoid stigma and bad feelings for stepping on other peoples’ ego. I’ll give your technique a try
- yaacov 6y agoFacebook names their biggest outages and turns them into parts of the company mythology. Part of that is cool naming.
- ChrisMarshallNY 6y agoI like that, but it probably won't work, as the people that jump in, out of context, are the same ones that scroll to the bottom of the Ts&Cs, and bang on "ACCEPT." That's OK. I've learned the benefit of building a community by example, as opposed to fiat. The people that follow it will be the ones that don't need to read it, and they will provide the example. I'm an "older" engineer (just turned 59. I really don't give a damn what people think of it. That's one of the benefits of being my age). I have about 40 years of experience in tech; the vast majority, writing software. Sometimes, quite badly. Also, almost my entire career has been in "shipping" software; not just "writing" it. This has meant that I've always been pretty damn close to the end-user; sometimes, to the point of receiving personal...erm...feedback. Let's call it "feedback." I've also been responsible for delivering complete product, with polish and support. It wasn't "someone else's job" to clean things up. It was my job (it still is -even more so, these days). I've watched (and caused) some real Jurassic-scale disasters, over the years. That's one of the reasons I write damn good software, these days. Nothing like being given a bag and a stick, and told to clean up the mess (even if it was someone else's mess), to teach humility and caution. So, that means that I'm often the guy that says things like "Are you sure you want to do that? I did it once, and it did not end well." In today's "cargo" culture, that's considered "being negative," or "being timid, and only the bold survive," etc. ad nauseam. I'm told that I'm "not a team player," or that I'm "harshing the vibe" (I actually made up the second one, but you get the picture). This is funny, because my entire life has been ferociously dedicated to making difficult things happen. Precisely the opposite of being "too cautious to leave the starting gate." I've always been about "That's a difficult thing, and here are some of the things that might go wrong, along with a bunch we can't foresee. Let's figure out how to do it, anyway. We just need to be careful and circumspect." That's pretty typical with experienced folks in any profession; not just tech. We often have a lot of callous and scar tissue. Yes, we can be so timid, that we are too gun-shy to try difficult things, but we are also fairly likely to actually make it happen, if we take on the job. For myself, I tend to look for "dreamers," who have ideas, and then help them to actually realize their dreams, as opposed to some of these Krakatoa-level explosions that we see happen, because the execution of a perfectly good idea was flawed and ill-considered. That's what "engineering" is to me.
- BlueTemplar 6y ago
- Lammy 6y ago> without being second-guessed to death and hounded by people who just wanted to talk about "our tone" or "a lot of work went into that" Assume the best intent?
- yongjik 6y agoWell, being an introvert dork, I'm not the one to lecture others on how to effectively correct others, but, reading this: > I was talking about infrastructure, and specifically the wobbly mess of shitty "we're gonna run Flask everywhere and call it microservices" that somehow let people accomplish things over the Internet. Absolutely amazing. If this is how she talks at work, it's unsurprising that people would find the attitude abrasive. (And if this is not how she talks at work, then maybe she could tone down on dramatization a bit? Well, I mean, sure, it's her personal blog so she can say whatever she wants, but still ...)
- yjftsjthsd-h 6y agoI assume part of the point of the personal blog is to let loose in a way that she wouldn't at work, yeah. I certainly would understand that; I've supported stacks that I didn't like because that's what the business used and being a professional (IMO) means supporting what the company uses even if you hate the product, when on the clock.
- rachelbythebay 6y agoYou’re part of the problem if you get hung up on my choice of words this way. You might think about that and really ponder why you decided to do that. Hint: don’t tell me to smile more, either.
- yongjik 6y agoI'm not sure if it's just your style or you perceive my comment as an extension of workplace sexism, but in case it's the latter - if I saw a male engineer ranting about (ex-)coworkers publicly like that, I'd still have thought "Wow this guy sounds like a rockstar."
- nomdep 6y agoJust pattern matching and self-fulfilled expectations at work
- andrewflnr 6y ago
- harrisonjackson 6y agoOne real issue here is Slack being used for a RFC rather than something like a github issue. Slack is a great medium for realtime chatting but someone jumping into a conversation without context is exactly where it falls down. "Ubuntu is doomed" is exactly the sort of comment someone skimming to catch up will fixate on and jump to a conclusion - even with a code of conduct... You need a place for conversations to exist that promotes asynchronous communication. A github issue is a nice starting point since someone can create a summary at the top. The summary can be continuously updated. And an intentionally slower/more thought out discussion can follow. "RFC: Company$ moving away from ubuntu" is exactly the sort of productive GH issue I've seen at past companies. Of course GH issues regularly devolve - lots of examples dropped into HN over the years where people get angry/inappropriate at some poor open source maintainer, but it is still an improvement over slack.
- busterarm 6y agoSlack is being used as a substitute for all kinds of communication patterns where it shouldn't be and people tend to be assholes about it. For example, mandatory-participation announcement channels that don't actually require any action on the part of the receiver. They're used for every corner of the company to self-congratulate and should be emails instead of notifications. For anyone who can make these decisions in their own comapnies, if a channel's messages: - do not require immediate attention, and - do not require an action, for the love of god, do not make it a mandatory-participation channel.
- rachelbythebay 6y agoThe decision had already been made, and not by any of the people in that chat. We were shooting the shit about the impending change and what it meant in terms of our stuff running on it going forward. You ever, you know, just talk with your coworkers? And not just sling bugs at them?
- _kst_ 6y agoThe URL linked from the title is http:// http://... It should probably be https:// https://...
- deknos 6y agoi kind of agree with much of this stuff, but: * i saw in one project shitting only on commits of a certain person, only on a technical basis, even if other commits were worse. i know this because of a real crappy testcommit i did. i did not get the shit the other person got. * i still think, some swearings even for code are over the line, like linus torvalds retroactive abort of code, for example. We code and build things. many people poor their soul into this. and then other people come around and shit on it. * people who shit are often very agressive and competent people. so less competent people may on the receiving end quite a bit, for example the guys who built the ubuntu base in that example. is their work doomed or shit? does this mean that they did not work well? are they bad workers or do generate bad results? should they be fired because their workresults do not perform well? can that be a general rule? and this line is not cut through by on-subject-shitters because "be an adult". and this in turn might create toxic culture. just as well as the toxic positivity which only comes more often because it's better understandable by non-it-guys from HR. but i admit, at least it's another approach. we need more approaches and studies about them.