About this episode

The episode discusses the importance of building contextual tools for software engineering to optimize code reading and improve efficiency.

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…

People in this episode

Hosts: Will Button, Warren Parad

Guest: Tudor Girba

Topics covered

• software engineering
• code reading
• development tools
• micro-tools
• contextual tools

Keywords

• software engineering
• code reading
• development tools
• micro-tools
• contextual tools
• deterministic tools
• structural interrogation

Mentioned in this episode

Organizations: Feenk

More episodes of Adventures in DevOps

• Technically We Have Code Reviews and the LLM Semantic Layer · July 9, 2026 · 1h 0m
• Who Needs Testers Anyway? · June 25, 2026 · 55 min
• You Wouldn't Implement A Database · June 18, 2026 · 53 min

Explore listener stats, chart rankings, contacts and more on the Adventures in DevOps podcast page.