2027 will be the year literally everything will burn down. it will be a glorious bon fire. and once we have paid for the past 40 years of software sins, we will rebuild it. hopefully for the better.
https://t.co/0Pl4RYIAmw
The Software Engineer is Dead
Long Live the Software Engineer
If you are confused about what is happening and how to face it emotionally - this is a great start
You matter, your ideas matter and we need every bit of you
i've been to 132 conferences in 11 countries.
this is the best talk I've ever seen in my life.
a coffin on stage
projection mapping
auto-advancing hands-free slides
and fascinating storytelling
@davekiss's talk had it all.
To be the cream of the crop, this is the guide
Only 5 minutes of your time but worth so much
This is the futurist view and will have folk that donโt agree with it
Donโt worry about them, focus on what youโre doing
Thanks for all the great feedback on Claude for iPhone Duo!
Lots of folk are now optimising their own Duo apps, so I wanted to share more about how we built it, and a few of the details we sweated along the way.
I have waited years for this, I love Call of Duty on my PSP
And now, I have that back through the Switch 2 and with @nvidia DLSS it runs so good handheld
God I love gaming, and being my inner kid
This is surprisingly the best ad for the iPhone Duo
You can tell the reporter is genuinely wowed, the developers featured want to make beautiful experiences
Mine is arriving tomorrow morning!
Excited ๐
https://t.co/vBAylimUDh
When we were at human-level AI we could take human tasks and translate them into benchmarks. In many domains, we can't do that anymore, those tasks are too easy.
Here are my guidelines on how to build benchmarks in this new era:
There's some senior engineers on here who, in the face of AI changing the very structures this industry is built on, present themselves as Stewards of the Craft of Programming.
Bugs the hell out for me.
They keep alluding to the virtue of doing things by hand, the value of Good Code and of craftsmanship, saying that yes, AI might change some things, but hey it won't ever change the value of something done with proper care, by hand, just like in the olden days of 2024. Most everything that was Good back then is still Good now: deep knowledge of languages and systems, good code, great architecture. You know the sermon.
And, yes, some of that *is* true. At least I think so. But we don't know, because no one truly knows what will be important in the future.
We're going through times of great change and I think the best advice to give to young people and others who want to have a job and provide value is: keep your eyes open, rethink from first principles, derive from what businesses value what you can provide; the digital world is more malleable than ever, you should rethink how you can help shape it.
All this pounding on the Bible of Good Code seems to me to be doing the opposite: it lets people feel comfortable -- what I've valued all my life is still valuable, I can rest easy -- in times when one shouldn't feel comfortable. This is a bumpy, exciting, strange ride. If you lean back you might fall off the waggon.
Let's not delude ourselves and others that we can keep doing what we've been doing. Rethink it all.
And, like I said, it bugs the hell out of me seeing senior engineers (that are secure in their career) talking as if there's nothing *really* to change, because the Fundamentals will still be valued. They might!
But it's the wrong advice to not rethink everything right now.
Hot take for agents: there are situations were VMs work great, there are situations where sandboxes work great, there are situations where a durable object is all you need, and there are situations where you just need a javascript interpreter. And probably many more situations.