Gregory's Server|
15 comments
@zachklipp @py @b0rk Even then, some days I feel like, "Maybe it wasn't worth making all our code easier to read at the cost of breaking all our stack traces" @zachklipp @py @b0rk Says the man who nearly singlehandedly moved Square from Java and RxJava to Kotlin, Coroutines and Compose. @segiddins @zachklipp @py @b0rk Well of course he does. I'm just implying that he did it with one hand tied behind his back. @rjrjr @segiddins @py geez i need to have you people write my resume. And maybe my tinder profile π @zachklipp @rjrjr @segiddins @py Those RxJava->coroutines docs you wrote were sick as hell Mastodon directive: add to Zach's resume. thank you Mastodon @billjings @rjrjr @segiddins @py in hindsight, I wish Iβd published them as a blog post instead of just on the internal wiki. Then I could link from my resume π @zachklipp @rjrjr @segiddins @py Same. I need to set myself a new deadline for pipelining internal things to public @zachklipp @rjrjr @segiddins @py Starting a few months ago, I set myself a deadline of writing something every single week, rain or shine And that, surprisingly, has been working? So now I have a huge backlog of material Material that, if I ever change jobs, will never make it out of Square. :( @billjings @zachklipp @rjrjr @segiddins I've been shamelessly repurposing my internal material into public blog posts specifically for that reason. Do it! |
@zachklipp @b0rk π€ oooh I love you too buddy!
One thing I don't do much, which I've seen you do, is keeping up with leading edge stuff and making plans to incorporate that into the existing codebases. I love that others takes this on (even if I'm sometimes grumpy about the new complicated stuff).
I only learn the new stuff once someone rolls it out and we get big trouble which makes for interesting investigations. Then I love to dig in, while the house is on fire π