9-5 by day, learning, building and shipping by night. Follow my journey from $0 to independent. Goal 1 to quit 9-5: $5k/month DM to get something built free.
San Francisco, CA
Joined July 2010
- Tweets306
- Following55
- Followers17
- Likes129
Pinned Tweet
Built an APIKey tester as OSS side project that auto-detects your key from 19+ providers; OpenAI, Anthropic, DeepSeek, you name it.
Paste once → results instantly. Nothing leaves your browser.
Check it out: apikeychain.app
Here's how it works👇
#buildinpublic
Generating a 0 to 100 risk score and a blast radius map will not fix lazy approvals. The backend demo report is longer and more complex than the diff, which just gives developers a second thing to skim.
Source: github.com/winnin/farol
Someone releases a free, MIT-licensed app that lets you run local AI on your files completely offline. The first instinct of any developer reading the announcement is to check the repository and complain that it was written in JavaScript.
Source: github.com/FrigadeHQ/hob
Git blame usually just shows the developer who ran Prettier last. Tying linear history to issue trackers in the commit hook prevents the context loss.
A router model implies they are handling dynamic compute allocation server-side rather than making developers build their own cascade logic.
100 downloads a day with zero ad spend. A solo iOS developer got traction entirely by finding an app category where the market leader is ruined by expensive paywalls and ad grinding.
In 2006 tracking was just basic cookies. Now ad networks use canvas fingerprinting and installed font arrays to identify you across different IP addresses.
The LTV of a customer buying distribution knowledge is usually much higher than a consumer buying a utility app. Perceived ROI allows for premium pricing.
Forks that deploy to Vercel without changing the source code often leave the original canonical tags intact. It turns every clone into a high-authority backlink.
How are you handling authentication between the local MCP server and your production database? Passing API keys through environment variables gets brittle.
How do you handle context dilution when asking it to review a pull request that modifies a shared library depended on by dozens of other files?