Well, some practical points:
- if the Java developer understands that all stuff (data DML, validation and retrieval and all business logic imaginable and doable in a real time in the database engine) must be in the stored procedures and just GUI can reside in Java then hire him as soon as possible.
The point is that GUI stuff has already changed many times (AWT, Swing, Struts, JFC, Java Script(countless versions), DHTML(countless versions), XMl+XSLT, .NET 1, .NET nn - what´s next?) while Oracle PL/SQL still compiles and runs - a truly platform independant ADA inspired computer language. There are more points in favour of pl/sql but the above is supreme.
- if Java developer happened to model with Oracle Case Designer, have red Oracle Case Method or anything compatible from another vendor - hire him.
- if he is not so much Java but was successfull in coding web application in any other language like ASP, PHP, even Oracle´s mod_plsql then he most probably knows how to architect. That´s good, very good.
You may ask some detailed GUI stuff:
- does he know lookup tables happen to exist? Does he know that lookup tables is about the pair <id, name>? Does he know that the parent table contains just lookup id but not the name? May be he is even going to code or use some generic modules for lookup GUI controls like combobox, listbox, ListOfValues window, radio buttons, etc?
- is he going to use some generic modules(well, classes or wizards, whatever) for date, datetime, timestamp GUI controls?
- the same for numbers entry GUI controls?
That's basically all for GUI to know: lookups, date, numbers.
Next level:
master-detail form. As I have told already he must know how to code dept-emp or order-item master-detail entry form for example. Both in web and rich-client.
Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jan 08 2007 - 16:39:40 CST
