My favorite thing about this article is that it was released the exact same day as Claude 4 Opus.
If it's satire, it's brilliant: because most of the comments I see (here and elsewhere) are clearly written by people who tried agentic coding before Opus 4, and haven't given it a fair shake over the ensuing five days.
IMO the most important engineering skill in 2025 isn't low-level programming, or the craft of debugging, or even having a firm grasp of system architecture. Believe it or not, I truly believe the vibe-first juniors will learn that stuff too, over the course of their careers, just as we did: through necessity (As an aside: if you don't think they'll encounter such necessity, then it's inherently not one any more than the countless other once-honored, fastidious hallmarks of craft that have since been rendered obsolete. And if you don't think they'll learn even upon encountering a true necessity, then you underestimate them.)
No, the most important engineering skill in 2025 is non-attachment: constantly update your priors, and hold your opinions very loosely. Because those opinions could be fully wrong before the essay even gets shared.
For users of Fabric/Crashlytics/Answers, is there a TLDR somewhere for the new terms? (specifically, the delta between their new terms preview and the old terms)
I believe I had spoken with 1 or 2 investors total about the company before that moment.
You're right: practice really seems like the key to getting this stuff down. One can have a clear intuitive understanding of their vision long before they have a clear way to express it in English.
Now that I've finally re-watched it, I can't help but agree. I definitely sounded like a jerk (and probably a fairly stupid one). It's funny how one's defensiveness can be interpreted :(
You've figured it out. Most people interpret defensiveness as an absolute sign that you're a jerk and that you're wrong. It doesn't matter if you're arguing in favor of the laws of physics, if you sound defensive, you will be dismissed as an arrogant idiot.
But anyone who would rush to judge someone so harshly is revealing themselves as the bad person. A little compassion is all that is necessary to see that you meant well.
Take pride in having gotten on stage and put yourself out there. You tried something that would scare most people to death. And you did quite well. Plenty of people like myself have nothing but respect for you and don't think you're a jerk.
Our thesis is that storing and analyzing ad hoc data is not a solved problem -- while it may be pretty easy at some scales, it is rather hard at others.
Keen IO takes an API-based approach to the problem, which means:
- developer abstractions are higher level than rolling your own
- scalability is as easy as "my bill went up" (as opposed to "my ALTER statements stopped working!" or "I need to leave mongo and buy a book on distributed system engineering!"
- ability to cover new/emergent use cases is a lot higher than you would get with an off-the-shelf analytics product
Cloud console does nothing.
They should host their support services on AWS and vice-versa.