A Developer's Experience

My experience with blogspot has not been pleasant so far. I have found the interface and the final page rendered broken many times. If I write just paragraphs of text, maybe that works fine. But in a technical blog where there is code and links and various other formats, blogspot fails miserably. I find the themes and other user interface oriented stuff within blogger crappy. Yes, you can edit the template but neither do I have the time nor interest in that. Google should have improved blogger to really compete with other platforms - WordPress, Ghost etc. Blogspot, obviously, is not of high interest for Google. Overall, I am not happy with the product. I will be (have already!) no more writing here on this blog. Will be continue to post at http://vivekragunathan.wordpress.com . See you there!

A short while ago, I had to write a compelling document for a client about a library that I had developed during my tenure, call it A-Team Library or ATL . Having to learn the " eyes-wide-shut " culture to maintain the couples-of-decades old code and simultaneously develop on the top of it was very disheartening. It was time a lot of things were given fresh thoughts. Not the least of all duplication of code and functionality . But not just that. Like in a programming language, when there is more than one way of doing something, when those ways are opposing, it causes nothing but confusion. So was the case. The business seemed to be far from realizing it.Instead of showcasing the issues that were being faced and yet not realized, let me state the alternate - how things in such cases can be better: Business has to realize or let known: When the engineering team accepts the authority of the business in deciding the priority of features, the business has to be prudent enough