With the skilled programmers becoming a rare commodity and uncontrolled growth of IT industry, there is a need to think differently. We now need to move from requirements based frameworks to skill-based frameworks. By skill-based frameworks I mean, designing the applications/frameworks in such a way that people with low skill levels are also able to develop the required applications. Yes, we have already been supporting programming languages like Java, various modern-day application servers, IDEs etc for the same reason. However, as the need for skilled people increases and we find there are lesser numbers available, we will have to keep moving to more encapsulation i.e. skill based frameworks.
So, in effect, what we are looking at is an additional parameter (skill level of people) for deciding the architecture and framework of an application, besides the usual thing (customer requirements). This is something that we might see in future.
However, the best way of achieving this would be to create 2 frameworks:
1) A customer-requirements-based framework
2) A developer-skill-based framework
So, the development happens using the developer-skill-based framework and you create a tool to directly convert the skill-based framework to the requirement based framework.
This is what I think is the future and the most realistic solution to the skill-shortage problem.
I will further elaborate on this in my future posts.
Any opinions on this are most welcome.
Tuesday, June 10, 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment