magic_lobster_party

Usually the most straightforward solution is good enough. And when you want to improve the performance, it’s rarely about time complexity.

The point about the Bechdel test is that it’s such an incredibly low bar, and yet most fiction fail at it.

Haven’t properly watched the videos, but I don’t think OOP is that bad. I even think encapsulation is one of the core strengths of OOP.

I’ve worked with systems where no thought was put into encapsulation, and those are often incredibly difficult to work with because everything is heavily interconnected. Can’t make a change in a small thing without risking breaking something else at the other side of the program.

I like to see encapsulation as a workspace. It defines the tools we have direct access to. Changing one thing in a workspace shouldn’t affect anything on the other side of the program. Makes it much easier to collaborate in large teams. Minimizes the risk of interfering each other’s work.

I think applying design patterns blindly without understanding what problems they’re supposed to solve is often more harmful than not using them. It can lead to difficult to manage code bases because the program is over engineered for problems that don’t exist.

My general rule of thumb is to write code that can be easily adapted to unexpected changes in requirements. Avoid writing code that paints yourself into a corner. Simple solutions are often easier to work with than complex solutions. If what you’re doing adds a lot of complexity, take a step back and seek other options. Maybe you’re overlooking an obviously simple solution to the problem?

I think inheritance almost always has this “painting yourself into the corner” tendency. Once the design is set, it’s often difficult to break free from it. Composition along with interfaces is generally the better choice. Often not even interfaces are needed.

This comes with experience. You learn what works, and what doesn’t. Often you do it the hard way.

Databases are tricky. I have no good advice for that.

I will have a heart attack if I can feel ur anus in my pocket.

Even if a fix was discovered quickly it wouldn’t prevent the problem that it must be manually fixed on each computer. In this case a fix was discovered quickly even without access to source code.

Just having more eyes on the source code won’t do much. To discover errors like these the program must be properly tested on actual devices. This part obviously went wrong on Crowdstrike’s side. Making the code open source won’t necessarily fix this. People aren’t going to voluntarily try every cutting edge patch on their devices before it goes live.

I also doubt any of the forks would get much traction. IT departments aren’t going to jump to the next random fork, especially when the code has kernel access. If we can’t trust Crowdstrike, how can we trust new randos?

I doubt it. Few people are volunteering their time reading pull requests of random repos. It probably went fast from pull request to deployment, so there would be no time for anyone external to read.

The only thing open source would’ve done is to give us a faster explanation of why it happened after the fact.

Yes, I’ve seen this resume before.

I think it’s ironic. The guy is quite influential in his field, so he doesn’t really need a resume.

They want to make stuff that look good in the quarterly earnings report. They want to show they’re fully committed to AI in all their products or whatever.

They don’t want satisfied customers. They want satisfied investors.

Chrome has fuckton more of Google telemetry, so it evens out.

If the cops are reasonable they would initiate an escort.

Given they’re reasonable that is.

The only thing stopping a bad driver with a fast car is a good driver with a fast car!

Especially SUVs. They’re death machines even at normal speeds.

Only a Sith would deal in absolutes. Same goes in programming. Microservices have their benefits . So do monoliths. Neither is going away in the foreseeable future.

Safest bet is probably to do monoliths first. Use microservices once it makes sense.

I think the reason why people complain about politics is:

• They want to find an easy scapegoat. They didn’t like the movie, and it’s easy to blame one aspect when the actual reason is far more complicated. It’s like how people think Jar Jar Binks ruined Episode 1 when he was just one small part of the movie.
• Politics can often be badly implemented in movies. Not all politics are black and white where there are obvious good and bad sides. The characters of Princess Mononoke, while it’s clearly on the environmentalist side, shares multiple perspectives on the conflict.
• It’s easier to notice something when it’s bad, so people tend to notice the politics when it’s bad.

One of my first Ghibli movies and also my favorite. Saw it first time on an anime showing at a local cinema. Such a great adventure epic.

A few potential obstacles:

1. Use of proprietary third party libraries. Havok seems to cost money for example. I’m not sure how Havok would work out in an open source model, but there are probably many other third party libraries that would stand in the way as well.
2. Distribution of assets. The game is not much without its assets, and many of the assets can be third party. For example Quixel Megascans. Even old games like Super Mario 64 heavily used third party textures and sounds. Not sure how they would like their assets be distributed freely.
3. Music. If the game uses licensed music this is a no go. It’s even difficult for companies themselves to release their old games with their original music.

Difficult to punch coworkers in their face in zoom

Is it going in the theaters?

Refactoring for the sake of refactoring is rarely a good thing. It should be done with a clear purpose in mind.