(If there's going to be something making the bubble burst, it might just be corpos realizing they're paying super expensive licenses for something that makes people worse at their job)

The worst part is that there's been a couple studies proving that doing a job with AI gradually makes you worse at it (because you get less and less practice as you let the AI do most of the work).

One of the things that DOES get covered is that making things look "too digital" makes people not trust the machines, so they use curved screens to imply they have physical reels.

And heck, the skeumorphism + pretty animation probably releases more dopamine than just showing you the random number.

Pretty much assumed so, but glad to have the confirmation! ^__^

I've gotten a primer from this video essay series on the historical ties between video games and gambling, it doesn't go super deeply into detail but brings up a lot of the tech and psychology.
www.youtube.com/watch?v=jQIH...

It wasn't AI, this was a couple years ago (before Copilot launched) and we were working with a legacy codebase that was even older (new version of the device launching on better hardware, reusing the same codebase). So SOMEHOW, it had all been written by a human with a software engineering degree.

EVERY SINGLE LINE in the codebase had a comment that described, on face level, what that line did. (Which you could already see by reading that line directly). No purpose, no explanation, no added information. It drove me insane.

The thing I absolutely despise the most is when the code goes

//add 5 to x
x += 5

I've seen a real codebase that did this, and the comment + extra newline on every "real" line resulted in the information density of the entire codebase now being reduced to one third of what it could've been...

"Documenting a case" for a programmer would be more like, updating a Jira ticket with comments on what you've done and why. Documenting code is a different field entirely (and things like sane naming, using whitespace to break unrelated things up etc go a long way to reduce the need for it)

The bottom one has some major kerning issues (spacing between letters LOOKS different sized) so I'd also say the middle looks the best. But IMO, it could be even better. Right now it's clearly just regular text, moving the letters around a bit to be less uniform makes the logo look more memorable:

(also IMO, a programmer WANTING documentation [as a separate document] is already a warning flag, if you don't store the information together with the code it WILL get out of date and/or end up in some web service with a bad search function so nobody can find it, turning it into a waste of time)

I wish we'd stop equating "X years of experience" with some sort of skill level, there's so many people just coasting by on seniority... every place I've worked at that's been SANE has at least done some sort of practical challenge to actually measure skill during/before the interviews

Stuff like using C++'s function operator instead of the constructor (code calling it looks identical, but you don't find the definition where you'd expect) and having an insane number of redirects, from program start to first line of code that DID something was 22 levels of abstraction.

That's the worst! I've seen some code that was so intentionally convoluted that it really felt like whoever made it was trying to make himself un-fireable (it landed on my table after he WAS fired, ironically)

It was the first western isekai, so it got the entire market due to lack of competition. And now all the fans from back then have developed nostalgia since they grew up with it.

"Cognitive Debt" is an excellent term, I'll definitely be using it next time I'm trying to convince people why AI is a bad idea~

I don't trust documentation, period. "The code is the documentation", and getting good at searching is key.

This incantation will grant you knowledge beyond your wildest nightmares...

As far as I know there's no established term for this yet. "Harmony" is the actual opposite of "dissonance", but "resonance" definitely SOUNDS better (and makes it more clear it's related to the established term it's opposing). "Alignment" or "consonance" could work but also don't sound as good...

(As a general rule I try to place enemies so they're in the way as much as possible but can always be avoided without harming them, you're expected to get past most encounters by fighting but should never be FORCED to. And of course, fighting slows you down and this is also a game about going fast)