For one the plastic casing was as cheap as you can get. I dropped my phone once while getting out of my car less then a foot off the ground and the thing looked like I threw it against the wall.
Second the gps did not work, this was not an uncommon issue, so uncommon that T-Mobile replaced my phone no questions asked for a G2.
Third the software they put on the phone, while not an issue for this phone, was slow, buggy and hard crashed my phone at least once a week. This coming from the G1, running community build roms, which hard crashed maybe twice in the 2 years I owned it.
Thats interesting the Nexus S has the same issue. And while this fix put a band-aid on the problem it in no way fixed the issue at all. And sometimes it actually made it worse.
"Microsoft does great things, but it’s become safe and dependable rather than exciting and risky."
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.
I doubt it. Maybe facebook will be worth more on paper, for a short period of time but Google provides a far far more valuable service and I think that will show in the end.
What public are we talking about? I don't think Apple are considered to be a big bad bad corporation outside of developer circles. On the other hand there have been news reports about how much Google knows about you etc. here in Sweden.
That game looks awesome but I found it rather amusing that the video shows the "hero" stalking a creature through the forest and into his home and then killing him for no apparent reason? Seems like a dick move to me.
It seems the author of the article is stuck in a problemscape where all the problems he would find interesting are already solved.
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.
"Primarily, I asked him why he didn't transition from building web apps to instead creating a solution using cloud technology and true mobile devices like BlackBerrys, iPods, and emerging tablets. He could offer a better solution, at about a quarter of the cost. "
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..
As an inexperienced jQuery user I expected more from the article. I have nothing against the author having issues with style but don't call them code smells.
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.
Yeah I hear you. But to be fair, if anyone uses jQuery to do a select that requires a lot of dom parsing in a loop, is jQuery really to blame? Even I avoid that and I'm not a real programmer or anything..
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.
