Skip to main content

Don't innovate!


Gopinath had a shocking news for me this morning... the site that we were cloning--cloning with additional features and innovations had just released a new version, but with six features taken from our version. Had we released it some days before, we might have grabbed the innovation pride. But...

The weirdest thing was that we're forced to clone including the landing page as in their previous version (and that is the reason for this delay), but when we're doing, they switched to our homepage version! Damn...

It doesn't stop here. I was pacifying myself and pushing the software to be released by afternoon--at least then to claim the innovation card. Now Kanagavel has another "good news" for me, that we have to "tune" the product to be exactly as in PSD that would take another week to ship...

Comments

abuthakir said…
we should document or blog the upcoming release items for proof

Popular posts from this blog

Converting PSD with PHP/ImageMagick

After seeing feature rich options in Imagick PECL extension at Mikko Koppanen 's (the author) website and also impressed with ImageMagick 's features, I have decided to use it for the PSD to XHTML conversion website that I'm architecting and managing. Since, the team wants programming help for converting PSD images, I have tried it (documentation is sparse on PSD handling) Converting PSD to PNG/JPEG/etc Note that, flattenImages() is needed for layered/multi-page PSD file. <?php $im = new Imagick('test.psd'); $im->flattenImages(); $im->setImageFormat('png'); $im->writeImage('test.png'); ?> Extracting PSD layers One by one <?php $im = new Imagick('test.psd'); $im->setImageFormat('png'); for ($i = 0, $num_layers = $im->getNumberImages(); $i $im->setImageIndex($i); $im->writeImage('layer' . $i . '.png'); } ?> Note that, there is a better version below In a single call with writeIm...

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

Tim Van Wassenhove's (PHP) Blogmarks

Tim Van Wassenhove , a c.l.php regular maintains wonderful blogmarks . Most of the blogs are PHP related and it is faster to access than my Sage, RSS reader . It is interesting to see that Tim has blogmarked my—this simple blog too:) IMHO, it would be better to display timestamps along with the links and to have a TOC of blogs in the top.