Don’t forget the child labor aspect. https://www.theguardian.com/games/2022/jan/09/the-trouble-with-roblox-the-video-game-empire-built-on-child-labour

Last time I checked it out there was a lot of racist spam. It seems better now. Maybe it was one bad actor or the spam filter is better.

They keep saying that but those Bitcoins are still in the dump. (I’m aware it’s not comparable since having the drive in hand versus missing is a huge difference. Just a little joke.)

The more insane, unlikely, and catastrophic the error, the more appropriate an insane, terse, apocalyptic error message is.

git pull
# you see bullshit
git reset --hard HEAD@{1}
git push --force

Solved! Tell your coworker to make their own branch!

Honestly, yeah. I mean, not the best but I definitely am more in favor of comments being a commentary than explaining what’s happening. Explaining why is better than what, but in general, comments where anything absolutely bonkers is happening are useful. Bare minimum, I think some sort of acknowledgement that the person writing the code also recognized their code was weird (necessarily or not) is nice.

Did either of those do banker’s rounding?

This reminds me of a time at work when we got sued. The company was allegedly using (or had copies) of some tool we couldn’t have anymore. Annoying, but fine. However, to check this, they scanned all of our computers for the name of that company. They told us all to delete our entire local Maven repository. Someone who worked there was on the commiter list for a couple of open source projects. I just manually deleted those files because I knew for a fact that our central Maven repository didn’t have some of the versions of our own code on it and I wasn’t confident we wouldn’t need them again. Turns out I was right and needed to grab one later on to upload. Because I manually deleted the files with the company’s name instead of just deleting everything, the scanner thing they were running didn’t detect offending files. (Not that a file listing someone’s email address as a commiter to an open source project should be offending, but still.)

It was a Java project and every class was in a separate Maven module.

Today I got told in a meeting by my manager that he’s being told we all have to use AI at every stage of the development process. I mentioned that, as a contractor, they don’t allow me to use these tools, and if they could give me access. Nope. I hate this. It’s all such bullshit.

This is my wife too lol, every time we’re in the car we’re playing them on repeat.

No, only top level comments specifically.

One thing I see a lot of instance specific meta communities that only allow top level comments from users if that instance. Auto removing those form other instances would be useful.

No, it’s impossible. The tech just isn’t there yet. We need AGI to be able to detect a string.

I can’t believe they fumbled their reputation so bad lol

You’ve been able to mock concrete classes in Java for like a decade or so, probably longer. As long as I can remember at least. Using Mockito it’s super easy.

I’m making a separate comment for this, but people saying “Liskov substitution principle” instead of “Behavioral subtyping” generally seem more interested in finding a set of rules to follow rather than exploring what makes those rules useful. (Context, the L in solid is “Liskov substitution principle.”) Barbra Liskov herself has said that the proper name for it would be behavioral subtyping.

In an interview in 2016, Liskov herself explains that what she presented in her keynote address was an “informal rule”, that Jeannette Wing later proposed that they “try to figure out precisely what this means”, which led to their joint publication [A behavioral notion of subtyping], and indeed that “technically, it’s called behavioral subtyping”.[5] During the interview, she does not use substitution terminology to discuss the concepts.

You can watch the video interview here. It’s less than five minutes. https://youtu.be/-Z-17h3jG0A

YAGNI ("you aren’t/ain’t gonna need it) is my response to making an interface for every single class. If and when we need one, we can extract an interface out. An exception to this is if I’m writing code that another team will use (as opposed to a web API) but like 99% of code I write only my team ever uses and doesn’t have any down stream dependencies.

Fork repo, make local changes intending to push to fork for PR, never push anything. Very common.

Also, SO MANY SITES have the button that says “Fork me on GitHub!” that is often wonder if people think it’s something that it isn’t.

“Oh, the deep dream stuff? Yeah, those look so trippy. What do you mean poop though? Usually it’s just dogs.”