Learning to code with AI: apply the eight rules to one real project

Try the problem before asking AI to solve it

The 30 June 2025 lesson argues for learning coding alongside tools such as ChatGPT and GitHub Copilot. Its first two rules are struggling before AI and choosing projects over courses. The practical objective is to understand the problem and evaluate help, not to avoid assistance or complete every exercise alone.

1. Choose a small application with a user task you can demonstrate and write what you do not yet understand.
2. Attempt one bounded part, then ask for help on the specific obstacle rather than replacing the whole project with unexplained output.
3. Use the project-over-courses segment at 2:43 to connect each lesson to something you can build or repair.

Choose a workable stack and use no-code where it fits

The next rules cover a fast-shipping stack at 5:28, problem solving at 7:12 and no-code at 8:11. The description does not name the exact recommended stack, so follow the recording for that choice. Tools should make the project easier to understand and ship rather than become another collection to learn without using.

1. Identify the minimum interface, data and deployment needs before adding another framework.
2. Explain what each part does and test the core task after connecting them.
3. Use no-code for a suitable part of the job while checking that its limits and data handling still fit the project.

Show the work, tolerate early mistakes and build systems

Build-in-public starts at 9:07, accepting initial difficulty at 10:34 and systems rather than code at 12:15. Sharing can produce useful feedback when there is a working example to inspect; it does not guarantee an audience or employment. Keep the evidence of what users can actually do alongside your learning notes.

1. Show a small usable version and collect concrete observations about where someone succeeds or gets stuck.
2. Keep a record of mistakes and fixes so later projects reuse the learning instead of repeating the same confusion.
3. Use the path quiz at https://links.zerotomastery.io/cpquiz-luke-june2025 and compare any recommendation with your actual gaps.
4. The retained learning resources are https://links.zerotomastery.io/aideveloper-luke-june2025 and https://links.zerotomastery.io/luke-june2025; check their current curriculum and terms before enrolling.

The takeaway

The eight-rule approach is useful when it produces a working project and stronger judgement, not merely more code or course badges.