Updates: 3 Months

After many months of anticipation and multiple delays in production, I finally have on my head a pair of “the world’s highest fidelity wireless headphones.”

And I think I will agree with their claim - although my word may not mean as much as some professional reviewers out there with $500+ pairs of headphones, I find that these headphones have clarity far beyond anything I’ve tried and reproduce sound so accurately it’s somewhat spooky.

A lot of people will probably disagree with me, I am no expert in audio, after all this is my first planar headphone experience ever, so instead of focusing so much on their pure audio quality, I’ll talk about my specific experience with them.

Read Keybase’s blog post here.

If all you read is the intro text, take this quote:

A bought-out company can never be trusted more than the parent company.

And unfortunately, Keybase, a company which I originally held in extremely high regard, just got bought by one which I personally have strong negative prejudice about.

And thus marks the downfall of Keybase’s trust factor.

If this were the other way around: If Keybase acquired Zoom: I would be ecstatic, because I truly think Keybase has the ability to create a great end-to-end complete platform for all kinds of communication, but not quite the best possible platform, as you’ll see lower down in this post.

Though luckily, not all is completely lost:

In December of 2018 I finally received my UHK after months of waiting.

After using it daily since, I’m 100% convinced that the UHK is worth the asking price, probably more, and I’m happy that I got it at an early adopter discount.

Currently at $275 USD it’s definitely priced like the split ergonomic keyboard that it is, but what I think makes this one worth that is the open source, hackable nature of the keyboard.

Here’s my thoughts after using it as my daily driver for many months,

Just bought Silicon Zeroes (I know I’m late to the game, been too busy in Zachtronics land) and I’m met with this screen…

Here’s some background about my current project, feel free to skip straight to the tips section below.

As of recently I’ve been hired as an undergrad research assistant at UTK. I’m developing a reimplementation of PatchWorks by Austin Henley (who I’m working for).

The new project is now named CodeRibbon, since we’re essentially starting from a clean slate in terms of codebase, and we’re rethinking a few human interaction factors.

For the reimplementation we wanted something that can be used in the real world, since the plan is to make CodeRibbon open source and easy to install & use.

In the end we chose to make it an Atom plugin because of how easily and rapidly we can prototype and design a full IDE experience. It’s not called “the most hackable editor” for nothing.

So here are some useful tips I’ve learned while working on Atom plugins.