OK I had this post in my mind for a while now — the only reason I’m publishing it so late is because it started initially with just small nags in my head about server side developers and I thought at the time one small nag from me hardly constitutes enough reason for a post. Since then though I guess you could say I’ve got a few more “nags” to add, hence finally this post 🙂
So bearing in mind that like I said a lot of the “fancy” stuff is taken out of the language and you’re stuck with Java-like syntax, what is difficult to understand? The DOM/DHTML processing bits? Let’s see…
right? You mean you haven’t done any XML processing in the backend and never heard of the DOM and the W3C traversal functions? Because it’s exactly the same API!
As for CSS — coming from a language like C# or Java where everything is OOP and inheritance you cannot understand it? The whole idea of “cascade” really means “inheritance” as for the CSS properties, you can get them listed on tons of websites nowadays so shouldn’t be a problem understanding that.
So all in all, I don’t get it: if you are a backend developer why can’t you work front end or at least assist with debugging some frontend code? Is it not the case that those who take this approach are not actually developing anymore and instead are so stuck in a routine where they just apply “patterns” (be it for Spring, Struts, or any other framework) that taking them outside that set of patterns (hardly called development!) makes them totally useless? And if that’s the case should you not be worried, if you do have such “developers” in your team, that in fact you might be spending money on something that’s not there really?