You know the story about how the frogs, thrown into a hot pot will jump out. But, if you turn up the heat slowly, they just eventually die? Well, the other day, at work, we were called into a room to watch a mandatory video of frogs in this environment. I actually noticed that management had turned the thermostat up really high. I hopped out of that meeting very quickly.
I arrived in a small airport at midnight. Served only by Uber. Since I use Lyft elsewhere, my phone had deleted the Uber app. It took 15 minutes to download that: crappy Wifi and some kind of 5G dead zone. Sometimes you really need to download the app.
Code size would balloon if you try to format verbose error messages. I often look at the binaries of old EPROMs. I notice that 1) the amount of ASCII text is a big fraction of the binary 2) still just categories (“Illegal operation”). For the 1970s, we’re talking user programs that fit in 2K.
I write really verbose diagnostic messages in my modern code.
There was also an implicit saving back then that an error message could be looked up in some other system (typically, a printed manual). You didn't need to write 200 chars to the screen if you could display something much shorter, like SYS-3175, and be confident that the user could look that up in the manual and understand what they're being told and what to do about it.
IBM were experts at this, right up to the OS/2 days. And as machines got more powerful, it was easy to put in code to display the extra text by a lookup in a separate file/resource. Plus it made internationalization very easy.
You seem to know Houston; alas yes Austin was formerly surrounded by open spaces.
But let's not miss the point of the article. This is a right-ward shift of the supply curve. It means that the economics of building the next unit got cheaper. That's the point.
I've seen a lot of neighborhoods across the USA, and Austin making way for higher-density housing on urban corridors (Lamar) is like, duh, this is more live-able. There are new towers along rail and bus route, townhomes packed in, and behind the tree line it's now possible for some single-family lots to become duplexes or fourplexes. And rather than McMansion ugly, the new Austin residents are dressing those up to look pretty darn cool.
There is a lot more to be done to remove supply-side barriers in every city.
See the photo in the above East Side article. In the old neighborhood, people talked to the photographer because the front yards didn't have privacy fences.
I don't think many home owners got a price for their land that allowed them to buy a similar house elsewhere.
The world is far from an ideal model where what you get is what you deserve.
Note the history of the East Side power plant, which depressed property prices. Ditto, I-35 construction plans. The article says the plant will become a park now. After the new developers locked in purchases.
You see this business model everywhere. They buy up all the land around an industrial site, small airport, race track, pig farm that smells bad, etc, etc. Then they and their Karens lobby for rule changes that force that use out or make it non-competitive in the broader market. Then they develop the land.
Nothing will fix it until some case goes up to the supreme court and results in some sort of "they were there first the .gov can piss off" doctrine.
/* If we can cache this partial result, and guarantee that the cache stays coherent across updates, then average response time will converge on O(log N) instead of O(N). But first make the response pass all the unit tests today */
I don't think that phrase means what you are trying to say here.
What it doesn't mean:
- learning by doing
I believe it generally means: a formalization that comes after a subject is understood so well that you can reduce it to "first principles" that imply the rest. Or, the production of a hypothesis by deduction from widely-accepted principles.
reply