I agree, it is an interesting thing to ponder. I often phrased it to myself that the cost of technical debt compounds the lower in the code stack you go.
Said another way, tech debt has a multiplicative factor the farther away from the end user you get. Tech debt in the database is worse than in the data layer. It is worse in the data layer than in the business logic. It is worse in the business logic than in the UI code. etc.
This is related to the fact that it gets exponentially more difficult to refactor code the farther away you get from the end user. Changing the database is usually more difficult and impacts more things than the data layer code. And on and on we go back up.
So beware, i setup my APP3 on my daughters ipad and had hearing aids set with a hearing test. This way when connecting to my Pixel it would still apply the hearing aid adjustments, but I would not have other things like auto-pause when removing the airpod.
Well, I installed this and now my hearing settings have been removed from the airpods. And I guess you could say that this would be obvious because librepods doesn't support the hearing aids, what is not obvious is that installing it takes a set of APP3 that has been already setup and basically wipes them. Good to know for the future
I agree. I see a lot of comments alluding to the 'regulations' being bad. They are there for a reason. To keep errant bankers from loaning out too much money and creating an even more fragile system.
People have to realize that banking as a business is inherently broken. It is about lending long and borrowing short, which is very risky. Deposits are used to provide funds to lend long, but deposits can be 'called' at any time. The loans cannot.
But banking is also critical for a properly functioning society. It is in the government's (the people's) best interest to have a robust banking system in place. How to reconcile the risk with the benefit? By heavily regulating it.
Another thing that I read about on this topic was that once a land lord has gotten into a groove of extend and pretend they lower their costs and cut out the overhead of property management. This means that if they took on one tenant they would have to ramp up property management costs (and potentially refurb/improvement costs) and they are not willing to do that, so you end up with the situation where you can't rent a property even if you want to.
Interesting. Prices, as they say, are set at the margins - so given that, what kind of liquidity is there? How many are transacting? If the price hasn't shifted from $16k, it could mean that everyone thinks they are worth $16k, OR it could mean that no one has bought one in years and the last transaction was $16k. Those are big differences.
50% is a stretch. 20% maybe, depending on the vehicle.
But here is another consideration. Sales tax. If I buy a car and trade one in, the sale price that I pay taxes on is the price of the vehicle I am buying minus the trade in.
For instance, if I buy a new car for $30,000 and trade in a vehicle and they give me $15k for it, I pay sales tax only on $15k. That saves me about $1k in my area in sales tax. If I could have sold the used car for over $16k, then I would technically be money ahead. But your time is also worth something. For it to be worth it to me, I would need to be able to get at least $17k for the used vehicle to make it worth the effort.
ok, so please don't take this wrong, but that last sentence was such a non-sequitur that I think I know what at least some of your problem is talking to other people.
EDIT: wait, I am going to go out on a limb and say that you meant
"I was in a car crash of a conversation one time and my buddies pulled up on the scene and gave me a ride home."
Thats funny because I thought it was shift-enter that creates a newline in a field where an enter submits. Just shows the fractured nature of this whole thing.
It's called Tragedy of the Commons, and it is just how things are unfortunately. I don't like it either, but if it wasn't this guy it would be someone else.
> selling an oversubscribed product with baked in usage assumptions is a functional business model in a lot of spaces
Being a common business model and it being functional are two different things. I agree they are prevalent, but they are actively user hostile in nature. You are essentially saying that if people use your product at the advertised limit, then you will punish them. I get why the business does it, but it is an adversarial business model.
I've never been as scared in a car as I was in an Uber in Chicago going to the airport. That man drove around cars like we were bleeding out in his car and had to get to the hospital or someone was going to die.
I love this. Thank you for introducing me to "Norman Doors". I hadn't realized someone else had described this in such detail. I have been complaining about this years.
Ok this will be a tangent, but I also take this one step farther and also talk about "documentation". Just for the record, I don't think documentation is all good or all bad, but it definitely can be used incorrectly and in excess. And Norman Doors and a great way to get this point across.
When someone creates or installs a Norman Door by accident or out of ignorance and then realizes there is a problem, they often think "I know, I will document it!" and they add little placards to the door that says "Push/Pull" or some such. They see that this helps with a small subset of users and thinks "there, I fixed the problem, people just need to read the documentation and now it is their problem if they don't". But if you watch users of the door, a large portion will still use the door incorrectly because... people don't read documentation. If they don't read documentation, is it the users fault the door was designed incorrectly or was it the designers problem?
I use this as an example for my developers on thinking before documenting troublesome code or a confusing interface to first ask "can I design this so it is less confusing?" and if so, that would usually be preferable to adding documentation "to solve the problem". Well designed code (or doors) with no documentation always beats poor designs with documentation.
The point is that the 'maximum motivation level' for an employee is an inherent trait. It is a ceiling. Some people have high ceilings and some don't. If an employee has a low ceiling, no manager can motivate that employee higher.
But if someone has a high ceiling, the most a manager can do is create an environment that allows the employee to achieve their max potential. A bad manager on the other hand, can very easily bring a normally high-potential motivated employee down to mediocre levels.
If you are one of those self-aware leaders that knows how to create an environment where people can excel, then hiring highly motivated people is the winning strategy.
Said another way, tech debt has a multiplicative factor the farther away from the end user you get. Tech debt in the database is worse than in the data layer. It is worse in the data layer than in the business logic. It is worse in the business logic than in the UI code. etc.
This is related to the fact that it gets exponentially more difficult to refactor code the farther away you get from the end user. Changing the database is usually more difficult and impacts more things than the data layer code. And on and on we go back up.