Share Episode         
         
Developers spend more than 50% of their time reading code, making it the single largest expense in software engineering. Despite this massive cost, the industry rarely discusses or optimizes how we read code. So we've brought in Tudor Girba, CEO at Feenk to help us rethink, just how software engineering should be done. Instead of relying on manual reading and generic text editors, teams must shift toward building deterministic, contextual tools to directly extract information and answer questions about their systems.

         

The suggested solution? Contextual and composable micro-tools writen by everyone focused on exposing just the right information at the right time. This creates the opportunity for structural interrogation of your solution.

         

And how many tools should we? We'll if one example of tool is testing, and 50% or more of your code can be tests, imagine what percentage of your software should be actually production related!

         

Most importantly, generic tools fall short, but where can we find how to build the right tools, listen in to find out....

         
💡 Notable Links:         

• ✨ Episode: IDE & Copilot & Critical Thinking
• Book: Moldable software development
• Wardley Map
• Guest Request: Formal Verification

🎯 Picks:         

• Warren - The real stuff: Underwood Ranches Sriracha
• Tudor - The beaches of Normandy