// coding tutorials
Notes from building for the web.
Practical PHP, Laravel, Inertia, and React tutorials. Short on theory, heavy on working code.
Learning tracks
view all ->
FHIR
Learn how FHIR models healthcare information, where it fits, and how resources connect to form useful exchanges.
3
articles
->
Scrum: a 60-day reading companion
Learn Scrum with three books, a daily reading plan, and original examples from a fictional software team. Start with the foundations and work toward practical decisions.
60
articles
->
Latest tutorials
- Scrum, day 60: choosing your next experiment #Scrum
- Scrum, day 59: reconciling the books #Scrum
- Scrum, day 58: inspecting the change itself #Scrum
- Scrum, day 57: moving beyond one team #Scrum
- Scrum, day 56: building lasting capability #Scrum
- Scrum, day 55: supporting an actual team #Scrum
- Scrum, day 54: sponsoring change #Scrum
- Scrum, day 53: designing a useful pilot #Scrum
- Scrum, day 52: evaluating the case for Scrum #Scrum
- Scrum, day 51: recognizing an unsuitable approach #Scrum
- Scrum, day 50: checking misconceptions #Scrum
- Scrum, day 49: taking stock #Scrum
- Scrum, day 48: expanding responsibly #Scrum
- Scrum, day 47: managing constraints honestly #Scrum
- Scrum, day 46: discussing bad news #Scrum
- Scrum, day 45: organizational constraints #Scrum
- Scrum, day 44: Scrum Master effectiveness #Scrum
- Scrum, day 43: growing capability #Scrum
- Scrum, day 42: finding an impediment’s owner #Scrum
- Scrum, day 41: a Retrospective that leads somewhere #Scrum
- Scrum, day 40: forecasts and promises #Scrum
- Scrum, day 39: selecting work for a Sprint #Scrum
- Scrum, day 38: making work understandable #Scrum
- Scrum, day 37: planning across different horizons #Scrum
- Scrum, day 36: listening to conflicting feedback #Scrum
- Scrum, day 35: choosing evidence of value #Scrum
- Scrum, day 34: connecting work to purpose #Scrum
- Scrum, day 33: defining useful results #Scrum
- Scrum, day 32: technical debt as a product decision #Scrum
- Scrum, day 31: quality throughout delivery #Scrum
- Scrum, day 30: too much started work #Scrum
- Scrum, day 29: finishing sooner #Scrum
- Scrum, day 28: keeping a Sprint coherent #Scrum
- Scrum, day 27: a shared quality boundary #Scrum
- Scrum, day 26: collaboration across skills #Scrum
- Scrum, day 25: ownership of the work #Scrum
- Scrum, day 24: working agreements #Scrum
- Scrum, day 23: shared team purpose #Scrum
- Scrum, day 22: a small improvement experiment #Scrum
- Scrum, day 21: assessing today’s practice #Scrum
- Scrum, day 20: choosing practices for a purpose #Scrum
- Scrum, day 19: making progress visible #Scrum
- Scrum, day 18: a Retrospective with an experiment #Scrum
- Scrum, day 17: a Review that informs the next decision #Scrum
- Scrum, day 16: a Daily Scrum that changes the plan #Scrum
- Scrum, day 15: planning toward a Sprint Goal #Scrum
- Scrum, day 14: what can change during a Sprint #Scrum
- Scrum, day 13: helping the team become more effective #Scrum
- Scrum, day 12: Developers own the delivery plan #Scrum
- Scrum, day 11: Product Owner decisions #Scrum
- Scrum, day 10: a Product Goal that guides decisions #Scrum
- Scrum, day 09: a team that can finish #Scrum
- Scrum, day 08: values when the news is uncomfortable #Scrum
- Scrum, day 07: how the framework fits together #Scrum
- Scrum, day 06: evidence that changes the plan #Scrum
- Scrum, day 05: where the work waits #Scrum
- Scrum, day 04: planning under uncertainty #Scrum
- Scrum, day 03: build something usable, then learn #Scrum
- Scrum, day 02: Agile values in everyday decisions #Scrum
- Scrum, day 01: when a good plan meets real users #Scrum
- Building apps for Zom-Boy: an API for Project Zomboid modders #Lua #Project Zomboid
- FHIR resources: the building blocks of an exchange #FHIR
- FHIR explained: a common language for healthcare data #FHIR
- Quick project checks with Bash #bash #javascript
- Code block tabs: one task, three languages #javascript #php
- Quickly debug a Laravel fillable error #laravel #php
- primul tutorial #php