My Computer Engineering Toolkit


This will be a bit of self promotion, but hopefully educational at the same time. Here’s a confession - I have many computers in my life 1. They have come and gone over the years, and all played a crucial role in my education and learning, leading me toward the engineer I am today.

I wanted to spend a post talking about the machines I currently use to do my thing.

For context, if you happen to go to my linkedin page, you’ll notice I’m an embedded software engineer by day. Basically, this just means my day job is the same as my robotics software-mentor job - just on bigger and yellower machines. My hobbies (robotics and otherwise) tend to flow straight from this occupation.

What I’ll talk through are what sorts of machines I use day to day to accomplish my personal and mentorship software development tasks. I hope that by getting some insight into how I’ve configured the tools around me, you may get some ideas of your own to form your own custom toolkit to support your hobbies!

Computer Hardware

The Main Show - the Desktop

My “daily driver” machine is my custom-built desktop. It was fairly up-to-date when I built it in 2013, but it has aged very well - it’s still more than fast enough to run any internet browsing, code editing and building, and occasional video games I throw at it.


Some basic specs:

  • Intel i5 3350P CPU - 3.10 GHz
  • 8GB RAM
  • 128 GB Main SSD, 1Tb expansion Drive
  • NVIDIA GeForce GTX 660
  • Windows 10 Professional
  • Samsung 4K 28-inch monitor
    • I’ve gone back and forth on this over the years. I really like all the screen real estate in one spot, and Windows 10 is great about managing it
  • RAT4 Mouse
    • Gotta get something that looks cool, and has programmable buttons. If you’ve never experienced a mouse with a dedicated “back” button, you haven’t lived!
  • Adesso Mechanical Keyboard
    • Mine is similar to this one, I don’t think they sell it anymore.
    • Mine has Cherry Blue switches - the really really clicky ones. Drives the wife mad. But I love the tactile feel.
      • Of course, it’s not for everyone. Try a bunch of different keyboards to see which one you like.
  • Mousepad is a chunk of fabric-covered neoprene that was surplus from the manufacture of Haken Continuum continuous keyboard. It’s a fun souvenir from one of my favorite college classes.


Again keep in mind - these specs are 6 years old at the time of writing. If I ever happen upon a spare couple hundred dollars, I this will probably be the first thing I upgrade. However, it’s still running so fast, it’s hard to bring myself to do so.

None of this is really top-of-the-line - it’s middle to cheap, but more than sufficient to support my personal coding and development projects.

The New Guy - the Laptop

For folks who do lots of FRC software mentoring, turns out the vast majority of my coding occurs on the road. For this reason, I recently splurged on getting a good machine that would take all the software-writing punishment I could throw at it. My choice? The Huawei MateBook X Pro.



That’s right - I got the Chinese hardware. But I have to say, it’s super awesome. Sleek and light, phenomenal battery life, a brilliant and giant display (my key criteria), and a pretty good keyboard and trackpad make for an excellent coding machine on the road.

The device sports a plethora of USB-C connectors. I usually carry dongle adapters to get me to VGA and HDMI, as well as extra USB and Ethernet ports (all very important for robot usage).

To address the elephant at the time of this post - Yes, Huawei devices are considered a security risk in the US. Most of the concern has been targeted at their servers and networking hardware, as it relates to the 5G expansion of wireless telecom carriers. Their consumer hardware is under target too. It was a risk I took when purchasing. I’m hoping the situation gets cleared up soon, but also keeping my finger on the pulse of the conversation, and actively monitoring network traffic. If something starts “phoning home”, I will probably re-evaluate what sort of network permissions this device will get.

No major changes to the OS or hardware since I’ve gotten it. I’ve got exactly what they say they sell on their website.

The Old Standby - the Server

At my home, I run one additional machine that acts as a server. I run a Dell PowerEdge R200 in my basement.

  • 2.33GHz Xenon CPU
  • 4GB RAM
  • 128 GB SSD

the server

It’s really not much - the thing is 10 years old. I got it for a steep discount on eBay - just had to provide my own hard drive.

I run ArchLinux, one of the most trimmed down operating systems with the Linux Kernel you can get. It’s a “no batteries included” approach to design - which means you get lots of configurability as a user. This server is the platform for a large number of continuous-running applications I keep at my house.

