I am sorry, but everyone is getting syntax highlighting wrong @ tonsky.me

This is one of those things I've been coming back to at least once a month. The idea seems sound, so I think it's just time for me to bite the bullet and test it out.

Applying human ergonomics and design principles to syntax highlighting

Claude is an Electron App because we’ve lost native @ tonsky.me

As much as I hate this - I think he's 100% correct. I was a big proponent of native software, but most times it's not worth the cost. If you care about performance, you can be performant. If you care about local-first, you can be local first. The problem is that the majority of folks don't care about it, or actively don't want it.

Article argues that Claude is not an Electron app not because LLMs can’t do it, but because there are no advantages left for native

You Are Here - Marc's Blog

This is mostly how I think about what AI is doing to the software industry. Things are changing, but writing code is just one piece of the puzzle. The harder piece remains.. and I think it's been made even harder. Everyone knows how hard it is to review code.. now you're churning out 1000s of lines a day? Shit, that's a bad idea all round...

Today, it seems like the biggest opportunities will be in the third of my opening statements. Building systems remains hard. Can I assume you’re familiar with Amdahl’s Law? That’s what’s going on: a massive speed up on a portion of the problem, but as that portion speeds up it becomes less and less of a contributor to the overall speedup

I miss thinking hard.

I'm seeing a lot of takes like this - I'm finding the opposite. AI takes care of a lot of the boring parts. The boiler-plate, the connections. But it leaves me to think about how things should be implemented and capture higher level problems earlier. Instead of leaving the AI to figure out the right way to query something from the db, I can flag a potential n+1 issue from the very start. I think I need to revisit this topic and share my approach in more detail...

Initial commit: App Store Screenshot Generator · YUZU-Hub/appscreen@20cfbbf

When we talk about the proliferation of AI-code and the "death of SaaS" it's tools like this that stand out put me. Before this would be a small line-time and accepted as part of your development costs.. now it's something you can handle in-house. The bar for paying for software is getting higher and higher, as it should.

Create screenshots for the iOS App Store. Contribute to YUZU-Hub/appscreen development by creating an account on GitHub.

Memory as Reasoning

Why AI memory should be treated as a dynamic reasoning task rather than static storage, & how logical reasoning enables superhuman capability in this dimension.

ASCII characters are not pixels: a deep dive into ASCII rendering

A look at how I used shape vectors to achieve sharp, high-quality ASCII rendering.

"Good engineering management" is a fad | Irrational Exuberance

This is an interesting read because it ties really closely to people that tightly identify with their job. For a while it's been easy to be "morally good" and really invest in the personal relationships on your team. But times are a-changing...

As I get older, I increasingly think about whether I’m spending my time the right way to advance my career and my life. This is also a question that your company asks about you every performance cycle: is this engineering manager spending their time effectively to advance the company or their organization? Confusingly, in my experience, answering these nominally similar questions has surprisingly little in common. This piece spends some time exploring both questions in the particularly odd moment we live in today, where managers are being told they’ve spent the last decade doing the wrong things, and need to engage with a new model of engineering management in order to be valued by the latest iteration of the industry.