@Shivamyadav When you approach people to contact you via mail with out any valid reason, it raises red flags why you can't discuss something in public forums. You could be anything from a hacker to an extortion ring or even Jeffrey way posing as a Level 16 user. Remember the first lesson of Laravel, never trust input from any user, not even Jeffrey way.

@Shivamyadav Thanks but no thanks buddy

FSMs are the way to go about making games even in Alpine.

This course should be titled how not to make Games with Sphagetti code ;-))

Students today have access to tools like AI that can provide them with clear explanations, direct answers, and high-quality code suggestions— instantly, and without unnecessary complication. When Human Teaching Assistants or Mentors withhold clarity or avoid giving straightforward guidance, the effect isn’t that newbies “learn less”; instead, the community is perceived as less supportive, and students naturally turn to tools that are straightforward.

If tutorials want their role to remain meaningful, you need to offer something better than what students can already get from AI:

1. clarity rather than obstruction
2. guidance rather than cryptic hints
3. generosity rather than gatekeeping
4. real human insight and encouragement

Good mentorship in 2025 isn’t about limiting learning—it's about accelerating it. When the community/mentors/TAs helps openly and constructively, students respect and value their roles. When they don’t, AI will inevitably fill in the void.

Any chance updating the source to use tailwindCSS ?

If not, its a good exercise for using AI as a teaching assistant for such tasks.

Woulda been nice if you did this small project with an FSM design pattern in Alpine. Starting with its design in a Mermaid document. But I can only wish.

Great tutorial. Wish you would mention the pattern (React/Vue pattern) "update the canonical state upstream & compute downstream", unlike updating a score with +1 as many unity tutorials demo.

Thanks

Test todos seem very good for documenting & Notes about the software behaviour we are learning in Tutorials than using disconnected markdown notes elsewhere.

Use IntelliJ multiple cursors when:

• You see all occurrences on screen at once
• The change is visually obvious and uniform
• You want to edit columns or aligned things
• You’re doing structural changes that aren’t semantic (e.g., aligning params)

Better use IdeaVim and the */n/. pattern

This is especially true in Laravel/PHP projects where variable names and method names are easy to accidentally partially match.

• Editing code identifiers (safe → whole-word match)
• There might be similar but not identical words
• You want to inspect occurrences one at a time
• You need to repeat a full edit sequence, not just text insertion

Very Good