React Hack Night!

This month we’ll be getting social!  We’re hosting ReactATL’s first Hack Night.  No talk, no real structure.  Just come with your laptop, your ideas, your code that just won’t work.  Share a project you’re working on.  Get the community’s input and walk away with your code looking better than it did when you walked in.  Or, just come and hang out!

We’ll have food and beer as usual, thanks to our sponsors VersionOne and Pindrop.

Feel free to post in the comments here or join us in the #react channel on Tech404 ( if you want to get people thinking before the Hack Night!

Looking forward to seeing everyone there,

– Taggart and Andrew (

Pizza & beer; but the real value was meeting new folks and finding new resources; books, people to follow, sites to watch and data to glean and learn from. Thanks guys!


So now that I know Node and Express, and Angular(better), so now I can break off and try out React. I just really needed to get the core down, and that needed really digging into JavaScript

Node May OpenSpaces

Hey, so this guy Ryan quoted me on his blog, from a comment I made in group.

WHOOOT, I think that is the first time someone else quoted me. Other than all the army quotes I came up with.

We talked about all sorts of things, like How to get Hired, proving your knowledge, and how to get started with Node.


Effective Minimal Viable Products

Building Effective Minimal Viable Products

A Minimal Viable Product(MVP) is one your most important tools, yet so many people mistake it for an excuse to build & ship badly designed sites. Consider delivering a product that gives you insights from day one by effectively mastering the creation of your next version.
I want to share some ideas about some steps I have learned over the last couple of years and why this is coming to a head now.
You should consider reviewing the benefits of why we build an MVP for delivering great products with A/B examples and case studies to back up our user research.
Choose the appropriate criteria, actionable and measurable, to define success for your business and this product.
Do you focus on the customer problems with your current framework, or business processes?
Do  you interview users to identify and prioritize the appropriate opportunities to tackle?

I want to know from folks reading this, how does your company integrate MVPs and experiments into your business units?
Do you a product roadmap to communicate opportunities and set priorities? I know I have seen lots of things over the years,  ISO and Six Sigma, and Lean and Agie, all great ideas with their own appropriate places in business, come along, and then next thing you know some business executive is saying we need to do this. But this XYZ might not be the right thing in your place. So how do you know?
IS there enough business and technical know how to integrate MVPs into your Agile and Kanban approaches?
Does this fall on Project Management, or the Product Owner to present a compelling argument for MVPs with internal stakeholders and clients?

Well, I wish I had more hands-on practice creating these experiments and writing better hypotheses. I know I would need an idea of what we are looking for, but how many people should you reach out to for brainstorming? How much data are you looking for? I know in the past, my boss asked me, and I gave him my gut feeling. Usually not wrong, but I usually didn’t have hard data to offer.
Is running inexpensive experiments part of the business team, or part of the UX design process? Or are they blended?
So overall what are the Big Questions about integrating the MVP process: outlining business goals, identifying problems, setting up experiments, and managing the MVP; any others?