Seattle Nerd Lunch Friday

FINAL:  Nerd Lunch, Chipotle in downtown Seattle, we’ll meet at 11:30 and eat in the food court. Hope to see lots of people there!

On Friday of this week how about a Nerd Lunch in Seattle? The questions are what time and where should we go? What’s the thoughts, leave comment or three and we’ll all get something ironed out.

UPDATED: It’s starting to look like it’ll be Chipotle at 11:30 on Friday. If you don’t want to meet for nerd lunch then, get some votes in ASAP!

ALSO: Signed up for some ATDD Workshop fun this Thursday in Bellevue at 6pm. Anyone interested should sign up!

Where Am I?

That title sounds like a Dream Theater song or something. But alas, I’m going to try and answer the question for the next few weeks per my calendar of logistics.

  • September 10th (Monday) – September 14th (Friday) I’ll be in Seattle for networking, work and a few rounds. Maybe a geek lunch or two too, who’s up for it?
  • September 20th (Thursday) I’ll be in Seattle for the Software Craftsman’s Meetup at Getty Images.
  • September 22nd (Saturday) I’ll be at the Portland Streetcar eastside Loop Party. Yeah yeah, it doesn’t really have anything to do with tech, but I’m a transit nerd, so gotta go see the new streetcar line.
  • October 8th (Monday) – October 17th (Wednesday) I’ll be in San Francisco for the RICON (A Distributed System Conference for Developers) and the HTML 5 Dev Conf (js, html5 and all that developer conference).

Thor & Cloud Foundry Hackathon & Installfest

Curious if anyone is up for meeting and doing an installfest or hacking on Cloud Foundry, Iron Foundry or checking out Thor this coming week in Seattle? Any takers? Leave a comment and I’ll also ping the people of the Twitterverse and App.net. I’m up for meeting at a coffee shop or other space and would be happy to come to an office or other environment if anyone is interested.

PDX & SEA Code Camp, OS Bridge, OSCON, Iron Foundry, Robotech and Action!

May has been insane. I’ve spent a total of about 3 days of the entire month where I live in Portland, OR. It’s kind of an odd feeling to try not to travel since I love it so much. But I’m going to try and take it easy  this month and next. Especially since some kick ass conferences and code camps are happening right here in Portland (and Seattle) which helps me spend some quality time right here with Stumptown (that’s a nick name for Portland btw). So here’s a run down of the crazy action happening in June and July. There are lots of events and I’ve got lots of things coming your way!

PDX & SEA Code Camps

I just wrapped up speaking at Portland Code Camp. Again, thanks for coming out and hearing about PaaS Technologies, Cloud Foundry, Tier 3, AppFog, AppHarbor, Continuous Deployment, Integration, and all the things that have been pushed forward with Platform as a Service!

At the upcoming Seattle Code Camp on June 16th I’ll be providing 3 presentation, or workshops, or sessions, or whatever you may want to call them.  Here’s a quick blurb about these, if interested, head down and I’ll make sure you get into the presentation workshop sessions. Also note the schedule, which no, I did not make the schedule so I apologize ahead of time that I will be talking about Node.js at the mind numbing early hour of 8 am.

  • Node.js Rulz! JavaScript takes over the full stack! => From the client side with some jQuery action to the back end with Node.js, with a touch of JavaScript Object Notation . JavaScript is everywhere these days and simplifying our lives. In this session I’ll run the full stack, with a live example, deployed to a live environment to show how JavaScript is freeing us from the constraints of the traditional development environment.
  • Removing the Operating System Barrier with Platform as a Service=> This session will cover the major advances of platform as a service technology, what’s available in the OSS space to enable faster, easier, higher quality software development cycles in the cloud. The session will complete with a demo of PAAS technology in use, deploying a highly scalable, distributed & dispersed web application.
  • Putting it All Together, Letting Apps Lead the Cycle, TDD In The Cloud =>  I’ll be taking a deep dive into cloud architectures and how to build applications, generally at the PaaS level mixed with a little IaaS, to get people rolling with high velocity, high quality, and without the need to worry about the little things.  Want to learn about why PaaS and cloud computing is altering the very fabric of the development cycle? Want to know how to dive in with some abstractions and behavioral practices on the cloud, using PaaS, to bring apps, prototypes, and UX to market faster than anyone else? I’ll be touching on all of these things during this long form session. The sessions will step through these core concepts and ideas.

