I don't think vibe coding is going to last long as a thing, because it's just a sort of intermediate step to telling the AI to do what you want and having it do that. Right now, people are telling the LLM to write code to accomplish a thing and then running the code to see how it works, then telling the LLM to refine it, but that's a lot of unnecessary extra steps. I'm sure that in the not-too-distant future people will just tell the LLM what they want to do, which may require creating a custom user interface to make user interaction convenient, and may require creating databases or performing network queries or whatever, and the LLM will understand what they want, and do it.

In that future, it's possible that the LLM may generate code to implement the requested functionality, but if it does so that will be a compute-saving shortcut, essentially a way to cache the LLM's work and be able to repeat it with less effort. There won't be any need to show any of the code to the user, or even tell the user that the LLM chose to generate some code.

As an aside, the whole notion of leaning "prompt engineering" is another intermediate step that will die. The whole point of natural language-capable AI is that it will be able to understand what humans want when we express ourselves as we would to other humans. As the LLMs get more capable, it will become less necessary to treat them as something different from an entity that is fully capable of understanding and acting on human communication.

One of the things Android did very right with the Rust transition was to set up a small team of people who were entirely focused on Rust support. It wasn't a large team, only 2-6 people (it varied over time) out of approximately 1500 engineers. Having that core team who either were or became deep Rust language and toolchain experts was critical to smoothing the path for everyone else. It provided a group that had the knowledge and bandwidth to solve the problems that inevitably came up, as well as to offer advice and code review support to the early adopters.

That group no longer provides code reviews and design advice because Rust knowledge is now widespread enough that teams have their own, homegrown, Rust experts (not people designated as Rust experts, just engineers who became enthusiastic and dived deep), but the group still exists to resolve complex technical problems with language integration and to work on improving tooling and performance.

I think any shop adopting Rust (or any new language or complex tool) needs to have some people who become deeply expert in it and are allowed the time and freedom to support others who are picking it up.

So does Android. Google has been a primarily-C++ shop since its inception and although I'm not sure if Android had a lot of C++ in it when Google bought Android in 2005, it definitely became a C++-based system as soon as that happened.

The highly-segmented architecture of Android really helped facilitate the transition. Most of Android is structured as a web of collaborating services that communicate through a common language-independent [*] IPC mechanism (binder). Implementing Rust binder IDL generation and support libraries was a moderately big job, but once that was done it was easy to begin writing new system components (or replacing existing system components) in pure Rust, generally without any unsafe blocks at all.

If your code runs as a monolithic process, or has a lot of different IPC mechanisms, or uses a lot of existing libraries, it will be a lot harder, and the benefits will come slower. You'll have to wrap a lot of C interfaces in Rust -- and they will have to be C, not C++, since there isn't a good way for Rust to interoperate directly with C++. People are working on that, but it's a very hard problem and at present the best option is to layer a C interface on top of your C++ code, then wrap a Rust interface around the C interface. Yuck. Or, in the alternative, insert some other language-agnostic boundary between them.

So in a lot of ways Android got lucky because of its modular architecture and single, language-agnostic IPC mechanism. OTOH, that wasn't really "luck", it was a lot of work, done for good reasons, one of which was cross-language compatibility, notably between Java and C++.

[*] Language independent-ish, maybe I should say. The binder IDL is definitively Java-based, but this maps fairly nicely onto OO languages that support common primitive types (int, char, enum), basic composite types (array, vector, class/struct, string (which is just a vector, but used enough to be worth treating as a first-class thing)) and Java-like methods (fixed argument list, single return value). Further, it's based on "old" Java, before Java acquired functional extensions, when doing things like passing method references as argument was uncommon, and therefore not supported. So it's moderately-expressive but avoids things that get weird and complicated. My one big complaint about it is that I wish it supported unsigned integer types. That's my biggest gripe with Java, too.

The cores do not lat 60 years. Roughly 1/3 of the core is replaced every 18 months when the plant is shut down for refueling. This means that any given fuel rod lasts about 4.5 years in the core before it is considered spent and removed from the core and put into storage as spent fuel.

