Yes, we still need engineers - mattsayar.com<br>Prototyping has done wonders for speeding up software delivery. I start with a clone of our UI repository and open Claude Code. I'll prompt it to help me add a button (or whatever), set up some test data, and record a demo of a full workflow. It looks great in a Loom video! But it's far from production-ready. We still need:<br>Backend support<br>Regression testing<br>Functional testing<br>Security testing<br>Performance testing<br>Scalability considerations<br>Edge case considerations<br>Architectural considerations<br>Accessibility requirements<br>Design system considerations<br>Maintainability considerations<br>User permissions considerations<br>That's just off the top of my head! What about:<br>Lots more stuffLogging, metrics, and tracing<br>Monitoring and alerting (how do you find out it broke before users do?)<br>Error handling and graceful degradation<br>CI/CD pipeline, deployment, and rollback strategy<br>Feature flags<br>Infrastructure provisioning, config management, and secrets handling<br>Rate limiting and abuse prevention<br>Retry logic and idempotency<br>Concurrency and race conditions<br>Backups and disaster recovery<br>Database schema design and migrations<br>Data validation and integrity constraints<br>Caching strategy and invalidation<br>PII handling, data retention, and deletion<br>Authentication<br>Authorization, roles, and permissions<br>Session management<br>Multi-tenancy and data isolation<br>Regulatory compliance (GDPR, HIPAA, SOC 2, etc.)<br>Audit trails<br>Dependency licensing<br>Data residency requirements<br>Localization and translation<br>Timezone, currency, and date/number formatting<br>Right-to-left support<br>Empty, loading, and error states<br>Offline and slow-network behavior<br>Responsive layout, mobile, and cross-browser quirks<br>Analytics and instrumentation<br>A/B testing hooks<br>Cloud cost / budget impact at scale<br>Code review<br>Unit, integration, and end-to-end tests (and coverage)<br>Technical and user-facing documentation<br>Runbooks, on-call, and support<br>Versioning, backward compatibility, and deprecation paths<br>I used Claude to generate the rest of this list<br>My prototypes have eased the communication from idea to delivery better than any other tool, but it's still far from a production-ready product. I enjoy making them, and engineering enjoys referencing them, but anybody that thinks their vibe-coded prototype is ready for production is fooling themselves.<br>A recent piece discussed how AI is not behind mass layoffs, and may likely never be. After working with a team rocketing forward with AI adoption in a space that needs protection from AI more than ever, I couldn't agree more.<br>sourceIndeed, it seems we're starting to hire more engineers even after the noticeable boost in quality in AI generated code in November's inflection point. Software is an industry intent on automating as much as possible. It usually automates the boring stuff, which lets us focus on the fun stuff. And the fun stuff is solving real problems, not typing code.

You should also read:<br>I love the idea behind the Pi-hole: block ads at the DNS layer so ads never even reach your devices. No ads, no trackers, and no worries about your extensions breaking! Works network-wide! Unfortunately, it caused me more grief than joy. I love most things…<br>Continue reading...