Agree on a learning objective

A project is a vehicle for learning, not automatically a delivery contract. Begin by naming the skill or decision you want to improve. “Build an app” is broad; “understand state and error handling in one mobile flow” gives a clearer basis for practice.

Write a brief that includes the intended user, constraints and what is outside scope. This helps prevent the project from growing faster than your understanding.

Work in reviewable increments

Choose a first increment small enough to inspect: a query, a scene, a prototype or an API endpoint. Bring your reasoning as well as the result. Explain what you tried and where you are uncertain so feedback can address the underlying decision.

Review should produce a manageable next step. A long list of possible improvements is less useful if you cannot identify which one matters now.

Keep ownership and permissions clear

You remain responsible for the work and for deciding how to use feedback. Clarify whether the arrangement covers conversation, review, guided implementation or another format before agreeing to proceed. A mentor is not implicitly taking over production delivery.

Use work you can legally share. Private repositories, customer data, footage and organizational documents may require permission or a synthetic substitute.

Reflect on the change in your reasoning

At the end of an iteration, compare the original decision with the revised one. What evidence changed your mind? What can you now explain? What still needs testing? This reflection makes the learning more portable than the finished artifact alone.

The website describes possible pathways, subject to suitability and availability. A private proposal would need to define scope, format and pricing; an inquiry or preview does not reserve a session.

Try this next

  • Write one learning objective and one boundary.
  • Prepare a small artifact for review.
  • Record the decision you changed and why.