There are two replies to the parent comment.
One saying that neo pronouns barely exist, and they’re imagining a person who would be angry at it.
The other comment is basically asking for a fight with their Xe preferred pronoun friend.
I just thought the contrast and dichotomy of that was noteworthy.
Tom Scott’s video is about to do the rounds again then
Was watching a YouTuber play Week One, and he was two floors down in a basement. A plane crashed into the building and all his stuff burned anyway. Then the nukes dropped. Total madness.
Reading it in the early 00s it made me wish I lived somewhere far more interesting with far more wild classmates.
All the rules and restrictions were so internalised, I think if we were abandoned on an island half of them would just sit still and starve.
I can’t imagine any of them being interesting enough to try to start their own religious cult or anything.
And the discussion on whether or not to pin versions.
Pinned, these packages work together, but don’t automatically pull in security updates.
Don’t pin, things randomly change on each build, best of luck debugging things.
Only the very junior ones who are writing code without understanding why they’ve been asked to write it. Anyone with more than about 18 months experience will be able to start deciding what to actually build, and I haven’t seen LLMs be particularly helpful with that yet.
The word “crawdad” will always remind me of this comic
Exactly. I got a drive by downvote which is a shame. Some people are in a situation where they’re happy to take a risk, and know that if it fails they won’t be destitute, and sometimes you might be paid more to account for the risk. Or less, but you get stock options to account for the risk. They’re all valid options as long as you’re not forced into it.
Someone else wrote some code, and he reviewed it and approved it, and merged it into the codebase.
Not sure why this is downvoted. It’s a lifestyle choice that is a genuine choice. You don’t have to live in SF if it’s not for you.
7 times is a common point at which the remaining radioactivity is considered enough halves
Finally, thanks I’ve been trying to remember the name of this for ages
I’m not sure there is a correct way to do this
I have the opposite issue with helm charts, where true and false are very, very loosely defined.
This is why I ask for the schema at the same time as asking for (even example) data at the start of a project. Don’t tell me you have the data, give me proof there’s a standardized structure, or the length of the project just tripled.
The fix might be 5 mins. Figuring out wtf was wrong in the first place is the time consuming bit. Especially if the report doesn’t contain a repeatable process to trigger the error condition.
Put it in the backlog and we’ll prioritise it in the next sprint planning. Except we’ve already got a good idea of what’s going in to the next sprint, so we’ll probably get to it in a month. Or two. End of the year tops. Bring it up in the quarterly planning if we haven’t finished it yet, and maybe we can squeeze it in before Q2. Unless the win the ACME project in which case all hands will be on that, so actually plan for it to be in production by Xmas. No, the one after that.
Thanks. Nice username, mine is also a reference.
I mean seriously, how have you not had chance to watch SG1 yet?