Some more published posts, mostly junk though

_posts/2012-05-22-lookout-hackers.markdown

@@ -0,0 +1,38 @@
+---
+layout: post
+title: About the Lookout Hackers Blog
+tags:
+- lookout
+- ruby
+- devops
+---
+
+I've neglected cross-posting some of the articles I've written over the past
+month or so for the newly inaugurated [Lookout Hackers
+blog](http://hackers.mylookout.com/). The generally idea of the Hackers blog is
+to give Lookout Engineering a bit clearer of a voice and an avenue to publish
+blog posts on things that are nitty-gritty and technical.
+
+A couple of the posts I've written which may interest you are:
+
+
+* [Integration Testing with Foreman](http://hackers.mylookout.com/2012/04/integration-testing-with-foreman)
+
+    *At Lookout we find ourselves building more and more APIs and backend
+    services these days. Naturally we would like to be certain that everything will
+    work fine and dandy once it has been deployed. The reality of building out a
+    service-oriented architecture is that you not only have to expect failure to
+    happen, you have to plan and test for it.*
+
+* [Continuous Deployment for Ruby Gems](http://hackers.mylookout.com/2012/05/continuous-deployment-for-gems)
+
+    *With the above workflow and these conventions in place, we’ve reaped a
+    couple of benefits, the most obvious one has been the severely reduced time it
+    takes for new gems to be created and incorporated into production systems.
+    At a higher level, we’ve gained more confidence in our gems with this emphasis
+    on testing, traceability and code review baked into the process from the start.*
+
+The blog is still fairly young, and we're getting more developers used to
+writing blog posts for it. You can subscribe to the [atom feed
+here](http://feeds.feedburner.com/LookoutHackersBlog) or just follow
+[@LookoutEng](https://twitter.com/lookouteng) on Twitter.

_posts/2012-05-27-hubboard-call-for-testers.md

@@ -0,0 +1,38 @@
+---
+layout: post
+title: "Hub board: Call for testers"
+tags:
+- resin
+- amber
+- github
+- hubboard
+---
+
+I've been working on [Hub board](https://hubboard.herokuapp.com) off and on for
+the past couple months, and I finally think it's ready for some more broad beta
+testing.
+
+
+Hub board itself is meant to be a more visual Kan-ban style board built on top
+of GitHub Issues. There are three states for issues "Open / Assigned", "In
+Progress" and "Closed." By default Hub board will not show you any issues that
+are not assigned to you; unfortunately there is not a means to assign existing
+issues to yourself through Hub board [issue #52](https://github.com/rtyler/Hubboard/issues/52)).
+
+
+<center><a href="https://hubboard.herokuapp.com/intro" target="_blank"><img src="http://strongspace.com/rtyler/public/hubboard-2012-05-27.png" alt="Hub board yay"/></a></center>
+
+Please visit the [intro page](https://hubboard.herokuapp.com/intro) to learn
+more, and file [issues on GitHub](https://github.com/rtyler/Hubboard/issues).
+
+
+---
+
+For the curious, Hub board is built with [Amber
+Smalltalk](http://amber-lang.net/) a JavaScript implementation of the Smalltalk
+language and runtime. It is also built and deployed with the
+[Resin](https://github.com/rtyler/resin) which embeds Amber and couples it with
+a simple Sinatra web server to make developing Amber applications exceptionally
+easy.
+
+