OS Bridge

Ouch, they didn’t pick any of my sessions.  :'(  Well, even though I wasn’t selected to present I will absolutely be at OS Bridge and you should be too! So if you can get into Portland between the 26th and 29th of June make the endeavor! There will be great networking, sessions and you get an excuse to hit up Portland’s awesome Cart Selection of exquisite food (if you haven’t been here, I’m NOT kidding, it is indeed epic!). Be sure to say hello or let’s pair up on some code or hack some PaaS apps.

OSCON

I’ll be attending OSCON, probably coding all the while. I’ll be reporting on a number of things, specifically the Cloud Track:

Rid the MAX to OSCON, from downtown, or the airport, or...
Rid the MAX to OSCON, from downtown, or the airport, or…

http://www.oscon.com/oscon2012/public/schedule/topic/805. If you’re going to be attending, again, ping me and we’ll meet and maybe build something, maybe start a twitter flame war and correct everything on the web, or something of that sort. Worse case scenario we’ll grab a beer and have some rocking conversations about OSS, Cloud Tech, and more.

Part II of this blog entry is coming a little later today…  so stay tuned for Robotech, Iron Foundry and all types of code action.

Coder Society Seattle, Inaugural Report!

Coder Society Seattle got off to a start this weekend on this beautiful sunny Saturday! We all mozied into the Blue Box offices in downtown Seattle a mere block away from Pike Place Market.
After a relaxed gathering we circled up to break out the kanban with the story ideas around our problem domain. We knocked this out in short order, all ready to dive into groups, frameworks, and determine what we’d learn for the day.

Clive, our picture taker, arriving at Blue Box
Clive, our picture taker, arriving at Blue Box (Click through on the image, you’ll need a Google+ Account)

We all then took a democratic vote on which tech stacks we’d all work with for the day. We came concluded the vote with Sinatra and Node.js as our primary two framework stacks.

During this voting however we broached the topic of doing Backbone.js and Knockout.js. So we decided that, instead of two, we would break into three groups. This created two server side web services teams and a more pure client side team. Each team would act as if they were an independent startup, working specifically to provide a web data service API or respectively a UI that offered a mash up of this data.

Kicking off the day...
Kicking off the day…

Using Sinatra for the Barista Business Data Domain

@ang3lfir3
@trevorbramble
@strabd
@ang3lsdream
@adron
@monkeynumberone

Backbone.js & Knockout.js for the Bash Up of Barista + Coffee Drinker Business Domain

@sechrest
@volturiussystem
@iamjoncortez
@ph477y

Using Node.js for the Coffee Drinkers Business Domain

@scottkfraley
@jayzeng
@anupamonu
@iC
@pOch1

(NOTE: Some members didn’t have twitters yet, I’ll add em’ when they send em’.)

I Can Write on Post Its!
I Can Write on Post Its!

After the breakout we all dove into getting our various domains done. Many of us were not versed well with our respective technology stack we chose. Some time was consumed digging into that. After a few hours everyone had gotten a few solid key features done. In addition we’d all broken out our direct business objects into a set of models, interfaces, etc.

Mid-day we used the “Put your order on a post it note” ordering system and I (@adron) headed off to retrieve a true Chipotle Lunch. While there I experienced the odd queueing mismanagement that can happen since I had multiple orders and an unclear way to provide the messaging needed to get those orders into the “queue”. However, I succeeded finally and we all enjoyed lunch, courtesy of Tier 3! Thanks Tier 3!

Coder Society Coders Coding Node.js (and Sinatra in the other room... etc)
Coder Society Coders Coding Node.js (and Sinatra in the other room… etc)

We came toward the end of the day having learned a lot, built various aspects of what we had intended and all joined back up in the common space for a review of the day. There were a number of lessons learned that’ll will be integrated into the Coder Society flow. It was unanimously voted to be a successful day by the group. We did a short review of things to do slightly different and came up with these conclusions:

  • Send links to git and github tutorials for those that aren’t familiar with this source control technology.
  • Determine frameworks and specifics to configuring machines ahead of time.
  • For web application development, PaaS by far saves hours of configuration and setup. Keep doing this in the future. However for certain “topics” we broach we’ll still use IaaS or other systems as needed.
  • Minimize user stories to 3-4 specific stories per team. Have more flexible kanban boards that can be moved around or taken (re: like a poster board) to the area teams break out to.

