rubyissimo
rippling gets a ton of the other bullshit done. ramp for expenses mercury for bank account
you prob don't need official cap-table if you're bootstrapping, right? if you do a SAFE you can angel list and RUV and get the table.
defer everything you possibly can until post raise / reality in some form.
Interactive feature flag pricing comparison
Is it time to leave your job
Definitely times it isn't true. But if you're not doing a load test bc it's a pita, do it locally. Most of the time I've wanted to do this, all the action is inside the app. Just be careful to acknowledge that there could be limitations / surprises.
Balancing engineering cultures: Debate everything vs. just tell me what to build
Python FastAPI if I want LLM backends.
Using Netlify for deploys. Prefab for config / logging.
commander-rb for CLI.
replit for projects I want to collaborate on with kids.
We did https://bullettrain.co/ but the longer we're on it the more painful upgrades are and we've basically given up now.
What is your approach to this?
Is npm specifically vulnerable to this kind of thing? Or is it just a cultural elelemnt of npm that there are more micro-packages?
We had a small down one, eventually company actually did a massive equity re-do for everyone giving us an option for a different strike and longer exercise window. It took 18 months from the "crisis" though.
Eventually the board realizes that they need the employees motivated.
Letting people be on-prem kills your upside for NRR. You need to have something compensating.
is this something like https://www.reddit.com/r/ruby/comments/15o9hc1/timetraveling... ?
Seaport is cool, even if it totally blows my mind how much they've built at a level that is clearly going to get crushed by rising sea levels.
:shrug: if it's working. It makes my stomach upset so at least _something_ is happening.
All those things that were so great and wonderful at bigcorp... pretty often turns out they fixed issues that are a decade old and the state of the world has often made them irrelevant. Certainly at startup scale.
It looks like that limit has been changed more recently: https://stackoverflow.com/questions/32950503/can-i-have-100s... but I'm still skeptical it's what you want. You'd need a consumer for each of them, you're tracking offsets for all of them.
Much more normal would be a single topic here, partitioned on user.
You can have 2 consumers then. One that pulls things off and notifies. Another one that pulls things off and stores to the DB, which is indexed by user ID.
Then when they read a notification, you flip a bit in the DB for the notifications.
If you put your head down and do great work, you just run the risk of getting out-politic'd, so you've got to do that too. But that makes the political players spend more time on it to make sure they're still ahead of the part time politicians. And it's an arms race of spending time making yourself look good instead of doing work.