> AWS doesn’t charge you in mysterious ways. It charges you in specific, predictable ways that nobody taught you to look for. That’s a knowledge gap. The purpose of this post is to shed some light on this.
Or it's a UX gap. If this is such a common complaint that's causing meaningful reputation damage, surely there'd be a better way to communicate this in the product? I think it's fair to assume that there's less interest in building features that encourage users to spend less money.
Agreed. AWS is downright hostile about giving you any idea about what resources you actually have deployed, to the point where it must be deliberately malicious. Even their billing page is terrible for tracing down the root cause of usage with the default configuration.
You have to go into third party tooling if you want any chance of seeing what’s actually going on, especially if there’s any odds of you deploying stuff in another region and even moreso if you have more than 1 account.
At this point, I’d say it should be a best practice of owning 2 AWS accounts, even as a hobbyist: one payer account with a HEAVILY locked down SCP and then a child account with the stuff you’re deploying.
Or they're charging people in at-best mysterious if not outright duplicitous/malicious ways because it makes them money without having to do anything (save for send a bill and have the right fine print in the right places. )
It's no accident, it's not just "bad UX", it's deliberate.
> AWS doesn’t charge you in mysterious ways. It charges you in specific, predictable ways that nobody taught you to look for. That’s a knowledge gap.
Observe the mental gymnastics to explain away "mysterious ways" by making it the users fault and calling them - *checks notes* - stupid, for not knowing something AWS is very intentionally keen on you not knowing.
I sure hope OP was getting payed for this AWS ad, imagine shilling for a multi-billion dollar company for free.
It's the UX, deliberately omitting information or not. There at least used to be some toggles for example without any indication that they mean anything other than a minor load balancer configuration change, but caused I think $200 month bill addition. No indication at all that they have a meaningful monetary impact.
Reading what they're offering, the stand-out to me is making publishing the applications easy for others on your team to use. That would he a pain point for non technical users.
I get your point. But if sharing with others is a vital part of this, then ... they'd be better off sticking to web apps instead :)
"Create with glaze, hit publish and we'll give you an url".
Even though they portray some of the benefits of this app as unique to desktop apps, they're not (e.g. storing data on device, offline mode etc.).
Am not a hater. Love Raycast. Saw the post and opened the link intrigued what they came up with and was somewhat disappointed tbh. Good luck to them anyway!
Most organizations I've set Sentry up for tunnel the traffic through their own domain, since many blocking extensions block sentry requeats by default. Their own docs recommend it as well. All that to say, it's not trivial to fully block it and you were probably sending telemetry anyway even with the domain blocked.
With the right tricks (CNAME detection, URL matching) a bunch of ad blocking tools still pick up the first-party proxies, but that only works when directly communicating with the Sentry servers.
Quite a pain that companies refuse to take no for an answer :/
"South Korea is second from bottom on our list in terms of the proportion of people saying their country “is heading in the right direction”, with only 15% stating so. A similar sentiment is also felt about the economy. Pessimism is usually the standard for South Korea; however, their economic indicator score has been particularly low in recent times, with just 8% believing the economy is “good”."
I'm not talking about how people feel about their life or country but about the concrete actions their governments are taking to improve their quality of life. For example, they all have high speed rail, something that is essentially impossible to build in the US, whether it be due to budget, regulations or sheer political will.
Florida's Brightline contradicts that, no matter how slow California's HSR project is going. Trust in greed if nothing else. The next one to go up will be LA to Las Vegas.
I assume the startup wasn't also leveraging typescript heavily on the frontend, that tends to shift the weight in its favor. Having one set of tools to use across everything, being able to share logic and types without needing to go through lossy translation layers, and giving (especially small) teams better flexibility to move people around is a huge benefit.
But the reality is that at some point, your FE and BE teams will diverge anyways and we use an OpenAPI spec as the contract (Nest.js, not Next.js).
So there was no benefit to using TS on both ends; only pain on the BE.
If a team is going to ship an OpenAPI spec and run it through a transformer, then it changes the selection criteria for a BE language:
- Easy for a TS team to adopt; similar core semantics like `async/await`, exception handling, etc.
- Flexible and pluggable OpenAPI spec generation for edge cases and advanced scenarios
- Excellent ORM to improve productivity around CRUD
- Good tooling
- Extensive docs, platform maturity, but modern language features
C# meets all of those in ways that no other language and platform does.
I can't speak to your use case, but for past projects I've not only wanted to share types but actual logic. For instance, if you want instantaneous validation on the frontend, while applying the same logic on the backend with submitted data. In many instances that would be simple and maybe even serializable, but in my case I was working with architectural data that had extremely detailed logic for what was and was not valid.
Using a TS validation library like Zod gives you both the shared validation code for both the frontend and backend, the TS types, as well as the json schema for openapi. It's a triple whammy too good to ignore. Especially as a small team it is huge leverage enabling you to go further faster.
Or it's a UX gap. If this is such a common complaint that's causing meaningful reputation damage, surely there'd be a better way to communicate this in the product? I think it's fair to assume that there's less interest in building features that encourage users to spend less money.
reply