I’m surprised that after almost 20 years of versioning C code, git still manages to assign the closing brace of a function wrongly.

Build caches are a bitch.

I mean, nowadays you can get wireless internet – via LTE/5G. For technologically illiterate users, I’d put the blame on whoever sold them a WiFi router.

I understand them. Someone saying they took the troubleshooting steps doesn’t mean they took them.

Also not everyone is on the same technical level. “I pressed the button on the screen. I thought that means the modem is off!”

Upvote for the title alone.

https://liberapay.com/Lemmy/

It’s not client-side anymore. You need a backend to produce the HTMX.

Are web servers that serve real HTML responses still a thing? Honest question. I thought JSON+client side rendering were the default by now.

Piped link: https://piped.video/watch?v=TIZKKmh6YM8

Who sends API requests if not frontend developers?

If your bandwidth can afford more than 3bps:

Source: https://twitter.com/nixcraft/status/1422824132249473025/photo/1

I feel like there may be a reason to this. It looks like the flowers got recently moved. Maybe it was in the way of the main footpath that sees the most traffic? I can see it getting moved if people repeatedly tripped over it at night or when drunk.

Remember kids, shitty code isn’t shitty until you find out how it came about.

“PR” lol. I’m the sole developer.

Jokes aside. I find it easier to have all the information in a commit message, so I can browse it in the git log without having to find the relevant PR(s) that finally merged it.

I don’t feel like “ditch comments” is the right solution to “we {forget, don’t care enough} to update comments”.

How much can you really put in 50 characters?

Fix: NPE in customer download component when users – That’s 50 characters. Should I not mention where I fixed the bug?

Fix: NPE when users downloaded customers without s – I think I can get rid of the actor in some cases.

̀ Fix: NPE when downloading customers without select`. The summary I want to give cannot be truncated any further.

Fix: NPE when downloading customers. This fits, but is so vague as to be pointless as a summary, in my view.

We’re lucky in that the inventors of our technology are still alive (for the most part). So we can ask them: Linus Torvalds on git commit messages

My personal cent: Some tools strongly suggest that your commit messages should not exceed 50 characters in the first line, and 80 characters on every other line. While the 80-character rule makes sense if you’re using a terminal (and someone on your team will even if you don’t), I strongly disagree with the 50-character rule. If you want to be in any way clear what you did, 50 characters is simply not enough even for the subject line.

Hot take: Even these ‘useless’ comments help, since they relieve you of the burden of reading the code itself, even if it’s trivial. One line of English is easier to parse than one line of trivial code.

*defederated, I think?