That is actually quite nice. I’ve been toying with the idea of mandating this 10% maximum margin for products and services on every for-profit company.
Trouble is, how do you prevent them making stacks of companies compounding the 10% profits. And is 10% sufficient to build up a buffer for when hard times hit?
This thinking has been triggered by fuel producers and sellers making sky rocket profits because of the increased oil prices. The same as the overheated graphics cards.
You hit on what, in my opinion, is the actual core issue with this type of thinking -- it doesn't compose.
To make a poor analogy to physics: if you measure something which changes when you change unit/frame of reference -- it's not a well-defined thing.
The best policies have the same effect regardless of the legal structure (within the policy) superimposed on the actual action.
Medium policies can be optimized/gamed (perspective) -- but are designed to be adversarial, in that the gamed outcome is at least OK but potentially in fact the desired one (for example -- if you tax land, then not paying the tax means not using up land, which may be a desired policy goal).
These can cause issues, though -- common law is an adversarial system, and "justice" can usually be translated to "access to lawyers," imo.
The connection with the above is that while the solution used is probably not universal -- sometimes, the optimal solution is, so the adversarial policy is just an approximation of "good policy".
Bad policies not only don't compose -- but then bureaucrats go on and insert discretion to try to make them compose. On the surface, this often looks like common sense -- but the result is insiders can keep doing the Bad Thing, but you can't do anything which isn't the Way Things Are Done -- because you need approval, and it Looks Bad.
Absolutely and costco has other interesting business model mechanics that make that margin feasible. Membership fees of course but other things as well. Like the fact they are all warehouses they don't have intermediate warehousing or unpacking like say Target does.
Yes. Unfortunately transit between public transit is always walking. No options to take a first part by bike or car, or folding bikes for intermediate hops.
The long tail of user desires is loooong. For example "I want to take transit, but please exclude transit options where I cannot take my non-folding bicycle". Or "I don't have a raincoat, suggest only bus stops with a roof, oh and by the way I don't like the uncomfortable seats on the purple line but will take it if there is no other way".
I think LLM's with access to lots of personal data and the ability to scout the web might solve all these use cases in one fell swoop, rather than trying to design a user interface with buttons, algorithms and data sources for every obscure use case.
I disagree. They should bring quality back before reintroducing more changes. Okay, maybe that means dropping Liquid Glass. But also readopt the HIG. Increase stability and performance and reduce attack vector.
It has been on iPhones for quite some while, but on androids even longer. Before that it was in the form of some smart charging scheme that it would only finish charging until the moment it thought you would unplug it.
The added cost of having an additional person to provide room and food for way exceeds that €300/month. Especially, when taking into consideration that you might have to extend/renovate the house to lodge another person. Adding an extra bedroom and possibly bathroom is not cheap.
Even if you assume the cost of lodging was 1000€ (which it isn't) then the au-pair would still be significantly underpaid.
A normal full time employee costs at least 2000€ a month (salary, tax, pension plan, health insurance, etc). If you are paying less than that you are definietly exploiting them.
Off-Topic: Are you sure delivery is free? When comparing prices online vs my local supermarket of the same brand, online prices trend higher. Locally the store also has more products on sale than available online. Only recently online shopping has become slightly cheaper because they now have “bulk” deals for 5-20% discount.
In my perception there is a difference between 1req/s as a rate limit, and 60/min. The difference has to do with bucketing. If we agree that the rate limit is 1/s, I expect to be able to exactly that and sometimes 2 within the same second. However, if we agree on 60/min, then it should be fine to spend all 60 in the first second of a minute, or averaged out, or some other distribution.
This also helps with the question I always get when discussing rate limits “but what about bursts?”. 60/min already conveyed you are okay to receive bursts of 60 at once, in contrast to with 1/s.
In my experience it is exactly the low rate service that care about rate limits as they are the most likely to break under higher load. Services that already handle 100k req/s typically don’t sweat it with a couple extra once in a while.
An effective rate limiting system has multiple bases in my experience, depending on what the goal is. But I usually implement the configuration as a list where you can define how much requests are allow maximum per how many units of time.
E.g. to prevent fast bursts you limit it to 1 request per 1 second, but to avoid someone sending out 86400 requests a day you also cap them at 100 per 86400 seconds (24 hours) and 1000 per 3600 seconds (1 hour).
Whichever limit they hit first will stop it. That isn't hard to implement if you know how to deal with arrays and it allows long term abuse, while still along fast retries if something went wrong.
That is why you would do it before you let your phone go out of sight. I used to even turn off my electronics to prevent damage by scanners. Now I don’t bother anymore but it could be a plausible excuse.
One of my favourite experiences coming up as an engineer was working with a very senior engineer right in the beginning. Whenever he had a task or problem, he would start out thinking, maybe doodling a bit on paper, go for a walk, and only then sit down at his computer and start typing. He would type in one go only compiling in the end, and it would work. (Even typos were rare.)
All this to say that it is extremely useful to have the program and the problem space in your head and to be able to reason about it before hand. It makes it clearer what you expect and easier to catch when something unexpected happens.
I see some of the value in planning, but experimentation is so cheap, there's also a lot of value in trying it, seeing what works, and learning from it. The main drawback I see from experimentation is failing to understand why something worked.
Trouble is, how do you prevent them making stacks of companies compounding the 10% profits. And is 10% sufficient to build up a buffer for when hard times hit?
This thinking has been triggered by fuel producers and sellers making sky rocket profits because of the increased oil prices. The same as the overheated graphics cards.
reply