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.

The big question with these is whether / how you expect people to update. Or whether you just start with it and then never update.

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?

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?

Be transparent with your boss about how it's affecting you, while also being sensitive that a lot of people are in a similar boat. The journey to liquidity is long. There will be more grants in the future.

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.

Tools in my space are usually 5-10x.

Letting people be on-prem kills your upside for NRR. You need to have something compensating.

I want to like passkeys, but so far it feels like they've just confused the issue.

how long can you time-travel?

is this something like https://www.reddit.com/r/ruby/comments/15o9hc1/timetraveling... ?

I liked boston the city whenI was there. It's no New York, but the common and esplanade are beautiful and it's certainly not _dead_.

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.

how cheap is "cheap"? I've never heard anyone say that about brooklyn.

This is only an issue if you have more than 1 language. Almost every language or framework has a good solution for configuration these days.

I'm trying serotonin right now because of https://www.pennmedicine.org/news/news-releases/2023/october...

:shrug: if it's working. It makes my stomach upset so at least _something_ is happening.

1000%!

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.

user specific topics isn't the right path, conventional wisdom would be that you want < 1000s of topics.

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.

This is a great write-up. Very similar to how I think about it.

I find myself spending a lot of time with junior devs encouraging them not to think about the problem. Can you repro? No? Then just focus on that. Save your brain power for later.

"We'll never know less than we know right now" is always true. So save the hard thinking time for when we actually have the information we need.

everytime I get a new computer it takes me 5 seconds to remember that I can't live without sizeup.

But I can never remember the name of the app because it's just ctr-opt-cmd-left in my head.

This is awesome.

Using ChatGPT in voice-only mode has been a totally eye-opening experience for me. It feels so much more natural and for the first time I can actually imagine using a system like this.

But yeah, it's got to be tied to the OS. It's got to be able to store my knowledge.

Prediction: Apple is the big winner of AI. There's no first mover advantage here. But there's enormous advantage to being built in / default. They can release an LLM OS in 24 months and still win.

The problem isn't so much the actual culling. The problem is the tax it puts on everyone for the rest of the year to self-promote and make sure they don't get caught accidentally.

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.