Software engineering · Growth

Turn feedback into a loop

Useful feedback is not a verdict on your ability; it is input for the next small experiment.

Inspired by The Software Engineer's Guidebook by Gergely Orosz. This is an original explanation, not a reproduction of the text.

The idea

Waiting for an annual review makes growth slow and mysterious. A shorter loop is more useful: choose a behavior, try it in real work, request evidence about its effect, and adjust. The narrower the behavior, the easier it is for someone to observe and for you to practice.

Ask questions that produce actionable information. “Any feedback?” invites reassurance. “Where did my design explanation become hard to follow?” gives a colleague something concrete to examine. Separate the signal from the delivery, decide what experiment it suggests, and return later to check whether the change helped.

Make it concrete

An engineer wants to lead clearer design reviews. After the next review, she asks two participants which decision was least clear and what context was missing. Both point to unstated tradeoffs. For the following review, she opens with the constraints and two rejected alternatives, then asks the same question. The second round shows whether the new behavior worked.

Keep this: Growth accelerates when feedback names an observable behavior and immediately feeds a new attempt.

Try it

Pick one skill you want to improve this week. Write one behavior another person can observe and one specific question you will ask them afterward.