I have been sifting through Chicago Android opportunities and wanted to share this little strange gem. I am keeping the firm name and person’s name undisclosed because it would somewhat be embarrassing to them but to say that this proves that the people who cannot code go into business management somewhat is an understatement.
Basically, we were discussing what the first steps of android developer executes in a new position and I brought up the fact that one obviously creates a utility library full of helper classes and UI widgets. The interviewer stated tha they do not do that as they want some UI widgets created via code and not xml. Now guess what basic java concept the interviewer does not get, and this folks is former java programmer doing the interviewing?
Well, by using method overriding one can have methods that create the UI widget via code and by xml in the same class. Not to mention that you can include such classes in an Android Project Library. Or even this gem of not understanding that the basic rule of not having non-UI stuff on UI threads all leads into why the Android Activity/Application life-cycle is the way it is as far as the difference between the Application context and the activity context.
MobileBytes 