Comments on: Most aggravating developer induced headaches for Middleware Administrators http://technology.amis.nl/2012/08/01/most-aggravating-developer-induced-headaches-for-middleware-administrators/?utm_source=rss&utm_medium=rss&utm_campaign=most-aggravating-developer-induced-headaches-for-middleware-administrators Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Andreas http://technology.amis.nl/2012/08/01/most-aggravating-developer-induced-headaches-for-middleware-administrators/#comment-7272 Andreas Fri, 17 Aug 2012 12:39:54 +0000 http://technology.amis.nl/?p=18714#comment-7272 Nice list – nicely long ;-)
However, you can’t blame developers alone. It’s also company policies, the lack of administrators to create appropriate guidelines, or the lack of communicating/gathering requirements within a project, or across them. Lust but not least: lack of time and money.

Also, the list would be of more help, if it was a guideline, instead of a bash-list. E.g. change “hard coded configuration stuff” in “Make settings (like …) configurable via an XML file that can be resolved via the classpath” (note that I’m quite specific with the file-format, the path and the kind of settings that should be configurable).

]]> By: Peter Brand http://technology.amis.nl/2012/08/01/most-aggravating-developer-induced-headaches-for-middleware-administrators/#comment-7270 Peter Brand Wed, 15 Aug 2012 12:02:46 +0000 http://technology.amis.nl/?p=18714#comment-7270 I think there is not much use in creating such a list – seems like trying to cure symptoms – the problem is so-called ‘middleware’ itself – in that it resides in the application layer on top of internet (technologically speaking) – but instead of providing a useful application it pretends to provide another layer – so-called ‘enabling technology’ – conceptually insane – will not survive

]]>