I’m going on a short vacation this week, so this post is coming out a bit earlier than usual. I actually had a different, more “useful” topic in mind — something educational, something responsible. But then I came across this fascinating article: I don’t like Tailwind. Sorry not sorry written by @freshcaffeine , and I couldn’t get it out of my head. So I decided to write a response instead. I actu
The task at hand is drawing the circuit schematics for a robot I'm working on. I had already written down the components and the connections, all that's left is to draw it in KiCad. I had already started doing that, but then... I got sidetracked forcing Gemini to create the circuit using KiCad. I would have made progress if I had continued doing it by hand. I spent yesterday trying to generate an
Comments
This is part three of a series on display consistency in embedded systems. The first two parts were technical. This one is about why the technical parts worked. The picture: ATtiny85 thermometer. Neural network inference. QUAD7SHIFT display. Built from datasheets. He had datasheets. No Stack Overflow. No libraries to install. No AI to generate boilerplate. No tutorials that abstracted away the in
🤔 Why v0 Output Alone Isn't Production-Ready If you've used v0.dev to spin up a landing page, you've probably hit the same wall on the next step. The component looks clean inside v0, but the moment you drop it into your Next.js project the design tokens drift, dark mode breaks, metadata is empty, and Lighthouse scores land in the 60s. This isn't a v0 limitation — it's that v0's output is "desig
If you've ever used a bottleneck calculator, you've probably seen a simple percentage telling you whether your CPU or GPU is holding your system back. But here’s the truth most people don’t realize: Bottlenecks are not fixed numbers — they are dynamic, workload-dependent behaviors. In this post, we’ll go beyond basic tools and break down how CPU and GPU bottlenecks actually work in real-world scen