For NASA, data types don’t matter when you’re programming Voyager 1 and 45 years later it gets hit by an energy burst causing 3% of the RAM to become unusable, and it’s transmitting gibberish. It’s awesome they were able to recover it.

This still isn’t specific enough to specify exactly what the computer will do. There are an infinite number of python programs that could print Hello World in the terminal.

You can send 4xx errors yourself too. If the client needs to change something about the request, that’s a 4xx, like 400 Bad Request. If the server has an error and it’s not the client’s fault, that’s a 5xx like 502 Bad Gateway.

The wikipedia listing of all HTTP codes is quite helpful. People also forget you can send a custom response body with a 4xx or 5xx error. So you can still make a custom JSON error message.

If those vibe coders knew what a binary tree was, they’d be very upset.

Is that even a thing on lemmy? Or are you thinking it’s just force of habit?

But then they’d have a dev team who wrote the code and therefore knows how it works.

In this case, the hackers might understand the code better than the “author” because they’ve been working in it longer.

Imo if they can’t max out their harddrive for at least 24 hours without it breaking, their computer was already broken. They just didn’t know it yet.

Any reasonable SSD would just throttle if it was getting too hot, and I’ve never heard of a HDD overheating on its own, only if there’s some external heat sources, like running it in a 60°C room

May I present to you: https://github.com/mame/quine-relay

Now print “¯\_(ツ)_/¯” with the quotes

Wanderstop

Ooh, I’ll have to check that out. I loved The Stanley Parable and Beginner’s Guide

I adopted this philosophy a few years ago and have bought maybe 2 games since. I played them immediately and had fun. Meanwhile I have no interest in playing my backlog games anymore. I don’t have time for them.

They mean time to write the code, not compile time. Let’s be honest, the AI will write it in Python or Javascript anyway

I always thought T&& made sense as a movable reference. In order to move something, you need to change where the reference points, so conceptually you need a reference to the original reference to update it. (Effectively a double reference)

i < array.length or else you overflow.

I will say, you can’t beat the satisfaction of tracking down the root cause and actually fixing the bug. I don’t understand why so many people meme about covering up bugs with crazy hacks. It’s not fun constantly looking over your shoulder to see if that bug has resurfaced. They start to pile up.

It’s so easy! Watch:

{"contents": "<garbled .docx contents goes here>"}

Unfortunately it’s my least favorite part. It’s good motivation to take better photos in the first place though.

These don’t seem to be particularly new panels. $600 and only 97% of the sRGB color space (= ~78% DCI-P3), meanwhile a similarly priced LG “QNED” can do 90-95% of DCI-P3. I’m not sure you can even call those TVs HDR if they’re only 8-bit color. None of these models can even remotely compare to a brand new OLED TV.

I prefer my tutorials without reading someone’s life story at the beginning. The intro contains so little info compared to the number of words being used. This reminds me of looking up a recipe and having to scroll past an essay on the history of someone’s grandmother. I like it when documentation is as dense as possible, and ideally formatted in a logical way so it’s easy to skim. Big paragraphs of English do not achieve this.

I got the same sort of impression in the “Write for beginners” section. The “good” example is like 3x as long but contains less actual information. The reader is already looking up a tutorial, you don’t need to sell them on what they’re about to do with marketing speak. I’ve really come to value conciseness in recent years.