Why It’s a Good Idea to Be a JavaScript Developer, and What it Takes to Be One

Re:Why It’s a Good Idea to Be a JavaScript Developer, and Wh... by alkonaut on Monday December 16, 2013 @05:32AM (#6913920)

The common denominator of all that is wrong with development today is the internet. Work on a library, thick client, compiler, or anything like that and you are fine, but work too close to any of the tiers in some kind of internet/web based application and your day is filled with misery.

Hopefully this internet thing will just fade away soon and we can all go back to real development.

[ Parent | on HN ]

Re:Why It’s a Good Idea to Be a JavaScript Developer, and Wh... by MDCore on Monday December 16, 2013 @07:56AM (#6914409)

Web development is a complex ecosystem. As a front-end dev I don't get to control much: many types of devices and software might run my code or display my HTML. Catering to that is the nature of the environment, and that heterogeneity (of devices and software) is what makes the Internet great.

I disagree that catering to that fills one's day with misery. In fact I think it's fun and I wouldn't enjoy working on a library, thick client or compiler quite as much. That's ok, development is big enough for us both to find something we like doing, without needing to denigrate what we don't like.

[ Parent | on HN ]

Re:Why It’s a Good Idea to Be a JavaScript Developer, and Wh... by chrisweekly on Monday December 16, 2013 @10:36AM (#6915322)

Well put.

Also, even for a front-end person, those don't have to be mutually exclusive options.

Case in point: this week I am working on both heterogeneous end user-facing UI stuff AND [relatively] controlled-environment node-based webdev tooling for our FE team. I enjoy both types of challenges and think its healthy not to get too pigeon-holed into one such context or the other.

/$.02

[ Parent | on HN ]