Leanpub: Isn’t ePublishing too new to be disrupted?

One of the more popular ruby bloggers (and I apologize for forgetting who) was recently raving about LeanPub, an online platform for creating eBooks in an agile fashion. I finally got around to digging more deeply and their platform is insanely cool. If you’re planning on publishing a book any time in the foreseeable future, you owe it to yourself to check them out. In addition to creating a platform for seeking constant feedback to your work in progress, most of the price of the book (over 90% usually) is paid directly to the author.

This is my somewhat-less-than-subtle way of mentioning that I’m working on a book. As part of my recent search for new work, I started putting together a curriculum for teaching Javascript development either as a WDI or an 8×6 class (8 weeks, 6 hours a week.) While I settle into the new company, I’m also drawing together those notes to turn that curriculum into a book called Full-Stack Javascript.

Posted in JavaScript, Leanpub | Leave a comment

Today’s Azure hiccup

I went a little nuts yesterday trying to find the URL for a freshly-deployed Azure service and couldn’t find it anywhere on the dashboard. Today, I went to delete the service and the warning message included the line, “Domain yourprojectname.cloudapp.net will be lost.”


Posted in Azure, Uncategorized | Leave a comment

Cutting myself on the bleeding edge of Azure

After a little more than a year building Rails applications and living almost entirely in FOSS-world, my current project is once more squarely in the .net universe – a SaaS solution for distributed medical imaging on the cloud. In this case, “the cloud” is Windows Azure. Three years using Amazon Web Services have given me a good grounding in cloud development and deployment, but it’s easy to make mistakes by assuming that Azure and AWS are the same kind of thing. Continue reading

Posted in .net, Amazon Web Services, Azure, Cloud, Rails, startups | Leave a comment

Plumbing the depths of shallow apps with Firebase

Being between positions has given me an opportunity to look around at the current tech landscape and decide how much (if any) retooling I want to do.

I’ve worked in .net for 10+ years, but most recently worked in Ruby on Rails. But the truth is that I’m not married to either technology (or, if I am, I’m the worst husband ever.) With a resume like mine, I’ve had the opportunity to interview with shops using a huge array of languages, frameworks, applications, and stacks. In just the last couple of weeks, I’ve discussed the possibility of working in not just those two, but also Python, Java, Haskell, Clojure, and good old, back-to-basics C. But what’s really caught my interest are the pure JavaScript shops. Continue reading

Posted in Angular, Firebase, JavaScript, node | Tagged | Leave a comment