AI didn’t just change how we write code. It changed how we build products. See 4 lessons learned by Progress Telerik and Kendo UI engineering and product teams.

Telerik's platform is  dedicated to providing insights and resources for developers and teams building web and mobile applications with UI components and developer tools. Through documentation, tutorials, and demos, Telerik offers insights into building modern and responsive user interfaces. Developers can learn about Telerik UI components, developer productivity tools, and app development frameworks to accelerate application development and deliver exceptional user experiences.

Telerik

Progress Telerik shares four lessons learned from integrating AI into their developer tools and internal engineering workflows. Key insights: AI excels at starting tasks but lacks judgment to finish them; AI-generated code looks plausible but can be subtly wrong, making context more valuable than cleverness; speed gains must be paired with accountability and observability to avoid amplifying mistakes; and AI should augment existing UI rather than replace it, preserving user control. The post draws on internal team reflections and product decisions around Kendo UI, an MCP server, and an AI Observability Platform.

What We’ve Learned Designing Dev Tools in the Age of AI

Lesson #1: AI Is Best at Getting Us Started

Lesson #4: AI Belongs in the Product—Thoughtfully