Network Storage

For saving files and doing server backup, I run a 2-TB Buffalo Network Attached Storage device, with two hot-swapable drives in a RAID configuration allowing for full redundancy. It’s primarily to supplement the other devices on the network - I’ll get into that later.

Other Home Networking Equipment

Along with the server, my small rack downstairs consists of two ethernet switches (one providing Power Over Ethernet, one not), an old Netgear combination Router & Wifi access point, and our modem. We’re lucky and have fiber internet service - I’m currently on a 300MBps plan that makes for a blazing fast experience.

When I moved into the house, one of my first projects was to install Cat6 ethernet wiring throughout the house. I added 7 new ports on two floors of the house, and ran all the wiring back down to the server & ethernet switches. This allows our media station (Roku & smart DVD Player) the desktop, and a few wired security cameras to connect to wired internet, even though they’re all in different rooms than the rest of the equipment. It also means the noisy server lives downstairs behind closed doors.

Network Equip

In a super simplified (to the point of inaccurate) diagram, here’s how it all is hooked together:

Home Network Diagram

Key Software

This hardware would be nothing without the software that sits on top of it to be useful. I’ll give a quick survey of the pieces of software that get used on a daily basis in my household.

On the Desktop & Laptop

I have a strong preference for free software because I like to spend my money on other things, like food. Sometimes you have to pay for good stuff. However, we are lucky that in today’s world, the majority of the tools needed for day-to-day software development can be acquired free of cost!

Development Environment

Visual Studio Code is my preferred code editor. The ability to support so many languages so flexibly, along with tons of built-in tools.

I’m also a huge fan of dark mode, and I really like the built-in color theme. Call me shallow, but if you have to stare at code all day long, might as well do it in a way that looks ascetically pleasing to you!


Git is a daily part of my development experience. Ever since I learned how to use it in college and on my first job, it’s become an indispensible tool for keeping track of how I change my software over time, organizing my development process, and creating backups of projects. Though I often manipulate my repos via the command line, I still really like having a nice visualization of my version tree. Git Extensions is my current choice for doing this, but there’s lots of great alternatives.


When connecting to the server, I generally use SSH to get access to a command line on the other machine. Putty is my tool of choice to get this done on Windows, though the one built into Git’s command prompt works just fine too.

Connecting between the Windows machines usually involves Window’s built-in Remote Desktop application.

For working with C code, I tend to prefer the msys/minGW to get the parts of the GNU/Linux environment on my Windows machines required to build and link C code to an executable. Cygwin is another super common option.

Python is my go-to language for most projects - it’s got easy & c-like syntax, cross-platform abilities, and batteries-included philosophy makes it a good choice for creating highly functional prototypes and super-flexible applications. For pure speed or robustness other options may be better, but Python is still my daily-driver for a language to implement my ideas in.

General Engineering Tools

Of recent, Discord has become the defacto tool for maintaining communication in our FRC team, amongst friends, and even family.

For CAD, I tend to like LibreCAD in the 2D drawings, and use Autodesk Inventor for 3D work. Both have many alternatives, these are simply the ones that I learned first, so I’m still the most efficient with them. I don’t have to do this super often, so I tend to stick with what I know, rather than invest in a new tool.

For electronics work, I have a few tools of choice. For doing research on the functionality of circuits and simulating their behavior, I use a program called LTspice. It’s a bit obtuse to get used to, I learned it in college. It helps when designing analog circuitry and validating functionality prior to building a real circuit.

When designing an actual circuit that I’ll build, I switch over to a different tool. KiCad has been my choice of recent, though Autodesk Eagle was my choice in college. Both give a vast library of components that you first assemble into a nice circuit schematic, then lay out physically on a printed circuit board (PCB). In addition to printing the schematic, you can export various files from the PCB design side that manufacturers can use to create a custom board for you. This will likely be the subject of a future blog post.


For documenting my work, I tend toward two tools.

