Gio 🐘
4.3K posts

Gio 🐘
@GioDev8
Working on https://t.co/yCQEYMguka







Someone on one of my PHP videos said they're following along fine and understand the concepts, but the knowledge keeps slipping away over time. Asked me for advice & how I'd take my own course. My advice was to rewatch the parts that felt hard and then rebuild the logic without the video, and use AI as a guide when something isn't clicking. Have it quiz you, give you exercises, explain the same thing a few different ways. Build something other than what's in the tutorial. But the bigger advice is that knowing PHP itself isn't that valuable anymore (as much as I hate saying it). What's valuable now is knowing the systems, the trade-offs, how things connect. Need to think about what goes into building an app beyond the language or framework.



Examples: Would you buy a Ruby language book? Would you work through a how-to make <insert thing> video course? Would you practice coding katas? What about an OOP book? Do any of these interest you at this point? Be honest.



I talk to engineers at other companies every day and hear the same thing: one person is 10x'ing their output with Claude but the rest of the org hasn't caught up. Watching teams adopt AI, I keep seeing the same 4 steps. I mapped them out here: Steps of AI Adoption claude.ai/code/artifact/…

I had Sonnet audit and review the plan created by Fable. It found couple of issues in the plan. Going to make this recurring to where in addition to Opus reviewing PRs, I'll have Sonnet randomly pick a commit or PR from last few days and do an audit daily. Might try Haiku also









