FYI - a new beginning?

Posting after a very long interval. A lot has happened in my personal life since my last activity - I have to shoulder new responsibilities and of course, I am not getting any younger (by age and body, if not by mind). I am attempting to break away from corporate life and become a freelancer, possibly a software architecture consultant, in due course of time. I have my hands full as of now.

Meanwhile, I have dabbled in Javascript, hybrid Mobile frameworks like Phonegap and Titanium and gained insight on the sundry mushrooming JS frameworks. The rise of Node.js, I feel, is a sort of vindication of my 2010 July article series - Do we really need Servlet Containers always?. I have also gained a whole new perspective and respect for user experience and GUIs, thanks to my recent-most employer - SapientNitro.

Looking at my earlier blogs, I found that the link of an earlier article of mine - The Dilemma of The Framework Creator had broken and the article was languishing in the internal site of my erst-while employer. As it had nothing to extoll or revile any particular product of any particular company and rings as true today as when I had written it, I thought it was a waste of a fine article and got it published in DZone's Architect Zone.

The Dilemma of The Framework Creator

Developing or contributing to a framework used by a majority of the software community is one of the prime sources of career satisfaction for a whole lot of software developers, designers and architects. A great framework can be an object of beauty to them, just as a fine cathedral is for its architects - an expression of their creativity.

But a framework can be sustainable and useful only if it is designed with certain principles. This post is an attempt to find what it takes to make a sustainable and widely accepted software framework.

Read the complete post here.