211–216 of 216 posts
All we will find in this thread is a bunch of remote workers trying as hard as they can to dismiss any finding that remote work might have downsides. Those damn managers only caring about butts in seats!
And a bunch of other people trying their hardest to justify stuffy office space and life sucking commutes. Oh but what about the socializing! It's so hard!
Next paper from these guys will say: "the shift from an open office plan to private offices caused work to become more siloed. Previous research shows this may impede the flow of information through the network" People need to stop fetishizing "breaking down silos" and "serendipitous hallway encounters" and all that nonsense and think about the big picture. You're more likely to have something worth saying, and a wor…
I can't tell you the number of times I've had arguments about what the point of unit test coverage is. The goal is not 100% coverage. The goal is to look at a green report and say, "I'm pretty sure this will work if you ship it." To trust the code. Yours, and everyone else's. To feel safe in making changes, or absorbing them. And for that to be useful, that report needs to arrive sooner and more reliably than another path I could use to arrive at the same conclusion. And that is why E2E tests are such a problem - they can take over 2 orders of magnitude as long to run as the unit tests, and still be wrong.
Earlier quoted context omitted.
> The key thing is here: > > over the first six months of 2020 This also implies that most of the employees already knew each other and worked together before being forced into remote work. One of the biggest problems with switching to remote work is that people carry over the in-person relationships they were already comfortable with. It's the new hires who suffer most, in my experience. When everyone else has month…
So true. I’ve personally experienced this with starting a new job in January 2020 and subsequently working on 3 teams. Team 1: 3 engineers of various tenure already on the team. Built good relationship with 2 before pandemic put us in WFH about 6 weeks in. I still talk to both of these engineers on a regular basis, even though we no longer work together. Team 2: Changed about 8 months in due to a reorg. Working with…
Two issues jump out at me: 1 ) It’s unclear to me why Microsoft, a leading software firm with distributed offices, should be considered representative of “information workers”. Contrary to this study of a digitally inter-connected firm, finding their preferred connection patterns and rhythms took a hit before adapting (see #2 below), most enterprises had no established digital connection patterns or rhythms and despi…
Many of us and some of your managers will recognize the Satir curve as the 'J-curve'. In fact the guy who introduced this concept to me did not allow that he'd heard of Satir. I'm slightly curious to ask him if he did but we haven't talked in a while.
Earlier quoted context omitted.
So true. I’ve personally experienced this with starting a new job in January 2020 and subsequently working on 3 teams. Team 1: 3 engineers of various tenure already on the team. Built good relationship with 2 before pandemic put us in WFH about 6 weeks in. I still talk to both of these engineers on a regular basis, even though we no longer work together. Team 2: Changed about 8 months in due to a reorg. Working with…
As someone who manages people for a living, the problems on Team 2 were entirely your manager’s fault.
I did not escape without a bad review. Somebody had to take the blame when things didn't work out. That was also some textbook bad management: my poor performance was first described in the meeting where the review was delivered. Never once in all the 1-on-1s we'd had. Skip said there was nothing that could be done because all that mattered was that I did not deliver compared to my peers.
My manager moved teams then left the company not too long after as well. I'll never really know what happened, but I assume they got a poor review themselves.
Earlier quoted context omitted.
At Spriggy we had senior developers enrolled into Intercom chat. This takes agile to a whole another level. I knew with certainty what we had to get done. It was not a jira ticket close but 100s of customers to help. Stressful, yes, but getting real problems solved, double yes.
Do you think that can scale to only half the real problems solved, but zero stress?