I'm a self-taught web developer with about five years of experience, mostly focused on front-end work. I've built projects I'm proud of, but I still regularly look up basic concepts or syntax that I've learned before. Sometimes I understand what a function, variable, or loop does in isolation, yet feel less confident applying those ideas in a larger real-world project. How much should a software developer be expected to remember? Is the important skill being able to understand a problem and find a reliable solution, or should I be able to recall and write most of the code without looking things up? I'm especially curious whether forgetting details means I'm missing important fundamentals or simply experiencing something that even experienced developers deal with.
4 Answers
It’s still important to understand code produced by tools, including AI assistants. Don’t blindly trust a generated answer—check whether it matches your requirements, understand its behavior, test it, and be able to maintain it later. Use references to fill in gaps, not to avoid learning the underlying ideas.
Looking things up is completely normal, even after years in the field. Languages, libraries, APIs, and tools change constantly, and nobody keeps every detail in memory. The valuable part is understanding the fundamentals, recognizing what kind of problem you’re facing, and knowing how to investigate and verify a solution.
Think of programming knowledge in layers. You should understand core concepts and be able to read, reason about, debug, and review code, but you don’t need to memorize every method or piece of syntax. Experienced developers often remember the problem they solved and the general approach, while the exact documentation and implementation details fade.
There isn’t a special checkpoint that makes you a developer. If you intentionally build software, solve problems with it, and keep improving, the title fits. Getting paid for it may make the role official, but it isn’t the only valid definition.
That helps. I understand the basic programming concepts, but applying them in a full project can still feel unfamiliar. I’m going to focus more on understanding the problem, checking my assumptions, and reviewing the code rather than expecting myself to remember every detail.