dybr

 First, check out what's up there. One case was about adding a field to a returned json. That's kind of stupid that for "returning a json" they had invented an intermediate class, which is jsonified "automatically". Why t.f. do we need this automatic serialization if we can't have a `toJson` right in the class we send? Reminds me a bunch of previous companies, and what's funny, this solution, with shit from Travis Brown, is probably the dumbest. But looks as if it's professional.

Whatever. 

There was also a pr sent me by a bot; it fails the build, and when I cloned it to my computer, some code did not even compile. The piece that was causing warnings was when they mixed Streams' >> and ++. And ++ in streams is defined via >>.

No big deal.

Then, later, we had a "Big Meeting", where our "big manager" was telling us about our big future. She has no education (some college, marketing bs), but since les incompetents love words like "metainformation", she was talking about "metainformation" and a "kernel product" team. The company exists for over 10 years, it turned out there's no kernel. Here I agree, it's a total mess inside. Oh, and she decided to do it all in Go. Ok.

So our team remains, because we are a Scala team. Maybe Mike will go. I have a mixed attitude towards Mike. He's cool. He's rather educated. He's smart. Well, whatever.

Also, they are introducing 24-hour pager duty cycles. Us, contractors, are not touched by that, because it will cost the company too much, paying for extra hours.

Anyway, the first meeting took 1 hour, and the second was 1.5 ("big planning"). It was a pretty relaxed meeting, but meetings are bad for me (unless I'm leading it).

See ya!