81 karma · joined January 5, 2010
So at least their unhappiness isn't limited by their genes?
What a trainwreck."
I find news about Nokia interesting, so thank you for posting this, but what is up with the tone of the article? It feels more like a youtube-comment than news.
After running into yet another bug in a new and shiny framework, costing me oh so much time, safe and dependable is starting to sound rather nice.If you always use cutting-edge do you really save time over using the tried and tested? A lot of time is lost due to having to learn new things, lack of documentation, lack of features and bugs. There is no absolute answer of course but it's a thing I think is important to keep in mind.
One solution is to move to a new area of software development that offers challenging problems.
I am currently, like many others it seems, working with creating enterprise CRUD-apps and integrating them. I try to find joy in reaching for a skill level where I can produce solutions quickly, solutions that are easy to change, solutions that immediately lets you know where and why an error has occurred, solutions that are secure, solutions that scale, solutions ran in the cloud instead of on servers that it takes it operations months to set up etc. There really aren't that many people out there that can do all of the above well (me included) and there are lots of money to be saved for your employee/clients doing those things well. I think we would see a lot less attempts at off-shoring if more people in enterprise-it would strive for that kind of knowledge.
I guess what I'm trying to say is, maybe one shouldn't have too high expectations of the technical challenges in problemscapes that have been mostly solved already but that, at least in my area, there are still challenges to be found. They are just of another kind and maybe you can find them interesting? They keep me interested enough at least.
sigh Why am I posting on hacker news again?
That quote made me chuckle since it just seems to be so out of context with what the article is trying to say.
Why not new buzzword instead of old buzzword?! At only a quarter of the cost! Seriously, if the development organisation is having problems creating CRUD-webapps maybe switching to "emerging tablets" is not the answer..
Anywho, my major use of jQuery is for dom parsing and manipulation. It's just so darn comfy! I still need to know javascript for all the rest of the stuff the app is supposed to do though.
Wikipedias definition of code smell:
"In computer programming, code smell is any symptom in the source code of a program that possibly indicates a deeper problem."
I don't see the deeper problems with the smells the article brings up and if there are any the article could've done a better job explaining them.