Note, I haven't used C in 15 years, have never looked at memcached code and in fact the last time I used memcached was before redis even existed.
It took me ~26 mins which included reading the article, googling the memcached repo, downloading all dependencies, compiling a first build, grepping for references to incr and adding mult with support for negative arguments, refactoring the guts of incr into two functions to support the changes, compiling, fixing a few compiler bugs then testing, given a few more minutes I'd probably be able to get it PR ready with a full test suite.
I did _one_ virtual meetup. After the presentation we were paired into small breakout rooms. Two of the four guys in my room just gave a quick summary of their background and said they were looking for work -- they had nothing else to say.
(a) it ruined the networking time for everyone else and (b) if I had an opening, I'd be less likely to interview them than before.
i haven't been in this particular situation, but people who don't know what to say are all to common. i am not the most sociable guy myself, but i learned to get people talking by asking lots of question, searching for common interests, or simply anything interesting about them. it is a lot of work though, and after such conversations i tend to be exhausted. the irony is that if they didn't want to talk, but get me talking instead, all they would need is to ask a few open questions and then i'd be able to fill the space.
The other participant and I had a pleasant conversation, but the dynamic was weird for the other two who basically said "give me work" without saying anything else.
Please do read a bit about history of TCP and how latency impacts the overall throughout. It's a classic thing and applies to any processing where you need results of some steps to proceed.