If you go for a denomalized approach to scaling, you might end up wondering where all the duplicates actually are in the system. Do people / can we just store a list of all the places in another record? So that you don't have to make your code hard-coded to know.

I am into the whole Leprechauns of Software Engineering thing; I did buy it.

yes. yes yes yes yes yes. (now, if only frp would really work out. maybe rdp will take us away.)

basically i have yet to find a source control ecosystem that doesn't have massive suck somewhere along the line. take mercurial and bitbucket for example vs. github. in the latter, if you go into a branch and down into the source tree, you get decent urls that do not have anything like a particular revision hash in them. whereas in bitbucket, they force you into a given revision (presumably tip of tree when you start browsing) which just seems stupid to me.

"The problem is we build on the assumption that we should not fail, not the assumption that we are bound to fail, but with early detection and fast recovery/exploitation we can turn the situation to our advantage. That means organisational structures that are agile before the crisis, not bureaucratic. It means network connections built and sustained in advance, the ability to delegate power when needed without complex process."

Some nice food for thought about what software Kanban might be.

While I am not particularly a user of Facebook, nevertheless I am interested in how it might have come so far. The overall catch phrase of the presentation of People Times Process is certainly not something I'd take issue with.