There has to be a country song in there somewhere.

The Confession

This weekend, I did something reckless.

Junie is JetBrains’ built-in AI assistant for PyCharm—smart, fast, and now fully embedded in my development environment. She is a stalker who pays better attention to shit than I do, fuck she does not just finish my functions, she writes the unit tests and the documentation, and then has the nerve to tell me what I’m going to do next. How the hell did this get turned around?

It Started Friday Night

I realized that I had some personal projects that I wanted to get done and I was alone and needed help. While I’ve had some success with Visual Studio Code and Co-Pilot, it always seemed like things were just bolted on and some of the bolts were shaking loose.

So I asked my ChatGPT what to do and it suggested JetBrain’s PyCharm with Junie (who has had a few recent upgrades).

So, after installing PyCharm and agreeing to a free trial that included AI, I recklessly asked Junie to

“Build me a Notion backup tool that extracts all my content and saves it to local folders.”

Ten minutes later, Junie chirped back: ✅ Done. Coded. Tested. Error-free.

I blinked. I ran it.

It failed.

But not by much.

After a few minutes of cleanup—mostly small things like missing environment variables or naming mismatches—I had a working Python script backing up my entire Notion workspace.

It was beautiful, fast, and dangerous. I come from a generation that has many stories to tell about backups that no one could restore.

The High

With Junie’s help, I knocked out three weeks of work in four days.

I wrote, tested, and iterated faster than I ever had before. I was flying through side projects, solving pain points I’d been putting off for months. It felt like the future had arrived, and I had a front-row seat.

Junie wasn’t just a code-completion tool. She was a collaborator. An architect. A dare-I-say… co-conspirator.

The Low

That Notion backup tool? It looked perfect.

It passed every test it had written—because it hadn’t written the tests that mattered.

A day later, in a different project, I tried to use the files we extracted. About 80% was missing. It turns out, Junie forgot to extract Notion’schild blocks.

Turns out:

Junie never added child block extraction in the original backup script.

Which means my "backup" had maybe 10–15% of my real data.

If I hadn’t returned to that code… if I had needed to restore from it...

I'd have lost nearly everything I thought I saved.

The Lesson

AI assistants like Junie (and yes, even my dear ChatGPT) are powerful.

But they are confident, not always complete.

They predict, but they don’t audit.

They don’t know what you didn’t ask.

And most dangerously of all?

They often give you something that runs. And looks done.

The Rule

Don’t confuse “it runs” with “it’s right.”

Treat AI-generated tools like gifted interns:

• Smart
• Fast
• Surprisingly helpful
• And absolutely in need of review.

The Takeaway

Junie helped me move mountains this weekend.

But if I hadn’t circled back, I would have buried myself beneath them.

Use AI. Love AI.

Just don’t blindly trust AI.

Your backups aren’t backups unless you test your restores.

Your code isn’t complete until you’ve asked: “What did it forget?”

🚀 Stay sharp. Stay curious. And always check the child blocks.

—

PS: Junie, if you’re reading this—no hard feelings. You did great. Just… maybe add a little checklist next time?

Let me know if you want a more technical appendix, Notion API footnotes, or a “Top 5 AI Mistakes to Watch For” sidebar.