<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="FONT-SIZE:12pt;FONT-FAMILY:'Calibri';COLOR:#000000">
<div>Are you meaning that - what you said about revealing peoples thought
process in an interview illustrates it is not specific check boxes but again
something more intangible or qualitative or human quality that is the sought
after quality? Along with the required technical proficiency of
course.</div></div></div></div></blockquote><div><br></div><div>Definitely. The person has to fit into a team and be able to work within the team you have. The person might be the most highly skilled programmer but if you don't think they will fit in why hire them.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="FONT-SIZE:12pt;FONT-FAMILY:'Calibri';COLOR:#000000">
<div> </div>
<div>Specifics on what you said:</div>
<ul>
<li>Debugging on paper – now that takes me back! my first programming
job had just that – there were more programmers than screens and that’s what
we had to do. Useful to be able to do, and to be grateful you don’t have
to do it for day to day work.</li></ul></div></div></div></blockquote><div>It's about understanding how code flows in situations, because if you need to debug it to know where it goes, you will be less efficient designing and writing it in the first place.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="FONT-SIZE:12pt;FONT-FAMILY:'Calibri';COLOR:#000000"><ul><li><span style="font-size:12pt">Exception handling – is this also an area where opinions vary?
For instance I read that the NASA Shuttle programming team had to produce code
so reliable that it never threw exceptions, and the production version had all
exception handling turned off. (This being my side step)</span></li></ul></div></div></div></blockquote><div>Every code you write should be so reliable that it doesn't throw unhandled exceptions at the user. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="FONT-SIZE:12pt;FONT-FAMILY:'Calibri';COLOR:#000000"><ul><li><span style="font-size:12pt">Any more examples of the sorts of questions you ask?</span><br>
</li><li>The original question – what is the difference between people who think
they are good and those who are good? Is there an answer? or is there an
answer only for a particular workplace and job?</li></ul></div></div></div></blockquote><div>When they say all the right things but when you get the test back or ask the verbal questions and they are found out of their depth. When things on the resume don't match the things you are hearing. When you rely on the generated code or don't know how to debug into the source. When you give them an offer and they ask for a lot more money than you think they are worth.</div>
<div><br></div><div>One issue with the money thing, is the often people get paid overs at a previous company for numerous reasons.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div dir="ltr"><div style="FONT-SIZE:12pt;FONT-FAMILY:'Calibri';COLOR:#000000"><ul><li><span style="font-size:12pt">Right back to the original question specifically – is there a
shortage for essential Delphi skills in NZ compared to Oz and
Switzerland? What is lacking – training/size of talent
pool/non-intellectual focussed culture/lack of or quality of IT industry
training/Delphi community being less lively etc?</span></li></ul></div></div></div></blockquote><div>There is a lack of developers here. The ones that are more senior are happy in their current roles. Many have moved one to other languages or into management. Which is what I've been doing recently as well, but I still enjoy writing code. Also a lot of developers seem to come from one or two people teams that do everything, so introducing them to procedures, peer review, source control can be an interesting experience :-)</div>
</div></div></div>