I usually squash my local into a single commit, then rebase it onto the head of main. Tends to be simpler

I’ve never had a complaint about logging stuff in python. It generally does what I expect.

“Create a copy of your object and print that” is what I ended up doing, but I don’t think most people would say that’s intuitive. I expect if i print something at a particular time, I get what it is at that point in time.

Some languages are just worse to work with. like JavaScript. Console.log is like sure I’ll log your object but I’ll tell you what it is now, not what it was when you logged it.

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’

Yeah JavaScript is a horrible language and ecosystem in a lot of ways, but package.json and friends don’t really give me much trouble.

And even if you hose something, you should be able to clear it out and reinstall easily.

I’m assuming the maintainer didn’t (knowingly) make a breaking change in a minor/patch release. That’s a high crime.

The correct initiative would have been to make a coding standard and get buy-in, not yolo unilaterally enforce your own idiosyncrasies.

We have one of those situations at work. We’re a small team, but one guy is kind of unilateral in his work style. He added a bunch of “interfaces” and “domain” modules in our python Django app. His idea seems to be like instead of doing Project.object.get(id=1) with the standard Django library, you’d do like import project_interface; project_interface.get_project(id=1). The “interface” then does some home grown stuff, and probably delegates to the Django library eventually. All of which to me seems unnecessary, “yo dawg” redundant, and error prone.

Also in some places he’s returning like a dict instead of query set or other Django object, which is going to cause problems later.

All of those specifics aside, because I’m sure he has reasons for all of this, but it’s annoying that he’s been doing it unilaterally. Worse, he had a project proposal to make the entire codebase like this and it was shot down. And every time it comes up in code reviews he’s like “well, I think this is good and we don’t have a standard saying otherwise”.

I started really putting my foot down in places I have clear code ownership, but it still turns into like 30 comment exchanges on the pr.

He also has his own import sorting. Which could be fine except he never shared it or put it in the ci pipeline. So no one agreed to sort and comment imports like this, it’s only in files he touched, and when other people change imports the comments become lies.

We have a standards meeting next week and I am not looking forward to it. We’ve been friendly for years and worked together before, but somehow at this job it’s just not a smooth time.

I was mildly annoyed the other day when someone moved a works-fine function and reimplemented it with dropwhile. This apparently was a divisive idea.

Me: it worked fine. Don’t reimplement it for no gains. Don’t send people to somewhat esoteric parts of the standard library. No one on this team is going to know how that function works off the top of their head.

Them: it’s in the standard library it’s fair game. It still works.

I mean, sure, it’s not good if they did sketchy stuff to bootstrap their network. I hadn’t heard there before but I wouldn’t be surprised.

But I don’t think it’s really the same as Yelp. Or at least not how I use it. Trust isn’t really a factor. I don’t use LinkedIn to review a company. I don’t look at their soulless posts about how great their team is. I use it to see “do I know anyone who works at this place that has an opening I want?” Then when I see my old friend is a manager there, I shoot him a message (possibly not even via LinkedIn if it’s someone I know well) and ask if it’s someplace I would want to work at. There’s not really a lot of room for fake in that process.

Also sometimes recruiters just message me. Some of them suck but that’s not really particular to LinkedIn.

You’re not thinking of Glassdoor, are you? Because that’s more like yelp and I don’t especially trust the positive reviews on there.

I don’t really want to go to bat for Microsoft though. I’d be happier if there was a better professional network out there. But, you know, capitalist hellscape.