@leemiyinghao: > ...which means Mark has had to bump out a little bit too to do more of the orchestration and code review, ... > He's not writing code as much anymore. And as most people will experience when this happens in their career, that sucks. You suddenly stop feeling productive when you're not writing code anymore. > And previously, you would measure your success in a day by how much code you had written, how much time you spent in your editor, and how many problems you had solved. If you're spending your time in the GitHub PR tab and not in your editor, you feel like you're not getting anything done. > And the amount of times Mark would have a crazy day where he did a ton of code review, got a ton of stuff shipped, handled a ton of support cases, all those things, but felt like he didn't get anything done simply because he wasn't in his editor at all. It's it became like an everyday occurrence and he was not loving that feeling because it sucks and I've seen this happen to a lot of developers as they move towards management towards tech leads towards roles where their job becomes less writing code and more orchestrating code. > This is part of what makes a senior engineer. ⋯⋯對，那種感覺真的是😢 人生中超過一半的時間在一點一點建構出自己想像中的世界，突然之間那不再是你的工作了。以前你跟著整個團隊一起努力、一起開心、一起崩潰，但你知道自己不再會是那個分擔大家工作的人了。你站在一個更高的位置可以看到每個人身上的壓力，卻又沒有辦法出手去幫忙。 轉變的當下會非常，非常焦慮。