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.


So yesterday, I learned how to use a .gitignore file. I had seen them in use, and knew some folks used them, but i had not yet. Again another thing, that until you do it, you’ve never done it. Then once you do it, ok. Turns out, like most things, no big deal once someone explains it to you. Well, no one explained it to me. It was my job to explain it to someone else. Ya. ok, I have never used it, knew a little about it, so go figure it out. And I did.

A file, with no file extension like .doc, or .txt,  and starts with the .dot, which makes it a “hidden” file. Like your hosts file on windows, c:\Windows\System32\Drivers\etc\hosts

I currently just have two lines in there


later I will have 3

Put the .gitignore file at the root of your project. Now in an earlier version of my project, I had the node_modules in a folder called flapper news, so it would have been /node_modules. But now its also at the root.
I later added the npm-debug.log to the .gitignore file once I started trying to deploy it and the log file poped up. I don’t need that in the git repository.
Later, if I use grunt, I will need to add “build/*.js” to the .gitignore file as well. So check out the Readit project and my use of the .gitignore file on my GitHub @gokemon

Got Git?

pro-gitJoined GitHub, and am reading a book on Git. I don’t think I have anything important to contribute to the world.

Well I like how the world solves problems, and or sometimes just decides to change something. Like back when I first started learning about source control, I learned about it by myself using my MSDN at CLFD back in 1999 using Microsoft SourceSafe. Next I realized that the rest of the world (the hardcore command line folks) used Concurrent Versioning Systems(which I later learned on when I was with FEMA in the Washington DC area in 2009. I spent a good amount of time in 2001-2003 learning Websphere & Java stuff, including Apache HTTP web server, and later found out they took over Subversion. So now, and for many years Apache Subversion was the top dog. But along came Git & GitHub. Now I have my cheatsheet coming from Subversion going to Git.
So yes, I have worked with MS-SS, CVS, Subversion, and something else, I think…. unless it was merely a commercial version of some Version Control software. And since Subversion(cheatsheet) is the most recent(one-back) so I included a link to read more about it.