You're right, the developer (or operator) will still need to know how to troubleshoot. For this first stage we're focusing on improving development and iteration speed while maintaining status quo on operating & troubleshooting. One of our design principles is to keep the application debuggable, which means if there's a problem in the application it should be easy for the developer to use the tools and methods they're used to to figure out what's going wrong. Similarly for the infrastructure, since Klotho utilizes existing cloud providers, existing tools are still a good way to debug.

To make sure troubleshooting the code is as smooth as possible, we keep the transformed code as close to the original source as possible. It's important that the code for the application that is actually running in the cloud is recognizable to the authors that wrote it.

Later on, we do plan on trying to tackle this problem (easier to troubleshoot with less knowledge requirement).