rubyissimo

I was worried a bunch about this as my kids got into the sporting ages. But I've been rally pleasantly surprised. Maybe it's our particular town (Boston adjacent), but all the parents seem have things in perspective. Well, maybe not _all_ but by far the majority.

stripe atlas is good for incorporation.

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.

awww man. is it the first. that stinks. I want it!

that's awesome

I'm definitely on the "down escalator: flow state is missing".

this had more info than i expected

fwiw, I know it's the right thing to run tests from a different computer. But it's more annoying. And I hereby tell you that 90% of the time it probably doesn't matter.

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.

We debate everything ad nauseum at work. I'm going to try the FG scale. We'll see if I get fired for being disengaged.

Rails if I care about the project more than about the tech.

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.

Does rubygems / go have "protections" against 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?