Humans of Computer Systems: Frenchie

-

Programming

How did you learn to program?

I was lucky that our 5th grade (age 9-10) teacher knew how to use the computers in the school. I learned a little bit of BASIC on a Thomson MO-5. Then I had other hobbies until high school, at which point I joined a semi-formal programming class hosted by a math teacher. That's where I really cut my teeth with Pascal and x86 assembly. Later I got a degree in software engineering.


Tell us about the most interesting/significant piece of code you wrote.

I would mention two. 

One is a critical component in a distributed system: several thousand lines of code, highly concurrent, performance sensitive, high risk (data corruption), lots of tests, months to get it right, years of refinements (optimizations, new use cases). Very valuable. It is far from perfect in several ways, but it worked very well in production for many years across many customers. An invisible part of a complex system.

The other is a short script (a couple hundred lines), a mix of shell and awk. It barely changed after one year, but users kept using it for over a decade. Fun to write, easy to use, with human users.

The first thing paid my salary several times over, it was deep, important work. The second was invisible to the business side but very useful to operations, and very fun to write and to use, and I got to help users solve their problems with it. I wish I could spend more (all?) of my time writing such small, useful programs, and not just large, complex systems.


Who did you learn most from about computer systems?

Most of what I learned, I learned reading stuff written by many on the internet. But I think I learned at lot of fundamental things, and in more pleasant ways, from programmer friends in high school and college.


Who is the greatest programmer you met, and what is impressive about them?

Probably this guy who could write high-performance HP48 assembly code for a stunning video game, at a time when we should both have been 110% busy with academic duty (and the guy got outstanding academic results).


What is the best code you have seen?

I'm not sure what I would call best. But I was somewhat impressed by CGEN, the system in GNU binutils that, based on a CPU ISA specification written in Scheme, generates almost all of the C code for an assembler, a disassembler and a simulator.


What do you believe are the most important skills to be successful in your field?

Some level of optimism and self-confidence, because you need to pick up new tech skills as time goes by. Paired with curiosity, because (almost) nobody is going to tell you what to learn next.

A good command of oral and written communication, because you cannot work alone all the time: at a minimum, you work for someone, you must learn from someone.

Personal management, like time management, idea management, note taking, drafting (to put ideas in writing, but not necessarily in code). Having a sense of what needs to be done now, later, or never. Don't be a mouse constantly running in a wheel, without a sense of direction.

Debugging, because very early in our journey, and then time and again, we reach the limits of our understanding, and must stay on top of the systems we create and manage.

Some amount of problem solving in general, some CS fundamentals (data structures, complexity, basics of OS, hardware and language).


What quality or ability do you value most in a computer systems person?

The ability to understand or design complex systems, where components interact to solve the right problems without creating (too many) new problems.


Personal

Which of your work/code/accomplishments are you most proud of?

I reinvented distributed tracing from first principles (then read the relevant papers), promoted the idea, designed and developed a working implementation. I was very proud that I came up with the idea on my own.


What comes to you easy that others find hard? What are your superpowers?

I tend to spot a lot of concurrency bugs. It's rather depressing, because it reminds me that there are so many incorrect programs out there, crashing or corrupting the data!


What was a blessing in disguise for you? What seemed like a failure at the time but led to something better later for you?

My very first project was not the one I was hired for; turns out, I made most of my career from the expertise acquired then.


What do you feel most grateful for?

As a seasoned programmer, I probably never will have a hard time finding a job with a decent pay. Since I graduated, money has never been an issue.


What does your perfect day look like?

Hear about someone's itch, find out I know how to solve it with a small piece of code, write it, give it to them, make them happy!


What made you most happy in the last year?

We got vaccines for COVID.


Work

What was your biggest mess up? What was the aftermath?

A script I wrote had a bug that corrupted data. The first engineer who used it was careful in rolling it out, sensed a problem, mitigated the issue, notified me: I fixed the bug, tested better, helped the engineer restore the data, and no data got lost in the end. But I felt quite bad for a few hours, and lucky that I worked with a smart guy.


What was your most interesting/surprising or disappointing interaction at work?

Some people appear way smarter than they actually are: that guy could juggle with a lot of advanced concepts and lingo, he could write a lot of code very quickly, but his systems were full of glaring holes. Any objection to his designs, he would counter with a proposal adding extra complexity that nobody really understood. Eventually I learned to laugh at the absurdity of the situation, but it took me years.


What do you like most about your job/profession?

The medium (code, data) is infinitely malleable.

The need for decent programmers gives us a lot of bargaining power, so we can enjoy good pay and flexibility that most people can only dream of (which is unfair).


What do you dislike most about your job/profession?

The field is so new that companies are immature and inefficient (and sometimes plain dangerous), and there is so much demand and money that companies get away with it.

Some days I think that a moderate amount of frugality would set certain things straight. Then I remember: it also makes people cut more corners.


What would be the single change that would improve your work environment most?

A healthy management structure: people managers who actually know how to manage people, and execs who understand systems of people, and know how to set up culture, incentives, and feedback loops between cooperating humans/teams.


Technical

What do you think are the hardest questions in your field?

What problems should we solve.

