Verifying behavior is great and all if you can actually exhaustively test the behaviors of your system. If you can't, then not knowing what your code is actually doing is going to set you back when things do go belly up.
I love this comment because it makes perfect sense today, it made perfect sense 10 years ago, it would have made perfect sense in 1970. The principles of software engineering are not changed by the introduction of commodified machine intelligence.
i 100% agree - the folks who are best at ai-first engineering, they spend 3 days designing the test harness and then kick off an agent unsupervised for 2+ days and come back to working software.
not exactly valuable as guidance since programming languages are very easy to verify, but the https://ghuntley.com/ralph post is an example of whats possible on the very extreme end of the spectrum
Absolutely no one is seriously clamoring for the old team name. It's an issue that DFM. But of course, because it's on the agenda of the day we need to drop everything.
This is no better then switch from master to mainline. They're both idiotic and performative.
“Oh you’ll never have to do this tech stuff ever again! How amazing! Ai all the things!”
Like, ok great. Good for you. Leave the rest of us out of whatever mission-to-replace-some-thing-you-don’t-like.
Or even better, if you don’t like, go away and do something else. I’m not big into jogging, but I don’t go around telling runners that their hobby is redundant and that “nobody will run now that we have segways”.
I've discovered submodules and build pipelines broken due to a changed name within the last year. Doesn't help that some people are late to the party and still changing things now. But, hey, at least I've done my part against slavery /s