Thank you very much -- I guess it's understandable given the tragic circumstances of his death, but Bob very much deserves to be remembered as you described him: an engineer's engineer. I first met him at Foo Camp in 2011, and we had a deeply enthralling conversation about building the Square reader. As it turns out, credit card swipes are (were?) fiendishly complicated! (I still tell others the advice that Bob gave…
"dang: Thank you for the black bar today for Bob" I want to second that.
Remembering Bob Lee
201–210 of 235 posts
Re: Remembering Bob Lee
#202Re: Remembering Bob Lee
#203I interviewed at Google almost 20 years ago, and Bob was one of 5-6 interviewers that I had. I don't remember the other interviewers, but I remember Bob. He was very high energy, and posed a really fun, original question about selective logging. The kind of question that you could tell was born out of his personal experiences at Google, not just something he found in a "ten linked list questions" blog post. The gist…
This is very interesting but I fail to see an issue. You listen to all incoming log messages and only store != success. What am I missing (obviously)
Re: Remembering Bob Lee
#204Re: Remembering Bob Lee
#205Earlier quoted context omitted.
You forgot to mention that the dependency injection library, Guice, that you were asking about was created by Bob himself! CashApp's monolith is still called Franklin today.
Ex-Square chiming in (I fondly remember Project Franklin), he was also arguably the inventor of modern dependency injection as we know it! https://jcp.org/en/jsr/detail?id=330
Re: Remembering Bob Lee
#206I find the obsession of ignoring how a person died shocking. Sure, let's remember the person (I never knew before). But... should we pretend he was not stabbed!? What is wrong with you people? How a person died is very much relevant for that person and for the world you are living in. This reminds me of the Ian Murdock suicide. You know, a very much public person in the tech world. Whose death was very much hush hush…
Re: Remembering Bob Lee
#207I interviewed at Google almost 20 years ago, and Bob was one of 5-6 interviewers that I had. I don't remember the other interviewers, but I remember Bob. He was very high energy, and posed a really fun, original question about selective logging. The kind of question that you could tell was born out of his personal experiences at Google, not just something he found in a "ten linked list questions" blog post. The gist…
This is very interesting but I fail to see an issue. You listen to all incoming log messages and only store != success. What am I missing (obviously)
He was probably looking for a distributed way to label logs and build an ingestion service that shards regionally with high availability, but still able to search and filter within an acceptable time for debugging purposes.
Re: Remembering Bob Lee
#208Re: Remembering Bob Lee
#209Earlier quoted context omitted.
This is very interesting but I fail to see an issue. You listen to all incoming log messages and only store != success. What am I missing (obviously)
It's a system design question. High throughout on the scale of Google means you'd laser any log ingestion service to death. He was probably looking for a distributed way to label logs and build an ingestion service that shards regionally with high availability, but still able to search and filter within an acceptable time for debugging purposes.
Re: Remembering Bob Lee
#210Earlier quoted context omitted.
It's a system design question. High throughout on the scale of Google means you'd laser any log ingestion service to death. He was probably looking for a distributed way to label logs and build an ingestion service that shards regionally with high availability, but still able to search and filter within an acceptable time for debugging purposes.
How can I learn about these topics? Junior self-taught dev, I read these things and kind of see what they're about, but I wouldn't know where to even start with this...
Other than that, several companies (such as Uber) operating on a large scale maintain engineering blogs.