I am writing a blog post about why it is bad to use AI.
-
@paul_ipv6 @mcc @glyph I wouldn't put this sentence in the past tense, at least not for France, but things are indeed improving in most cities.
-
@glyph @FayeDrake @mcc @mhoye That makes sense. I guess another concern is the actually pairings and who works well together. Thank you for the response. Obvious though it is in one sense, the information sharing and community building part just… overshadow that in my imagining
@griotspeak @FayeDrake @mcc @mhoye indeed. in my own imagination too! the difficulty that Faye points out is real—if you try to force people, you get higher turnover and alienate a whole personality type (one that's common in tech and tbh kind of important to round out a team). but if you make it "optional" then you keep getting back to the default assumption that it is a "distraction" to pair with someone (or mob with the team) where only the "primary" gets credit for closing "their" tickets
-
@paul_ipv6 @mcc @glyph I wouldn't put this sentence in the past tense, at least not for France, but things are indeed improving in most cities.
-
@griotspeak @mcc @glyph @mhoye honestly, I love pair programming. I would pair most of the time and ditch asynchronous PRs if given the choice. And part of the issue with mobbing was just plain toxic management.
With pair programming the balance of dynamics is usually such that as long as you have two people working in good faith and a good culture you can usually work it out and be flexible enough for both parties. It’s also easier to pick and choose effective effective relationships.
My experience with extended (as opposed to occasional) mob programming is that it requires actual skills/training and either a specific set of personalities or a lead with strong emotional intelligence in order to bridge the gap. Mobbing is a lot harder to get right and if any team wants to try it for extended periods I whole heartedly recommend getting an experienced coach in.
@griotspeak @mcc @glyph @mhoye
In the job where this was an issue management refused to provide any of that. It was implemented badly, we went straight into chaos with no guidance. We had certain individuals with certain neurodivergent traits who, and as I say this I lay the fault at management and not these individuals, flourished at the expense of the rest of the team. Leadership refused to step in in order to make sure that everyone’s needs were met while still insisting on mobbing.
I can’t speak for the other individuals who got burned out.
-
@FayeDrake @mcc @glyph @mhoye What about mob programming burned folks out? I’ve always kinda wished mob programming or pair programming was more common than “go off somewhere and return with the PR” but it sounds like it didn’t have much upside where you were
@griotspeak @mcc @glyph @mhoye honestly, I love pair programming. I would pair most of the time and ditch asynchronous PRs if given the choice. And part of the issue with mobbing was just plain toxic management.
With pair programming the balance of dynamics is usually such that as long as you have two people working in good faith and a good culture you can usually work it out and be flexible enough for both parties. It’s also easier to pick and choose effective effective relationships.
My experience with extended (as opposed to occasional) mob programming is that it requires actual skills/training and either a specific set of personalities or a lead with strong emotional intelligence in order to bridge the gap. Mobbing is a lot harder to get right and if any team wants to try it for extended periods I whole heartedly recommend getting an experienced coach in.
-
@glyph When I think about "AI" I often think about how we had cities built to be navigated by people, and then we rebuilt the cities to be more easily navigated by cars, and now people without cars can't navigate the cities because we specifically designed them to require cars
RE: https://mastodon.social/@mcc/116314231162423866
@mcc @glyph this is an apt way to describe it, not even a metaphor. digital spaces are an extension of architecture, and the more we think that way the better we can understand the consequences of interface design
-
@griotspeak @FayeDrake @mcc @mhoye personally I used to be of the opinion "pairing is always good, you just gotta give it a try" and for a lot of people, even some who thought they wouldn't like it, I was right. but for a few people (who I have now long since made amends to) the growing expectation that they would do it all the time made them feel anxious about coming in to work.
I've never been anywhere that it really settled in to a final steady state that everyone was happy with.
@glyph @griotspeak @mcc @mhoye very much so.
Both mobbing and pairing require emotional intelligence, or at the very least leadership who can ensure that needs are met for everyone.
My personal experience is that mobbing requires exponentially more of both and in some cases just isn’t practical.
-
@griotspeak @FayeDrake @mcc @mhoye indeed. in my own imagination too! the difficulty that Faye points out is real—if you try to force people, you get higher turnover and alienate a whole personality type (one that's common in tech and tbh kind of important to round out a team). but if you make it "optional" then you keep getting back to the default assumption that it is a "distraction" to pair with someone (or mob with the team) where only the "primary" gets credit for closing "their" tickets
@glyph @griotspeak @mcc @mhoye with the “optional” part, at least in pairing, a big part of that is culture.
There’s a shift to be made in a team from “a group of individual contributors” to “we all sink or swim together, and it’s the job of the experienced members to lift up their juniors”.
This is, and again I speak from experience, a very difficult shift. But it makes a massive difference to both morale and productivity.
I’m lucky to work in a team where the senior staff are all of that mindset and we’re able to propagate it to anyone who joins. Honestly, it’s the only reason I’m still here.
But again, you need a bunch of powerful and emotionally intelligent people to set that baseline. And that’s… not guaranteed in engineering teams.
-
@griotspeak @FayeDrake @glyph @mhoye Is mob programming the one with random encounters
@mcc @griotspeak @FayeDrake @glyph I think it's the one where it's a real nice codebase you've got there and it'd be a shame if anything happened to it.
-
I am writing a blog post about why it is bad to use AI. It is extremely heavily sourced. I have a tedious automation problem formatting my citations. No problem, I think. I will write a computer program. The computer program does not work, because websites are blocking simple computer programs in an effort to block AI. Solution? Simple. Browser comes with AI embedded, browses like a human, has all my cookies. Just ask the AI. It sails through the primitive anti-AI measures easily.
@glyph *hiss*
-
E em0nm4stodon@infosec.exchange shared this topic
