I got a PIP because my manager mistakenly thought I was stealing equipment, and he just kept adding agile story points until I failed.

I was too pissed off to go to an ombudsman. It honestly didn’t occur to me. It just felt like “this guy hates me and wants me out.”

He called me two years after I was fired to inquire about missing equipment that I never had.

You made the mistake of allowing PIP to be invoked on you for a fake reason given by your manager, and you made the even more serious mistake of getting fired because you "stole equipment".

If you were innocent of that dangerous charge, you should have fought hard against it, and ensured the top management, HR head and Ombudsman became involved in the investigation.

Being fired for theft or such serious crimes, can and will leave a permanent black mark on your employment record with the HR, and it may get pulled up during BGV (Background Verification) invoked by a prospective employer evaluating your candidacy for hire, thus seriously affecting your career and life.

I think you should now reach out to that company HR and clear the conspiracy and black mark against you. Perhaps, you can hire a lawyer who deals with employment matters, so he or she can legally get the matter resolved in your favour.

Never thought of it this way; isn’t it always safe to assume env is in PATH?

Maybe `#! env <shell>` could be considered a DSL for hashbangs. My reasoning is that `/usr/bin/env` is the thing that seems to be hard-coded to a system path, in most cases.

Some environments (like containers) have no, or extremely incomplete PATHs.

I think POSIX requires env but doesn't mandate a location for it.

This has always been the hardest problem in computer science besides “Assume a lightweight J2EE distribution…”

This is annoying. It’s because errors were designed to be a bitset and not have pointers. I would also prefer that they were a `union(enum)`.

We are free to do that as a return type like `Result(T)` and just forgo using `try`, but yeah, I wish this was in there.

This is the most surprising comment to me. It’s that bad? I haven’t benchmarked it myself.

Zig has @Vector. This is a builtin, so it gets resolved at comptime. Is the problem with Rust here too much abstraction?

I think you misinterpreted GP; he's saying that with some hints (explicit chunking with a branch on the chunk size), the compiler's auto-vectorization can handle the rest, inferring SIMD instructions in a manner that's 'good enough'.

Meme versioning could work. Memes are temporal.

You can derive a lot of information about my age and current version from the dad-joke version string “I thought it was 6 7 when 7 8 9”

You might have to skip 9 to avoid faulty version checks

I don’t think it’s nostalgia, skillful hand drawings are just nice.

It's uncluttered and purposeful.

Yeah but can it run doom

Actually, very nearly so: https://typst.app/universe/package/soviet-matrix/

I am so mad that I spent that much time watching an anthropomorphized bill moving through congress. Useless knowledge.

“And we’ll make ted kennedy payyyy

“If he fights back, we’ll just say that he’s gayyyy

I talked like that before this happened, and now I just feel like my diction has been maligned :p

I think it’s because I was a pretty sheltered kid who got A’s in AP english. The style we’re calling “obviously AI” is most like William Faulkner and other turn-of-the-20th-century writing, that bloggers and texters stopped using.

IDK all the breathless "it's not just X, it's Y --" reminds me of press releases

Yeah it was trained on bullshit more than Faulkner for sure. +1 you.