What happened this week?

My most fun work task this week has been to debug a service written in Kotlin. I got notified because one endpoint is throwing 500 with the sidenote that one never performed well. Turns out the data was fetched too many times and someone tried to make it more performant by making it run in parallel, like 30 times. That reminded me of Bill Kennedy’s workshop in Berlin this year I attended. As a sidenote he explained how the resource definition in Kubernetes works. Naive me, thought that 250ms is concerning a time duration. But 250ms == 25% of one cpu core. Actually that service is deployed. with 100ms == 0.1 CPU. What’s the point of processing that in parallel?

What I was watching

  • I’m eventually catching up with the talks from Gophercon that I have missed. the business of go
  • And I also managed to watch my own for the first time. It’s been turtoure to watch myself on stage.
  • This talk about website optimization by Andreas Taranetz. https://www.youtube.com/live/KRemC82gsBk
  • On Netflix I’m still rewatching Dark and I started with Monk S1E1 which is surprisingly entertaining.

What I was reading