|I have been asked to consult a company in how they should speed up their development process.|
Today the application which in the end of it all is a web application, consists of a lot of old ASP classic code, a COM+ bridge for being able to function within a mix of a lot of different .NET libraries written in .NET 3.5 (CLR 2). COM+ acts as a bridge between the two technologies.
The teams cannot compile code inside the development tools, it can't debug unless they do it with some obscure hacks and workarounds and it seems that no one is really in control of what is going on in the core code base and no one really want to touch the original code base to clean it up and refactor/re-write it.
My concerns are really rooted in different aspects of the project.
The project has been like this for multiple years, i mean, the ASP code base is around 10-13 years old. There is nothing wrong with old technology I think but building on top of it for over 10 years was probably not a great idea.
Then someone has tried to build a gap between ASP and ASP.NET and I assume this is because of business-needs and also no one really wanting to get their hands dirty with a refactoring.
Why would a business do this ? Keep patching and re-patching old code instead of cleaning up and making things smoother and safer.
Not to talk about the effeciency of developers and teams.
I am frustrated, only 3 weeks in, and I am obviously not the only on whom has tried to figure this out, but everyone has just given up and said "this is just how it is.".
Given those facts, would you engage or walk away ?
I just don't like to walk away, but this is basically a big mess which in turn runs a multi million dollars business.