Skip to main content

No, Don't Move to Canada

The 2016 presidential election year is upon us Americans. As the parties narrow on a candidate, it feels as though the atmosphere manages to get even more polarized. Eventually we start hearing the stories from friends and family, to even celebrities, stating “If [candidate I hate] get’s elected, I’m moving to Canada!”. We then all laugh once candidate X is elected (especially if we were a fan) as said person(s) don’t move to Canada.

Even though we know most people are not literally serious when they state this, I feel it highlights a bigger issue that we don’t talk about enough. Simply put, we place way too much importance on who holds the U.S. Presidential office. When we say “I’m moving to Canada”, we’re essentially saying that the fight is over, there is no hope, even though we don’t actually pack up our bags and move. Which indirectly is stating, that there’s nothing we can do as an individual or community. That out of all the issues America faces, no non-profit, grassroots organization or group of concerned citizens can do anything to make things better. All the power and potential rests solely in the presidency. This is simply not true.

I won’t go into the plethora of examples of people who have made a difference in America without being president. Thus, while the POTUS position is certainly an important item to discuss and be concerned about, it is hardly the end-all-be-all of one’s existence as a U.S. citizen. Conversely, if your favorite candidate were to get elected, such a view of the presidency would allow one to feel “Great! My pick got in! They will fix everything and I can sit back and watch.”

Both conclusions are an actionless state. If we want to make a difference, helping efforts for positive change in the community will go much farther than any box we check on the ballot. So, this year, I encourage you to go out and find a group of people in your city who are working on something that speaks to you and join them, in addition to hitting the polls.

Comments

Popular posts from this blog

Quick Deepstream.io Setup Using JSPM

Cross post from my employer's development blog: http://rootinc.github.io/2016/02/12/deepstream-jspm/
Want to use JSPM rather than Bower for running the Deepstream.io example? Follow these steps. This is basically a duplicate of the [Getting Started tutorial][tutorial] on the [Deepstream.io website][website] but using a really simple JSPM setup. This is a very crude guide where I list everything I had to do to get things running.

Create an empty project folder npm install deepstream.io Copy server code verbatim from the Getting Started guide jspm install npm:deepstream.io-client-js Hit enter for all the prompts from JSPM

We’re going to modify the client side code a little bit. We have native support for ES6 compiling with JSPM/Babel so we can import the Deepstream client directly:

import deepstream from 'deepstream.io-client-js'; let ds = deepstream( 'localhost:6020' ).login();

let record = ds.record.getRecord( 'someUser' );

let input = document.querySelector( 'inp…

Atari E3 2004 PAL digital press kit

Making note of some old swag. The Atari E3 2004 PAL digital press kit. See video for details.






Accessing other HTTP servers on Cloud 9 IDE

If you're using Cloud 9 to do development, you'll quickly realize that only ports 8080 through 8082 are available to the outside world from your development box. This is generally not an issue as you can set your application to bind to the $PORT environment variable when in development mode. However, there are sometimes other servers that we want to make use of that host on different default ports.

I recently had to setup a Neo4j server which defaults the admin interface of port 7474. Unfortunately, I could not access the admin interface even through the IDE based web browser window. So, what to do? I could change the default server settings so that it runs on a different port. However, the app I'm working on with a team has 7474 hard-coded and I currently don't feel like writing a local only work-around.

After some searching, I ran across a neat Linux tool called socat. This allows us to easily forward one port to another. After a quick install via apt-get, I ran the …