With that, the inaugural meetups in Seattle and Portland are complete. I’m aiming for one more in San Francisco and then working to organize regular monthly meetings for the Coder Society. I hope you’ll join us in the future. If you’re interested in kicking off a Coder Society user group in your city feel free to ping me @adron on Twitter and we’ll coordinate.  Cheers!

Coder Society Seattle, Meeting this Saturday

Here it comes. Coder Society Seattle, Inaugural Kick Off!

I hope you can make it. Here’s the plan so far. We’re all meeting at Blue Box in beautiful downtown Seattle at 10am. We’ll setup a board (ala kanban style) and immediately jump into breaking our domain out (re: See the Coder Society Google Group for conversation around this, or check out below). I’ll have the post its, you bring the desire to learn new frameworks and build a cool something another!

One thing learned while getting things done and learning at the first Coder Society Portland meeting was that building infrastructure elements really held us back. So for this meet up we’ll dive straight into a PaaS option with Iron Foundry’s Cloud Foundry Environment. This will allow us to use almost any environment application option we want and couple it to whatever database.

Some of the things you’ll need for the meet up:

  1. Desire to learn.
  2. Intent to code, code, and deploy.
  3. You will need a laptop. So buy one, steal it, borrow it, or whatever you gotta do.
The meeting will be held at Blue Box at 119 Pine Street, Suite 200, Seattle, WA 98101    
Updates will also be provided via the Twitter Account: https://twitter.com/#!/codersociety and the site http://codersociety.org

Here’s a run down of our initial kick off goals. Polyglot applications for the win!

Here’s a review of our goals for the meeting:

Primary Goal: PolyGlot Systems
For this we will do a simple project where we pick technologies using at least two different programming languages and have them perform different roles in an application and share information across something neutral like Mongo or Redis. The prime choices, and we can add others, will be to use Node.js/Express.js + Ruby & Sinatra, and possibly C#/.NET MVC. This all depends on the desire of the meeting audience.

Stories: We’re kicking off the meeting goal with a theme many software developers will be super familiar with. Coffee!

  • A coffee drinker wants to add a rating for the coffee beverage.
  • A coffee drinker wants to list the price of the coffee beverage.
  • A coffee drinker wants to review the Barista.
  • A coffee drinker wants to rate the Barista.
  • A coffee drinker wants to know where the beverage.
  • A coffee drinker wants to know where the Barista was working.
  • A coffee drinker doesn’t want to read huge reviews.
  • A Barista wants to be able to list their coffees they use.
  • A Barista wants to be able to comment on reviews.
  • A Barista wants to be able to list their prices for coffee.
  • A Barista wants to be able to select their specialty.
  • A Barista or coffee drinker wants to be able to add or view outlets, wifi, or other information about the coffee shop.
  • A coffee drinker wants to be able to “follow” their favorite Barista.
  • A Barista wants to be able to send an alert to all of their coffee drinkers.

Arbitrary Limits:

  • Coffee Drinks are limited to: Cappuccinos, Lattes, Mochas, Macchiatos, Espresso.
  • We’ll be deploying to the Iron Foundry (Cloud Foundry core) PaaS, which really doesn’t put any particular limitations on us.  😉

Frameworks: After splitting into teams, we’ll iron out which frameworks we want to use and implement using the choice frameworks.

  • Node.js + Express.js / Bricks.js
  • Ruby on Rails
  • Ruby + Sinatra
  • ASP.NET MVC
  • Assembly. Ya know, for the insanely hard core. 🙂

Database:

  • Mongo DB, maybe Redis, Postgresl, or Neo4j if needs arise.

Prerequisites:

  • Bring a Laptop (or computing device you can do development on).
  • Bring some familiarity for setting up and using your development platform. This could be .NET, Ruby on Rails, Sinatra, Node.js, PHP, or whatever.
  • Bring a spirit to learn about new frameworks, get all polyglot, and have fun.

Meeting Workflow:

  1. The meeting will join.
  2. Teams will form.
  3. The kanban board will be explained and setup for use by the teams.
  4. We’ll unpack the user stories, setup workflow, and idea behind the meeting will be reviewed.
  5. Select team technology & domain element (barista or coffee drinker).
  6. Setup tasks within teams.
  7. Pick pairs to work on tasks.
  8. Code… implement…
  9. After implementation, we’ll review everything, and trade war stories.