Skip to main content

New Years Resolution - Reduction

I've decided that the word that will describe 2012 is reduction. In that spirit I have noticed that I have a number of articles in my instapaper queue that need to be read. Once they are read I will do my level best to reduce the number of articles that I actually collect. So if I'm scanning my news feed the criteria for a read later is going to be more strict. But let's review the stories so far.

  • reducing code nesting: We've been talking about this since CS101.

  • SQL to MongoDB mapping: I really like mongo but the argument for SQL is too strong. There is no need for an end user mapper... just implement SQL.

  • programming competitions: really?

  • Assembly Language Hello World: It's not much bigger than a DOS assembler version of the same. It's not the assembler that I grew up on.

  • DropBox Automator: only if you do not care who reads everything in your account.

  • scripting the un-internet: history repeats itself is not the same as a loop.

  • Digital Wallets: They've been talking about digital wallets for years. No one is interested.

  • Interarchy: interesting and possibly helpful. Needs better docs because there are side effects to every action. Would be nice if you were in the app store.

  • Trying to mount a file system: So may bad choices to select from. Since this is sensitive data how many to rey and trust.

  • Django Reusable Apps: It's just a general outline from 50K feet. Would be nice if there was some sample code or at least a sample project template. (see python's moder template)

  • Avoid Apress: I don't think I care enough to read this article. Not sure I know why I saved it in the first place.

  • "good enough": It's a maturity thing. At some point some of the details no longer matter. For this reason ideas like PEP-8 and Agile no longer matter.  GTD is more important.

  • Rob Pike: I like GOLANG but this guy seems to be off the reservation.

  • Lua 5.2: This would be better of the BDFL-Lua were more open. They only release about every 18 months and it's just not that interesting other than it's small footprint.

  • Show and Tell MongoDB: How many times is the same talk going to be linked to?

  • Burn DVDs on OSX Lion: There are a number of articles and most try to solve the problem. The real issue is that Apple does not include iDVD with new machines. Therefore iLife is not really installed with a new machine.

  • Mongo's write lock: First Python's GIL and now this.

  • direvn: Interesting but a bad/incomplete description. Integration with rvm and virtualenv should be addressed better.

  • different by design: Maybe, but it's not enough to be different... you need to be good too.

  • Credit Reports: credit reports and social security numbers need better consumer protection; whatever that needs to be.

  • Don't hire remote programmers: I need to read this one for company research.

  • Hire more remote programmers: I need to read this one too.

  • Renegade: I don't think we agree on the role of a CTO.

  • MySQL to Solr: I'm not going to read this article because I think Solr is not a DB but a search tool like Lucene.

  • For-if anti-patterns: This does not help anything. Check your O() at the door.

  • ...

(I have about 10 more... I only allocated 30 minutes for this post... so in the interest of reduction; this is it.)
I thought I was done... this one caught my eye and the rest have been deleted before I waste another momennt

  • Pay your programmers $200/hr: I'll be reading and rereading this one. I'm not sure that I warrant 200/hr but then I'm certain that the electronic traders do not. Not that they are smarter or willing to take risks but that they make mistakes too and the results are much like football games of old without a replay system that can keep up and rules that allow for correction on a grand scale. Even in football; once the next play has been started and the clock ticking there is no looking back.

And two keepers that I have not read yet but are worth a last minute reprieve. The future of retail, and recruiting for a startup.

Happy New Year! Welcome to 2012!


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: (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 answer all of the questio…

Prometheus vs Bosun

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


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…