This is what I always say. Put the tickets in order and we’ll do them.

Management always pushes back.

I am going to get a lot of use out of that URL.

I’ve been telling people they need to put a dollar in the jar when they do that, but I haven’t actually been enforcing it.

I understood that reference

I mostly work in Python, but we use types at work. For a hack day project I skipped typing stuff for like an hour, and then went “wait this sucks” and added types. It was easier overall.

Maybe it’s part of an elaborate vampire hunting scheme. It seems like something idiot PCs would do in a role playing game, and the protagonists of “What We Do In the Shadows” would fall for.

Kind of off topic but some people are really bad at writing jira tickets.

“Show the user a list of projects [eof]”

Ok but like, only their projects, right? Do they need to be ordered? Searchable? Paginated? Only active ones or soft deleted ones, too? Do you just need the name or do you need metadata too?

Somehow product doesn’t love my stance of “if it’s not on the ticket or in a sop, the behavior is undefined and you get what you get” stance.

401 is “I don’t know who you are. Get fucked”

403 is “I know who you are and you’re not allowed here. Get fucked”

I was a QA engineer. I think one of the guys on the team I was on developed a stress response from hearing me walk over to his desk.

Lots of “page crashes if the user doesn’t have a last name”

“Why wouldn’t they have a last name??”

“No idea, but 372 users in the DB don’t, and 20 of them were created this month so it’s not an old problem”

“incoherent muttering and cursing”

Mouselook, huh? More like Quake. :old man yells at cloud:

I don’t trust anyone not using semver.

A whole train of thought happened in my head here about transitioning and semver.

Because I didn’t want someone to yolo connect to production, and we don’t have infrastructure in place for running arbitrary scripts against production. An http endpoint takes very little time to write, and let’s you take advantage of ci/cd/test infrastructure that’s already in place.

This was for a larger more complicated change. Smaller ones can go in as regular data migrations in source control, but those still go through code review and get deployed to dev before going out.

I have several times insisted that a migration be done via an ad hoc endpoint, because I’m a jerk, but also it’s much easier then to test, and no one has to yolo connect directly to prod.

There’s that old saying ‘everyone has a development environment. Some people are lucky enough to have a separate production environment, too’

Remember when Facebook unethically ran experiments to see if they could make people sad? We should have hanged the board of directors then.