I certainly hope it's not true. But I can also understand how it's hard not to be a little salty. After a decade of development experience, it certainly feels like IOS Safari has consistently made life more difficult when developing web apps.
No, this is purely anecdotal. I found that it helped when sat up straight and adjusted my hips. But, pushing out too far does put a different pressure on your lower back, and I agree, is just as bad. I think it's about getting the right alignment for the best support for your whole back.
I found this Ted talk helped me with some lower back and leg issues. I don't do exactly what she demonstrates in the video, but I find focusing on the 'tail out' posture helps a lot. Also regular breaks and going for walks.
It strikes me as a little naive to only consider job security from the perspective of "can a machine do my job". Once AI and automation start taking people out of the workforce at scale, it seems likely there will be a lot more people competing for the jobs that are left.
Exactly this. I think some of the tutorials and introductions were a bit overwhelming with their huge dependency lists (see Polymer catalogue), and a lot of opinionated ideas about how to form a Polymer application. Core Polymer is so easy to pick up and flexible. It's been a joy to work with. Well ok, there's a few gotchas, and the build process if you're mostly rolling your own can be a real pain. But once you find your feet with it, everything works pretty well.
Also, using the two way binding is optional. We've been using Polymer for about the same time with Redux and a unidirectional data flow. I'm very happy with it.
This would have been fun if I was able to catch more than MountainView California stamps. I was going to share this with the kids, but as it is, there's very little return on investment. Also, using the view my planes showed me nothing. :( Nice concept, with some rough edges.
The plain text file has been fixed up since I made my comment. I agree, the plain text file is now quite easy to read, making my snarky comment look quite silly... :)
I think I was conflicted over the idea of making a point by making said point hard to read. But to be fair, since I last read the text file, the width has been fixed up, which has... made it much easier to read (the original was full width lines). If it had originally been presented in it's current format, I would have never made my comment.
I think this is a bridge too far. Justin Jackson made a good point about approaching your content first etc, but stripping back to just plain text just makes this harder to read. In fact, if you've read the first post http://justinjackson.ca/words.html, I'd argue that this almost impossible to read through to the end without skipping. Which sort of dilutes the whole point...
Perhaps the post should read:
This is a regular text file.
Nothing advanced and not much to see here but some words.
And you're pretty sure you've read this already, quite recently in fact...
AND THAT'S ANNOYING!
You're probably not even reading this bit, as most of you will have elected to skip to the end only to find I'm plugging something.