On 3/8/2012 12:29 PM, Brian Conrad wrote:
On 03/08/2012 08:43 AM, Chris Stratton wrote:
On Thursday, March 8, 2012 10:36:37 AM UTC-5, Veronica wrote:
I am working on hiring developers who have experience in Android
development. I'm finding it a challenge. I understand that's a
relatively new technology so the employee pool is still growing.
Unless you are in a situation where in addition to project time frames
being extremely short, the period of product lifetime during which code
must be maintained, supported, and potentially improved is also quite
short, then it really makes sense to search for those with software
engineering skills, rather than than focus on the specific target
technology. It's true that every platform and language has its
quirks and
thus learning curve, but its also true that most of the architectural
and
implementation mistakes which create schedule and reliability nightmares
are "old" ones which have been made many times before in many preceding
technologies.
Reminds me of the days in the mid-90s where companies were asking for
5 years of Java programming experience when Java had only been around
3 years. :D
I remember those days and I'm seeing similar ads for Android developers
now. Shows a disconnect somewhere between HR departments and engineering.
I'm a greybeard developer learning Android and finding it a comfortable
platform. most of the learning issues I'm having are related to UI and
graphics, but that is consistent with my background as a server guy more
than a UI guy.
Oh, I'm in the DC area and looking for a gig.
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
