3 ms·
The above comment describes everything I work with on a day to day basis at my job. Every solution contains multiple layers of abstraction from the aspx to the
by boyter 16y ago
The above comment describes everything I work with on a day to day basis at my job. Every solution contains multiple layers of abstraction from the aspx to the code behind, to a controller to multiple services to multiple daos and with all of them implementing something to allow for testing.
Except very little is tested (its getting better) and everything is so tightly coupled it dosnt make a difference anyway.
- arethuza 16y agoI once had to try and salvage something useful from a huge J2EE application where the development team were obviously as they say "taking the p*ss". At one point I counted 23 layers of abstraction between the fairly simple JSP page through EJBs and a connector to eventually make a simple SOAP call to get the data to go on the page. Everyone of those layers had an interface, a factory and an implementation....
- arethuza 16y agoSome of the source code was missing too - so I had to decompile great chunks of stuff and wade through the resulting code to find out what was going on. Imagine my delight when I found multiple jar files, all with the same name but with different contents, all included in the classpath for WebSphere. Something like 98% of the code did nothing useful.