← Back to Spring into AI

Week2 in Review

A Week 2 round-up from Spring into AI: markdown-as-deployment, tools for AI tools, and the submissions that pushed the competition forward.

Source note: Originally published on Eric's Advisory Hour Substack. Read the canonical post.

.md file is the app
.md file is the app

For the competitors, I’m not sure if you noticed but Week2 had an interesting quirk about it: the deployment was the markdown file. The tool for your AI is now just the text file. The reason this is true is because AI can author code so fast, and at such a low cost, that it’s trivial to port application software by a text file.

We are in a new world now where articles are software programs. What that means is that tutorials that benefit humans also benefits AI. If you want a hint about Week3, it’ll be related to teaching. If you want another clue: most video games have them.

This is a round up post of the submissions for Week2 for Spring into AI. Here they are.

Submissions for Week2

That said, you can still do some wickedly interesting things with textfiles with code as the skill files demonstrate. Let’s consider the example of database tuning. What if we just handed off database tuning to an AI? What would you need for that-and would it work? “This solved a real production problem this week,” I’m told.

When you run a competition like this, you never know what clever twists and turns will emerge. In this case, Myles takes a clever spin by building a tool that serves up this competition’s tools. So, yes. A tool that serves up the tools written for AI tools.

Jake continues his exploration of the world of crypto with an agent skill that works for collecting in signal intelligence from the crypto markets. What’s it mean when the dev tools can just snap-in to the analytics data of the market, in real-time, without having to wait on three months of enterprise security approvals to process?

There’s often a clever idea and then there’s the idea that just makes me laugh. The “Thanos Fix” as an AI skill is likely to keep your security professionals awake at night. What if the AI had the ability to just arbitrarily remove half your code? What this teaches me is that if you have data backups? Put them on media not connected to the internet! Evan Rhea[I deleted half my code with my new agent skill and couldn't be happier[I’m sure we’ve all been there, wanting to go scorched earth on a project, just needing to start over with a fresh slate. Well what if we didn’t? What if you were in an in between of wanting/not wanting to? Welcome to Thanos-fix, an agent tool that deletes…[Read more[3 months ago · 1 like · Evan Rhea

Last is my humble entry. This was a fun, little skill. What if every git commit had a jingle. It’s a silly idea, but then this is a competition that’s meant to push us in new and interesting ways.

Generating a new song with every git commit is new to me.

Week 2 comes to an end and we march along towards week 3 of our four week competition. Kyle benefits from an out of state trip and a lack of camera time from many of us, but next week? Next week I’ll be reclaiming gold.

See the public website (it’s updated by AI, too)...
See the public website (it’s updated by AI, too)...

Keep updated about the competition and AI perspectives from Eric by subscribing today.

Original source

This local copy preserves the article text, source link, and inline media. Canonical Substack URL: https://advisoryhour.substack.com/p/week2-in-review.