It’s these terrible single washer/dryer combos that are the cause of this pain. I can only assume their popularity is because they are small and cheap.

It may be the one thing America gets right - overwhelming people have larger washer / dryers with dedicated washing and drying sections. Takes up more space and I’m assuming requires hookups that aren’t common elsewhere, but man, they are SO much faster and far more effective. You can be done with all your laundry in a couple hours tops - and I’m talking like 1-2 weeks of laundry all at one time.

Meanwhile we have one of these, and I feel like we’re doing small loads of wash the entire week. And don’t even bother with the dryer setting on it - for 90% of items, you’re just spending 6 hours raising your electricity bill.

/rant

It obviously depends on your exact git workflow, but my last team had things setup so that the code content of a MR was automatically squashed on merge, and the text if the MR itself was automatically set as the content of the new singular git commit.

This was largely the best of both worlds because your commits could have almost any text, and the description of what changed could be updated as needed when making the MR. But it ultimately ended up in the git history where it belonged.

Of course, I still had some trouble trying to get the team to describe their changes well in the MR at times - but that’s a different problem entirely.

Bleh, maybe I’m an old man, but when I’m searching stackoverflow, I find the context of stack overflow answers really helpful.

I.E. the top result may include caveats itself or have comments indicating why an answer might be problematic. And sometimes the best answer isn’t even the top answer. I’ve not used AI code assistance very much, but these all seem like things that the model is likely to take for granted.

But I also never contribute to stackoverflow, and agree I’d much rather engage with with an AI than do THAT.

I had a similar situation where a fence of this style was placed directly next to a bike path. At walking height, it would have been hard to land on, but on a bike at speed? It would have been way too easy to be impaled, and it was terrifying.

Another solution to this situation is to squash your changes in place so that your branch is just 1 commit, and then do the rebase against your master branch or equivalent.

Works great if you’re willing to lose the commit history on your branch, which obviously isn’t always the case.

I ran into this exact situation at work - though for me it was more the case that getting approvals for new software / installing new dependencies in our system is a massive pain.

So I went with Python since it’s already installed on basically any Linux system. It was fine - I mean Python is a good language and can certainly handle string processing and data manipulation with relative ease.

I still think the Python docs are pretty bad, and I wasn’t thrilled with the options for calling a subprocess in Python - they all felt kinda clunky, though I was barred from using the newest versions since I had to run an older version of Python.

But I ultimately got something that worked and it was certainly better executed / shorter than the bash equivalent it was replacing.