What should we build, what should acquire, what should we discard.


What are you most disappointed about the state-of-the-art in your field?

Most computer users have extraordinarily complex and mature apps to help them do their work.

Most programmers are stuck with ancient text editors, debug with print statement, design with MS Word, test with a few unit tests, and just try to guess what would be valuable to users. Our entire toolbox feels lame, at least in most companies, compared to e.g. a CAD suite or video editing.

Why can't I make good systems like others make good spreadsheets?

We should be using more: simulation, model checking, profiling, data viz (for perf analysis, or debugging).


What are the topics that you wish received more attention? What do you think is a promising future direction in your field?

Modeling in general is great, model checking in particular is a game changer.


What is your favorite computer systems paper? Why?

The first that comes to mind is the Google Dapper paper. It exposes a simple, not new, yet very useful idea, it has useful charts and screenshots, it shows great feedback from field use. And when I read it, I felt a lot of validation for my own findings.


What are the most interesting blogs/twitter accounts you follow?

But I really recommend reading books, because books can take you so much deeper.  I liked those:

  • How to solve it, by G. Polya: problem solving for math, applies to other domains
  • The mythical man-month, by F. Brooks: a (somewhat dated) view of management issues at IBM in the 70s. Still some good parts, mostly the questions it asks.
  • High output management, by A. Grove: a view of management at Intel by their star CEO. Biased towards large companies, still some good practical advice for small entities.
  • Thinking, fast and slow, by D. Kahnemann: how our brains trick us into thinking the wrong things (cognitive biases).
  • Range, by D. Epstein: how generalists beat experts in many ways (I am prone to glorifying expertise, and found this refreshing).


If you enjoy reading this series, consider taking 10 minutes and submitting a response. All questions are optional. You can skip most, and tell a lot more on other questions you choose. 

Comments

Post a Comment

Popular posts from this blog

Hints for Distributed Systems Design

-
This is with apologies to Butler Lampson, who published the " Hints for computer system design " paper 40 years ago in SOSP'83. I don't claim to match that work of course. I just thought I could draft this post to organize my thinking about designing distributed systems and get feedback from others. I start with the same  disclaimer Lampson gave. These hints are not novel, not foolproof recipes, not laws of design, not precisely formulated, and not always appropriate. They are just hints.  They are context dependent, and some of them may be controversial. That being said, I have seen these hints successfully applied in distributed systems design throughout my 25 years in the field, starting from the theory of distributed systems (98-01), immersing into the practice of wireless sensor networks (01-11), and working on cloud computing systems both in the academia and industry ever since. These heuristic principles have been applied knowingly or unknowingly and has proven
Read more >>

Learning about distributed systems: where to start?

-
This is definitely not a "learn distributed systems in 21 days" post. I recommend a principled, from the foundations-up, studying of distributed systems, which will take a good three months in the first pass, and many more months to build competence after that. If you are practical and coding oriented you may not like my advice much. You may object saying, "Shouldn't I learn distributed systems with coding and hands on? Why can I not get started by deploying a Hadoop cluster, or studying the Raft code." I think that is the wrong way to go about learning distributed systems, because seeing similar code and programming language constructs will make you think this is familiar territory, and will give you a false sense of security. But, nothing can be further from the truth. Distributed systems need radically different software than centralized systems do.  --A. Tannenbaum This quotation is literally the first sentence in my distributed systems syllabus. Inst
Read more >>

Making database systems usable

-
Image
C. J. Date's Sigmod 1983 keynote, "Database Usability", was prescient. Usability is the most important thing to the customers. They care less about impressive benchmarks or clever algorithms, and more about whether they can operate and use a database efficiently to query, update, analyze, and persist their data with minimal headache. (BTW, does anyone have a link to the contents of this Sigmod'83 talk? There is no transcript around, except for this short abstract .) The paper we cover today is from Sigmod 2007. It takes on the database usability problem raised in that 1983 keynote head-on, and calls out that the king is still naked.  Let's give some context for the year 2007. Yes, XML format was still popular then. The use-case in the paper is XQuery. The paper does not contain any  reference to json. MongoDB would be released in 2009 with the document model; and that seems to be great timing for some of the usability pains mentioned in the paper! Web 2.0 was in
Read more >>

Looming Liability Machines (LLMs)

-
As part of our zoom reading group ( wow, 4.5 years old now ), we discussed a paper that uses LLMs for automatic root cause analysis (RCA) for cloud incidents. This was a pretty straightforward application of LLMs. The proposed system employs an LLM to match incoming incidents to incident handlers based on their alert types, predicts the incident's root cause category, and provides an explanatory narrative. The only customization is through prompt-engineering. Since this is a custom domain, I think a more principled and custom-designed  machine learning system would be more appropriate rather than adopting LLMs. Anyways, the use of LLMs for RCAs spooked me vicerally. I couldn't find the exact words during the paper discussion, but I can articulate this better now. Let me explain. RCA is serious business Root cause analysis (RCA) is the process of identifying the underlying causes of a problem/incident, rather than just addressing its symptoms. One RCA heuristic is asking 5 Why&#
Read more >>

Foundational distributed systems papers

