Sabitlenmiş Tweet
Zeke Gabrielse
4.4K posts

Zeke Gabrielse
@_m27e
Soli Deo Gloria. Father of 3. Building https://t.co/erKlLqUMBW since 2016. Sometimes I like to argue with people online about licensing, startups, bootstrapping, etc.
SGF Katılım Temmuz 2024
327 Takip Edilen878 Takipçiler

@peer_rich @iammoizfarooq I actually quite like Stripe Sigma for this. I calculate everything like time to convert, forecast cash flow, etc. and email it to myself. Tools like this that are built on fetching subs/etc. via the Stripe API become unusable past a certain scale due to volume and rate limits.
English

@iammoizfarooq oh goddd yess
i hope its accurate
all previous attempts were at least 20% off
English

stripe has no MRR endpoint.
baremetrics charges $129/mo to calculate it for you.
I built a free open source CLI that does it in 3 seconds:
npx stripe-pulse mrr
→ $392.00
MRR, churn, LTV, NRR, 20 commands. free forever.
github.com/progrmoiz/stri…

English

@jessethanley @balindenberg Four year olds have some big emotions. Hardest year imo, so gl. (My second just turned 4.)
English

@balindenberg I said this at 12 months.
Then at 2 years.
Again at 3.
And will say it at 4 too.
I think for dads the bonding gets stronger the more active interaction we have with them. We don’t really have the same bonding experience out the gate that mums have.
English
Zeke Gabrielse retweetledi

New post up on the @sentry blog, apropos @fairsrc in light of recent shenanigans: “You can’t use clones of Fair Source software to compete with the software you’re cloning.”
blog.sentry.io/fair-source-so…
English

@_m27e I think a big difference is that you don't serve "marketers" and they basically behave like indies but function like that inside all companies.
English

I try to avoid being a doomer, but I do feel immense pressure to have my product conform to the new way of working in a way I haven’t felt before.
Organic traffic is no longer a distribution strategy, customers don’t want to login anymore, you need to have a CLI/MCP or customers will go elsewhere, our AI features need to be updated weekly and one-shot the most random requests…
Your company is at risk if you don’t move fast enough.
I’m embracing it but I understand why people are anxious.
It’s never ending.
English

@jessethanley @Bento Curious on if there's a particular user segment that wants these features? In my experience, the main people that ask for this are indies obsessed with agentic workflows and being on the cutting edge, but they're also the ones who pay the least. (Not trying to be a naysayer lol.)
English


@djm_ Just using Clickhouse Cloud and the activerecord-clickhouse adapter
English

@_m27e Congrats! Are you managing Clickhouse schemas with any IaC and if so, what did you choose and how did it go?
English

@GregorySchier I was just complaining about this last night when I thought I used my credit card but it was my debit card lol
English

To be clear I’m going to keep shipping using LLMs. It’s harder to optimize for when not to use them. It’s just a simple observation that I and many of my peers have had.
Sometimes the performance hit justifies the long term outcome - understanding the tech deeply does.
David Cramer@zeeg
im fully convinced that LLMs are not an actual net productivity boost (today) they remove the barrier to get started, but they create increasingly complex software which does not appear to be maintainable so far, in my situations, they appear to slow down long term velocity
English

@nateberkopec @mscccc It really is. I did find that the default session-based read-your-own-writes resolver doesn't work well for API-only apps, but the foundation's extensible enough that it isn't too hard to write your own Redis-based resolver (as always with Rails!)
English

@mscccc you've talked before about "send all gets to reader, send all POST to primary" on a per request basis IIRC? Where was that done? And how did you handle post -> redirect -> get not having stale info for the final GET?
English

@nateberkopec @keygen_sh Just getting to this. How would you update the docs here? Just adjust the WEB_CONCURRENCY default to auto? You also said docs make some incorrect statements, so lmk.
English

@keygen_sh keygen.sh/docs/self-host… is not correct via puma tuning. Tell people (or do it yourself) to set WEB_CONCURRENCY to `auto` and leave RAILS_MAX_THREADS as it is. The current docs make some incorrect statements, see Puma's deployment docs for more info.
English












