April 2024

Leaving Rust gamedev after 3 years by LogLog Games

2017 Letter to Shareholders by Jeffrey P. Bezos

Intrinsic or Teachable?

First, there’s a foundational question: are high standards intrinsic or teachable? If you take me on your basketball team, you can teach me many things, but you can’t teach me to be taller. Do we first and foremost need to select for “high standards” people? If so, this letter would need to be mostly about hiring practices, but I don’t think so. I believe high standards are teachable. In fact, people are pretty good at learning high standards simply through exposure. High standards are contagious. Bring a new person onto a high standards team, and they’ll quickly adapt. The opposite is also true. If low standards prevail, those too will quickly spread. And though exposure works well to teach high standards, I believe you can accelerate that rate of learning by articulating a few core principles of high standards, which I hope to share in this letter.

Shareholder letter 1998 by Jeffrey P. Bezos

During our hiring meetings, we ask people to consider three questions before making a decision:

• Will you admire this person? If you think about the people you’ve admired in your life, they are probably people you’ve been able to learn from or take an example from. For myself, I’ve always tried hard to work only with people I admire, and I encourage folks here to be just as demanding. Life is definitely too short to do otherwise.
• Will this person raise the average level of effectiveness of the group they’re entering? We want to fight entropy. The bar has to continuously go up. I ask people to visualize the company 5 years from now. At that point, each of us should look around and say, “The standards are so high now – boy, I’m glad I got in when I did!”
• Along what dimension might this person be a superstar? Many people have unique skills, interests, and perspectives that enrich the work environment for all of us. It’s often something that’s not even related to their jobs. One person here is a National Spelling Bee champion (1978, I believe). I suspect it doesn’t help her in her everyday work, but it does make working here more fun if you can occasionally snag her in the hall with a quick challenge: “onomatopoeia!”

LLVM is Smarter Than Me

What is Longevity? | Peter Attia, M.D.

Database Fundamentals by tontinton

High-Speed Packet Transmission in Go: From net.Dial to AF_XDP by Andree Toonk

You are firing people too late by Anton Zaides

If you imagine the scenario of an employee quitting, and you feel relieved, and not upset – that’s a sign you need to let them go.

What makes a great technical blog by Phil Eaton

• Tackle hard and confusing topics
• Show working code
• Make things simpler
• Write regularly
• Talk about tradeoffs and downsides
• Avoid internet slang, memes, swearing, sarcasm, and ranting

Designing potion items correctly by Woojin Kim

This approach is highly sophisticated and well-suited. It almost seems as though he has designed something similar on numerous occasions before.

A year in the life of a platform team to build Japan's largest delivery service by 송재욱

Maximize personal and professional self-interest

The ‘life-changing questions’ from Silicon Valley's top career coach by Keeyong (기용) H

After three weeks of sobriety by KBS Secrets of the birth, old age, disease, death

The likelihood of alcohol dependence and depression co-existing is 30% to as much as 50%.

Every team will have conflict - 4 stages of team development by Hyunsol Park

Forming, Storming, Norming, Performing

Right guide for forming a team.

Tasks should be assigned in much greater detail for each role, goal, and process, with the goal of communicating frequently and gaining understanding through task performance.

Spend much more time explaining roles, goals, and processes with the expectation that they won't ask questions or voice their opinions until they feel comfortable, and actively check in with them to see if they don't understand or need clarification. Intentionally do a lot of activities to create a sense of security and bonding.

Beyond Safety and Speed: How Rust Fuels Team Productivity by Lars Bergstrom

Rust teams at Google are as productive as ones using Go, and more than twice as productive as teams using C++.

March 2024

Some of My Favourite Query Planning Papers by Justin Jaffray

Money spent, time passed, no impact by HoonLee

A good team uses people skills, not money.

멘토링 이야기 #14 퇴사의 기술을 알고 싶습니다. by Keeyong H.

1. 그만두기로 결정했다면 (즉 무슨 카운터 오퍼를 지금 회사에서 주더라도 그만둘 생각이라면) 먼저 매니저와 이야기를 시작해서 마지막 날 정하고 내 일을 누가 대신 할지 정한다. 특별한 이유가 없는한 2주가 딱 좋은 것 같다. 하지만 당장 일을 대신할 사람을 찾기 힘든 곳이라면 시간을 더 여유있게 잡지만 한달 이상은 너무 길다고 본다.

