copynpaste, 7 weeks in
- 6,300 people in the last 90 days
- 4 paying users
- 12 integrations shipped, every one from a user email
- $0 on marketing
built it because pasting between apps kept wrecking my formatting. turns out it wasn't just me
somewhere between the broken builds, confusing errors and "one last change", you actually got better at this.
give yourself credit for that.
now commit your code and go to sleep.
there's a special kind of confidence that comes from fixing a bug without understanding why it was broken.
enjoy it for 5 minutes.
then write the tests.
paying for an API without giving the provider a permanent identity trail?
that's the kind of practical privacy problem zero-knowledge proofs can help solve.
cryptography gets interesting when it makes better products possible.
one of my favourite things about zero-knowledge proofs is that they challenge an assumption we've accepted for too long:
why should proving something be true require revealing everything?
not every problem needs a blockchain.
but if your system needs shared ownership, verifiable execution and coordination without trusting one operator, now we're having an interesting conversation.
your github contribution graph is not a measure of how good an engineer you are.
one well-designed system can be worth more than 500 meaningless commits.
AI making vulnerability discovery faster is exciting.
AI making vulnerability discovery faster for attackers too is the part we can't ignore.
the window between finding a bug and fixing it matters more than ever.
we're giving AI agents access to terminals, credentials, cloud infrastructure and wallets.
but the question isn't just "how smart is the agent?"
it's "what can it do when it gets something wrong?"
ethereum delaying an upgrade because of a security concern is a good reminder:
shipping on schedule is nice.
not breaking existing contracts is better.