Why does writing things down matter more now than it used to?
In the AI era, a docs folder in your repo is not optional. It is where your thinking lives.
You are just starting, and AI is part of the job
You got the internship. You are on a front-end team, expected to prove you know what you are doing while you barely do yet. That gap is normal. Sooner or later you will work alongside coding agents (AI tools that read and write code with you, like GitHub Copilot, Cursor, or Claude Code). This lesson asks you to take one habit seriously.
Notes used to be optional, now they are the work
Before AI, notes were a good habit. Now they keep your code aligned with the requirements and the decisions you made. Write your thinking, your decisions, and the reasons behind them in plain markdown instead of trusting your AI tool to remember the whole conversation.
Make a docs folder in your repo and let it grow: requirements, technical decisions and why you made them, discussion notes, mentor feedback. If it can be written in plain text, it belongs there.
Here are the files in my docs folder: [list them]. Suggest a clearer structure that keeps related notes together, and flag which files look redundant.
This has a name: spec-driven development
Writing what to build and why before you build it (that written description is a spec) is the heart of spec-driven development: you write a clear spec, then let the agent implement against it, instead of winging it prompt by prompt (that looser opposite is "vibe coding"). Your docs folder is where the specs live.
During the internship
Lean on agents to learn, not to write your code for you. Keep the AI-generated code you accept to a minimum and type it out yourself. You only learn the syntax by writing it.
Let the AI clean up the writing, not the thinking
Do not spend hours polishing docs. Write ideas down as they come (in English even if you think in Romanian), then ask the AI to tighten the wording. The thinking stays yours, only the phrasing is assisted.
Improve the writing in this note without changing my meaning or my decisions: [path to your note]. Keep it short and in plain English.
Give the AI your context once
A full docs folder is context you can hand to any AI conversation instead of re-explaining your app every time. If your tool reads files, point it at the folder and ask your question. In a browser chat, upload the relevant file first. Either way, the AI stops guessing about your project and starts answering for it.
Here is my project context: [path to your docs or attach them if a browser based tool]. Based only on this, answer: [my specific question]. If the docs do not cover it, say so instead of guessing.
Write your thinking down. A docs folder you can hand to any AI beats a chat history you cannot reuse.
Additional Resources
Explore these carefully curated resources to deepen your understanding and practice the concepts covered in this lesson.