Playing with AI tools feels like being that chess prodigy in the movies—the one playing ten games simultaneously, walking from board to board, making moves while opponents are still thinking.

That's what the workflow looks like now. Run a task. Watch the model do its thing. While it's rendering results, spin up another project. Then another. Juggling, parallelizing, seeing if one task can feed into the next. It's disorienting and exhilarating at the same time.

what's possible now

Right now, I can be:

• Building data visualization tools that generate charts from company data—automating my own workflows while uplifting my whole team to do the same
• Synthesizing information across APIs—Gmail, Granola, Slack, Notion—into a comprehensive note-taking and to-do system that works not by me taking notes, but by my tools tracking my correspondences automatically
• Creating blogging commands that let people who aren't engineers, who aren't "AI native," take advantage of these tools with just a little scaffolding

All at the same time. In parallel.

the edge engineers still have

The discourse says engineers are becoming irrelevant—the models can do the work now. Maybe that's true. Maybe it comes sooner than we think.

But here's the thing: engineers still have an edge. We understand how software works. We have mental models for how things get pieced together. We understand the limits of these models, how to productize them, how to orchestrate them effectively.

What once took a team of engineers, we can now do on our own—if we're smart about delegating, if we're patient with the models, if we get to know them and work with them.

what a time

Things that seemed impossible before? I can do them in an hour now. Things that would have taken months—or that I simply would have never done—I can ship today.

Never did I think this technology would arrive.