What does “engineering” look like when people approach problems by just throwing the entire codebase away and generating an entire new one?

Technical debt? Just pretend it doesn’t exist!

This would be a deeply unsatisfying world, to say the least.

I think it’s interesting to think about insofar as it challenges some pretty fundamental assumptions.

All the thinking so far has been about how to keep code understandable and maintainable as it changes over time. What happens if code becomes so cheap as to be disposable?

There’s something charming even about seeing all the wildly outdated books mixed in there

It also shares the sins of micro usb where some cables can handle data, and some are only for power, and there is no indication of which a given is

Peter has a nice blog post about making his card. Check it out peterkagey.com/blog/2025/12...

My laptop isn’t good; it has an ancient cpu and 4gb of RAM. But it just keeps going