News for hackers. Stuff that matters.
Re:Why We Hire Great Developers, Not Great Mobile Developers by dozzie on Monday January 11, 2016 @05:11AM (#10879927)
Also, most of mobile development seems to be writing another UI for sensors or SQLite database, or sometimes another game like the plenty out there. Why would anybody think of that as exciting?
Re:Why We Hire Great Developers, Not Great Mobile Developers by V-2 on Monday January 11, 2016 @05:13AM (#10879939)
Like your typical web app isn't yet another CRUD or CMS ;)
Re:Why We Hire Great Developers, Not Great Mobile Developers by alkonaut on Monday January 11, 2016 @06:17AM (#10880161)
> Like your typical web app isn't yet another CRUD or CMS ;)

Indeed. To avoid the CRUD groundhog day, I'd stay away from both web and mobile.

Re:Why We Hire Great Developers, Not Great Mobile Developers by V-2 on Monday January 11, 2016 @06:54AM (#10880266)
What do you do then?
Re:Why We Hire Great Developers, Not Great Mobile Developers by alkonaut on Monday January 11, 2016 @07:43AM (#10880456)
There are tons and tons of areas in software that aren't web (or mobile, which is usually just web with another toolkit).

Games, Desktop apps, Industrial, embedded, ...

Personally I do desktop applications and love it.

Re:Why We Hire Great Developers, Not Great Mobile Developers by V-2 on Monday January 11, 2016 @09:07AM (#10880789)
Yeah I did desktop apps for a while (in .NET), but they can be just as repetitive and non-inventive. In my case they were mostly shelf-stacking / syncing apps for internet shops.

I simply don't believe that a domain (understood broadly, ie. desktop/mobile/web) in and of itself dictates whether projects are original and interesting.

Not until you work on something really specialized, like AI etc.

Re:Why We Hire Great Developers, Not Great Mobile Developers by alkonaut on Monday January 11, 2016 @01:32PM (#10882168)
Yeah, so long as a desktop app could have been a browser app, it tends to have the same problems as a browser app (i.e it's just CRUD).

They are usually only interesting if they are desktop apps because they have to, like image editors, games, CAD.

My test for interesting work is the fraction of lines of code that relates to processing data and not just input/presentation/persistence/validation.

Re:Why We Hire Great Developers, Not Great Mobile Developers by dozzie on Monday January 11, 2016 @05:23AM (#10879965)
Good point; I noticed that, too. Especially when it's RESTful. People seem to have forgotten about RPC protocols, where it's operation, not a resource, that is most important.

Personally, my typical web app is not CRUD, it's merely an R. And I don't write those daily. Much more often I write network or system daemons.

Re:Why We Hire Great Developers, Not Great Mobile Developers by castell on Monday January 11, 2016 @06:24AM (#10880180)
Complex protocols will bite you. All these over engineered XML based protocols...

That's why REST and JSON are great. Very simple and perfect for many web use cases.

Re:Why We Hire Great Developers, Not Great Mobile Developers by dozzie on Monday January 11, 2016 @07:32AM (#10880397)
REST is a shitty abstraction. If you happen to need to do anything with a resource, you suddenly need to reinvent RPC, except that error reporting will not be standarized and most probably will cram two different levels (transport and procedure execution) together.
Re:Why We Hire Great Developers, Not Great Mobile Developers by s73v3r on Monday January 11, 2016 @01:16PM (#10882046)
I dunno, why would anyone think of the stuff you write as exciting?

Other people have different definitions for "exciting". Don't knock someone else's idea of it just because you don't agree with it.

Re:Why We Hire Great Developers, Not Great Mobile Developers by smt88 on Monday January 11, 2016 @02:50PM (#10882854)
I used the word "personally" to clarify that I was expressing my own preference and not making an absolute generalization.

What I generally do is write web apps, and much of my enjoyment comes from figuring out how to creatively use other people's libraries and to write very DRY code.

The libraries I use abstract browser fragmentation away from my presentation layer, so I don't have to do endless run-debug-fix loops on the front end.

At this point, the code I write for each new project is 90%+ unique to the project and very thin, so I get to do the fun part of releasing and iterating it.

Re:Why We Hire Great Developers, Not Great Mobile Developers by s73v3r on Tuesday January 12, 2016 @12:26PM (#10888771)
You're still crapping on other people's stuff. Honestly, what value did your original comment have other than to potentially make you feel better at the expense of others?