Junior developer, 1–3 years
You can write the code. Now decide what to build.
Nobody hands you the object list any more — producing it is the job. The time goes into the approach, and a specification your lead accepts.
The skill isn’t producing an approach. It’s producing one you can defend.
Writing the technical specification
Turning what you'll build into a defensible approach, in your lead's template, takes longer than the code.
Generate it in your templateSurviving review
The same comments return because nobody explained the standard — they only enforced it.
Catch them before your reviewer
What actually moves you forward
- Write the approach before the object list
- Record the alternatives you rejected
- Take the approach to your lead early, as a proposal
- Read your own diff as though someone else wrote it
Questions junior developers ask
Usually it's the reasoning, not the content. A specification that lists what will be built reads as a task list; one that explains the choice and the rejected alternatives reads as engineering.
Before, briefly, as a proposal: “BAdI here rather than an implicit enhancement, because it survives upgrades — any objection?” Two minutes now saves a rewrite later.
Understand the reason rather than just applying the fix. An understood comment changes the next development.
Get to a reviewable draft sooner.
Bring the requirement you're about to write up.
No SAP connection. No template rewrites.