853 karma · joined December 14, 2017
Define real.
Oh... and... "Not all MBAs"
Or maybe your record isn't borked like mine is.
So far it doesn't seem like I was double-billed or anything, but I trust the BWB guys to resolve that if it does happen. But fulfillment might be borked, so let's see what happens when their back-end fulfillment systems try to make sense of this order. But, again, I trust them to fix problems if they arise. This is the first complaint I've had w/ them in over three years of being a customer.
Which is to say... I think there's less inventory than we would have seen had rates remained lower. But that's sort of unrelated to the issue of builders manipulating their rates of inventory creation (which I can't imagine they don't do, at least in response to macro-economic conditions.) The reason I think they should be treated differently is it takes a noticeable amount of time for a builder to build a house. First they have to negotiate financing and insurance, negotiate plans with the county, recruit a construction crew, etc. Home owners in the secondary market can respond to market conditions much faster.
https://www.lendingtree.com/home/mortgage/vacancy-rates-stud...
If you trust the data (some of which comes from the 2020 census), it implies a nation-wide vacancy rate of 11.67%. Which was lower than I suspected, but higher than @falcolas' guess at 10%.
Also... I think I saw something go by indicating prices were still falling, at least in some markets.
This is from last year: https://www.cnn.com/2022/10/22/homes/us-home-prices-falling/...
And more recently: https://www.msn.com/en-us/money/realestate/bay-area-home-pri...
Though that last one is a little confusing, citing data from the last three months in one section and data over 2 years in another. But it does (at least) make a nod towards explaining pricing in terms of supply and demand. I assert, and I think this is similar to @falcolas' point, that participation in the market by builders, foreign and domestic investors and banks has veered US house pricing noticeably away from true elasticity.
I do not damn builders for trying to increase their profits. We're a "wealth creation" economy, after all. But there does seem to be some conflict between stated national policy objectives of "affordable housing" and "profitable housing market." Alas, I bemoan the erosion of sensible policy-making in Washington. In the old days we would have just come out and said something like "we have affordable housing targets and will manipulate the market to achieve them." Now we're too spooked to say anything lest we upset the markets; or at least it seems.
Person 2: Here is a suggestion.
Person 3: How dare you offer a suggestion when someone asked for suggestions!
I think the best you can do is just search for "lisp on <platform>" or "FORTH on <platform>" and see if any of the hits are useful to you.
On the downside, the FORTH community seems to be shrinking and many people find postfix notation a bit of a brain-twister. While it's "kind of" portable, it's probably not as portable MicroPython. Both FORTH and Lisp "allow" you to build programming constructs other languages provide out of the box. This is a blessing and a curse. If you ever wanted to change the way a for(){} loop worked, it's not uncommon in these languages. If you just want for(){} loops to work out of the box, you may be annoyed by having to check whether the person who wrote the for(){} keyword in your language is doing what you want. (Forth has the LOOP keyword and lisps like fe or micro-lisp have various flavours of if you use to build your own control structures with macros.) I also imagine you may have to write your own drivers for anything more complex than a UART.
I've recently gone back to some of this as I'm working again with old controllers whose dev tools have atrophied. I spent quite a bit of time in the 80s building commercial products with FORTH and Lisp, so I've already climbed up the learning curve. I'm not trying to convince you YOU MUST use FORTH or Lisp, but they're interesting language / environments from a simpler time. ( "This is the tool chain of the Jedi Developer; not as clumsy or random as C++, but an elegant environment for a more civilized age." )
Which is to say... there's still some benefit in learning a little bit about these old systems in that understanding what their constraints and objectives were might help you create evaluation criteria for modern systems.
</snark>
This one reads off like BADGER-BADGER-BADGER-MUSHROOM, but it's GRAPH-GRAPH-GRAPH-HAYAK QUOTE.
Not only is someone trying to get rich off of hashes, they're trying to convince you any theory which suggests burning fossil fuels to calculate hashes might not lead to increased productivity is heretical.
I guess what I'm saying is there's probably no one factor that made '71 special, but a collection of factors; a "perfect storm" of economic sadness.
I mean... most of my daily effort goes into supporting a bank. There's A LOT of mainframe stuff. Some COBOL. Some guys using AIX (actually, a surprising number of guys using AIX) and (as mentioned previously, xterms and emacs or vi.) On the dev side there's more focus on file format standards than tools. So use whatever tool that generates files in the appropriate format. We probably could use Win11, but they started using AIX in the 90s and just never got around to moving to Windows.
You would think that Irving (in the heart of the D/FW metroplex) would be a place you would encounter homophobia, given the popular opinion of Texas. But people there seemed to not care who I was holding hands with.
Maybe we need something like "Tech Masons" where you have a built-in social group, continuing ed and everyone promises not to disrespect each others' tech stack decisions. "Oh. So you're going with COBOL? I'm sure there are aspects of the project I don't understand that make COBOL the ideal language for that project. Let us grab a beer and talk about inverting trees, brother (and/or sister.)"