While Drupal Planet can be a fantastic resource, it can also be a megaphone used when someone has an axe to grind. It's particularly unfortunate when one of those people don't open up comments. Theoretically useful code that comes with an axe to grind should always be suspect to begin with. When the first thing that the author says about the module the code is for is derogatory, it's a pretty good hint to distrust everything that follows. After all, "I don't like this module, and here's some code for this module I don't like," probably suggests that the author would rather you didn't use that module.
That's fine, I don't have a problem with that part. I'm pretty used to people with bad things to say about Panels with varying levels of justification for their words.
However, today Josh Waihi posted an article that contains some code that if you use it, you run the risk of totally breaking your site and having no idea why. I'm completely against people posting code that will break your site, if you use it. I'm especially against people posting code that will break your site with comments turned off, so that no one can actually comment to tell the readers that the posted code is broken.
In particular, this code should never be used:
ctools_include('node_view', 'page_manager', 'plugins/tasks');
ctools_include('panel_context', 'panels', 'plugins/task_handlers');
You see, both of those files are plugins. They're specially included files that contain more than just code. They contain an array of variables. Unfortunately, those files can only ever be included once. If they are included once, like this, and then later loaded as a plugin, that array of variables never gets read. And your plugin will just randomly disappear and leave you with an incredibly broken site.
Judging by the code after it, the first line isn't even needed (page_manager_get_task() will load the plugin) and I'm pretty sure the second line isn't needed either, since the get_handlers call should load the second plugin. That said, if you absolutely positively must load a plugin file for some reason (and I often have needed the file loaded to get at functions in it), you have to use ctools_get_plugin().
Also, on a somewhat lighter node, the last line is totally against Drupal code style. You shouldn't use it just because it's a silly way to save 6 keystrokes at the cost of legibility.