-
I talked about the importance of reading foundational papers last week. To followup, here is my compilation of foundational papers in the distributed systems area. (I focused on the core distributed systems area, and did not cover networking, security, distributed ledgers, verification work etc. I even left out distributed transactions, I hope to cover them at a later date.)  I classified the papers by subject, and listed them in chronological order. I also listed expository papers and blog posts at the end of each section. Time and State in Distributed Systems Time, Clocks, and the Ordering of Events in a Distributed System. Leslie Lamport, Commn. of the ACM,  1978. Distributed Snapshots: Determining Global States of a Distributed System. K. Mani Chandy Leslie Lamport, ACM Transactions on Computer Systems, 1985. Virtual Time and Global States of Distributed Systems.  Mattern, F. 1988. Practical uses of synchronized clocks in distributed systems. B. Liskov, 1991. Expository papers
Read more >>

Advice to the young

-
Image
I notice I haven't written any advice posts recently. Here is a collection of my advice posts pre 2020. I've been feeling all this elderly wisdom pent up in me, ready to pour at any moment. So here it goes. Get ready to quench your thirst from my fount of wisdom. No man, think for yourself, only get what works for you. It is called foundations, not theory Foundations of computer science (or rather any field of study) are the most important topics you can learn. These lay down the frame of thinking/perspective for that area of study. Yet, I am saddened to hear these called as "theory", and labeled as "unpractical". This couldn't be farther from the truth. Take a look at how I recommend studying distributed systems . Don't you dare call this "theory" and "unpractical". This lays the bedrock that you build your practice on. Don't skimp on the foundations. Don't build your home on quicksand. Keep your hands dirty, your mind cl
Read more >>

Linearizability: A Correctness Condition for Concurrent Objects

-
Image
This paper is from Herlihy and Wing appeared in ACM Transactions on Programming Languages and Systems 1990. This is the canonical reference for the linearizability definition. I had not read this paper in detail before, so I thought it would be good to go to the source to see if there are additional delightful surprises in the original text. Hence, this post. I will dive into a technical analysis of the paper first, and then discuss some of my takes toward the end. I had written an accessible explanation of linearizability earlier; you may want to read that first. I will assume an understanding of linearizability to keep this review at reasonable length. Introduction I love how the old papers just barge in with the model, without bothered by pleasantries such as motivation of the problem. These are the first two sentences of the introduction. "A concurrent system consists of a collection of sequential processes that communicate through shared typed objects . This model encompass
Read more >>

Scalable OLTP in the Cloud: What’s the BIG DEAL?

-
Image
This paper is from Pat Helland, the apostate philosopher of database systems, overall a superb person, and a good friend of mine. The paper appeared this week at CIDR'24. (Check out the program for other interesting papers). The motivating question behind this work is: " What are the asymptotic limits to scale for cloud OLTP (OnLine Transaction Processing) systems? " Pat says that the CIDR 2023 paper "Is Scalable OLTP in the Cloud a Solved Problem?" prompted this question.  The answer to the question? Pat says that the answer lies in the joint responsibility of database and the application. If you know of Pat's work, which I have summarized several in this blog , you would know that Pat has been advocating along these lines before. But this paper provides a very crisp, specific, concrete answer. Read on for my summary of the paper. Disclaimer: This is a wisdom and technical information/detail packed 13-page paper, so I will try my best to summarize the sa
Read more >>

Understanding the Performance Implications of Storage-Disaggregated Databases

-
Image
Storage-compute disaggregation in databases has emerged as a pivotal architecture in cloud environments, as evidenced by Amazon ( Aurora ), Microsoft ( Socrates ), Google (AlloyDB), Alibaba ( PolarDB ), and Huawei (Taurus). This approach decouples compute from storage, allowing for independent and elastic scaling of compute and storage resources. It provides fault-tolerance at the storage level. You can then share the storage for other services, such as adding read-only replicas for the databases. You can even use the storage level for easier sharding of your database. Finally, you can also use this for exporting a changelog asynchronously to feed into peripheral cloud services, such as analytics. Disaggregated architecture was the topic of Sigmod 23 panel . I think this quote summarizes the industry's thinking on the topic. "Disaggregated architecture is here, and is not going anywhere. In a disaggregated architecture, storage is fungible, and computing scales independently.
Read more >>

Designing Data Intensive Applications (DDIA) Book

-
Image
We started reading this book as part of Alex Petrov's book club . We just got started, so you can join us, by joining the discord channel above. We meet Wednesday's 11am Eastern Time.  Previously we had read transaction processing book by Grey and Reuters. This page links to my summaries of that book. Chp 1. Reliable, Scalable, and Maintainable Applications I love the diagrams opening each chapter. Beautiful! The first chapter consists of warm up stuff. It talks about the definitions of reliabilty, scalability, and maintainability. It is still engaging, because  it is written with an educator and technical blogger voice, rather than a dry academic voice. This book came out on 2017. Martin is working on the new version. So if you have comments for things to focus on for the new version, it would be helpful to collect them in a document and email it to Martin. For example, I am curious about how the below paragraph from the Preface will get revised with 8 more years of hindsight:
Read more >>