This is the second post in my series of getting started with Node.js.
In my last post, I installed Node.js on both my Windows 7 machine and my Macbook Pro. My next step was to get started building a static website for one of my domains. Mark Drew suggested getting started with using the MEAN stack - Mongo DB, Express, Angular and Node. I had looked at MEAN before really getting started, and I agree that it's probably the best stack for me, so I went to http://mean.io and followed the install instructions right there on the home page. That's where I ran into my first issue.
On many occasions I've decided to get acquainted with a new technology (language, framework, etc.) - SOLR, FW/1, Jenkins, Semantic UI, and a long list of others. The amount of time I've spent dedicating myself to getting proficient at each of these has varied, and based on the number of years I've spent writing code, I can say that the term "proficient" is pretty subjective. I've been mostly happy with ColdFusion over the years, but it is apparent to me that cfml is a little like a salmon swimming upstream, and there's a need to expand my horizons in order to remain relevant as a developer (not that I'll be ditching CF or Railo anytime soon). So I decided to give Node.js a shot.
Posted by Kris Korsmo in Aviation on March 17, 2014
So it's been more than a week since Malaysia Airlines flight 370 went missing. The entire world is speculating on what happened to the airplane, so I'll go ahead and add my scenario. It's not as exotic as the current hijacking scenarios, but I think it's a lot more realistic.
I've been trying out Semantic-UI recently and it really appeals to me on a lot of levels. I thought I'd show a quick example of how to bind one dropdown (Semantic's version of a select form field) to another. This comes in handy if you're trying to filter the options of one based on the other.
A while back - too long ago - I started a series of blog posts about getting up and running with Jenkins for continuous integration. I left off with talking about Apache ANT (which stands for Another Neat Tool). ANT is basically XML which allows you to tell Jenkins the steps you'd like to take to "build" your site continuously. Installing ANT was not as straightforward as I thought, so I'd like to share a bit of my experience so that hopefully it will be smooth sailing for you.