swearwolf
Joined 5 years ago
Joined 5 years ago
2.) The U.S. is not a monolith, so looking at the prison population of the United States as a whole doesn’t tell you about what’s going on in an individual state or city.
3.) The number of people incarcerated has a long tail. In the U.S. in particular, many people received long sentences during the years following the ‘94 crime bill. Little if any effort is being made to commute these despite policies centered on new incarceration changing.
4.) In the places where reduced incarceration is being tried in the U.S. it’s important to recognize that it’s being tried effectively in a vacuum. In many other places which are able to sustain low incarceration rates, there are a lot of social programs that help make that possible, and also programs to help people rehabilitate after a conviction. The U.S. has little if any of that. Where reduced incarceration is being tried, it’s usually not replaced with something that’s more effective.
If you don’t believe it, pull up Zillow or Redfin and set a price threshold under $1M and see how many listings instantly disappear. If you want a good laugh, take a look at what’s left.
Which should tell you something about why your friends in SoCal don’t want to live in those cheaper places.
Basically the bank issues a loan to a developer, based in part on how much income the developed property is expected to bring in. If the expected revenue isn’t coming in (say because the rent is too high), the bank doesn’t always want to admit that it’s a bad loan and call it a loss, so they extend (the length of the loan) and pretend (that the rent the developer is trying to charge is realistic). This incentivizes the developer to keep the high rent as-is even though nobody is going to pay it.
A case of terrible incentives causing terrible outcomes.
0.https://www.wsj.com/articles/SB10001424052748704764404575286...
Just a thought.
Also, no company I've ever worked for makes their budget after asking people what they need. Instead, the Finance team just copy-pastes last year's budget, usually with a little haircut off the top for "efficiency." So let's say you run a team that depends on a handful of servers. You bought the current ones five years ago, and it cost $500k. Now it's time to replace them. But since you didn't buy $500k in servers last year, it's not in the budget for this year, so now your entirely reasonable request is being scrutinized as "unplanned spend". Several times I've seen teams try to build a plan for the upcoming year, only to find that there's nobody to give it to, because the "budgeting process" is done in about a week's time, usually two or three weeks after the fiscal year starts and with commensurate effort.