Home » 2016 » October

Getting Started with Angular 2

Angular 2 is finally released.  But the biggest problem with learning Angular 2 is that it is a “Choose your own adventure” kind of framework.  And while React has a similar problem, I think Angular has out done them.  This means that you can learn bits and pieces of Angular 2, but it will be a while before you get a cohesive understanding of what choices you need to make, which choices are the right choices, and why all of this matters.

And all of this is even more difficult if you are a relatively new programmer.  I’m talking those of you who have less than 5 years of experience and even some of you who have less than 10 years of experience.

So, what I thought I’d do to address this very real problem is to assemble a very opinionated Angular 2 tutorial.  Over the next several weeks I plan to show you how to create a simple CRUD application using Angular 2 in a way that will scale up to larger projects.  While I may mention some of the other options along the way, what you’ll end up with is the “right way.”  OK.  To be fair, most of what I consider “right” is opinion.  Some very smart people disagree with me.  But, some other very smart people agree with me too.

Getting Started with Angular 2
Photo credit: mikecogh via VisualHunt / CC BY-SA

Continue reading “Getting Started with Angular 2”

The Myth of Sloppy Code

  • Tightly coupled code runs faster.
  • Tightly coupled code is easier to write.
  • Test Driven Development increases development time.
  • Test Driven Development negatively impacts code design.
  • Knowing the names of design patterns isn’t important as long as you can use them.
  • All my customer cares about is how soon they can have the product, not how clean the code is.

All of these statements, and others like them, are excuses for not writing code correctly.  And you know what an excuse is, right?

The skin of a reason stuffed with a lie.

The Myth of Sloppy Code
Photo credit: dynamosquito via Visualhunt.com / CC BY-SA


Continue reading “The Myth of Sloppy Code”

Revisiting The Technical Interview

I’ve written about the technical interview before.  I’ve written both for and against code interviews.  And I’ve provided both C# and JavaScript questions to weed out fake programmers. But a little more experience under my belt has me rethinking what makes a good interview.

Now, you may wonder why I think I’m particularly qualified to speak about the interview process.  Most people who have opinions about the interview process in particular have it from only one side.  The one of being the guy looking for a job.  And, most of you only interview when you need a job.

What makes me qualified is that, I help interview people looking for a job and I interview for lots of jobs.  In my opinion, you should be interviewing for a job, even if you don’t need one, at least twice a year.  I interview more frequently than that.  In the last 6 months, I think I’ve interviewed at least 4 times.

So, let me start by telling you what the current interview process looks like, and why it doesn’t work.  Then, I’ll move on to the few interviews that I believe captured the information everyone was looking for quickly and how you can move the conversation in this direction regardless of what side of the table you are sitting on.

Revisiting The Technical Interview
Photo credit: Gangplank HQ via Visualhunt / CC BY

Continue reading “Revisiting The Technical Interview”

Angular 2 Thoughts

I was asked this past week what my thoughts were on Angular 2.  I wrote early on about my impressions of Angular 2 when it was barely done enough to review.  But now that I’ve been working with it for a while and know a bit more, what I want to discuss is more along the line of what it means to the average developer and, more importantly, organizations that are planning to use it.


Continue reading “Angular 2 Thoughts”