Donk. This Foone is under new management:

I'm Alice Averlong now.

A'ight. The whole vibecoding thing deserves a chance to prove itself.

So here's something that I haven't seen done sufficiently well by regular coders; if AI is truly that much more innovative, it shouldn't have any problem.

One of the problems with compute is the whole billing and scheduling thing - a lot of places have specific cost-per-hour to run batch processing; a lot of large enterprises have complex pipelines that need scheduling in order to interleave things that need processing with resources available to process them.

So a vibe coder who's confident they can prove themselves could create a utility that can look at a given program's binary, analyze it, and determine how long it will take to run, and calculate the cost to run it. Do this within 1% of actual and you'll have a truly innovative new product.

Voting with your feet works. But honestly, don't look back. It's better elsewhere.

https://www.theverge.com/policy/883852/discord-age-verification-global-walkback-delay

Today in InfoSec Job Security News:

I was looking into an obvious ../.. vulnerability introduced into a major web framework today, and it was committed by username Claude on GitHub. Vibe coded, basically.

So I started looking through Claude commits on GitHub, there’s over 2m of them and it’s about 5% of all open source code this month.

https://github.com/search?q=author%3Aclaude&type=commits&s=author-date&o=desc

As I looked through the code I saw the same class of vulns being introduced over, and over, again - several a minute.