Except that code is generally made of… other code. And generally gets transformed from some kind of source form to some kind of deployment form. And then executed by some kind of runtime, made of code. On some kind of OS, made of code.

The level of abstraction at which you make paper by hand is pretty much constant. The level of abstraction at which you make even a “hello world” program by hand is extremely flexible.

Depending on your operating environment, even an incredibly complex and impressive task may just be a matter of passing the right flag to a CLI tool that you already use.

Being attentive to the manual experience of how a codebase “feels” is pretty important for making sure a system has a coherent (read: not over-engineered) approach to bridging the high and low levels of the tasks it performs.

Not paying attention to that, because you can delegate it to a chatbot, is kind of like forgoing having light switches in a room because you can just keep a crane parked outside and have it slam a lighting fixture through the ceiling when you need it and then dump a mound of dirt to cover the hole when you don’t need it.

Like, that functions and accomplishes the task in a pinch, but you do not want to try occupying that room in person at any point to do any kind of detail work.

In order to be effective at software engineering, you must be familiar with the problem space, and this requires thinking and wrestling with the problem. You can’t truly know the pain of using an API by just reading its documentation or implementation. You have to use it to experience it. The act of writing code, despite being slower, was a way for me to wrestle with the problem space, a way for me to find out that my initial ideas didn’t work, a way for thinking. Vibe coding interfered with that.

If you’re thinking without writing, you only think you’re thinking.

– Leslie Lamport

Yep. This what I don’t get about people who are using these spaghetti-bots. How do they figure out the right solution to a problem without actually walking around the whole perimeter of the problem?

My guess is they are not, and they’re just waiting until someone complains and they’ll get a job somewhere else and leave the mess for someone else(‘s chatbot) to clean up.

Between that and the death of open source, our industry is about to become a disaster area.

I mourn it too, because there are dumbasses like this who are buying the hype and setting the industry back by decades as a result.

If hardware cost/availability is an issue, there are a few hardware simulators out there. Wokwi (ESP32 sim) is free for personal open-source use.

I’ll let someone much smarter than me speak to this:

https://youtube.com/watch?v=KtQ9nt2ZeGM&t=4420

Just waiting for another xz utils situation

The horrible names of these things…

o4-mini, not to be confused with 4o-mini

And 4o, not to be confused with 4 (aka 4.0 or v4, but 4V is different)

Also, like… the fact that it has a compiler. It’s like saying C is incompatible with assembly because you can’t yeet a .c file at an assembler.

Yeah, that’s uhh… that’s technically true for very strange and specific definitions of “compatibility”… but it wildly misses the point of TypeScript. Not sure what he was thinking there.

Trusting your own judgement on ‘AI’ is a huge risk

All IP laws are fundamentally “honor system”. The idea of digital locks is a pipe dream, only possible as long as legal threats scare people away from looking too closely at how the lock works.

But every digital lock can be broken, because we only know how to make one type of computer: the turing-complete universal von neumann machine. It can run any program, as long as it’s presented the right way.

So yes, it’s piracy. Just like how the crime of “breaking and entering” means “breaking the seal” and entering without permission (not necessarily breaking a physical lock), piracy just means unauthorized use of IP-law-protected content (not necessarily breaking a digital lock).

Breaking a digital lock is an additional crime on top of piracy, under the DMCA. 5 years and 50k fine for a first offense, I believe.

Now as to whether we should even have a concept of “piracy” to begin with… that’s a reasonable question.

Beautifully put.

I especially like that they called out the “it’s just a tool” BS:

Yet technological artefacts cannot be separated from the conditions under which they are created, or from the realities of who controls and profits from them. Today, developing these technologies expands racial capitalism, intensifies imperialist extraction, and reinforces the divide between the global North and South. The technology is inseparable from the labour that produces it — the expropriation of work by writers, artists, programmers, and peer-production communities, as well as the highly exploitative crowdwork of data annotation.

Big agree.

But also: people seem to only focus on the output side of the task of writing code, and forget that the developer also receives input from the codebase in return.

Even if you end up with exactly the same code artifact after completing a work item, you’ll have a better understanding of the codebase without delegating swaths of it to AI. But bosses tend not to consider this.

Tech bros have successfully convinced people that mental states do not exist, or at least do not matter — for laborers, anyway, cuz they’ll happily claim that their superior thoughts are exactly why they deserve to be billionaires.

Code is a liability (not an asset)

Related: Jevons Paradox

Not sure about Apple-mediated payments, but you can usually support the creator more directly and get an ad-free RSS feed that you can plug into the Podcasts app and it Just Works™. Usually ends up being a better deal for the creator, too.

Trying desperately to keep the ponzi scheme going, but his biggest customers already have warehouses full of GPUs that will never get connected.

The bubble is full, dude. Just try to minimize the damage from the pop so we don’t try to figure out what size pitchfork your dumb leather jacket is.

It also discouraged you from finding/starting an open source solution for those problems, thus undermining the high-quality open knowledge ecosystem that it relied on in the first place.

As Cory Doctorow says: code is a liability, not an asset

Keychron is solid, and offers a wide range of sizes so you can balance real estate vs functionality