What I'm trying to express is that when people say "AI is a bubble," the don't understand that AI will actually survive that bubble, even if many "AI companies" do not.
What I'm trying to express is that when people say "AI is a bubble," the don't understand that AI will actually survive that bubble, even if many "AI companies" do not.
Again—the internet was a bubble, and yet it eventually far surpassed even the frothiest expectations.
If you're investing for the short-term, do what you gotta do. The AI bubble will burst and lots of superficial companies will be washed away. But we're just getting started. This next wave will make a new round of companies like Netflix, Amazon, Apple, etc.
It's still 1994. We won't be near the top until the Telegraph publishes an article overly exuberant about AI and saying AGI is here.
If every idiot commenting on Reddit, HN, X, and mainstream news publications is pessimistic and constantly shouting "bubble!," then definitionally, we have not reached irrational exuberance and we're not even remotely near the top.
[1] https://d.newsweek.com/en/full/566807/theinternetbah3.webp (1995)
I’d like to see the proof for TDD; last I heard it slowed development with only minor reliability improvements.
EDIT: typo
There is maybe some truth to the LLM vibe coding and there maybe is some truth to the “old guard” saying “this is shit”, because this might be shit for very good reasons.
Absolutely. And what I find fascinating that this experience is highly personal. I read probably 876 different “How I code with LLMs” and I can honestly say not a single thing I read and tried (and I tried A LOT) “worked” for me…
Just yesterday I uploaded a few files of my code (each about 3000+ lines) into a gpt5 project and asked in assistance in changing a lot of database calls into a caching system, and it proceeded to create a full 500 line file with all the caching objects and functions I needed. Then we went section through section of the main 3000+ line file to change parts of the database queries into the cached version. [I didn't even really need to do this, it basically detected everything I would need changing at once and gave me most of it, but I wanted to do it in smaller chunks so I was sure what was going on]
Could I have done this without AI? Sure.. but this was basically like having a second pair of eyes and validating what I'm doing. And saving me a bunch of time so I'm not writing everything from scratch. I have the base template of what I need then I can improve it from there.
All the code it wrote was perfectly clean.. and this is not a one off, I've been using it daily for the last year for everything. It almost completely replaces my need to have a junior developer helping me.
It definitely sounds nice to go and change a few queries, but did it also consider the potential impacts in other parts of the source or in adjacent running systems? The query itself here might not be the best example, but you get what I mean.
The former is desirable, not common. The latter is common, not desirable.