~/vladvisinescu_

// 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 ->

Latest tutorials

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