Recently I've been getting back into doing some algorithms coding challenge problems, and I really wanted to setup for myself a nice, comfortable coding environment that I could be proud of and that really followed the TDD principles of Uncle Ben, Ken Beck, and all the other gurus. Anyway, this is a guide for setting up simple, barebones TypeScript node.js projects for TDD. I'll show you how to set up a brand new node project, how to make your project a "typescript project", how to add mocha and chai in watch mode, and finally how to see your test results in a nice code coverage report. It's a lot I know, so let's dive into it!

I went on an interview today for a senior dev position at a large bank by world trade center today, and it was a great experience. They had an open floor plan and everyone had a super-wide monitor which looked pretty awesome. There were stocks shows playing on tv's  hanging from the ceiling and people were relatively dressed up, but the people who interviewed me seemed nice. I probably won't get an offer because the one interviewer asked me TWO relatively simple Angular questions that kind of stumped me. I don't think I would have really liked it there for  long but big thanks to this person for pointing out these gaps in my knowledge. 

People ask me, "Jim, if you want to do typescript and node.js they why do you waste you time learning about functional languages like Haskell and Clojure?

As a professional software developer I have had the luxury of being able to work on successful professional projects in AngularJS, React, and now the modern Angular. To me it's so funny how similar the two frameworks are in terms of the problem they are trying to solve and even the way they do it.

I've recently been building web applications with front-end frameworks like React, Reagent, and Angular 2. I was recently working on an Angualr 2 project and thought, "man, this sure seems like a ton of lines of code", but had no concrete evidence to prove it. After a quick google search I came to this stack overflow question, and the awesome answer(s) therein.