With AI, it’s tempting to create big tickets because AI can handle big tasks, and it generates code so quickly. But the benefits of small, focused tickets remain relevant in the AI era. - Get feedback quicker. - Avoids context bloat / compacting. - Less chance of spending a bunch of time going in the wrong direction. - Leads to small PRs, which are easier to review. - I’m more likely to understand a small ticket, and to notice gaps, inconsistencies, and logical issues in the requirements. - Small tickets lead to smaller releases, which reduces risk.

Effective dev practices are mostly the same as effective AI practices. - Limit WIP. - Check in often. - Iterate based on feedback. - Create small, focused tickets. - Implement strong automated quality checks. - Avoid vague requests. Garbage in, garbage out.

This. So tired of people discounting expertise. All abstractions leak. Nearly every coding decision has tradeoffs. AI cuts corners on performance, security, validation, and accessibility. Software created without expertise is a ticking time-bomb.