I’ve spent the past two decades in tech, mostly as a developer or system administrator. In that time, I’ve worked in a variety of different markets, in six different cities, across three different countries. There are, of course, a number of similarities between companies, no matter where you go. But I also found a lot of oddities that were specific to certain regions and markets. People who only work in one market could get used to an IT mono-culture, and may not realize how things operate differently for their counterparts on the other side of the country, or the planet. In this post I will start with my experiences in Chattanooga, Tennessee and Cincinnati, Ohio. I’ll also talk about international markets and tech scenes from my experience in Melbourne, Australia and Wellington, New Zealand. Finally I’ll cover my return to the West Coast working in Seattle, Washington, and my current scene in Chicago, Illinois.
My first job out of University was in the IT department of a payment processing and debt collection company. My desk was juxtapose to a call center where, all day, I listened to people on welfare collect bad checks and credit card debt from other people on welfare. When several of our sales people left to start their own business, taking many of the company’s customers with them, the company began to have everyone in the office, from those in data entry to customer service, sign a non-compete agreement. It was the first non-compete agreement I refused to sign. Over the course of the next fifteen years, I would be asked to sign non-competes several more times, always prior to employment. I’ve always refused, and until recently, I’ve never been denied a position because of that refusal.
Since 2012, at the last three jobs I’ve held as a software engineer, I’ve always used Linux natively on my work desktop or laptop. At some companies this was a choice, and at one it was mandatory. Most development shops give engineers the option of either a Windows PC or a Mac upon hiring them. However, my most recent shop did not. I considered simply running Linux in a virtual machine, however VirtualBox proved to be so slow that it was unusable, and I had some EFI booting issues with a demo of VMWare Fusion.
I probably could have worked through those issues, but instead I decided to take the leap and attempt to dual boot into Linux natively. A considerably amount of work has been done in the open source community to get modern Apple hardware working under Linux, much of it documented under the mbp-2016-linux project on GitHub. I was able to leverage quite a bit of that work to get a mostly working development environment. Although some things are still broken, I’m confident I can work through those issues, and hope this post can help other engineers who want to use modern MacBook Pros as powerful Linux development machines.
In a previous post, I introduced Bee2, a Ruby application designed to provision servers and setup DNS records. Later I expanded it using Ansible roles to setup OpenVPN, Docker and firewalls. In the latest iteration, I’ve added a rich Docker library designed to provision applications, run jobs and backup/restore data volumes. I’ve also included some basic Dockerfiles for setting up HAProxy with LetsEncrypt and Nginx for static content. Building this system has given me a lot more flexibility than what I would have had with something like Docker Compose. It’s not anywhere near as scalable as something like Kubernetes or DC/OS with Marathon, but it works well for my personal setup with just my static websites and personal projects.
I went to University in a small town whose population reduced by a third when school was out of session. Past the edge of town was a state park filled with amazing waterfalls, but if you turned off a few roads early, you’d come to a dead end. Beside the road was a trail that led back between houses and down to a secluded creek, a series of cliffs and a maze of paths used by dirt bikes and all-terrain vehicles. We spent weekends exploring this crazy area which so few people knew about.
Today it’s now officially part of the larger state park network. The old entrance has been closed off and an official parking lot has been built three kilometers away. Many of the most amazing trails have been closed off to the world, either sighting safety concerns or with no trespassing signs indicating the borders of private property. What was once a place of imagination and exploration became tamed. Other hikers I met from that era are glad the area is preserved, but I could hear the sense of loss and nostalgia in their voices; that feeling of saudade from that time when we felt like we were on the frontier, trekking through an undiscovered country in our own backyards. On those weekends, between the deadlines of projects, assignments, fraternity parties and final exams, we spent time exploring, both our world and ourselves.
Sometime in 2008, MySpace had a data breach of nearly 260 million accounts. It exposed passwords that were weakly hashed and forced lowercase, making them relatively easy to crack. In 2012, Yahoo Voice had a data breach of nearly half a million usernames and unencrypted passwords. Now you may think to yourself, “I don’t care. I never use my old MySpace or Yahoo account,” but in the case of the Yahoo data breach, 59% of users also had an account compromised in the Sony breach of 2011, and were using the exact same password for both services!
Using leaked usernames and passwords from one service to attempt to gain entry to other services is known as credential stuffing. People should use a different password for every website or service. Password reuse is one of the major ways online accounts become compromised. For the average person, using a password manager to generate unique passwords for every website and app may seem a bit cumbersome or complicated. But there is another way to have unique passwords for every website; passwords that can easily be remembered, yet are difficult to guess. The solution, often discouraged by security experts, is creating a password algorithm.
In a previous post, I showed how I wrote a provisioning system for servers on Vultr. In this post, I’m going to expand upon that framework, adding support for Firewalls, Docker, a VPN system and everything needed to create a small and secure infrastructure for personal projects. Two servers will be provisioned, one as a web server running a docker daemon with only ports 80 and 443 exposed, and a second that establishes a VPN to connect securely to the docker daemon on the web server.
In 2015, due to a series of events, I began a journey across the globe where I lived out of two bags for eleven months. In May of 2017, I left my full time job and started another journey, this time driving across the US. It’s been several months since I started this new minimalist adventure, and it’s not been entirely what I expected. I’ve seen a lot of amazing friends and family. I’ve had a couple of setbacks. I’ve struggled with people, relationships and burnout. My journey is not quite over, but I’ve already learned a considerable amount about myself, people and America.
The Daily Stormer, a website with highly controversial hate speech, was recently scrubbed from the Internet. This wasn’t due to government censorship or illegal content, but due to the fact that no private hosting provider would allow their content. DigitalOcean and DreamHost refused to host their content in 2014. In August of 2017, CloudFlare terminated their CDN services for the website. GoDaddy terminated their domain registration with a 24 hour warning. The site owners migrated to Google Domains, which also refused to allow the domain transfer. NameCheap refused to allow them to register a domain as well.
What is interesting about this situation is the Daily Stomer carried only content. Although legally protected as free speech, at least in the US, hosting and infrastructure providers are free to refuse service to any company. Many of the companies mentioned above quoted specific clauses in their terms of service about hate speech or inciting violence. On its surface, it seems like these tech companies are helping to make it difficult to host hateful content on the Internet. However, with such a limited set of providers and domain registration services on the Internet, does the dominance of such few companies in the hosting space allow the means for industry to decide what content is allowable? Are Google, GoDaddy and others effectively censoring opinions they find disagreeable?
Newer