I feel like this is no different than passwordchart.com but is a bit less configurable. I use 1password myself after using passwordchart for a while. Ever thought about how to handle services that require you to change your password every few months?
I work at Webs and we also recently abandoned scrum for a more kanban approach. While all points in the article resonated with our company, the biggest problem we had was not delivering projects on time.
We focused too much on fitting as much work into a sprint as possible for maximized throughput. The problem with that, especially when you have alot of projects going on at the same time, is that alot of work was being burned across the board, but the needle for each individual projects didn't move forward fast enough and we ended up missing deadlines.
Another problem with scrum is that it turns creative developers into code monkeys, and this in turn lowers code quality. Developers are constantly worried about trying to meet deadlines for the next two weeks rather than taking the time to do things correctly. This ultimately creates technical debts and hurts the team in the end.
(also, if you're a manager and you use the developer points burned in order to rate performance and distribute bonus, then fuck you)
I very much agree with the last point. Objective evaluation of a developer is much more than burned down points.
I worked at Amazon and could see evidently that Scrum was turning good developers into mediocre ones. But not many raised a finger against it as Scrum was seen as the norm. And there was no scientific way to establish this fact.
Context absolutely matters! Techcrunch sold the article as Facebook betting too much on HTML5, period. His quote was that at the time 2 years ago, it was a mistake betting too much on HTML5 over native for their mobile application. And it's true, 2 years ago and even now, most phones have a hard time handling Facebook's intensive need in HTML5. It's true, Facebook could have spent more engineering resources improving the HTML5 spec and push it forward, but anyone saying context doesn't matter is just being ignorant.
Regarding his whole point of using css, that upvote image should really be a background in the css file and the innerHTML should be text with a negative indent.
The company I work for was recently acquired. A part of the agreement for the founders, aside from having to stay with the company for 2 years, is they can't have more than 1% ownership of a competing company for that duration and up to a year after employment termination.
sorry if I sound like a markup nazi, but... the pricing table contains tabular with headers and should be treated as such. The columns should be table cells and not divs (all a sudden you no longer have to provide a width on the entire container and it could stretch to fit and used in any location). The header-class container should either be a th, or if you opt for a non-table element, then an actual header tag would be appropriate. Maybe an h6? The bold tag was a poor choice; either <strong> or <em> would be a better option.
As far as reusability goes, the id="pricing-table" should really have been a class.
I'm afraid that using a regular table wouldn't allowed me to create this pricing table as it looks now. Although this is called a "pricing table", I think using a table isn't recommended in this case as it is quite restrictive.
Also, I avoided using HTML5 elements like "header" because I didn't wanted to include an extra HTML5 shim (for older browsers) dependency.
Regarding using <b> versus <strong>, this could be a long discussion here :). I think <b> just fits in this case as I don't want to add any importance from a content or SEO perspective.
As an argument for using HTML5 elements like 'header', the only older browsers that don't support them are IE 6/7/8, and the shim is < 5 lines of JS you can easily throw in a IE conditional comment block.
i'm sure other people have mentioned but it doesn't work in IE9 or below. You should at the very lease support IE9. If you wanna throw away IE8 or below, it would make sense to just use canvas rather than a base64-encoded image.