For simple technical documentation, I really really like Markdown. That’s what this website is (mostly) written in! My liking is primarily because it’s super simple to write - basically just editing a text file. The rendering into nicely-formatted viewing is done by some other tool. To me, this is awesome because even if the visualization tool goes extinct, the base content is still super accessible and readable (unlike Microsoft Word or the like). Github and its clones support it natively, so .md files you produce display very nicely via their web interface (which is how most 3rd party folks will first see your projects). The feature set provided is, for me, “just-right” - simple formatting of code, images, headings, lists. All without the overhead of pure HTML/CSS/Javascript to accomplish the same thing. Of course, if doing a website from the ground up, you’ll want to be more familiar with those. However, for something like this blog, Markdown is an awesome choice for entering the information with enough complexity to fully describe your ideas, without unneeded overhead.

For more formal documentation (think, scientific papers or resumes), LaTeX is by far king, and I also love it. It produces beautifully formatted documents with top-of-the-line scientific equation editing. It also does great resumes - I recently moved mine over using the ModernCV templates! It’s a bit obtuse to learn at first, but the end results are well worth it!


Looks even better unredacted!

On the Server

The Gerth Household Server (affectionately nicknamed “Geezer” for its age) runs a number of applications which improve out lives on daily basis. I got into having a household server after my college laptop’s screen died, leaving it only useful by SSH or Remote Desktop access. I was bored one weekend, got Arch Linux up and running, and it kinda just snowballed from there. A few years back I finally decided running my laptop to death wasn’t a great idea, and swapped for the PowerEdge server hardware.

HomeAssistant is our home automation hub. It was one of the first things I attempted to get running on the server, and has been serving use well ever since! We’ve got a number of wifi-controlled light switches and outlets, smart speakers, some homebrew devices, and of course many networked devices. HomeAssistant has a ton of built-in functionality - you just have to configure it that “yes, these things are in my home” and it will automatically do some really slick integration, providing a super useful user interface for controlling the devices. Additionally, I can write automation scripts to allow the smart speakers to trigger action on light switches and whatnot. Highly recommended!

Home Assistant Sample

Github is my go-to service for hosting repos online, and making them publicly available. However, there are a handful of projects I really don’t want to make it outside my home network. Some of them concern the internal configuration of my network, others contain personal info (like my tax returns or resumes). To still be able to have totally-private, not-at-all-in-the-outside-world git projects backed up on a separate device from my PC or laptop, the server also runs an instance of Gitea, a simple Github-lookalike that I host myself. I’ll also back up critical projects (like this blog!) just in case Github disappears off the face of the earth - my data won’t disappear with it. Though I will have to find another host.

For home media, we use Plex to stream media files from our NAS to various viewing screens throughout the house. Both TV’s have some smarts built into them to where they can stream from the server.

Both Gitea and Plex are backed up against the Network Attached Storage device, which is nice, since the big files don’t take up space on the server’s internal hard drives.

For monitoring the server status, aside from just remoting in via SSH and running top, I recently installed NETDATA to provide a slick web-based view of how the server is running at the moment. It’s made basic checkups much quicker!

netdata sample

All of the applications are contained behind our router’s firewall - no one should be able to access them externally. While on the go, my wife and I use openVPN on our phones and laptops to connect back to the home network. The server runs the server-side implementation of openVPN.

The concept of this Virtual Private Network is simply putting your data in a “tunnel” - one end on the device your using, the other end inside our home network. This not only makes sure we have access to our home network applications, but also that we can protect our data from potentially untrusted wifi networks (Sorry random coffee shop XYZ, your baristas make great coffee, but probably don’t spend a ton of time analyzing the security of their local branch’s networking equipment). By encrypting our data with our own trusted devices and security keys, we can up our safety factor online quite a bit.

The server also happens to be hooked up to an amplifier that powers some weatherproof speakers we have outside. The server runs both a Pianobar instance controlled within HomeAssistant, as well as a Scream server. Using these, we can play and stream audio to our outdoor speakers from quite a few different devices.


Ok, this is enough of a technical flex for now. I’m not necessarily recommending that anyone use these tools, or endorsing them in any particular way, other than to say that they work well for my family’s current purposes. If you’re in need of similar solutions, try out the tools and let me know what you think! I’m by no means an expert in any of them, but would be happy to give more feedback if needed.

Happy coding!

  1. Though, not as many as my friend whose insurance company wanted to classify him as a small business due to his sheer quantity of high-powered hardware.