Leetcode is a great way to polish your skills. When I was your age, I read programming books and made projects I cared about, it’s turned out very well.

I’ve helped a few others learn programming, practice and working on any project at all always help more than anything.

I explained a little about buffer overflows, but in essence programming is the act of making a fancy list of commands for your computer to run one after the other.

One concept in programming is an “array” or list of things, sometimes in languages like C the developer is responsible for keeping track of how many items are in a list. When that program accepts info from other programs (like a chat message, video call, website to render, etx) in the form of an array sometimes the sender can send more info than the developer expected to receive.

When that extra info is received it can actually modify the fancy list of commands in such a way that the data itself is run directly on the computer instead of what the developer originally intended.

Bad guy sends too much data, at the end of the data are secret instructions to install a new program that watches every key you type on your keyboard and send that info to the bad guy.

There is a ton of literature out there, but in a few words:

Rust is built from the ground up with the intention of being safe, and fast. There are a bunch of things you can do when programming that are technically fine but often cause errors. Rust builds on decades of understanding of best practices and forces the developer to follow them. It can be frustrating at first but being forced to use best practices is actually a huge boon to the whole community.

C is a language that lets the developer do whatever the heck they want as long as it’s technically possible. “Dereferencing pointer 0?” No problem boss. C is fast but there are many many pitfalls and mildly incorrect code can cause significant problems, buffer overflows for example can open your system to bad actors sending information packets to the program and cause your computer to do whatever the bad actor wants. You can technically write code with that problem in both c and rust, but rust has guardrails that keep you out of trouble.

Wow what a neat project, I have spent a lot of time recently working around vulkan on m1 machines with compatibility layers and while it’s not a huge pain it does suck to miss out on some of the more powerful features of vulkan that the hardware is certainly capable of. I’m not keen on learning metal to bridge the gap and this is just what the doctor ordered.

This will be a huge boon for me, way to go!

We don’t deserve our open source heroes, so grateful for the incredible free software ecosystem

Gimp, 7zip, blender, vlc, open office, the kernel, thousands of others, I feel like our lives have been universally improved by these inverted charity projects. The few taking care of the undeserving many.

Why in the world would you need such a large budget? A mac studio can run the 70b variant just fine at $12k