OT: Frustated hiring here

[meadandale]

BTW, there are some weird things with Android and the G1 that you don’t discover when you are on the emulator but cause great pains when you deploy to the real phone…they’ve bit a few of my colleagues :-0

Like, your app starts and you show a login page and everything looks fine. Using the emulator, you enter your credentials with the keyboard. You don’t realize that on the real phone you have to slide open the keyboard and the screen rotates..now your nice UI not so nice anymore…funny stuff.

[meadandale]

[quote=sdcellar]In my personal experiece, it’s been challenging to find truly talented developers for some time now and I don’t expect that the larger candidate pool that exists as a result of layoffs has done much to improve upon that.[/quote]

It’s been that way for years in SD. As recently as 2005 I was interviewing people and would get flooded with resumes. 90% of them couldn’t pass a basic phone screen dealing with some very basic java, web development and network programming questions that virtually any developer with more than 3 years of experience in the enterprise development domain should be able to answer. All of them thought they were rockstars…

And, btw, I vetted the phone screen with some of my colleagues who are truly good senior developers and none of them had a problem with the questions.

It’s like you’ve heard in one way or the other, the candidate pool you are choosing from when you are trying to fill an opening aren’t the cream of the crop. Those people already have jobs or, if they find themselves out of work, quickly find new ones.

[meadandale]

[quote=sdcellar]In my personal experiece, it’s been challenging to find truly talented developers for some time now and I don’t expect that the larger candidate pool that exists as a result of layoffs has done much to improve upon that.[/quote]

It’s been that way for years in SD. As recently as 2005 I was interviewing people and would get flooded with resumes. 90% of them couldn’t pass a basic phone screen dealing with some very basic java, web development and network programming questions that virtually any developer with more than 3 years of experience in the enterprise development domain should be able to answer. All of them thought they were rockstars…

And, btw, I vetted the phone screen with some of my colleagues who are truly good senior developers and none of them had a problem with the questions.

It’s like you’ve heard in one way or the other, the candidate pool you are choosing from when you are trying to fill an opening aren’t the cream of the crop. Those people already have jobs or, if they find themselves out of work, quickly find new ones.

[meadandale]

[quote=sdcellar]In my personal experiece, it’s been challenging to find truly talented developers for some time now and I don’t expect that the larger candidate pool that exists as a result of layoffs has done much to improve upon that.[/quote]

It’s been that way for years in SD. As recently as 2005 I was interviewing people and would get flooded with resumes. 90% of them couldn’t pass a basic phone screen dealing with some very basic java, web development and network programming questions that virtually any developer with more than 3 years of experience in the enterprise development domain should be able to answer. All of them thought they were rockstars…

And, btw, I vetted the phone screen with some of my colleagues who are truly good senior developers and none of them had a problem with the questions.

It’s like you’ve heard in one way or the other, the candidate pool you are choosing from when you are trying to fill an opening aren’t the cream of the crop. Those people already have jobs or, if they find themselves out of work, quickly find new ones.

[meadandale]

[quote=sdcellar]In my personal experiece, it’s been challenging to find truly talented developers for some time now and I don’t expect that the larger candidate pool that exists as a result of layoffs has done much to improve upon that.[/quote]

It’s been that way for years in SD. As recently as 2005 I was interviewing people and would get flooded with resumes. 90% of them couldn’t pass a basic phone screen dealing with some very basic java, web development and network programming questions that virtually any developer with more than 3 years of experience in the enterprise development domain should be able to answer. All of them thought they were rockstars…

And, btw, I vetted the phone screen with some of my colleagues who are truly good senior developers and none of them had a problem with the questions.

It’s like you’ve heard in one way or the other, the candidate pool you are choosing from when you are trying to fill an opening aren’t the cream of the crop. Those people already have jobs or, if they find themselves out of work, quickly find new ones.

[meadandale]

