Sitemap
Level Up Coding

Coding tutorials and news. The developer homepage gitconnected.com && skilled.dev && levelup.dev

Member-only story

My AI Workflow, One Year Later

--

Not a member? Read this story for free here.

Press enter or click to view image in full size
A laptop on a wooden desk showing a terminal window running an automated deployment. Tasks executing in sequence, progress at 64%, ETA 01:42. A second monitor with code in the background, a coffee mug and notebook beside the laptop. Dark room, warm desk light.
(This image was generated using AI technology.)

A year ago I said this would feel outdated in six months. I was right.

The original article ended with:

I don’t know exactly what this collaboration will look like a year from now. But I’m paying attention and adjusting as I go.

Now I know. What I didn’t expect was how structural the change would feel. In 2025, I was building context manually — open a chat window, paste in a code snippet or an email thread or a half-formed argument, work from there. The AI had whatever I’d brought it.

In 2026, the AI reads my files directly. It sees my calendar. Notes from two weeks ago. I’m not constructing context anymore. It’s already there.

Here’s what happened.

A Year Ago, I Brought Things to the AI

The shift from chat to filesystem is the most significant change of the last twelve months.

In the original article, I described pasting things into chat: code snippets, document excerpts, rough outlines. The AI responded to what I gave it, with no memory of yesterday and no view of what I hadn’t shown it. That worked and still does for certain things. But it had a ceiling.

--

--

André Bergholz
André Bergholz

Written by André Bergholz

Writing about AI for leaders who need to understand it, not just deploy it. CPO & Co-Founder @Implisense.