Richard Wysocki

The Clean Coder A Code of Conduct for Professional Programmers I hope I don't get in trouble for posting my notes as I recommend all developers to read The Clean Coder book.  These are just some of MY personal highlights from the book.  I'm sure you will get a lot out of it reading it for yourself vs. my notes.  I wrote this up so I can read over this daily and keep focusing on what I enjoy about coding and enjoying my profession.   Author:   Robert C Martin (Uncle Bob)     First Rule:   Do no harm QA should find nothing Test, Test, Test Every Line of Code should be tested! Design your solution to be easily tested Best way is to Write Tests first – i.e. TDD (Test Driven Development) Merciless refactoring:   Always check in a module cleaner than when you checked it out. Why do most developers fear to make continuous changes to their code:   They are afraid to break it.   Why, they have no tests. Work Ethic Your Ca

JavaScript NodeJS                http://phillydotnet.org/labs/20150304/ Philly.Net NodeJS event. Rob Keiser started event and walked through how to setup and run NodeJS manually.  Why might you use NodeJS.  Light weight, Demo API’s, etc.. Some big companies are doing it.  Supposedly, you can use it within Azure if you want. 1.       Go to NodeJS and Install Node on your PC.  Recommended you Reboot once you install product. http://nodejs.org/                Install Project 2.       Used Subline Text for Editor (i.e. No Visual Studio in this Demo) Install http://www.sublimetext.com/ 3.       Manually created files to start up a little webserver.  Rob walked through how to create different js files which started up the Server, do Routing, handle different URL requests, etc..  It was challenging to follow along as he was jumping between JS files and I was more concerned with getting at least some of it to work. Below are some screen shots of a Working De