The main question is if the plant is still safe. It hasn't been used in years. Is it still in good maintenance? Was the design meant to be idled for years? What are the risks of restarting that particular design of reactor after all those years? Is the land there safe for workers of the plant after reactor 2's accident all those years ago? And what plans are in place to prevent what happened at reactor 2 from happening at reactor 1?

I actually don't know the answer to any of those questions. But I hope experts are actively asking those.

When in the history of humanity has there not been a big problem coming? Or occurring, for that matter.

The problem in this story is not the wealth, but its form. Cryptocurrency transactions are generally irreversible and not subject to the layers of process and protection that have been built up around large banking transactions. Keep your money in banks and brokerages like a sensible person and you don't have much risk.

Uh, yes, the 24-hour cancellation option is always the most expensive one for a given room (ignoring paying extra for add-ons like free breakfast or extra points). What other option would be more expensive? The one that gives the consumer the most flexibility is the one with the highest risk to the property, and that's priced in.

Yeah, TFA overstated it. Though if you're not booking through the chain directly, in many cases it is hard to get a 24-hour cancellation policy. Many of the travel aggregator services hide them.

Yep. That's all true even if AI is the most transformative technology ever invented, even if it generates trillions per year in economic output -- it might not do it soon enough to prevent another crash. You don't have to believe that AI is "sand-castle based or vapor based" (which it's really not) to see a big problem coming.

The market can remain irrational longer than you can remain solvent.

The better strategy, IMO, is to keep your money safe and wait for the bubble to burst, then pile in for the recovery. Where to keep money safe is a good question, though. Just holding cash might be risky if inflation comes back, and the current administration seems anxious to pump up inflation.

There's a pair of seriously bad assumptions underlying your analysis:

(1) What AI does right now is all it's going to do. Given the way capabilites have grown recently, this is a ludicrous assumption. Keep in mind that ChatGPT was launched November 30, 2022... it's less than three years old! And the reasoning models are barely a year old. There is no reason whatsoever to assume that this technology has peaked.

(2) We already know how to take full advantage of AI. Every time a new technology comes along it takes decades for us to fully understand how to effectively use it, and to deploy it everywhere it is useful. I'd say we still haven't fully incorporated the Internet into our society, and we've been working on that for over 30 years now. We're barely beginning to understand how to use what AI we've already got, and it'll take years, if not decades, for the full economic benefits to be achieved -- and in the meantime AI is probably going to continue improving.

The AI thing absolutely is a bubble, but it's not "sand-castle based or vapor based". It's very real. The problem is that the massive wave of investment is going to have to start generating returns within the next 3-4 years or else the financial deals that underpin it all will collapse. That doesn't mean the technology will disappear, it just means that the current investors will lose their shirts, other people will scoop up their assets at firesale prices, and those people will figure out how to deploy it effectively, and create trillions in economic value.

Well, assuming AI doesn't just kill us all.

It's like the railroads. Enormous fortunes were made and then lost as the railroad boom played out and then the bubble burst. When people were driving hard to push rails across the continental US, the business case for doing so wasn't there. Yes, linking the east and west coasts had some value, but not much, since there really wasn't that much on the west coast. And there was a whole lot of nothing in between. But it was obvious to everyone that when the railroads connected the coasts and opened access to the interior, there would be enormous value. What exactly, no one knew, in the sense that no one knew where all of the railroad-enabled interior cities would be constructed or what kinds of things they would do. But it was clear that there was value in access to all of that land and that someone would do something with it.

On the other hand, realizing that value didn't happen right away. It took decades for all of the land granted to the railroads to become really valuable, because it wasn't valuable until people came and built farms, dug mines, established ranches and generally built lives and industry. The return on that massive investment was there... but it came far too late for most of the people that invested it. Lots of bankruptcies resulted, and others swooped in and snapped up the resources for bargain-basement prices, and they're the ones who became incredibly wealthy (well, they and the ones who supplied the steel, e.g. Carnegie).

It's been the same with pretty much every technology-driven bubble. Remember telecom/dot-com bubble in the 90s, with all of the "dark fiber" that was laid everywhere? Bankruptcies and consolidations resulted, and all of that fiber got lit up and used. That bubble built the Internet, and huge fortunes were made as a result -- the top half-dozen most valuable companies on the planet are all a direct result.

OpenAI and Anthropic are betting that this time will be different, that the payoff will come fast enough to pay back the investment. Google is betting this somewhat, too, but Google has scale, diversity and resources to weather the bust -- and might be well-positioned to snap up the depreciated investments made by others. If history is any guide, OpenAI and Anthropic are wrong. But, then again, AI is fundamentally different from every other technology we've created.

Like most racists, your critical thinking skills (assuming you have them) are shoved aside by overwhelming confirmation bias. Otherwise, you'd have noticed that the US was also a lot whiter before the Pendleton Act, and that the post-Pendleton boom continued and even accelerated after the Civil Rights acts and a large influx of non-white immigrants. We became the world's sole superpower and continued increasing our economic, political and cultural dominance as a diverse, melting-pot society. The rise of China as an economic power (oh, wait... how is that, they're not white, how can they possibly do well?) has flummoxed us somewhat, but even with Trump beginning to throw away the apolitical civil service, our international partnerships and, well, the rule of law as a whole, we're still on top. But the decline is beginning, and it's not the brown-skinned immigrants who are taking us down, it's the white nationalist administration.

If you could discard your biases and examine the situation objectively and critically, you would notice that the timeline you're referring to completely and utterly refutes the conclusion that you're trying to draw.

Really isn't. I haven't seen cursive anywhere but on documents in a museum at any point in my life. That includes signatures, which are more likely to be a squiggle than anything resembling actual cursive. There is zero point to mandatory instruction on it anymore (if there ever was- the idea that it was a faster way of writing is backed by 0 proof. And even if it was, the ease of reading script more than cancels out those speed gains).

That's because you're taking the default, most expensive, booking option. On hilton.com, which I almost always use for business travel, click through the "more rates" link and you'll typically see rates for prepayment with no cancellation, rates with 2-3 day cancellation and rates with 24-hour cancellation. Also rates with free breakfast, rates with double points, etc.

Only consumers who are okay with possibly not being able to book a room.

I actually do this quite often on vacation. We like to fly to an interesting place with only a rough itinerary -- basically a list of things we want to see in approximate order based on a rough driving route -- then during the trip we book each night's accommodations that day, usually mid or late afternoon. By searching the whole area reachable by driving from our current location (and in the direction of what we'd like to do the next day) we can usually find a really good price on a decent place, and very often end up finding nice places that we'd never have stayed otherwise.

A few times we've really hit the jackpot, such as one night we spent at the fantastic Liss Ard Estate in southern Ireland, paying about 120 EUR for a room that usually goes for upwards of 500. That was so nice we almost decided to stay a second night. Another time, a call directly to the hotel got us the owner who offered us the night in a nice room for 50 EUR on the condition that we pay in cash :D . The flip side is that we have a couple of times had to stay places we really didn't like. It's likely that if we do this for long enough we may eventually have to badly overpay for a room (since hoteliers sometimes hold back a small number of rooms they hope to rent at very high rates when things are busy), go to a hostel, or even end up sleeping in the car. But on balance it's a risk that has paid off for us, mostly because it makes our vacations flexible and casual rather than tying us to a rigid schedule of locations, or keeping us restricted to one region.

I highly recommend this vacation strategy if you can be flexible and a little adventurous and when traveling in countries where you speak the language (or many of the locals speak yours) and which are generally safe. We've done it on a western US road trip (UT, NV, CA, OR, WA, ID), and in New Zealand, Ireland, Puerto Rico, Italy, Slovenia, Portugal and the US Virgin Islands. This is a vacation strategy that wasn't really possible before smartphones and Internet booking. I guess it could have been done pre-Internet, but it would have required a more adventurous mindset than I have at this point in my life, or than my wife has ever had.

For business travel I want my hotel reservation locked in, well in advance.