а вот что гитхаб говорит о популярности языков

Как я понимаю, это в профессиональной среде. Ну и... кобольщики про гитхаб и не слыхали, наверно.

Боевая тройка, Rust-Scala-Кotlin, на своём месте.

source 

1   Python  
2   Java   
3   Go 
4   JavaScript 
5   C++    
6   TypeScript 
7   PHP    
8   Ruby   
9   C  
10  C# 
11  Nix    
12  Shell  
13  Rust   
14  Scala  
15  Kotlin 
16  Swift  
17  Dart   
18  Groovy 
19  Perl   
20  Lua    
21  DM 
22  SystemVerilog  
23  Objective-C    
24  Elixir 
25  CodeQL 
26  OCaml  
27  Haskell    
28  PowerShell 
29  Erlang 
30  Emacs Lisp

dybr

 So, maybe Jeremey was right, and that other team is really a team of assholes, who knows.

Sam, the bitch from Canada, who was teaching me how to develop software... so, I spent about 3-4 days, trying to figure out how to adapt that monadic spaghetti from one version of library to another, then sent my fix for an additional review to Sam and Esteban - both ignored it silently, so I approved it (it was not my pr after all, I just made it work), and the pr was automatically merged.

Obviously, "that team" was not happy (but they seem to have taken the right to set up the rules of the game), so she just rolled the pr back. For me it's good; I'll pull out of the role of fixing these prs later on, after all, I'm just a humble contractor. The management seems to be just away, busy with other shit/stuff. Brad only has time to ask me whether I looked into that problem with wrong email address being used, etc. I was sure it was all about eventual consistency between the hundreds of services running around, like those athletes at Boston marathon. I did not answer it yet, thinking about what can I say? Make a list of information I think I need to even investigate it? I can fix code when I know what code we are talking about. And we don't have a "hound" app that looks through the whole collection of repositories.

Oh, whatever.

Another thing, that case, "get rid of persistence module", I did get rid of it, eventually, migrating its remaining kafka sinks to the remaining module. But then, strangely, Esteban was investigating the waves of processor peaks in the same project, so they want me to postpone the merge. Oh, FIIC, right.

I started looking into the documenter. There was one bug, when I changed the scala code parsing, I did not check the behavior on another project, so there. Added a test. BTW, these tests don't run in IntelliJ, have to run them in sbt (in IntelliJ). 

But ok, after I fixed that, I decided to look, wtf is going on with the output. And it turned out that Bermi's part, the generator of README, uses shfmt, which does not expect parameters wrapped in '<', '>' (duh), so... so I wrote to him eventually, asking, where in the scripts we have this? I could probably find it myself, but it was about 6:30 in the evening, too late to work.

So that's it for today.

Oh, and I got yet another "thank you" from Janet. We did not have a "standup", just a couple of people posted the status on slack - Esteban and me. But Janet does need information, does not she?

And besides, at one of the meetings Esteban told me he's watching "Turning Point" on Netflix. He said it was about the last half of the previous century, and how the USSR... and how it was in the '90s... for someone from Columbia it's as exotic as the life of Uighurs in China's gulags. He said he can't believe how dangerous it was in the USSR. A guy from Columbia finds it dangerous. We did not see it this way.

Well, whatever. And so it goes.