🕯 R.I.P 达叔.
I have finished the following books:
- Computer Systems: A Programmer’s Perspective
- Designing Distributed Systems: Patterns and Paradigms for Scalable, Reliable Services
Recommended by @laike9m.
A privacy-first, open-source(frontend now, backend later) platform for knowledge sharing and management.
Inspired by Roam Research, Workflowy, and Emacs org-mode.
Async communication is about allowing team members to “consume and respond to messages on their own time instead of on the sender’s schedule.”
- Compile list of papers and articles.
- Skip around the list. Read 10% of each paper and choose the ones worth the time to delve into.
- The bad way is reading from the first word to the last word.
- Read the title, the abstract, and the figures.
- Read the intro, the conclusions, all figures and skim the rest.
- Skim related work.
- Read the paper but skip the math.
- Read whole things but skip parts that don’t make sense.
- Read to answer the questions:
- What did authors try to accomplish.
- What can you use yourself?
- What other references do you want to follow?
- Math and code:
- Re-derive/Re-implement from scratch.
Turn the contributions chart to a 3D model. Here is mine in 2020.
A curated list of papers.
Some tips about reducing the size of the Rust executable.
Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.
— Melvin E. Conway
- Mistake 1: Thinking people give feedback the way they want to receive it
- Mistake 2: Trying to do everything yourself as a manager is the best way to help
- Mistake 3: Communicating something one time is enough
- Mistake 4: You have to have everything together all the time
- “Tell me more.”
- “Thanks for your understanding.”
- “Am I making sense?”
- Absolutely nothing.