GitHub Update

As St. Patricks Day approaches I reflect I was at WordCamp last year about this time and decided it was  time for a GitHub update.

GitHub Update I created my GitHub account back in 2012, and never really knew what to do with it. I mean, I didn’t have code that was so magical or wonderful that it needed to be shared with the world. And the years rolled by; 2012 became 2013, then 2014, and 2015 came and went. Then in 2016 I took part in an amazing program at General Assembly(GA), a coding school, called Web Development Intensive (WDI).

HTML 3.2 Compliant Web Page Logo
HTML 3.2 Compliant Web Page Logo

Now remember I have been building web pages since before HTML 3.2 can out, because I remember when it came out, or at least I started using it sometime in 1998. And I started building pages to the new 4.01 standard in 2000. So the WDI was a reboot for me. I had dealt with the buzz word Dynamic HTML, and XHTML phase, and then HTML 5 came out in for real in 2014.

HTML5 standards compliant
HTML5 standards compliant

I had tolerated JavaScript back in the early days because it would work in Netscape and IE, where as my beloved VB-Script only worked in IE. I was starting to use CSS back in 2000, but by 2011 CSS3 was here to stay, and growing. MY Basic JavaScript days were gone with jQuery, a cross-platform JavaScript library designed to simplify the client-side scripting of HTML, having taken its place in my tool-set some time back in 2012. All this adds up to still nothing worthy of adding to GitHub.

Along came 2014, the year of JavaScript fatigue. Every time I turned around, every MeetUp I would go to there was something new, that I was aware of, but didn’t really know. NodeJS with its V8 engine, Angular JS was replacing Backbone, Gulp was taking over from Grunt. And in 2016 I took part of the WDI at GA, and got me back on track.

GitHub Update 2018

ProGit BookcoverFinally I learned how to work Git and GitHub. In 2016 I had 210 contributions, and then had a lag. Bounced came back in 2017, after the WordCamp 2017 with a pledge to do 100 Days of Code.
I had 409 contributions in 2017.

So my “State of the Union” GitHub Update is that I made 421 contributions in 108 repositories in the last year.

JavaScript fatigue

  • Ember,
  • Angular,
  • React,
  • Express,
  • Grunt,
  • Bower,
  • npm,
  • Broccoli,
  • Gulp,
  • Lodash,
  • Underscore,
  • rxjs,
  • Knockout,
  • SocketIO,
  • Threejs,
  • D3,
  • Backbone,
  • Ionic,
  • Angular2,
  • React Native,
  • Redux,
  • Alt,
  • Reflux,
  • Webpack,
  • Bluebird,
  • Express,
  • Mocha,
  • Jasmine,
  • Chai,
  • Less,
  • Sass,
  • Postcss.

MEAN Study Group 2017

Starting out 2017 with a BANG, Snap crackle and pop, maybe some Rice Krispy Treats. And a MEAN-stack study group.  Going to start a new study group. MEAN Study Group 2017 will cover the whole project from design ideas to user statements to front-end HTML & CSS work to Angular with dummy data, to building the database and node infrastructure needed to make a data-driven dashboard app.

I think all New Years celebrations need to have some kind of Bang, sizzle, and flair to it. And with Chinese New Year apron us, we should make some noise and drive away the evil spirits and orange blobs.

Here are three free PDF books you can download and learn from.

Learning Web Development with Bootstrap and AngularJS

Learning Web Development with Bootstrap and AngularJS builds a Contact Manager.

Learning Single-page Web Application Development

Application development using the MEAN stack with JavaScript on the server & client side, covering concepts such as Yeoman, RESTful APIs, Passport authentication, cloud deployment, Bower dependency manager, Karma and Protractor, deployment.

AngularJS Up and Running

This book is about Angular, but every other chapter is about testing the material from the chapter before it. Almost a 1/3 of the chapters are about testing. Highly recommended read.

In case you didn’t notice I am excited to start doing this project again. I want to welcome Mike Baker as my co-study-group-leader. Check out his blog.

Introduction to npm as a Build Tool

gulpJSGrunt and Gulp are the heavyweights in the JavaScript build tool landscape. These tools can automate almost anything you find yourself doing repeatedly in a project, from minifying and concatenating source files, to running tests or compiling code. But the question is, do you need them? npm’s script directive can do everything that these build tools can, more succinctly, more elegantly, with less package dependencies and less maintenance overhead. In this session Jennifer Bland will discuss what npm is capable of as a build tool.

Jennifer Bland is a Software Developer for CNN, specializing in MEAN stack development. She has more than ten years of development experience. Jennifer is the author of the book “Developing e-Business Applications Using Lotus Domino on the AS/400″, published by IBM.
She runs the website which provides interview questions to assist programmers in preparation for job interviews. Her personal website is
Jennifer holds a B.A. in History from Furman University and an MBA from San Jose State University.

After Jennifer’s presentation, Joe DeCarlo hosts an Open Spaces

  • Open Spaces is a discussion format that allows attendees to vote on and participate in conversations on topics chosen by the audience. It is a great way for you to talk about or just learn about a topic that you chose. It also allows other audience members to share their expertise.

npn-nodeAfterwards social time, we will meet at a nearby restaurant for drinks and food.
Thursday, July 21, 2016, come on down about 6:30, starts at 7…General Assembly at Ponce City Market (PCM)

Node Design Patterns Explored

Design patterns are a part of good design once you realize there are common patterns that you apply to software development. First discovered many years ago in a galaxy far away, and then rediscovered by the gang of four and brought into our Java-based solar system, design patterns have also found their way into JavaScipt and then into the NodeJS world particularly.  I thought I would share some ramblings about Node design patterns as food for thought.

Node Design Patterns

Node design patterns explored and considered
Node design patterns

Oh ya, whats a design pattern? A design pattern is a general, reusable solution to a commonly occurring problem. My take on the broad strokes on what we see in the NodeJs world are as follows;

    • Asynchronous Control Flow Patterns,
    • Coding with Streams
    • Design Patterns (regular named ones)
    • Wiring Modules
    • Basic Recipes
    • Scalability and Architectural Patterns
    • Messaging and Integration Patterns

Basic Recipes should cover Implementing a server with no batching and caching, asynchronous request batching, and its buddy, asynchronous request caching, and finally batching & caching with promises.

Scalability and Architectural Patterns should cover cloning and load balancing, and decomposing solutions like dealing with monolithic and microservice architectures

But for me, the core basic Node design patterns are the general ones that everyone knows about;

    • Factory
    • Proxy
    • Decorator
    • Adapter
    • Strategy
    • State
    • Template
    • Middleware
    • Command

The last section I think you should read up on in terms of Node design patterns is wiring modules. Modules and dependencies, cohesion and coupling. Do you go with hardcoded dependency, and deal with dependency injection? and what service locators and dependency injection containers.

As you know I am often full of questions for you to ask yourself, and sometimes I give out tips and places to look. Like

There are several books on Node design patterns out there to peer into and lots of posts that talk about them, but it’s something you have to learn for yourself.

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