Yannick

Kind of glad to have begun coding in the 90s. Skipped Kubernetes. Skipped graphql. Skipped microservices. Skipped react unless absolutely necessary. Got mocked a bunch by “senior devs” who started coding in 2010. Didn’t care, preferred shipping value to customers rather than technical wankery that only bloated teams and slowed delivery. Glad those senior devs have now earned their title and realizing it was dumb too. You can’t replace actual experience.

2 things developers get completely wrong when using AI: 1. No, you don't need to understand the code. You need to help the model enforce good software engineering practices (like testing) and iterate over time (and over new model releases). 2. No, you shouldn't download skills off of the internet. Codex and others actually have the "skill builder" skill embedded into them. Go fetch the information and create the skill yourself. Refine them for your taste and needs. Models perform way better when they're steered out of being generic. They need OPINIONS. And they can actually help you improve your opinions.

Did my first attempt at automating an entire workflow with Claude today (plan > implement > simplify > review > test > PR), the idea being to get to a decent first draft for a task, which I can review and refactor. But it keeps stopping at random steps. Not sure how to fix this