dybr

 Now I have to kind of schedule my work. Because, well, in the morning I like to work, but then I stay till almost 23 working.- it is stupid.

Anyway, I did check that during the night no memory was leaked, I rest my case, and started looking for the right jvm params.

Found them, put them in build.sbt, started playing with it again.

At 17 we had a meeting, and Renato asked me first, and I told my story, and so he was happy, Jacob was happy, and I almost felt like some people became jealous. Wow. I grow my feelers. 

Anyway, I slapped together my PR, but there were interesting comments from Qian, regarding "why do we need debug output in production code". Right. Should I start quoting Dijkstra? I could. And I'll find that quote, about a plane where all the measuring devices are removed after the plane is built.

Anyway, the problem is different now. It works ok locally, but in Jenkins it complains either about "stylecheck", in the build file (I barely touched it, and more, the plugin does not allow me to say that a build file should be ignore), or about "coverage report" being in the wrong folder (that I already had in another project, and I'm also still clueless).

So by the end of the day I just split that 88-file PR into two; one with "copyright years being updated" (88 files), and another with 6 files that contain some meaningful stuff. I could have left just one update, the jvm gc params, but it won't "check the style" anyway.

Well, tomorrow.

Jeremy, our new enthusiast from NC, is shining; he updated a bunch of docs, and now suggests to fix our builds by using sbt 1.4.7 everywhere (won't work: Scala 2.11 requires sbt 0.14 the latest).

Oh, whatever. I like this kind of enthusiasm. I was like this... триста лет тому назад.

Anyway, feeling good.