Davorin Ruševljan

When looking at a system developed following #MoldableDevelopment, people's attention is attracted by the existing tools. But those are secondary. The most important part is the act of creating a new tool. Take a look at the attached picture. It's a profiler tool that is targeted at the execution of a debugger. - On the left you see the duration of rendering frames, red frames being those that took more than 16s (as we are targeting 60 frames per second). - On the right, you get details of a single frame, one of which is a visualization of which parts requested a relayout and which requested a repaint. This tool helped us improve the performance of our debugger with an order of magnitude. We actually had the performance issue for a long time, but it was only after we figured out what we wanted to see that helped us to materialize the tool that eventually made the problem apparent (the issue was the too eager update of the user interface). Here is the thing: tools are built by someone. That's what matters. For your problems, there are no ready made tools. True, there are approximate tools, but not the tools you really care about. Only you know what those should be. And that's the magic. Learn to build your tools and reasoning about your systems will feel humane.