Writing
Refactoring as ROI, training as investment, data retention as a cost line: engineering decisions in the language of the P&L.
Three signals to invest in developer training, how to tie it to business goals, and how to measure ROI, with a $10,000-a-month cloud saving as the example.
Why Shadow AI, Copilot-style vulnerabilities and automation bias threaten businesses, and four controls from corporate LLM access to data residency.
How to pitch refactoring to executives as ROI: cost the legacy burden, cite Southwest and Netscape, pilot one module first.
Five big-data mistakes from running a 16 TB, ten-billion-records-a-day platform: retention, quality, uncapped autoscaling, surplus fields, wrong database.
Four traits that mark product-minded engineers, and the retention practices behind five-to-eight-year average tenure.
I'm always interested in thoughtful conversations about technology, engineering organizations, AI and ambitious products.
Get in touch opens LinkedIn in a new tab. Email reaches [email protected].
