Much of the time I spent as a developer and architect was centered around customizing features for a particular client. Tedious? Yes; thank God for new hires. Ultimately, I outgrew this more tactical level of IT and have continued in a leadership role. However, there are time where being hands on is still interesting. Why rely on a vendor when I can make a change (of fix problems from other vendors) when I can make the change in 1 minute. This dates back to a conversation I had with my mentor in the client service space.
“It’s often easier to do a job then explain it to an associate”.
Response time in the Web ultimately depends on the ability to turn on a dime. This falls on either technology or a vendor. Workflow and follwing (and sometimes defining) best practices are another place for improvement. For those of us that love defining practices and streamlining workflow, the bottleneck created by rigid technology platorms and/or incompetant vendors is maddening. A solution: dynamic content management.
Dynamic — i.e. database-centric — development has been around for years. While I was working on various projects, I wanted a way to automate the development. It was out of touch until a year ago. In the throws of a difficult period in my career (another story), I crafted a dynamic CMS; one capable of responding to any request, in particular 80% of the issues that come up in a given project. This sat idle for some time, until earlier this week a meeting with a new vendor got the gears going.
What’s next? I’m going to use the cms platform for a project at my firm, and if I’m lucky, can perhaps find someone to assist in the productization. I know it could make life easier — and make some nice cash at the same time. Watch for more!
0 Responses to “Improving Responsiveness with Dynamic Content Management”