News for hackers. Stuff that matters.
Re:How to spot symptoms of burnout on your engineering team by blurnsball on Friday April 14, 2017 @03:36AM (#14113161)

  How do you spot this symptom? It might be 
  that a team member isn’t commenting on pull 
  requests as much as she used to. Or he’s not 
  speaking up in sprint planning and retrospective 
  meetings. 
Ha ha! Oh god.

This is basically the worst thing I've ever read. And why? I think you already know, but let me tell you anyway!

Meetings are bullshit. At all times they are unrealistic. There is what people say during a meeting, and then there is what actually happens during the interplay of the group dynamic, as work gets done.

Sit at tables all day, and bullshit about diagrams and ideas, with zero concrete examples, and some ham fisted emails where people dump screenshots into MS Word documents, and then forward as email attachments, with captions like "it's broken. fix it."

Then go and try to write some code, and see what happens when someone else in the meeting drops a JSON object on you, that has half the properties you need to do anything, and most of them are in the wrong place, or at magic number slots in an array or something.

You have to have your head up your ass, to expect people to be chipper little busy bees at all times, and then write feel-good blogarticles like this.

But you have to be Satan himself, to put an article like this in front of a so called "scrum master" and tell them that happy thoughts at all times are the only "normal" that is the correct and proper Normal, and all other "normals" are actually signs of workplace PTSD.

Now uppity tough guy managers will bring motherfuckers in for review only to remind them that they forgot their flair, and they seem to have a case of the Mondays lately, and ask them to put on a happy face, and pitch in for the big win!

That's not how it works.

You have a team dynamic, and that team dynamic doesn't change if your team members are supporting a "Sick System." A Sick System is doomed to be inefficient, and foments disappointment, because the process is inefficient by design, but doubly punishing when hopeless, lost people are involved.

But even so, different team members have different perceptions of progress, based on skill level and experience. So one individual may be happy with the current sick system, because it's an improvement from their last shit show, while another will be fucking miserable because this is the tenth motherfucking shit show they've had to tap dance in, and the routine never fucking changes.

If you're looking for symptoms of cynicism after they happened, then it's too late. You don't understand how they happen, why they exist, or how to prevent them before they occur. If you can't prevent a loss of enthusiasm and morale, and expect all hands to express the same cordial cookie cutter productivity, then you are already lost at sea.

Re:How to spot symptoms of burnout on your engineering team by jrs235 on Friday April 14, 2017 @06:39AM (#14113652)
Speaking of BS meetings: http://amzn.to/2oeIpEs

Seriously. Good. Stuff.

"Where did This Book Come From?

I wrote this book because someone paid me to. But I also wrote it because I had a deadline. I began jotting down meeting tricks in the summer of 2007 while working for Yahoo!, as I observed them firsthand in meetings with Directors, VPs, Senior VPs, and Senior VP Directors. Seven years later I became a manager at Google and got invited to even more meetings than I ever had before. How did I achieve such an intense trajectory over the course of my luminous career? I went to meetings, and I looked damn smart in them."

I bought this book for my coffee table at home. It's worth the laughs. Sometimes my passive aggressive thoughts make me want to bring it into work and leave on my desk. Or my boss' desk. Or my boss' boss' desk.

Re:How to spot symptoms of burnout on your engineering team by tkaboutit on Friday April 14, 2017 @04:44AM (#14113320)
Agreed, except a slight visual-tweak I'm seeing on the tough guy manager is the 'servant-leader'. Somehow these 'servant-leader' action-item lists never spur any introspection within the manager-deity themselves. The servant-leader sounds like a great idea to managers who have enough self-awareness to have an inkling that they have no idea what they're doing aside from following "industry trends".

They read from the Book of Jobs every monday morning. "If thee bees have passion, they never work a day in their life. And we hiredest thee smartest to tell us what to do, not to tell them what to do." But the freedom and passion they're talking about is in deciding how many story points to attach to the minute tasks that have been pre-ordained for you to be passionate about. This is because we would have never hired you if you would not be passionate about the roadmap at all times. Leaders don't admit mistakes in the Book of Jobs, they first travel through the bloggosphere on their quest for validation that it's someone else's fault. If that does not work, they check if the naysayer can be replaced, preferably at a cheaper rate. If so, the naysayer will be sacrificed to the land of better opportunities to boost team morale.

This article is telling the story of an engineer who tried to collaborate and voice their concerns constructively to start, but found out it was all the meetings and listening was just an empty act on the part of their managers. Their managers kept cramming so much work into the release that quality suffered under the unrealistic expectations. Those same unrealistic expectations that were previously carefully regarded by the subordinate engineer as risks and concerns.

So the engineer realizes that to get something done, they have to do it themselves. They work longer hours to rearchitect and/or introduce some new tools to improve the pipeline, but the manager was unable to understand how this related to this sprint's burndown chart or the pre-ordained roadmap. And the only conclusion the manager is capable of, even after reading all the blogs they could find on the subject is: When there's a misunderstanding with "their" engineer, it was either a bad hire or even though "their" engineer speaks fluent C,C++,Go,Haskell and Scala, they just do not seem to understand pie-charts and maybe they need a 1v1 to talk about it. Yes, more meetings is what they need to get their work done. The engineer stopped trying to waste their time voicing anything in meetings.

Their rate of commits dropped because they were working on design work, aka thinking. But their manager literally treats the github commit graph as an indicator of the engineer's health vital signs. The manager believes themself very technologically advanced by not resorting to that barbaric practice of correlating LOC with an engineer's vital signs. Throughout the whole story, the manager never actually learned or changed one damn thing. *In the article, this same story is told through the perspective of a manager with their head quite far up their ass.

Anyways, what a bunch of back-patting patronizing bullshit. I feel truly sorry for anyone who has to work under this guy or anyone influenced by him.

Re:How to spot symptoms of burnout on your engineering team by jrs235 on Friday April 14, 2017 @06:51AM (#14113682)
Part of the issue is too many people, managers in particular, fail to realize that "manager" and "leader" aren't synonomous. Managers want to believe they are though! More than likely because charismatic narcissists tend to rise to the "top" ( https://hbr.org/2017/04/if-humble-people-make-the-best-leade... ).