I keep saying that permitting should be - broadly - same as driving.
You get handed a nice set of rules, you get tested on them.. and then you can go ahead and build within those rules without asking anyone for permission.
If you break the rules - we break your piggy bank to set everything straight. You can buy insurance (which will have its own set of rules) - or not.
Maybe in some jurisdictions you need to buy insurance, while in others you get to have a choice.. after clearing it with your financier.
Zoning is actually rule-making. Permitting is just bureaucracy. Keep them separate.
This is called as-of-right development or by-right development, which is how things (nominally) work in several states. That is, as long as a project adheres to the zoning and other regulations, approval is as-of-right or a so-called ministerial process.
It's not necessarily a black or white approach. In theory as-of-right is supposed to be the rule everywhere as Due Process guarantees mean government can't act capriciously. And there's actually pre-existing SCOTUS precedent regarding how zoning plans are supposed to be applied, and how community input processes aren't supposed to allow mobs to subvert the rule of law with a de facto but informal veto power. In practice, non-as-of-right municipalities and states basically have zoning rules and approval processes that are fuzzy and ambiguous, effectively granting regulators significant interpretive leeway and discretion.
Federal and often state courts are extremely reticent to jump into the fray and defend the rule of law. In fact, there's SCOTUS procedural jurisprudence designed to make it difficult to "make a federal case" out of zoning disputes. NIMBY battles are just too politically fraught and courts are afraid of falling into the bottomless tar pits of adjudicating public grievance, which is what politicians are supposed to be for.
California is especially bad for multiple reasons. First is CEQA, which allows literally anyone in the state to erect legal hurdles to any project (modulo some very recent carve outs). Second is home-rule principles enshrined in the state constitution, which makes it difficult for Sacramento to force municipalities to behave a certain way or even abide many mandatory state regulations--the state often has to rely on indirect means, such as contingent funding, to cajole cities. Third is California Supreme Court procedural principles that demand state courts entertain law suits in a way that allows interlopers to drag out court cases, e.g. CEQA cases, for long periods of time.
I’m aware of this - what I’m curious about is whether we can go a step further and skip the “as by right” process.
This is similar to the difference between “shall issue” and “constitutional carry” states.
In the former you still have to deal with the system to exercise your right, and the system has to have staff to deal with you.
In the latter you’re approved - without anyone being on a taxpayers dole and having an incentive to keep themselves employed by enacting more laws and keeping the system inefficient.
Imo this should be the biggest political issue. By-right zoning and permitting accross the board. So much graft, corruption, waste, and stagnation from discretionary approval/denials.
Don't want factories zoned next to elementary schools? Perfectly reasonable rule, but then you don't get to pass a variance for the mayor's nephew's cousin's factory. And vice versa.
And it’s also the question of different use cases.
Asking to trust in an authority (while the main authority Microsoft/GitHub has is essentially figuring out enterprise sales well enough to be acquired by a company desperately needing developers after fumbling badly in the 2000s) is exactly the opposite of my stance - it is a large corporation, with heavy employee rotation, with substantial exposure to various forms of regulatory pressure and to various forms of corruption.
Which is why the cryptography exists to prove the developer-to-consumer trust without trusting the intermediaries. Yes, I do check GPG signatures. Yes, I do include a git commit hash in the binaries I build. And surely I want to make sure that this doesn’t mutate because some unknown engineer at GitHub had a bad case of gambling debt.
Well, there are two big equivalents here:
One, Uber successfully lobbied cities (NYC DeBlasio comes to mind, but there was one in London) - getting to a scale before meaningful enforcement action (which sometimes means investors maintaining their trust in the team, and the team sticking through the lawsuits) usually means you now have a customer base that is of voting age, and can substantially impact politics.
Two, Chevron deference is over. This is linked somewhat to the first - the overreach of federal agencies is now judicially balanced against the economic impact, not merely presumed authorized by Congress. Under this SCOTUS it is relatively uncertain which way FDA's authority will be curtailed - people will try, the fact that FDA wants to regulate the sale of non-invasive diagnostic equipment and mobile apps.. does warrant review and political discussion.
This is even more interesting (full disclosure - I vibecoded a lib for it lately - lowzag) when you take into consideration working set restrictions.
In almost every case, downscaling-while-decoding is going to beat decode-then-scale on performance - merely keeping the uncompressed image in RAM is going to cost you, when you can scale it down in L1 or even vector registers.
I'm actually curious if nowadays some ML-based algorithms are not beating Lanczos 3-lobe to it - at least in perceptual quality of the downscale. The have /long/ surpassed it in upscaling.
As a scientist and an adult immigrant to the US, I came to appreciate both systems as useful for different objectives.
Celsius/Metric is neatly rooted in science - where it truly shines by removing /most/ of the conversion factors (but does it? we still have, today, speed of light that should be 1, Avogadro and Boltzmann constants are just odd numbers you memorize too) - but doesn't match neither everyday weather and life (0F being "coldest you'll experience in a place humans commonly live" and 100F being "hotest", and close to wet bulb temperature and, through a fluke of an undiagnosed fever of Fahrenheits' wife, nice threshold for fever).
Fahrenheit/Imperial is actually relatively convenient to machining, industry and agriculture (but not engineering or science) - how much of that is actually fractional measurements (1/16th makes a ton more sense than 0.0625), and how much are the "fingertip/decent meal/daily water intake/sustains a person" idea of an inch/lb/gal/acre.. is quite intuitive. Far more so for composite units. 1 PSI is intuitive - you know what force to exert at what area of a piston, same for torque'ing to 80 lbs-ft.
But.. it makes a ton less sense when you separate N from kg (yeah, I am a physicist, I know why, it just makes less sense when building stuff in a dirty corner of an industrial revolution), then somehow apply it to a whole square meter to get a Pascal, and now you need decimal fractions of a million of those.. to represent what you actually see. Quick, do you think you can plug a 2cm diameter garden hose at 0.5MPa with your thumb to spray your dog?
CGS system was quite popular and useful, IMHO for that reason, at the time when Europe was actually manufacturing stuff and inventing them in barns and factories. But it was essentially "neither" - bastardization of sacred kg and meter - lost to SI.
US keeps inventing and making stuff in garages and fields.. and it shows in its devotion to imperial system. But I can see convincing mechanics to 1/8th of a cm and 40g way before I can see them taking up 1.25 mm and 0.04 kg.
I accept that psi is more intuitive in many cases than Pascals. But I remain unconvinced about Fahrenheit. I reside two places during the winter. One has temperatures around 0C, and the difference between -1C and +1C is much more important than the difference between -1F and +1F, it's the difference between rain or snow! The other place regularly sees temperatures around -25C. In both places -18C is just some random uninteresting temperature, letting it be 0 is... disturbing.
Well, the reality of those types of businesses is that once set they do become a relatively low maintenance (and for some, very low 'urgent' maintenance) passive income.
It's really easy to pull $300k/y as an SRE (but that does amount to about $100/hr equivalent in SMB, assuming realistic >40h workweeks and the tax advantages in SMB, even less if you have to pay for services you enjoy and can't find time for due to FTE - nannies or even changing your own oil).
It is extremely hard to keep that $100/hr and a sliding scale - one week you work 50h, the other 30h, then you take a month or three off at $5h/week.
Mine (and I don't regret these) is running midsize PV plants. Slightly bigger than residential (hey, does OP want solar PV on the rooftop? I have a bowling alley as a client, they are a great match), but again not large enough to attract a scaled business.
I approximately put in 5h on each a year after the initial setup (around 100hr each), for $10k/y in profit from each.
You get handed a nice set of rules, you get tested on them.. and then you can go ahead and build within those rules without asking anyone for permission.
If you break the rules - we break your piggy bank to set everything straight. You can buy insurance (which will have its own set of rules) - or not.
Maybe in some jurisdictions you need to buy insurance, while in others you get to have a choice.. after clearing it with your financier.
Zoning is actually rule-making. Permitting is just bureaucracy. Keep them separate.