When will people finally realize that defining and documenting practices alone doesn't make good code? You need good programmers that care and that monitor each others and (more junior) programmers' code quality. Encourage feedback between the programmers, etc.
I've been in consulting for over a decade, have seen this at almost every large company I've been in contact with. At varying degrees of course, from the mild annoyance with business to the total refusal to talk to the business side.
Funnily enough, the business side is usually the one with the funding, the tech side with attitude and trying to enforce questionable best-practices.
That sometimes leaves a consultant caught between scylla and charybdis;)
Of course there's a ton of "pretty" code out there.
Even though even great code bases can quickly turn into a mess by being maintained to hell by unsupervised maintenance programmers and lack of good programmers on the team. Let's be honest, maintenance is boring and which A+ programmer wants to do maintenance. And, let's not forget about stupid business decisions;-)
Maybe you need to just find a boutique consulting company or a product development company that honors tech skills!
If you do want to see great code, look at the code of the Spring framework sometimes!
Might as well go ahead and use JSPs, because they are more flexible than servlets when it comes to separating content and logic (unless you need to transfer binary data...). I would only recommend XML/XSL if the amount of data displayed is somewhat small. You can see your server grind to a halt when the DOM is built for big XML files to do the XSL transformation;)
When will people finally realize that defining and documenting practices alone doesn't make good code? You need good programmers that care and that monitor each others and (more junior) programmers' code quality. Encourage feedback between the programmers, etc.
I've been in consulting for over a decade, have seen this at almost every large company I've been in contact with. At varying degrees of course, from the mild annoyance with business to the total refusal to talk to the business side.
Funnily enough, the business side is usually the one with the funding, the tech side with attitude and trying to enforce questionable best-practices.
That sometimes leaves a consultant caught between scylla and charybdis ;)
Of course there's a ton of "pretty" code out there.
;-)
Even though even great code bases can quickly turn into a mess by being maintained to hell by unsupervised maintenance programmers and lack of good programmers on the team. Let's be honest, maintenance is boring and which A+ programmer wants to do maintenance. And, let's not forget about stupid business decisions
Maybe you need to just find a boutique consulting company or a product development company that honors tech skills!
If you do want to see great code, look at the code of the Spring framework sometimes!
- jz
Might as well go ahead and use JSPs, because they are more flexible than servlets when it comes to separating content and logic (unless you need to transfer binary data...). I would only recommend XML/XSL if the amount of data displayed is somewhat small. You can see your server grind to a halt when the DOM is built for big XML files to do the XSL transformation ;)