The Developer Tool Intelligence Platform

May I recommend thinking of Emacs as your Fortress of Solitude

I've noticed I get way more out of Claude when I treat it less like a search engine and more like someone I'm thinking through a problem with. Instead of asking "what's the best way to structure a REST API?", I'll say "here's what I'm trying to do and here's what I'm leaning toward push back on me if I'm missing something." The responses are noticeably different. It actually disagrees, flags assumptions I didn't realise I was making, and sometimes lands on a direction I wouldn't have reached on my own. Curious if others do this deliberately, or if you've found other "modes" of using it that changed how useful it was for you?

I wanted to make a dashboard for Home Assistant on my Kindle, and since I know Slint from a previous project I was curious to see if I could use that. This resulted in a slint-backend for kindles (probably not a lot of them for now, as I only have the one device to test on). [https://github.com/sverrejb/slint-kindle-backend](https://github.com/sverrejb/slint-kindle-backend)

A few days ago there was a thread here asking what he most useful thing you've built with Claude was. A LOT of replies. I read all of them and then something clicked, I wanted to put it on the table. First of all, the list was incredible. An HTML file on someone's phone correlating migraines with barometric pressure, because the App Store wanted 80 bucks a year. A Garmin data archiver, because the official app deletes them. A grocery list sorted by the aisle layout of one specific supermarket. A bioinformatics pipeline for a handful of microbes, written by someone who isn't a bioinformatician. A three-line command that explains the last terminal error you saw. Every single one is perfect for one person. And by the same measure, basically useless to anyone else's scenario as-is. That's not a bad thing. That's the whole thing. Bear with me, please. Here's what bugged me when reading the thread: almost everyone showed the artifact. "Look what I built." Screenshots. Product names. Feature lists. Almost no one articulated the thought pattern, how they looked at their own life, found a friction, and shaped a tool to its exact contour. And that pattern is the only thing that actually transfers. The reason we default to showing the artifact isn't (only) ego. The mediums we use are all calibrated to distribute objects, not practices. GitHub measures stars and forks. Reddit upvotes screenshots. Product Hunt ranks launches. None of them have a way to register "I read your README, understood how you thought about your problem, and built something completely different but that fits my life." That transmission of ideas, the only one that matters in this new paradigm when can vibe code a whole new solution in minutes, is invisible to every metric we have. There's an economic layer too. A product has a market. A thought pattern doesn't. Nobody monetizes a cognitive habit. Nobody pays royalties for "this is how I framed the problem." So the medium rewards what has a market, and…

My dashboard after removing everything that is not important. One page, compact, all the information I need. Screenshot from last week. The dashboard is Dynacat, a fork of Glance.