And did some tests on the favorite guinea pig: Wordpress.com. I was testing future post dates using forward dates so I set 1 post to publish in 15 minutes and one in 5. I was doing my thang and was refreshing every now and then. The publish time arrived and I was anxious.
but…
The timer showed 1 minute to ... and when it reached the ETA it started … going up!?!?! So it went like this: 5,4,3,2,1,2,3,4,5 and is still growing. When I move the mouse over the date it's the right one when it should have been posted so so it should work.
It took me a while to recover from the shock. So I took all the steps a person potentially exposed to a time anomaly must take:
I checked my hand watch, wall watch and (had to call someone to make sure the anomaly did not affect my entire home) called a friend to confirm the time to make sure I'm not caught in a time loop or any other time anomaly / paranormal shit is going down on me. After making sure the time still flows the right way I realised the problem is with the mind-flow of the Wordpress dudes and…
I decided to take a look at the source code. My hands are still shaking after being exposed to the horror. I couldn't, I just couldn't! Never have I seen such unclean, unorganized code and I remebered why I don't work with others and I don't outsource shit. This is the reason.
The code is not only non-followable but this bug exists sience 2006 and they didn't fix it yet. No tracked bug has lived more then 24h around me. Imagine how well they know their own code and how easy they can get around it.
So, don't rely on Wordpress.com for scheduled posts… anyway, not those made with XMLRPC (those I care about).
You did a good job guys. A great job but its that moment when you need to take a few steps back, get an overview of things and start over. I have a 100.000+ lines C++ code library that consists of core (Pointer/Memory handlers, String handlers, File handlers) and rest. The core exceeds 10K lines easily. And untill now I rewrote the core twice, each time with huge performance improvements. And by the end of this year I'll be doing another rewrite and I'll be timing it in microseconds to improve speed.
I would say you reached this point and some rewriting will help a lot and it takes a lot less time each time. Gained experience kicks in and makes a difference every time!
Post Feedback