Learning live
Choose a coding course by the project you want to build
A course title is a starting point, not a complete learning plan.
PublishedSI100x learning notes
Original exercises and checklists for learning AI and coding, making projects and asking better questions in live classes.
Explore free live demos →50 articles
Learning live
A course title is a starting point, not a complete learning plan.
PublishedLearning live
A demo is a chance to understand the teaching approach and the course fit.
PublishedLearning live
A long transcript is difficult to use when you sit down to practice.
PublishedLearning live
An instructor can help more effectively when a question includes the smallest example that still fails.
PublishedLearning live
Following an example can make a new skill feel familiar before you can use it independently.
PublishedLearning live
A practice plan should fit the week you actually have.
PublishedLearning live
A focused topic is easier to study than a request to learn an entire field at once.
PublishedLearning live
A useful learning journal shows how you approached a problem, not only the final answer.
PublishedLearning live
A project can look complete while its empty and error states remain confusing.
PublishedLearning live
A portfolio entry is stronger when it explains a real problem, the choices you made and what you verified.
PublishedWeb projects
A practice contact form teaches more than placing four fields on a page.
PublishedWeb projects
An empty list is a normal product state.
PublishedWeb projects
A card layout that works only with a short example title is not ready for real content.
PublishedWeb projects
A navigation menu should work when someone uses Tab and Enter as well as a pointer.
PublishedWeb projects
Search is a conversation between a query and a set of results.
PublishedWeb projects
Responsive design is more than shrinking a desktop screenshot.
PublishedWeb projects
A label such as Submit can be technically correct but unclear in context.
PublishedWeb projects
Images can fail even when the surrounding page is working.
PublishedWeb projects
Losing a completed form after a network error can turn a small failure into a frustrating restart.
PublishedWeb projects
Headings help readers find the structure of a page.
PublishedDebugging and testing
Changing several things together makes it hard to know what actually fixed a problem.
PublishedDebugging and testing
A regression test keeps a repaired behavior from quietly breaking again.
PublishedDebugging and testing
Validation often fails at the edges rather than on an obviously invalid example.
PublishedDebugging and testing
An empty response can be a correct result, while a failed request means the result is unknown.
PublishedDebugging and testing
Test records are easier to clean up when you track them from the beginning.
PublishedDebugging and testing
A feature can work for its owner and still expose another account’s records.
PublishedDebugging and testing
Fast local responses can hide loading problems.
PublishedDebugging and testing
A local repair is only one stage of delivery.
PublishedDebugging and testing
A screenshot of the default page misses menus, errors and populated states.
PublishedDebugging and testing
A precise bug report saves time by turning a complaint into an observable case.
PublishedAI practice
An AI feature is easier to evaluate when its job is narrow and visible.
PublishedAI practice
A prompt is more useful when the desired result is concrete.
PublishedAI practice
Without stable examples, a prompt change can feel better while making other cases worse.
PublishedAI practice
When a generated answer uses source material, readers need to distinguish what the source says from what the assistant infers.
PublishedAI practice
A useful assistant should have a way to communicate uncertainty.
PublishedAI practice
A summary should make information easier to review without quietly changing its meaning.
PublishedAI practice
A prototype does not need private customer records to demonstrate a workflow.
PublishedAI practice
A rubric makes output review more consistent than choosing whichever answer feels most impressive.
PublishedAI practice
An AI-backed interface needs useful behavior when the request does not finish.
PublishedAI practice
Reading a generated explanation can create a feeling of understanding without showing whether you can use the concept.
PublishedProject planning
A small finished journey is easier to learn from than a large collection of half-working screens.
PublishedProject planning
Acceptance criteria translate a feature idea into observable behavior.
PublishedProject planning
Sample data is part of design.
PublishedProject planning
A milestone should describe a result that you can demonstrate.
PublishedProject planning
Setup instructions are useful only when they work outside the author’s memory.
PublishedProject planning
A useful project demo follows a task rather than jumping through disconnected screenshots.
PublishedProject planning
A good review points to an observable issue and explains its effect.
PublishedProject planning
A change log helps readers understand what improved and what remains unfinished.
PublishedProject planning
An estimate is a planning aid, not a promise.
PublishedProject planning
Publishing makes a project easier to share, but it does not erase its unfinished parts.
Published