Month: April 2013

The biggest merge ever

I am having a really proud and exciting moment at work right now.  We’ve just deployed the biggest merge ever.  I can’t really share enough details to provide you with the context (NDA and all), but here is a GitHub screenshot that gives you an idea.

the biggest merge ever

If you are not familiar with GitHub and don’t know how to read this, here is a summary:

  • 1,633 individual commits
  • 2,696 modified files
  • 424,292 lines of code added
  • 82 lines of code removed
  • work done by 4 people

And it all went so smooth, that we even deployed it on Friday, without a single second of downtime.  Awesomeness!

Update (April 15, 2013): And just when I thought that that was the biggest merge ever, we did one more the next working day.  Have a look!

the biggest merge ever again

Cool stuff in upcoming WordPress 3.6

WordPress 3.6 is not too far away, with the first beta already released last week.   WordPress VIP blog did a very nice and very visual overview of the changes and new features in the release.  For me personally, these are the highlights: log out notifications, better autosave, and a new look for post formats.

WordPress logout notification

Things that I still hope to see one day in WordPress are: some sort of standard for post formats (cross-theme support, mobile app support, etc), and easier way of development and deployment across multiple environments (dev/test/live servers, etc).  Regardless of my pending wishes, WordPress is still an awesome piece of software, which gets even more awesome with each release.

PHP is meant to die

PHP is meant to die

This one is not your average PHP bashing.  It only covers one, but rather generic, problem with PHP – dying, no matter what.  Personally, I am familiar with the problem and I had to work around it as well (that’s how Locker came to be), but I’ve never had a project with high enough load to trigger a major issue.

There’s more to this. If you’ve used PHP an awful lot , you may have experienced this very weird issue:

Fatal error: Exception thrown without a stack frame in Unknown on line 0

What does that mean? I honestly have no idea. I can’t find the line #0 into an unknown PHP file.