Everything is My Fault

2021-03-28T08:00:00+08:00

I’ve been panic-reading management and leadership books in preparation for my new job as SVP of Engineering at Wego</a> (something that I'll probably write about). One of the books I really enjoyed was Turn the Ship Around</a>. This led to me devour other sources of knowledge from the author, David Marquet: his bite-sized YouTube videos</a> and Leadership is Language</a> are awesome.

Before reading these books, I’d a pretty strong bias against military-flavoured leadership books — the military that I had the opportunity to be a part of did not impress my young mind as being particularly strong at leadership. And I'd judge as naive the people who try to apply what they learnt in or from the military to the business arena.

As my past self has repeatedly learnt, there're gems to be found in unexpected, unsolicited perspectives.

But this is blog post is not about these books – I might write about them in future because they taught me a lot about leadership and using better words to communicate what I really mean.

Rather, I want to write about one of the most valuable takeaways from another book written by military leaders: Extreme Ownership</a>. And it's this, paraphrased heavily by me:

Everything is my fault. And when I see it that way, I can fix it. If someone isn’t doing what I want them to do, look in the mirror first and figure out what I can do to better enable this.</blockquote>
In truth, I lied – there are 2 takeaways in that:

Taking ownership of everything keeps me in a positive, problem-solving mindset.</li>
If my manager/reports/peers/executives are not doing what I need them to do, stop complaining about it. Instead, since it's my fault, ask what do I need to do.</li> </ol>
These are brilliant reminders for two very common occasions when working in teams: facing setbacks, and situations of unclear ownership (which often means no ownership).
It also equips me with some handy organizational smells (akin to code smells</a>):

Are people really supported when they're asked to work on an initiative? Or are they consumed by their </a>day-to-day whirlwind</a> while their managers are wondering why nothing is getting done?</li>
Are people speaking about problems but seldom speaking about their part in the solution?</li>
Any hint of placing blame really grinds my gears</a>. "They should get their shit together." "It can't be that hard to do X." I'd smile and remember the days I'd hop on their cathartic ride of placing blame. I struggle with helping people be aware of the impact of what they are doing. Send advice.</li> </ul>
For a quick idea of whether Extreme Ownership</a> is worth your time (and we have very little time), I recommend Mike Crittenden's book notes of Extreme Summary</a>. If you've got the time, the entire book is a recommended 5-star read.

Remapping keys on macOS

2020-06-24T08:00:00+08:00

I ramble a bit here - you may want to skip to how to remap keys on macOS</a>.

I attended WWDC</a> for the first time ever (making lemonade in the COVID-19 situation), and after watching the keynote</a>, got pretty excited about macOS Big Sur.

I wanted to install the macOS Big Sur developer beta but not at the expense of making my main development MacBook Pro virtually unusable. One of the things I thought I really needed working was Karabiner-Elements</a>, which I use to remap keys, specifically:

Caps Lock</code> to Esc</code></li>
Esc</code> to `</code></li> </ul>This particular remapping is really because I use `</code> (backtick) as my tmux</a> prefix key. I picked this up from an ex-colleague</a> after watching him fly while switching tmux panes. And I use either a compact 60% or 65% keyboard which meant I didn't have a dedicated `</code> key - I'd have to hit Fn-Esc</code> which is even more terrible than the default of Ctrl-B</code>. Unsurprisingly, Karabiner-Elements was not working in Big Sur</a>. Not satisfied with that, I quickly found that macOS has supported native key remapping</a> since macOS Sierra via the hidutil</code> command-line tool. If you're not beyond scrappily writing some JSON and XML, this just works: Decide what keys you want to remap. In my case, I wanted to remap Caps Lock</code> to Esc</code>.</li> Apple's docs</a> say: The keys take a hexadecimal value that consists of 0x700000000 or’d with the desired keyboard usage value</blockquote> Pretty cryptic, but what it really means is you just have to add 0x700000000</code> to your key's "usage ID" in this table</a> (techically, this is a bitwise OR</code>, which is not addition, but the usage IDs are small enough for it to not matter). </li> Caps Lock</code>'s usage ID is 0x39</code>. Adding 0x700000000</code> to that gives 0x700000039</code>. </li> Esc</code>'s usage ID is 0x29</code> - we'll use 0x700000029</code>.</li> Caps Lock</code> (0x700000039</code>) is the source, so we will specify "HIDKeyboardModifierMappingSrc": 0x700000039</code>.</li> Esc</code> (0x700000029</code>) is the destination, so we will specify "HIDKeyboardModifierMappingDst": 0x700000029</code>.</li> Repeat for each pair of keys you want to remap.</li> Try it out in the command-line: hidutil property --set '{"UserKeyMapping":[ { "HIDKeyboardModifierMappingSrc": 0x700000039, "HIDKeyboardModifierMappingDst": 0x700000029 }, { "HIDKeyboardModifierMappingSrc": 0x700000029, "HIDKeyboardModifierMappingDst": 0x700000035 } ]}'</pre> </li> This remapping will be undone whenever you reboot your Mac, so one way to persist the remapping is to run the hidutil</code> command every time your Mac boots. For that, we can rely on Launch Agents</a>. Create a file named ~/Library/LaunchAgents/com.example.KeyRemapping.plist</code>:

chuyeow.wtf

Everything is My Fault

Remapping keys on macOS