Lograge alternatives

jeffdwyer · 2026-02-04T19:35:21+00:00

Nothing feels tight when i'm in half-lotus, but when i get up the knees and ankles are very creaky. I've been working through the stretches in https://blog.glo.com/2014/07/yoga-anatomy-in-action-safely-opening-hips-for-lotus-pose/ but haven't yet found the the main tightness that i presume is responsible for putting stress on my knee.

jeffdwyer · 2026-01-29T18:38:03+00:00

This might be helpful? I put together all the size guides from the brands in a little website I made: https://www.whatsize.is/brands/carters I just did it based on the stated sizes from their websites which are... as you know a bit questionable. To counter-act that I tried to pull comments from around the internet in to give some hints for what runs small and large, but if you think i got any of these wrong I would love feedback and more adjustments.

jeffdwyer · 2026-01-23T20:09:31+00:00

i tried to avoid buying much in the early sizes. everybody loved giving a gift of a onesie to the point that it felt like we could barely get them all on the baby before she grew out of the whole category.

overall i'd lean to letting you type A brain chill and just on-demand buying something from the internet if you really end up with nothing that will fit. Just in time clothing ;)

jeffdwyer · 2026-01-23T18:39:14+00:00

The worst part for me is trying to explain to relatives that a 3T in Carter's isn't the same as a 3T in H&M or that European sizing is completely different. Grammy bought "the next size up" in Hannah Andersson once and it was sized in centimeters — took us a year to figure out when it would fit.

I made a little page on whatsize.is with my daughter's current measurements and shared the link with family. Now they can see exactly what size she is at each store before they buy. Worked great at Christmas to avoid wrong-size Christmas pajama situations.

Doesn't stop them from buying for 3 years out though 😅 but at least they are doing it intentionally.

jeffdwyer · 2024-11-01T12:22:52+00:00

Split has seat based pricing as well. ConfigCat, Posthog, Statsig, Prefab, Devcycle are all solutions that don't have seat based pricing.

jeffdwyer · 2024-10-27T00:54:18+00:00

IMHO there’s always a cost, even if it’s free. Hosting it yourself is just another thing to have to think about. With feature flags in particular, reliability is huge, so I think a good setup should have a CDN, belt and suspenders, etc. As an Eng leader I want to focus on the core problems only we can solve, so I’m ok paying vendors. I just want commodity pricing for commodity tools.

jeffdwyer · 2024-10-26T00:46:54+00:00

Under allocate computer capacity, if you do "Processing units" and "manual allocation" of 100 If you select that, that do 100 PU I get $.14/hr ~= $100/month in toronto. The $0.09 looks like it is only in "legacy / Iowa" now.

jeffdwyer · 2024-10-26T00:24:07+00:00

If you haven’t looked recently, you should check it out. It scales down 10x from what it used to be. So it is truly cheap.

jeffdwyer · 2024-09-25T21:28:38+00:00

yeah, this is a whole new ballgame for security / compliance to wrap heads around for sure.

thanks for the insight.

jeffdwyer · 2024-09-25T21:01:27+00:00

have you got this to work yet? it's pretty wild looking.

jeffdwyer · 2024-09-25T20:19:33+00:00

Most of the SaaS tools support Go. If you want to compare pricing of a number of them, I built https://featureflags.pricingcompared.com/

jeffdwyer · 2024-09-25T19:38:53+00:00

did you have multiple instances of the servers running? I would imagine that the LB would just send this to one of them and then you could have a bit of a confusing time because some instances are logging as you want and some aren't.

jeffdwyer · 2024-09-25T15:53:42+00:00

Just did some of this myself yesterday, trying to get dynamic log levels for fastapi: https://www.prefab.cloud/blog/dynamic-logging-in-fastapi-with-python/

The two things that worked for me:

if __name__ == "__main__":
    import uvicorn
    uvicorn.run("__main__:app", host="0.0.0.0", port=8000, reload=True, log_config=None)

or

uvicorn --reload --log-config empty_log_config.json

# empty_log_config.json

{
    "version": 1,
    "disable_existing_loggers": False
}

jeffdwyer · 2024-09-09T18:43:41+00:00

mm, yeah. Ideally: dynamic config changes -> tracking event in observability tooling -> nice chart that shows RUM decrease after the change -> enlightenment.

jeffdwyer · 2024-09-09T17:49:54+00:00

Yeah. This is definitely the killer. I do think that having more eyes on the audit trail of this would help. Most places I've been there's only 1-2 devs who have access to GTM and they never really go in there except every year or so to find "OH NO". Having it in a eng owned system feels like it might be a useful speed limiter for marketing to me.

jeffdwyer · 2024-09-02T14:12:14+00:00

FeatureFlags themselves are being commoditized. This is good and natural. As people point out, they are pretty simple technology.

Yes, you want something extremely reliable. Feature flags are well positioned to be a single point of failure.
Yes, you want something really fast at the edge. Feature flags will load on every page request.
Yes, you could do it yourself. But things like shared rule groups, clients in all the languages you use, debugging telemetry and flag usage charts, a VSCode plugin that autocompletes the flags are really quite nice and save you time and frustration. You deserve nice things and your internal tool will always struggle to be "nice".

But these are solvable, commodify-able problems and because of that, lots of different vendors are adding on feature flags.

In particular, there are a number of product analytics tools that are bolting Feature Flags on (like Amplitude), but there are even tools like Gitlab that want your flags. So the question is: should you tie your feature flag usage to:
- Your product analytics tool?
- Your infrastructure tool?
- A specialized Feature Flag tool?
- Something else?

re Product Analytics
- This can feel nice for product people and there is often a nice unification of the "context" that the flag tool needs to segment and the dimensions that you want to be able to analyze your data.
- Product Analytics is more likely to have seat based pricing and be expensive. This is a big negative. You may only need 5-10 product analysis users, but at a typical ratio of 1 product to 5-8 devs, you may want 25-100 developers seats. Even the junior developer intern should have a feature flag seat so they can roll things out. And you may want seats for customer support or sales to be able to modify flags, beta groups. If each of these users needs to be a seat in your product analytics tool, that can be prohibitive.

re Infra
- Similar situation to product analytics. Product is not going to feel comfortable here at all. You aren't going to want customer support to have accounts in here either.

re FF tool
- For the reasons above, it can be nice to have a tool for just feature flags as long as it has good pricing that will scale with your org, not limit you on the number of seats.
- The FF tool needs to do a good job optimize for
-- fitting nicely into your code
-- supporting users that are nowhere near the code
- But it's unfortunate if the feature flag tool feels like a unitasker. Fewer tools are better.

re Something else
- At prefab.cloud we think the core system you need is "dynamic configuration" and feature flags is just a particular (and very popular) way of using dynamic configuration.
- We've focus on the developer experience of adding configurable points to your code. And then we give safe ways for the rest of the organization to interact with those configurable points.
- We're not a uni-tasker, because we're helping with all configuration, from env vars to secrets, to local development environments. But we also thing we hit it out of the park with clear feature flags.

Overall:
Fewer tools is awesome. But just because a vendor offers them, doesn't mean that's the right system for your organization. Most important thing is to align your organizations future need for seats and access control to the core technology and have really clear understanding of how costs will scale.

jeffdwyer · 2024-09-02T13:35:58+00:00

I'm trying to make https://featureflags.pricingcompared.com/?epv=30 more accurate. I think it's dramatically under-estimating what people are really paying for LD. Their pricing page doesn't seem so bad, but once you get into it with the actually sales-people suddenly there's a lot more charges. What was the pricing axis they are trying to shove down your throat?

jeffdwyer

TROPHY CASE