magic_lobster_party

I consider Dell’s naming scheme of their monitors the gold standard. It’s short, descriptive and easy to remember.

I got a U2720Q myself, and I know I got it because I know what size it is and when I bought it. I also got another monitor that’s seemingly just a random series of numbers. I can’t remember a single digit of that one.

I don’t hate AI art. I hate people who pretend they’re artists when all they do is writing prompts.

”All features are xy problems”

”PM adds new features to the sprint faster than they’re solved”

”Each release require two weeks of testing”

”Each release introduces new bugs for customers despite the two weeks of testing”

Because it’s sensational that so incompetent people are in charge.

It’s the magic word that makes any story seem more significant than it really is.

From a maintainability point of view consistency is important. I’d rather work with an consistent but incorrect code, than correct bit inconsistent code. With a consistent code base it’s easier to do something about the incorrectness, especially if it’s consistently incorrect. It’s also easier to delegate the work.

Code is rarely correct forever. Sooner or later, requirements will change. What once was thought to be correct is no longer correct. It’s difficult to do anything about it if the code is inconsistent as well. It requires a lot of mental effort to understand the thought process behind some code.

I agree that correctness is the goal, but consistency is one of the best ways to ensure this goal.

One thing that isn’t mentioned regarding consistency is that it makes the code more searchable. When you start on a new issue you can easily find where you should do your work. You’ve maybe never seen this part of the code before, but you know how to find it.

This is impossible with a largely inconsistent code base. Anytime you start with a new issue you have to find a needle in the haystack.

I wanted something silly and something completely unattached to who I am. Maybe I went a bit too silly.

They will resort to vibe debugging

Or the EA Sports games: same game but with a different number on the box art.

That’s not a mutually exclusive or

How many open source projects have 2000 concurrent contributors working full time on it?

As John Green put it: we can no longer say that the deaths of tuberculosis are caused by a bacteria. The deaths of tuberculosis are caused by human choice. We have the choice to live in a world where millions don’t die by this treatable disease, but we chose not to.

I’m eagerly waiting for his upcoming book about this terrible disease.

then it’s a DEI hire

”DEI hire” (and ”woke” for that matter) is used as some form of a right wing code word. They point at thing they don’t like and explain it’s because of [insert code word here]. Repeat it enough many times, and you get the impression there’s a pattern.

”Politically correct” served the same purpose before (until it somehow went out of fashion).

I guess it can be a fun hobby project to learn Rust

That’s what we use in my company: a series of mini waterfalls

Waterfall only works if the programmer knows what the client needs. Usually it goes like:

• Client has a need
• Client describes what they think they need to a salesperson
• Salesperson describes to the product manager what an amazing deal they just made
• Product manager panics and tries to quickly specify the product they think sales just sold
• Developers write the program they think product manager is describing
• The program doesn’t think. It just does whatever buggy mess the programmer just wrote
• The client is disappointed, because the program doesn’t solve their needs

They’re overlapping concepts, and can be used interchangeably. Sometimes a library can be all of them at the same time. In simple terms:

• API is the interface to the library.
• Library is code that is shared.
• Package is how it’s distributed.
• Framework is the methodology the library is used.

Not all APIs are libraries. For example, all websites have some interface to interact with them. A website is not a library.

Not all libraries are packages. A library don’t need to be distributed through a package manager.

Framework is a bit blurry where the line is drawn. I think if the library is used in such way that your entire program revolves around it, then it’s a framework. If you’re just using it a handful of times, then it’s not a framework.

React and Angular are frameworks in this regard. If you use them, then your entire programming is revolving around them. Any decision made is in regard to these frameworks.

I would say OpenGL is API, library and framework. Maybe also package depending on how it’s distributed.

He love the uneducated

Maybe I’m nostalgic, but I think Pokémon graphics peaked with the Gold and Silver generation. They really nailed the color palette in that one.