Mystery solved!

That is indeed a big one!

Look, an alert is an alert…

Look at all the pretty green check marks!

Can someone, anyone, tell me where it is that you work where input speed is the bottleneck in software development?

Because I have genuinely never worked at any company where the main thing holding up development was that developers weren’t typing fast enough.

Yep, same here. I went to MX after starting with Ubuntu. Now I’m a Debian guy.

Go on…

I’m a simple man. I see Debian, I upvote.

Is that Xfce?

Slowly reaches for shotgun…

Well, I do wear a lot of hoodies…. But that’s more because I live in the PNW than the fact that I’m a programmer.

I also have the sleeves pushed up to my elbows most of the time. Only wear sunglasses when I’m driving and the sun is in my face.

I really enjoyed Avowed. Played all the way through it. Sure, it’s not as open as a Bethesda game - it takes place in large zones. But it was a lot of fun and I enjoyed the story.

So, it looks like Bluefin used to do some PATH gymnastics to keep things working pretty smoothly.

But now, they just make sure that brew is last in the PATH. This prioritizes the CLI commands baked into the image.

Thanks for the info, I really appreciate it!

So far, I will say that I haven’t run into any issues but it’s interesting to learn about some of the pitfalls/limitations too.

It’s all about trade offs, I guess!

I have also been a Bluefin user for a while now…

Could you say more about the PATH issues with brew? Or point me to where I can learn more about them? I was kind of enjoying brew for installing development tools, and was thinking about adopting it on my non-atomic machines too. Should I not do that?

I am parent of two elementary school aged children. I have just lived through the “6 7” era.

I will regard “let’s go” as a blissful respite.

You are amazing, you beautiful lemmy stranger, you.

Honestly, in DevOpS, when you’re running stuff in a GitHub Action/Azure DevOps Pipeline/Jenkins, yeah… sometimes a run will fail for no obvious reason.

And then work the next time (and the next 100+ times after that) when you haven’t changed a damn thing.

You got me!

Thank you for saying that about the documentation.

I work in an Azure shop and I’m in charge of our infrastructure… sometimes I feel like, surely I am an idiot… I must be incompetent to not understand something in some Azure service…

But no, the imposter syndrome spike that Azure sometimes triggers in me is NOT actually me being deficient in some way. Their documentation is truly awful. And often the solution to the problem is found by asking myself, “What is the dumbest way Microsoft could have implemented this thing?” And that turns out to be right!

Thank you for confirming that I have not completely lost my mind and it’s not just me.

This is an example of the old adage that “When you use a regex to solve a problem, you end up with two problems.”