Our changelog, announcements, dev posts, and anything else we think you'll find interesting.
When Liz Fong-Jones, Principal Developer Advocate at Honeycomb and experienced Site Reliability Engineer (SRE), joined us for Dev Tool Time on September 1, 2021, she shared how her setup and workflow bridge the current state of development and the future that’s already arriving.
You can watch the recording of this episode at the bottom of this blog post, but first let’s check out Liz’s main desk setup:
Liz’s setup stresses ergonomics, and includes two monitors and a mechnical keyboard. On her desk are two computers: an AMD64 box and an ARM64 box with a 16 cores at 2.2GHz, 32 GB ram.
Liz’s desk isn’t the only place she works, though. Despite an ergonomic setup, Liz’s chronic fatigue condition makes it difficult to work at the desk for long periods of time. As an advocate for disability visibility, Liz is open about working from bed as needed. To make this more effective, Liz works on a 2017 Google Pixelbook, which is lightweight enough to be balanced with a pinky finger. When she needs to, she can SSH in to her desktops to access further computing resources.
Her approach to making work possible in different setups carries over to many of the development tools she uses.
“I live and die by my terminal... I don’t use VS Code. I literally only use browser tabs and terminal.”
Liz aims to use tools that are accessible across devices with different levels of computer power, and regularly installed in most computing environments. For a text editor she uses GNU nano, which is installed everywhere, lightweight, and relatively easy to learn and use compared to other terminal editors like Vim and Emacs.
In her terminal, which runs Bash, she uses Powerline with the default config to manage complexity and add nice-to-have features, such as visiblity on current host and background jobs. Using this set of tools makes Liz’s setup easily accessible in new computing environments.
Liz’s dev workflow follows a structure that might be familiar for many devs. She uses Git for version control, works on a local copy of a repo in her editor (GNU nano), and pushes to a remote that’s hooked up with CircleCI to run a variety of actions. Differently from some devs, she doesn’t rely on her local editor to run formatting steps or lint code. Instead, CircleCI] takes care of these steps, along with deployment and other actions.
This automation goes hand in hand with Liz’s attention to observability, which emphasizes the capacity to introspect a system and understand its internal state. Automated builds and infrastructure configuration, using tools such as Chef and Terraform, increase the transparency of the systems with which Liz regularly works. As part of her work for Honeycomb, Liz uses Honeycomb, and shifting into its interface to understand workflows, processes, and debug errors or failures is a key part of her workflow.
“You heard it first at Dev Tool Time: 'The future is Linux on the desktop on top of ARM64.’”
One of Liz’s desktop machines has an ARM64 processor, and she notes that it runs on 25 watts, roughly a quarter of a comparable AMD64/Intel CPU. ARM64 processors are generally more energy efficient, very performant, and can be cheaper than alternatives. Honeycomb already runs part of its compute workflows on ARM64, despite the relative paucity of cloud providers. Liz’s own ARM64 desktop makes it easy to run native builds locally, while CircleCI’s support for ARM64 automates the process for other developers at Honeycomb.
The use of ARM64 is compelling, not just for the performance and cost. It’s also part of a future of computing that attends to the sustainability of our environment given the ever expanding role of computing in society. This concern for sustainability isn’t just business, but a commitment that shapes Liz’s own choices in hardware.
Watch the recording
Check out the recording of the episode below, and be sure to sign up for upcoming events!