burnout is a serious issue

C was my first language some 18y ago, and I wouldn’t recommend it to anyone starting today. If anything, learning C is a great way to teach why, maybe, we shouldn’t be using it to build customer applications, web servers, and whatnot.

Keep your gold, I’ll stick to sane error messages, memory management, a packaging system, and a dozen other things that actually make working on multiple projects somewhat doable and not a constant fight against seg faults.

that’s one way to swing the pendulum all the way back to the 1970s

These things are the other way around. The older something is, the more likely it is to find a bunch of questionable choices, spaghetti code, and security holes.

The questions I have surround the “since 2012” bit. FB exists since 2004, so what happened in 2012? Was it a data dump, a careless logger, system migration, or something else?

hunter 2

unhackable

You probably don’t have to write to specific broswers. Just stick to the baseline and you’re golden. Optionally use a headless chrome for e2e testing to be sure.

an email for a receiver that doesn’t exist, more often than not, goes back to the sender after e.g. 72h. That’s by design.

I’ll admit that in 10 years using git, I don’t think I’ve ever used reflog once.

IME they usually proxy and/or prefetch images for caching instead of blocking them. Only spam content is blocked by default.

tldr

• it affects the desktop app of chatgpt, but likely any client that features long term memory functionality.
• does not apply to the web interface.
• does not apply to API access.
• the data exfiltration is visible to the user as GPT streams the tokens that form the exfiltration URL as a (fake) markdown image.

I’m glad they’re moving the world update and other massive downloads to something in the cloud and on-demand. Anything between 10-40% of my “play time” on steam was actually downloading stuff.

that’s MSFS 2020

they do

I’ve used plenty of sshfs a few years ago, but x11 forwarding is a compromise. The latency makes it painful to work with for more than a few minutes.

Same, ranger was painfully slow at times. For some reason it would take multiple seconds to start on a few machines I connected it to.

I can’t believe no one mentioned this, but: remote access.

I spend most of my day connected to machines via SSH and yazi offers a great UX with file previews and all. Using kitty I even get image previews in the terminal.

And I thought developers were bad at naming.

The Microsoft school of naming things is really showing their ways

get rid of companies making money off the FOSS

I’m afraid if we discourage companies from adopting open source we’ll end up with even more closed source garbage.

There are industry sectors where closed source is the norm, and it just leads to more vendor lock-in and less standardization and interop.

I’m a bit young to say for sure, but I believe closed source was the norm in the software world 20-30 years ago and openness was stigmatized. I certainly don’t want to live in that world.

as opposed to human-generated code

tldr

1. Keep Commits Small: Ensure commits are small and manageable to facilitate easy reverts and debugging.
2. Continuous Refactoring: Prioritize frequent, minor refactorings to simplify future changes.
3. Deploy Continuously: Regularly deploy code to ensure it works in production, as working software is progress.
4. Trust Frameworks: Avoid over-testing framework capabilities; focus on application-specific logic.
5. Create Independent Modules: Place functions in new modules if they don’t fit existing ones, preserving code organization.
6. Write Tests Early: Use tests to design APIs and guide development, but don’t be rigid about TDD.
7. Avoid Duplication: Prevent repeated code by abstracting similar implementations after copying once.
8. Embrace Change: Accept and adapt to evolving designs, understanding that change is intrinsic to software development.
9. Manage Technical Debt: Focus on minimizing immediate blockers and plan for potential future issues.
10. Prioritize Testability: Ensure that your code and design facilitate easy testing to maintain code quality and coverage.