

B5 was a show where a lot of character actors got main/recurring roles and really got the chance to shine.


B5 was a show where a lot of character actors got main/recurring roles and really got the chance to shine.

We use Azure DevOps at work… I felt every single word of this reply.
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?


Even the first season is pretty good by Trek standards!


Always seemed like more of an airport to me.
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.


I was a kid in this era, saw some of these episodes, and thought nothing of it.
After all, the Muppet Babies were doing Star Wars….


I can hear that album cover…
You are amazing, you beautiful lemmy stranger, you.


Because he’s the EEH!
The Emergency Engineering Hologram.


I agree… but I also think that applies to LOTS of other foods, particularly in the setting of a restaurant.


Yeah, that’s also my question. Partially because I am a former-lawyer-turned-software-developer… but, yeah. How are the kernel maintainers supposed to evaluate whether a particular PR contains non-GPL code?
Granted, this was potentially an issue before LLMs too, but nowhere near the scale it will be now.
(In the interests of full disclosure, my legal career had nothing to do with IP law or software licensing - I did public interest law).
You and me both. We will be the next version of the COBOL Cowboys.
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.


The Chief and MacGyver always seemed to have a lot in common. Get this man some duct tape, a paper clip, and some chewing gum!


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 may an overly cynical take, though that seems hard to do these days, but I’ve always believed they are intentionally vague… even to their customers.