[quote=sdcellar]In my personal experiece, it’s been challenging to find truly talented developers for some time now and I don’t expect that the larger candidate pool that exists as a result of layoffs has done much to improve upon that.[/quote]

It’s been that way for years in SD. As recently as 2005 I was interviewing people and would get flooded with resumes. 90% of them couldn’t pass a basic phone screen dealing with some very basic java, web development and network programming questions that virtually any developer with more than 3 years of experience in the enterprise development domain should be able to answer. All of them thought they were rockstars…

And, btw, I vetted the phone screen with some of my colleagues who are truly good senior developers and none of them had a problem with the questions.

It’s like you’ve heard in one way or the other, the candidate pool you are choosing from when you are trying to fill an opening aren’t the cream of the crop. Those people already have jobs or, if they find themselves out of work, quickly find new ones.

[sdcellar]

[quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit]

[sdcellar]

[quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit]

[sdcellar]

[quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit]

[sdcellar]

[quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit]

[sdcellar]

[quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit]

[meadandale]

[quote=sdcellar][quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit][/quote]

I did quite a bit of work on sony ericsson handsets with J2ME…and you only found out about the device idiosyncrasies when you put the phone on the actual device; the emulators would run the app fine.

I’m talking screen resolution, UI widget placement, color, memory…everything looks slightly different when it is on an actual phone. A real device has to be part of your development loop because if you wait until you are about to release to just ‘check it out on a real phone’ it will be the last time you ever make that decision 😉

Not to mention that some phone’s have firmware bugs (this was very common in the J2ME space where each phone would have a hand rolled JRE) that you’d never find on the emulator..only when your app was running in QA…

[meadandale]

[quote=sdcellar][quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit][/quote]

I did quite a bit of work on sony ericsson handsets with J2ME…and you only found out about the device idiosyncrasies when you put the phone on the actual device; the emulators would run the app fine.

I’m talking screen resolution, UI widget placement, color, memory…everything looks slightly different when it is on an actual phone. A real device has to be part of your development loop because if you wait until you are about to release to just ‘check it out on a real phone’ it will be the last time you ever make that decision 😉

Not to mention that some phone’s have firmware bugs (this was very common in the J2ME space where each phone would have a hand rolled JRE) that you’d never find on the emulator..only when your app was running in QA…

[meadandale]

[quote=sdcellar][quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit][/quote]

I did quite a bit of work on sony ericsson handsets with J2ME…and you only found out about the device idiosyncrasies when you put the phone on the actual device; the emulators would run the app fine.

I’m talking screen resolution, UI widget placement, color, memory…everything looks slightly different when it is on an actual phone. A real device has to be part of your development loop because if you wait until you are about to release to just ‘check it out on a real phone’ it will be the last time you ever make that decision 😉

Not to mention that some phone’s have firmware bugs (this was very common in the J2ME space where each phone would have a hand rolled JRE) that you’d never find on the emulator..only when your app was running in QA…

[meadandale]

[quote=sdcellar][quote=meadandale]Don’t get me wrong, I’m always learning a few new things here and there (I read alot) but going full bore into doing phone development on a new platform requires an investment in equipment (you need at least one phone to develop to) and quite a bit of time.[/quote]A real handset, er phone, is nice at some point, but the majority of your work can (and should) be done with an emulator.

[edit]Never mind. Just read your follow-up post on emulators, and yeah, a real phone is key at some point.[/edit][/quote]

I did quite a bit of work on sony ericsson handsets with J2ME…and you only found out about the device idiosyncrasies when you put the phone on the actual device; the emulators would run the app fine.

I’m talking screen resolution, UI widget placement, color, memory…everything looks slightly different when it is on an actual phone. A real device has to be part of your development loop because if you wait until you are about to release to just ‘check it out on a real phone’ it will be the last time you ever make that decision 😉

Not to mention that some phone’s have firmware bugs (this was very common in the J2ME space where each phone would have a hand rolled JRE) that you’d never find on the emulator..only when your app was running in QA…

[Author]

Posts