39 karma · joined November 1, 2016
We lived in different countries where people speak a different language, during their earlier years, though, so maybe that also contributes to it.
And you can do live preview via plugins.
I don't think there's any reason not to ask, and the worst they can say is no.
If it's a no, they might have something comparable that'd be helpful that they can share.
And if they have nothing, that's also good information to help you decide. :)
Sometimes I'll prompt again to scrutinize further.
If something highly sensitive, yes, and in general, a tendency to review with more scrutiny on backend changes.
But for frontend, less and less every week.
This is basically what I'm doing with the existing subscriptions I have. I can't remember the last time I cleaned up obsolete code, my coding agents do it for me now.
- Going for a walk at least 1h a day
- Sitting 20min first thing in the morning in sun doing absolutely nothing
- Working out every day, even if just doing some pullups or pushups
- Trying to only use social media for work, not for pleasure
- Talking to AI (Claude) while Claude Code is running in different session, about topics that are interesting to me
I spent about 6-8h online every day on average
Hope it's helpful
And Figma has an MCP server which they talk about in this blog post: https://www.figma.com/blog/introducing-claude-code-to-figma/
Hope that helps.
Personal: $19.99 on Google AI Pro
Safari on iPhone
People that can do this with a verifiable track record I think are in a good position to connect with job opportunities right now.
Was prescribed for ADD
Glad I got off it
At the same time, it was difficult working with the domain owners behind it who at times were self-serving and very ad-hoc with respect to wanting to push their own agendas.
So definitely one of my most proud projects, but also bittersweet. :/
So I'm building an app a week and focusing on solving niche problems I've experienced in my own life to start
I think it's never been easier to build prototypes, but because of all of the slop, building community and finding users around them are harder than ever before
This latter part I think is going to be the hardest part of going out on my own
But going to try
Things I'm working on right now:
https://a2ciple.pt/ - testing prep for a language exam required for residency & citizenship in Portugal
https://basehub.org/ - a docs site for agents to get the latest context on Base, an Ethereum L2
https://playgokab.com/ - a vocab game to learn words in diff languages
https://mru.space/ - a protocol to run software that gracefully degrades across failing hardware
https://shiponeshot.com/ - a framework to help me ship prototypes more quickly
Anyhow, cheers :)
There are three execution modes:
* Scheduled, cron-based. For example, my daily email triage runs at 6 AM, processes ~50 emails, archives the noise, and sends me a Telegram summary before I wake up.
* Watcher, event-driven. A cheap check script (JS/Python) polls for changes. Only triggers Claude when something actually happened.
* Persistent, long-running sessions with heartbeats, checkpoints, and restart policies.
Tools use MCP (Model Context Protocol) servers that you write and control. No plugin marketplace, no third-party code touching your credentials. Cost tracking is first-class. Every run logs its cost in USD. Per-run limits, daily budgets, monthly caps. The daemon pauses everything if you hit your budget. This matters when agents run unsupervised.
Everything is plain text, agent definitions, run logs, memory, cost ledgers. git diff your agents, grep your run history. I'm currently running this on a $5/mo Hetzner VPS.
Requirements: Node.js 20+ and the Claude Code CLI.
Anyhow, hope it's helpful and happy to answer any questions.
I'm by no means against Lightning, it's just got a long road of ecosystem, development and better UX ahead of it before we see general mainstream adoption. At the moment, bitcoin's killer feature is holding bitcoin. Most people don't know what Sats are. There are few bitcoin-payable apps. Few stable assets that remove volatility for every day payments like you would need with 402. Stuff like that.
Transactions confirm every 2 seconds on Base, and preconfirm even faster (every 200ms); there's no lag from a peer to peer payments perspective since they settle so quickly.
Through account abstraction and spend permissions, you also don't have to wait and authorize every single payment. It's a customizable from a developer perspective depending on how they want to build out their application.