5

About 3 years ago, we had 4 different WordPress sites for various clients.

My colleagues thought it'd be a genius idea to keep them all in one repo. Even more genius, for local development, a single installation which implements a switcher for the wp-config.php files so we can switch between sites. Not bad in theory.

Fast-forward to present day. 1 client left; another site got converted to using Laravel because they always asked us to update their content so no point using a CMS; whereas the remaining 2 sites use differing versions of WordPress on their live sites, no less than 18 months out of date, have no dev sites, different collection of plugins and themes and both modified to the deepest darkest depths of fucking hell that's barely recognisable as WordPress anymore and next to no documentation or comments around the changes.

The functions.php file of one of these themes is over 4000 lines long!!!

We're keen to upgrade our servers to use Ubuntu 16.04 which defaults to PHP7, so all the already deprecated WordPress functions will then fail to work completely as will have been removed.

Both of these clients have agreed that they wish to convert Laravel as well so there's not really much point in going through the clean up process of their WordPress sites. Just copy the database nuke it all and start a fresh with Laravel FFS!

They also wish to completely redesign and discuss what features to keep/add/remove. With no date for these redesign meetings in sight, we won't be converting to Laravel any time soon, nor upgrading our servers in the foreseeable future either!

This is all because of one dev in the office and his history of failing to keep on top of breaking changes!

Fuck you! Seriously, fuck you!!!

If I was your superior, then you'd have been fired long ago!

Comments
  • 0
    Damn, wasn't him fired yet? 😱
  • 0
    @azous unfortunately no. While he may be highly disorganised, he is to be slightly fair to him, able to write this code that works (surprisingly) very quickly. He also gets by on brown nosing our director who doesn't have a clue about technology.

    I'd be considered slower because I document and try to keep my projects organised and minimal and I'm also not burying my nose in the directors arse crack.
  • 1
    @beningreenjam that sucks.

    This tends to happen all over the place, people being responsible for professionals outside their field of expertise usually are treated like that or think the subordinate is doing a good work cause "it works", usually everyone else who actually does a good work end up being fucked up by that one, having to clean the mess.

    Wish you good luck 🙏
Add Comment