brianmcd

> For example, a huge amount of UI problems we catch belong to the Screenshot testing stage. Fewer problems belong to the Linters / Unit / Render tests. That doesn’t make those tests meaningless. On the contrary, it could mean that we work in these areas well enough to prevent tons of issues.

They don't say how they measure "issues" in their chart, but if it's through CI failures, it seems likely that "Linters / Unit / Render tests" catch fewer issues because developers run them locally before pushing code.

> I was very unpleasantly surprised that it was possible to lose a substantial part of my retirement fund contributions, taken out of my salary, after quitting.

To be clear, anything you directly contributed from your paycheck is yours and isn't subject to vesting. That's always your money. The part that may have vesting rules is the employer contribution.

> The point of failure wasn't "using a non-gmail address," it was "using an untrustworthy registrar."

But wasn't his point that gmail.com is much less likely to have its MX record compromised than any domain you could possibly register? So using your gmail.com address removes the issue of registrar trustworthiness completely.

Check out tmuxinator: https://github.com/tmuxinator/tmuxinator. You can create configurations for your projects that specify windows, panes, which apps to run, etc. It's great for starting all the servers/shells/workers required for a project.

I believe he's talking about node's behavior when requiring a folder: http://nodejs.org/api/modules.html#modules_folders_as_module...

This is an example of the "stack ripping" problem, described here (section 3.2): http://www.stanford.edu/class/cs240/readings/usenix2002-fibe...