So I've decided to go about converting a Java project that I've been working on to Kotlin a little bit at a time. I started out with basic entity classes converting them to simple `data class`es in Kotlin.

Eventually, I got to my first beast of a class to refactor. This class had over 40 service classes depending on it, so even a little hiccup would throw everything into chaos.

I finish all of the changes on all of the dependent classes, update the tests, and the configurations (as necessary), and I was finally ready to spin up the app to test for any breaking changes I may have introduced...

Well - I broke everything! But I was sure I couldn't have! So what the hell happened?

Turns out that as I was building my project with a Gradle watch, at one point something failed to compile, which threw an unhandled exception in the gradle daemon that was never reported.

So when I tried to run my app, gradle would continually re-throw the error in the app I asked it to run...

After turning the daemon off and on again, the app worked like a charm.

TL;DR warning!

Please help me out on this, fellow ranters:

I have a js app, a sandbox for musicians, which everyone is checking out once, then after fiddling around, they never really come back.

What can I do, to make an app more desirable, so that musicians would incorporate my tool into their musical repertoir?

One advice I've got from a friend is to save the session, like jsfiddle, so that the user can continue his/her work later and don't have to start all over.

If you want to check out my app, then the link is in my profile.