Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think its so great that we have so many new toys and such innovation going on in the world of the web. I remember when I was first starting out as a developer (when I was 10, it was 1996, I wasn't very good) all we had was HTML and CGI scripting. CSS was the new hotness that no one understood and PHP was just learning to crawl. Those two technologies were all there was and I don't remember other developers ever going nuts like an adoloscent girl at a Beatles concert over any of the stuff that was coming out then. It really is nuts how we push all this latest and greatest stuff only to abandon it next week. I remember just about a year or two ago the HN community was in absolute love (like 'The Notebook' style, forever and ever, everlasting love) with Rails - even more so than now. There were endless debates over its merits and its pitfalls and I watched as the people who took those debates the most personally agonized over every small bit of the development process while those who didn't really care as much just built stuff.

It really is great that these new toys are coming out but what I see as the real problem is that we lose sight over one particular piece of the bigger picture. We forget to ask ourselves "Does this solve my or my users' problem(s)"? Even when we do ask that question we then get caught up over minutia like the elegance of code and performing between two competing tools.

That stuff doesn't matter yet! What matters is that you grasp the concepts the tool promotes and can use it effectively. Beyond that there's usually not much difference in the "elegance" or performance of your code between two tools and it usually comes down to subjective views and how you work. Even if you do choose the "optimal" tools you're most likely fucking up some other part of your codebase anyway. None of us write perfect code. That's why refactoring is a thing.

Are you stuck when it comes time to choose handlebars or mustache? Can't decide between Ember and Backbone? Is Rails or Sinatra better? CodeIgniter or Laravel? Thinking of using Django over... uh... whatever the competitor to Django is? Then you've got your head stuck way too far up your ass and focusing on the wrong thing. I don't mean to offend with that crack - I too have had my head up my developer ass many times before and all it got me was a 'Hello World' page in a project that was stalled before it even started.

So my point is that using the new hotness is fun and challenging and it can do you a lot of good but the moment you stop developing and start chasing the new hotness you've become kind of a tech groupie rather than a developer.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: