Skip to main content

mobile first

I'm writing this post in advance of my 10 day vacation but it seems appropriate nonetheless and by the time it posts I should have already returned.

My employers, customers and family members have always had different ideas on how I should behave on my vacations. From totally connected to totally disconnected and all points in between. For me I like to be somewhere in between. For me it's not about being "Wally Pipp" but about being responsible and taking pride and ownership.

With that in mind I'm looking at my briefcase and wondering how I'm going to carry everything.
  • ipad mini
  • iphone
  • 11" macbook air
  • 15" macbook pro
  • 2x iPad 2's with iGuy cases (say bulky)
and then plenty of accessories and power adapters. And carryon for my, my wife, 2 kids and the huge double stroller. And let's not forget winter coats and whatever the rest of the family is going to stuff into the stroller. Some of these are easy to carry and some are difficult. The iPads are trivial and the TSA does not require that they be taken out of your suitcases.

Looking back this year I had promised myself that I was going to stuff everything in the cloud. And I seem to have forgotten this promise. My local storage is simply running out and I have to carry these two laptops with me. It's exhausting.

As I'm getting ready to head out the door I think the idea of mobile first for everything is the best plan. There are tools like prompt and diet coda that make things easier but they are incomplete without an end to end strategy. Even chromebooks are a good idea but they are just as bulky as any laptop but at least they make work time easier.

So as I start on a complete mobile first strategy here are the first steps....

Ditch the laptops. Install the necessary VPNs, add a bluetooth keyboard, install prompt and diet coda, pre download my code to the cloud servers and get ready for the fun.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…