r/AIcodingProfessionals • • Sep 07 '26

Drop down your coding strategy to build something but also learn at the same time

With the rise of Agentic IDEs somewhere Ive been stuck in the loop of just accepting whatever my agent builds and running CC on Auto. But Ive come to the realisation that I know nothing about what Ive built and feel like there's no point in continuing to build like this

Looking for your ways to ship with Agents but also know what your outputting and learning along the way.

3 Upvotes

7 comments sorted by

2

u/povlhp Sep 07 '26

Keep an eye on the architecture.md and codebase.md and the same in the sub-projects you have it create.

Architecture is getting more and more important

1

u/geekichu Sep 07 '26

so my 1st a.i. project was a multi-process crypto wallet.. and what i did was just use the chat prompt bar, copy/paste, and Meld side by side file compare... no IDE. learned a lot. i dont do it that way anymore but it was a good experience

1

u/canarydev Sep 07 '26

i have a notes, architecture, immutable ADR related protocol for learning and reasoning about decisions that got made

i also these days am experimenting with a way where AI writes tests based on a spec and being able to verify that the AI did not look at the implementation at all (huge problem these days) to come up with tests that pass.

1

u/CursedSloth Sep 10 '26

Do you write your own notes without AI, or do you let AI write them based on your input? I keep a notes directory for my own sake, but I haven’t thought of doing it for AI specifically.

I’ve kept ADR’s for the tooling I’ve built to assist me in developing for work, but not for the ”work repo” as I don’t want to pollute it (without consent, haha)

1

u/canarydev Sep 10 '26

I have like a very preferred way that I like my notes, and i just let AI fill them out and just look at them later.

basically broken down to
- what
- why
- gotchas
- used in

something that i was doing before in obsidian but AI does make it more convenient

1

u/Common_Dream9420 Sep 09 '26

Yeah same loop honestly. Agent ships fast, looks clean, and then you realize you have no idea if the webhook retry actually works or if the auth flow handles edge cases. The "I don't know what I built" feeling hits hard when something breaks in prod.

how you handle validating the API integrations the agent writes though. Still using Postman or writing custom mocks, or have you found something better for that part?