A lot has happened since the last Drupalcamp in Manchester, and when I say a lot I mean a hell of a lot. It’s been quite a few years since (over 3 years in fact!). Back then I was working a shitty job writing ASP code for a company that had no passion, no motivation. I didn’t realise it at the time but that Drupalcamp weekend would bring big changes for me. After way too many copy paste sessions adding new sections to brochure sites I figured there had to be a better way of doing things. That’s when I...
After reading way too much Hacker News and talking with a close friend recently, I stumbled across an interesting problem with new startups and their plan for the future. Plan for failure For those not familiar with this concept it’s a fairly simple one, you take your hipster nodejs/rails app and make it scale across multiple servers and data centres so when your cloud hosting fails your app doesn’t fall over in a pile of flames. The other failure This failure is even more depressing than server failure. What happens when your funding runs out and your app hasn’t taken...
‘CCFLAGS’: [‘$DIALECTFLAGS’, ‘$WARNINGFLAGS’, ‘-march=armv5t’],
snapshot = “”
snapshot = “”
To find and replace using querypath without destroying existing context you can use the following:
$temp = qp($output, 'table')->addclass('table');
$output = $temp->top('body')->innerHTML();
Herein lies the coder manifest.
Thou shalt not commit debug to production
Thou shalt create test for everything
Thou shalt not commit code to production and not deploy
Database shall not be kept it thy repository control system