2. 어떤 메시지를 퇴사 이유로 보낼 것인지 먼저 바로 위 매니저와 이야기한다. 최대한 솔직하되 어떤 메시지를 전달할 것인지 매니저가 아는 것이 여러모로 좋고 그 메시지에 충실하게 모두에게 이야기하는 것이 좋다. 즉 사람에 따라 말을 바꾸지 않는다. 앞에서 이야기했던 것처럼 되도록이면 감정적인 메시지를 전달하지 않는다. 감정적인 메시지 밖에 생각이 안 난다면 상처가 있다는 증거니 상처를 분명히 인지하고 치유하는 노력을 병행하는 것이 다음 직장에서 잘 하는데 도움이 된다. 안 그러면 상처와 분노를 그대로 들고 새 직장에서 시작할 가능성이 높다.

Ensure consistency in your message regarding the reason for your departure, regardless of the individual.

SSDs Have Become Ridiculously Fast, Except in the Cloud by Viktor Leis

How I write HTTP services in Go after 13 years by Mat Ryer

Result and process by @lqez

결과물을 우아하게 하는 일에 집중하는 사람과 과정을 우아하게 하는 일에 집중하는 사람 둘 다 모두 대단한 사람이라고 본다. 많은 사람들은 둘 다 신경쓰지 않고 적당히 하거나 둘 다 신경쓰느라 한 발자국 내딛기도 힘들어 했다.

I'm all about getting results.

February 2024

From slow to SIMD: A Go optimization story by Camden Cheek

Go 1.22 Release Notes

Related documents:

• Go 1.22 Released by Andrew Phillips
• What's Coming in Go 1.22 - Daniel Martí - November Gophers 2023

Start With the Go Standard Library by Matthew Sanabria

나는 일을 즐기며 일할 수 있을까? by Woojin Kim

이 분은 그냥 순수하게 자기 하고 싶은 일을 하고 있을 뿐이고 회사에서 오랜 시간 즐겁게 머물며 현대에 분업화 된 여러 가지 일에 관심을 가진 나머지 그냥 자연스럽게 팀에서 일어나는 모든 일을 알고 있을 뿐이었습니다.

Translation: This person is just doing what he wants to do, and he has been staying at the company for a long time, enjoying various modernized tasks, so he naturally knows everything that happens in the team.

What’s New in Go 1.22: reflect.TypeFor by Carlana Johnson

What’s New in Go 1.22: slices.Concat by Carlana Johnson

Accidentally Quadratic Constant Folding

벌이는 놈, 말리는 놈, 치우는 놈 by Kihong Bae

Who am I? Perhaps a cleaner?

January 2024

Short-lived Datacenter

Authors: Michael Wawrzoniak, Ingo Müller, Rodrigo Bruno, Ana Klimovic, Gustavo Alonso

Peer-to-Peer Communication Across Network Address Translators

Authors: Bryan Ford, Pyda Srisuresh, Dan Kegel

TCP Connections for P2P Apps: A Software Approach to Solving the NAT Problem

Author: Jeffrey L. Eppinger

InfiniCache: Exploiting Ephemeral Serverless Functions to Build a Cost-Effective Memory Cache

Authors: Ao Wang and Jingyuan Zhang, George Mason University; Xiaolong Ma, University of Nevada, Reno; Ali Anwar, Lukas Rupprecht, Dimitrios Skourtis, and Vasily Tarasov, IBM Research–Almaden; Feng Yan, University of Nevada, Reno; Yue Cheng, George Mason University

2023-04부터 실천중인 스프린트 기반의 팀 업무 프레임워크

• 회의록을 작성한다
• 회의 목표를 정하고 시작한다
• 목표를 달성하면 회의를 빨리 끝낸다

• Write the meeting notes
• Set the goal of the meeting and start
• End the meeting as soon as the goal is achieved

만약 정보전달성 회의라면 가급적 회의를 하지 말고 이메일이나 문서로 공유한다.

If it is an information transfer meeting, it is better not to have a meeting and share it by email or document.

Whole world richer by Jeff Bezos

What does cost reduction really mean? It means inventing a better way. Right, and when you invent a better way, you make the whole world richer. So, you know, whatever it was, I don't know how many thousands of years ago, somebody invented the plow. And when they invented the plow, they made the whole world richer because they made farming less expensive. And so it is a big deal to invent better ways. That's how the world gets richer.