Spoken like someone who knows absolutely nothing about vim/unix.

I’m sure it’s fine for small-scale usage, but overall it’s extremely inflexible and doesn’t really scale well at all. There’s also a lot of very basic functionality that’s straight up missing. For example, there’s no way to have a global epic priority. You can rearrange epics in an epic board, but the ordering of the epics there is not persisted elsewhere. There were many, many other shortcomings we kept running into.

Oh, and after a lot of our tickets had been imported (which itself was a huge undertaking since the auto import tools are complete trash), it started to be very slow. It feels like a very unfinished, unpolished product.

We use Gitlab’s CI/CD features extensively at my current job and it’s very, very nice. That’s what they are actually good at, not project management.

I also wonder if people complaining about Jira are still on Jira Server. Jira Cloud is a much nicer experience. Certainly not perfect, but I’ve yet to see an actual viable alternative (once worked someplace that tried to move all project management to Gitlab… 🤮).

Uh, there are an absolute fuckload of Java libs out there with nothing more than auto-generated garbage Javadocs.

I dunno, plenty of those sound pretty reasonable.

I’m a senior software engineer with a pretty uncommon skill set. Recruiters are the primary way that companies hire in my industry outside of networking contacts and I get contacted frequently. The job before my current one was through a recruiter.

I very much dislike Microsoft and LinkedIn in general, but not using it all is a huge handicap that isn’t worth taking on.

It’s how recruiters find me, so unfortunately I can’t. I almost never open it, though.

It’s speed, but it’s also flow and a continuous stream of thought. If all your editing is being done with muscle memory and minimal thought, you can continue thinking about the problem at hand rather than interrupting your thoughts process to fumble through some context menu to make a change.

All it means is if you were to reverse the order of the characters, you’d get the same string you started with. So “dog” isn’t a palindrome because when you reverse it, you get “god”. “dog god” is a palindrome, though, because if you read it backwards, it’s also “dog god”.

It’s not complicated at all: https://en.m.wikipedia.org/wiki/Palindrome. Not really something that’s education-specific, in this instance (though I suppose it’s commonly used in entry-level programming classes since it’s a simple concept).

Okay, but it is false to claim that she is a enthusiastic supporter without any evidence of said support.

How is Harris an enthusiastic supporter? https://www.aljazeera.com/program/newsfeed/2024/7/26/harris-says-she-wont-be-silent-on-gaza-after-netanyahu-meeting

Oh, if you worked at a company that uses them (which is a lot of companies), you’d definitely be familiar with them as they hog up a ton of fucking CPU/disk. I basically had an entire CPU core dedicated to running their bullshit.

After working at a company that had Crowdstrike installed on all machines, it is most certainly malware.

I’m not, really. They’re one of our largest operating expenses and we’re trying to work on reducing our log output to reduce the cost.

For what they do I’m not aware of any players in the space that come anywhere close, though.

Why in the ever-loving fuck would it do that? My hatred of Go only continues to grow.

It has the return type declared to be double.

That’s what the If-Match header is for. It prevents this problem.

That being said, I generally think PUTs are preferable to PATCHes for simplicity.

It’s about making APIs more flexible, permissive, and harder to misuse by clients. It’s a user-centric approach to API design. It’s not done to make it easier on backend. If anything, it can take extra effort by backend developers.

But you’d clearly prefer vitriol to civil discourse and have no interest in actually learning anything, so I think my time would be better spent elsewhere.

As I already said, it’s very simple with JSON Patch:

[
  { *op": "replace", "path": "/Name™, "value": "otherName"}
]

Good practice in API design is to permissively accept either undefined or null to represent optionality with same semantics (except when using JSON Merge Patch, but JSON Patch linked above should be preferred anyway).