Ask HN: How do you keep up with *developments* in front end web development?

9 points by votr ↗ HN
So not learning new technologies, but just being aware of new ideas, approaches, early releases, progress on standards, etc.

At the moment, I just sort of browse HN/Reddit and look at books being published.

How do you stay informed?

5 comments

[ 2.6 ms ] story [ 24.1 ms ] thread
I read http://webplatformdaily.org/ daily, and I subscribe to a few newsletters (PonyFoo, HTML5 weekly, JS Weekly). I read the changelogs for new versions of browsers. And, occasionally, I browse all the pages linked from chrome://chrome-urls. I've learnt about all sorts of old-but-new-to-me browser technologies doing that.
You don't.

Really a good majority of the stuff that is released at any given moment is pretty worthless.

Fixing something that doesn't need to be fixed, begging you to move to something for the sole reason that its new without a valid reason, etc etc etc.

You don't have to keep up at any given moment. Things that are actually worth paying attention to will filter through eventually.

I got out of the JS ratrace but if I had to I would read the helicopter view of the top JS frameworks and then talk to people at a meetup about facts on the ground of using those tools. For a small amount of work you can gain enough knowledge to know when to delve deeper and when to not bother.
This.

Unless you are unable to do something and need a new technology to solve a problem, but then, probably be best to stick with things that have a track record of just working.

If it looks cool do some side R&D with it, but until you see expected results I'd take any new technology with a grain of salt - especially if it's proprietary.