Shane Spencer

Shane SpencerSep 19, 2026

I'm officially a Lovable Certified Partner. What I actually build with it: business applications, agent frameworks, and automation command centers for small businesses. Mostly trades. HVAC, appliance repair, plumbing, electrical. Now moving into wine. Making sure the teams can access the data they need, when they need it! The work that surprises people is the leaderboards. Take the performance data a shop already collects and never looks at, make it visible and accurate, and put it in front of the crew. Friendly competition does more for output than most software does. It only works if the numbers are right, which is the hard part and the reason it's a build rather than a spreadsheet. Certification means something specific. It puts a verification step between you and the risk of hiring wrong, and it connects me directly to the Lovable team when something needs an answer I don't have. The path here was paved with over sixthousand hours in Discord, and over a year as Lovable Champion, Most of those hours were unpaid and unglamorous, spent answering the same question for the fortieth person who was stuck on it. I would do it all again. Thanks owed, and none of it is simply decoration. Thanks to the partner team, Maximilian Keil, Opeid E., Kim Veerbeek. Also to Sophia Nabil and mallory contois, for helping guide the Champions program into something that develops people instead of labeling them. Bobby Siegfried and Jonathan Osburg, who set the standard the rest of us measure against. Lazar Jovanovic, for arguing vibe coding was a profession, back when so few saw it, that lead straight to the chance to build with the Lovable team as a Vibe Coder in Residence, fantastic experience! Thanks Elena Verna for making that happen, so empowering! Of course the biggest thanks to Anton Osika and Fabian Hedin for creating such a Lovable platform! So, that all said! If you're building something and want it done right the first time, that's what the certification is for. Comments or DMs, either works. What are you trying to solve? Lovable

Shane SpencerSep 17, 2026

Somebody just scrolled the entire Chromium codebase at 120 frames per second. 51 million lines. Rik Arends demoing Makepad Scope, with a full repo index in around 2.5 min and roughly 3GB of RAM, static analysis and caller lookups working the whole way through. It really is something else. Editors generally get unhappy at a large monorepo and politely ask you to exclude some directories. Something Worth understanding is why it's possible. Makepad isn't an editor that just so happens to be fast. It's a GPU-accelerated UI framework for Rust that Arends has been building for years, and the code tooling is an app running on top of it. The performance isn't a clever optimization. It's what you get when the interface layer isn't a browser engine pretending to be one. Which connects to something I posted this morning. The bottleneck in AI-assisted work isn't generation, it's comprehension. The model produces more than you can absorb, so you skim, and the part you skimmed is where it breaks. Nearly all the money right now goes to tools that write code faster. Almost none goes to tools that help a person understand code faster. Different problems, and only one is getting funded. Rendering 51 million lines as something you can move through is a comprehension tool. It's aimed at the half of the problem that's about to matter much more. It's on GitHub. Links in the comments. What's the biggest codebase you've had to get oriented in, and what actually helped?

Shane SpencerSep 16, 2026

1.5 million words that I did not have to type. This is peak computer use. It's so damn accurate, I don't even find myself really worrying about checking the output hardly at all. By far, Wispr Flow is in my top three pieces of software of all time! I'll join you at the 2 million club soon enough Bobby Siegfried.