The argument against this approach is that it's not always humans accessing web pages. And even if it is humans, sometimes they need computer assistance to interpret the content.
http://en.wikipedia.org/wiki/Semantic_HTML
As the article says, this is equivalently achieved by naming div classes and IDs (or some other attribute like itemprop a la schema.org). Also I'd say a completely style-free HTML scheme with open-ended semantic tag names (XML) styled by CSS is equivalent. The point is HTML doesn't serve a useful styling purpose.
I don't have a strong opinion on whether browsers should provide default styling, as it's trivial to override (although many web pages do rely on it). I agree that HTML tag names don't serve a very useful styling purpose, but they provide a useful structural purpose that cannot be easily replaced by using open-ended tag names or classnames. Custom Elements (http://w3c.github.io/webcomponents/spec/custom/) are in the process of being implemented, but I don't think that's an argument for throwing out the standard, structural elements that provide a common API for interpreting document structure.
We run a network of alternative weekly magazines / websites in several mid- to large-sized markets in the United States. Our publications cover local news, politics, and culture with a brash, liberal slant. They also host events such as music awards and cocktail festivals in their respective markets, to which employees are offered complimentary tickets. We offer full health coverage (including vision & dental) and 401k.
* Python/Django web developer *
In this position, you will lead a small team to build a single web publishing platform for our network of alternative weekly papers from the ground up. You will be responsible for making high-level architectural decisions, as well as day to day coding, testing, and deployment. Our goal is to have a flexible, modern news and events platform that provides a great reader experience while simplifying management for our editorial and sales (advertising) staff. Once the system is built, your team will work with our writers and editors to help develop custom, engaging reader experiences such as immersive stories and interactive data features.
In this position, you will join a small team to build a web publishing platform for our network of alternative weekly papers from the ground up. You will be responsible for designing the user experience and implementing the design using JavaScript best practices. Our goal is to have a flexible, modern news and events platform that provides a great reader experience while simplifying management for our editorial and sales (advertising) staff. Once the system is built, your team will work with our writers and editors to help develop custom, engaging reader experiences such as immersive stories and interactive data features.
But isn't the point of all this to make the process of getting health coverage less painful? A few glitches or a slow site are to be expected, but from what I can gather, the site was literally unusable for several days.
As I see it the point was to make it less unaffordable. Certainly "less painful" would be desirable, but as long as people can get the coverage (open enrollment is several months long, so a few days of downtime is bad, but nonfatal from a service perspective) and care gets reimbursed (still unknown, but I don't think it uses this particular infrastructure) I think you have to view the system implementation as a success.
Again, BCBS et. al. have been inflicting terrible web experiences on their users for quite some time now.
My thoughts exactly. This website was supposed to go from "testing" to "ready for millions of users who will present loads of unexpected corner cases" in just one day? That is not remotely trivial.
I have to admit I've been a little surprised at the level of outrage about the NSA on HN. Did no one think that the spy agencies of various governments were, um, spying?
At the same time, there's been a lot hyperbole about what these revelations actually mean. The fact is, we still don't really know, and a lot of innuendo has led people to conclude things that in all likelihood aren't really true.
I certainly think we should scale back wiretapping powers and beef up oversight, but to anyone who had bothered to look into what these agencies are likely capable of doing, this shouldn't be a huge revelation.
This is a real weak spot for companies like Google and Amazon, which have very little experience delivering quality tech support. Rackspace is playing catch up on the technical side, but they really understand support. It goes a long way.
Some people may see "Fanatical Support" and cringe at it as marketing: it's really not. It's a company core value, and baked into the DNA of every person in the company from HR, to IT, support, engineering - customers, developers, etc are not just revenue - they're our family and friends.
Fanatical support is what makes Rackspace, well - Rackspace.
That's really reminiscent of Zappos. I don't know how their service first attitude was taken at first, but I think over the years we've accepted it as a genuine thing.
Racker here, joined about five years ago. Spent some of that time in direct support roles and one of the things that we did was take a trip to Zappos, participate in their culture program. Routinely we would engage with other companies who we believed to be providing great service and find if there were ideas we could apply to our own product. Fanatical Support is home grown, but we definitely look to others in the industry who are doing it right.
Or using images for text? Many of these have very little to do with HTML5. Unless it's really about people abandoning Flash and bringing bad design habits to HTML. But even that doesn't explain the 404 "trend."
