There you have it. All the parts that I’ll be assembling for the Bottlehead S.E.X. version 2.1. The parts in the image include the impedance switch and the C4S components. To the far left, there is a bag I didn’t bother unraveling because it is mainly little screws and bolts that felt easy to lose.

Build Order

I will do incremental builds. This way I can test the quality of a build on it’s own before adding additional components. This is a good practice I follow in daily software development and has proved helpful in debugging. The order will be as follows:

1. S.E.X. kit.
2. Impedance switch installation.
3. C4S Upgrade.

After almost a month of waiting, my Bottlehead S.E.X. has finally arrived. This will be my first of many electronic DIY projects. I will detail the journey from start to finish. Including details like what tools I used, any problems I encountered, and any suggestions I come up with on the way. This blog series is sort of like an enhancement to the original guide provided with your Bottlehead S.E.X. purchase.

Rebuilt from the ground up, the new site is refined from the presentation to the source. The theme has been modernized to load faster and I created more ways to navigate the site so more data is easily accessible while keeping the idea of simplicity in mind.

There’s a popular text message going around today that restarts a recipients iPhone (if notifications is turned on) when they receive the following text:

effective. 
Power
لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ
冗

I started using ECMAScript 6 in a project which required supporting the dependencies I was upgrading from. I used Babel JS to transpile my ES6 code with browserify and everything was working fine until I got to jQuery-mobile.

A style guide should be chosen when working on a solo project or with a team. This keeps the code manageable when you or your peers come back to work on it in the future. It doesn’t matter which style guideline you choose as long as you stick with it. In a sense, writing clean code will also help reduce technical debt. Below is a collection of style guides that I collected over time. Some important rules are repeated in other styles. It’s nice to keep consistency (to a degree) if you are writing in multiple programming languages but ultimately it’s best to do what’s best for each language.

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”

Martin Fowler, Refactoring: Improving the Design of Existing Code

tl;dr: Use this post-commit hook.

A great source for all sorts of packages such as Node.js, Zshell, BitTorrent Sync, Redis, and Firefox Sync Server just to name a few. Check out the full list of packages or just add the source to your package manager :)

My home network is wired through a Dell gigabit switch which is connected to my AirPort extreme. Needless to say, this has worked well for me as the only wireless devices connected are mobile devices. I decided to set up another room in the house but I didn’t want to go through the hassle of running wires through the walls again. It’s undoubtably the best thing to do but this isn’t meant to be permanent. I figured the next best thing to do is extend the network by purchasing another AirPort Extreme. The hardware in it is better than an AirPort Express plus I get a few ports to hardwire a few devices. My rule of thumb is the less WiFi, the better.

Assuming you have aliases setup in Gmail, it’s fairly easy to configure the Mail application on iOS to respond to the emails using the correct alias.