- “How many of you are more like me, where you’ve been finding these cool dropdown menus in other sites, viewed source, copied and hacked your way through it… not working? Let’s add some alerts!” - At least 80-90% if not all raise their hands.
Great question! Maybe fourth-ish years ago I started to really gravitate to more client-side work as it just makes sense to me to push more of the work onto the client for scale reasons & because I believe the user gets a better experience. Silverlight was the first tech that I was sold on. But that got nixed and then we saw the rise of libraries like jQuery & KnockoutJS.
Then maybe two-ish years ago I started to work more on primarily client-side applications. I jumped on the single page application bandwagon with DurandalJS first and then Angular. Its funny because I was doing these types of apps in the late ’90’s when they didn’t have a name… but tools & frameworks we have now make it much easier to work with.
Like any typical developer, I was curious and started poking around. This opened up my eyes to a whole new world that really leads into the…
I can’t stress that last part enough… the developer utility & tooling ecosystem has exploded thanks to Node.js! Why does this matter to me?
I love the fact that it’s one language all the time, all the way up, down & sideways on the stack. No context switching between languages and tools. This was a surprise how the lack of switching languages and within projects made things so much cleaner and easier. And a cool little bonus: recently I got Node.js working on a Raspberry Pi 2 so I it even works on IoT projects… which is totally killer!