Still reckon all the years in ecommerce taught me more about building software than any dev stuff i read, customer journey mainly. what did ur job before tech teach u that u still use
Early products can become a pile of good ideas pretty quickly.
Pick one job users repeat and make it feel obviously better before adding more.
Can they do it faster? Feel more sure they've done it right? Enjoy it more?
What's the repeat job in your product?
Two ai coding agents on the same repos can be nearly 3x apart on speed.
Ran claude code and codex side by side for two days and pulled the run logs.
Not a clean test - claude was running the show and codex had the smaller jobs.
Median run was 77s on claude and 221s on codex
Side projects get out of hand fast.
Built a mini football manager game to test something for my main project.
Ended up making over 100 fictional club badges and every one has its own lore.
No idea why i did this to myself 😭
[ADD: grid image of the badges]
Probably less needed in the future as more of my workflow goes headless using things like Grok bot, but it is still good to know that I can go in and see things at a bird’s eye view relative to the project rather than just endless streams of chats. I have to keep things unread, so I can’t always keep it inbox zero annoyingly
I forked it to have “work streams” I basically have a thin rail down the left-hand side, like slack, where I have each of my work streams, which are essentially just projects, and then in each one I will group them by repo if they have multiple repos. This is by far the best UX if you’re working on multiple things across multiple different businesses or brands/products
@QuantumPionier@theo Why can’t you structure your work into folders or projects? You don’t just have it all sat mashed all over your desktop, do you? 🙈