Yeah this is article comes out and says that it's based on gut, not science. So speaking for anecdotal evidence, unit tests that don't break and frequent deploys are way better than finessing one more Gherkin test.
I worked on a codebase with a similar address problem. Oh, and there were no primary keys. Instead, each row referred back to a separate table with four keyed initials.
Good database design upfront, and vigilant upkeep will keep the application layer tidier.
It seems like there are two things at play - whiteboarding interviews vs. using whiteboards in your day-to-day job.
If the test is to see how well a person works in a whiteboarding interview to solve a problem, then it should be a simulation of collaboration, while trying to avoid the Clever Hans effect.
Otherwise your DP whiteboarding problems are worthless.
The comment section of the announcement has plenty of Pocket-switchers. I think Instapaper is much more focused than Pocket, which seems to be more geared towards recommendations now.
