Orchestrate.io, Webstorm, Hacking Some Code and Project Pivots

In the previous blog entries “Orchestrate.io JavaScript Client Library” and “How to Build an NPM Package, Beginning the Symphonize Project” I kicked off a client library project. However, as things go in techlandia, they have changed. Just a few days after I created the project I learned of Steve Kaliski’s project he’d just rolled out on NPM. So he’d beaten me to the punch for a client library! I didn’t want to do a completely redundant project, so it was…

…Pivot Time!

So a quick pivot and I’ve decided to shift what would have been a client library called symphonize.js to a different project. Here’s the new plan. I’m doing the series, to be posted on the orchestrate.io blog with the first blog entry now live at, “Test Data Builder Symphonize.js with Chance.js“. The next entry will go live soon, diving more into the data structures and who, what, where, when and how to use them.

Using WebStorm for Orchestrate.js Hacking

This is a quick video I put together that outlines the steps to get Webstorm IDE setup to hack on the Orchestrate.js Code base that Steve has setup. I’ve assumed in the video that you’ve already downloaded node.js, Webstorm, and got the version of node.js setup in Webstorm already. The second assumption that I’ve made is that you’ve already downloaded the orchestrate.js code base somewhere and are opening it with Webstorm with the open directory option.

References:

5 thoughts on “Orchestrate.io, Webstorm, Hacking Some Code and Project Pivots

  1. Webstorm looks a very nice IDE. I spent last Friday at Microsoft open technologies garage setting up VS for node hacking. I hadn’t run my bootcamp for 2 years so my MBP had some surprises after Mavericks upgrade solved by installing IE11. Feels very cool we now have auto-completion and intellisense for nodejs. NJVS is alpha and the core VS team were on hand to answer questions. I asked about auto-adding test cases for node code, and gained positive feedback support is planned before release (writing tests doesn’t come natural to me). The prior evening at UW, GraphLab team introduced GraphLabNoteBook which runs on AWS. It might be interesting to injest huge data into orchestrate.io then groom with graphlab via node for recommendations in the data. I’m unsure about how this might work because of bringing code to the data (rather than data to the code). https://msopentech.com/nodehackathon2013/

    • One of my next big steps is to load a decent chunk of data into orchestrate.io and see how & what I can get out of it. Get some solid queries running, graph it, etc. It’s gonna be a lot of fun to dig through the results. I’ll have the blog entries up for that posted over at the http://blog.orchestrate.io. :)

  2. History of Symphonize.js – JavaScript Client Pivot to Data Generation Library | Composite Code

  3. History of Symphonize.js – JavaScript Client Pivot to Data Generation Library – Composite Code

  4. History of Symphonize.js – JavaScript Client Pivot to Data Generation Library : CloudAve

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s