> I liked the article. Every feature flag contributes to hockey stick growth of version variations of your software.
This is specious reasoning. When you add a feature flag, your goal is to purposely introduce version variations. How come is your explicit goal framed as this sneaky gotcha?
And let's be serious for a second. Do you see this "hockey stick growth" as an issue when you look at user settings?
> So cognitive overload is unavoidable after feature flags 5 as you have so many permutations.
Not really. Feature flags have a life cycle which is managed by release managers, and the goal is to always get rid of them asap. They are introduced to manage the risk of a rollout, and when the transition is over you pull the feature flags. Done.
Some things that initially seem like benefits at a small scale become less so at large scale. Owning one cat can be lots of fun. Owning 50 cats, not so much.
Everyone intends to collect the garbage. Few actually do.
Do you care to show prices? The true benefit of heroku for me was really predictable pricing model. Build.io website doesn’t have it on mobile site at all. I don’t want to look at demo, i want to hook up my credit card, set a monthly budget and explore
llIIllIIllIIl & runako give me an email on steven[at]build.io and I'll share. As mentioned, we stripped the site back while we overhaul and we certainly didn't expect this today!
You’re right - reading that back, it comes across as a “no,” and that wasn’t my intent.
We should show pricing, and we will. We temporarily stripped the site back while overhauling positioning and pricing, which is why it’s missing right now. That’s on us, not a stance against transparency.
In the meantime, I’m more than happy to share pricing directly.
At a high level on our pricing:
- Current customers are on a mix of usage-based and fixed monthly plans, depending on their needs. We've found many of our customers love the fixed plan as it's a whole new level of predictability.
- We’re generally architected to land well below Heroku’s Enterprise pricing and to be competitive with a IaaS.
- We want pricing to get out of your way as you scale, so no big steps in pricing as you add services.
- Databases are HA by default and support replication.
- Pipelines and review apps don’t require hacks to avoid per-review-app database costs.
Happy to answer specifics here or over email if helpful.
I guess it depends on how people interact with LLM. Cognitive debt may be acquired when people `talk` with machines, asking personal questions, like asking what to answer to the sms from a friend, etc.
It may seem different when people `command` LLMs to do particular actions. At the end, this community, most of all probably, understands that LLM is nothing else than advanced auto-complete with natural language interface instead of Bash.
> Write me an essay about birds in my area
Than later will be presented as human’s work compared to
> How does this codebase charge customers?
When a person needs to add trials to the existing billing.
The latter will result a deterministic code after (many) prompts that a person will be able to validate for correctness (another question if they will though).
I had very similar experience with my disabled organization on another provider. After 3 hours of my script sending commands to gemini-cli for execution i got disabled and then in 2 days my gmail was disabled. Good thing that it was disposable account, not the primary one.
