<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Meeting deadlines in itself is a very bad measure. Too often have I
seen people "Meet the deadline" but the cost of ownership because 4
times what it should have because of implementation. It's good to have
someone that can assess the time of a job based on their own
limitations, (and be accurate to +/- 25% :D )<br>
<br>
Everyone has different styles of development. Neven has his own
framework, I also have a framework for my applications, and many
others. When hiring anyone I would be looking for people that can
follow instructions well, don't go off on a tangent, and code
consistently to the standard requested by the employer (including
syntax layout, as well as just how to do the job) I would also be
wanting staff that can see the potential pit falls of a design and
offer suggestions to improve or enhance the work they should be doing
(This is different from the employee "knowing" his way is better and
doing it without telling, which ends up costing lots of money later),
ie Forward Thinking rather than a human typewriter with Delphi Syntax
skills. <br>
<br>
Lastly, someone who doesn't leave the job deciding that all the ideas
you left him with would be a great idea for a new competing product :)<br>
<br>
David Brennan wrote:
<blockquote cite="mid20050715040437.A703BAE3CC@smtp-3.paradise.net.nz"
type="cite">
<pre wrap="">What do you mean?
An excellent programmer = 2.5 good programmers = 10 mediocre programmers =
infinite number of poor programmers
Something like that? Or are you meaning how do you identify a good
programmer?
-----Original Message-----
Secondly, how do employers rate a good programmer?
David O'Brien
(<a class="moz-txt-link-abbreviated" href="mailto:dave@iccs.co.nz">dave@iccs.co.nz</a>)
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:delphi-bounces@ns3.123.co.nz">delphi-bounces@ns3.123.co.nz</a> [<a class="moz-txt-link-freetext" href="mailto:delphi-bounces@ns3.123.co.nz">mailto:delphi-bounces@ns3.123.co.nz</a>] On
Behalf Of Neven MacEwan
Sent: Friday, 15 July 2005 2:07 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Skill shortage?
David
This is exactly my point, .Net was a reaction to Java, XAML is reactive
to XUL, Freedom to inovate, bullshit, I also find in hilarious that
people who buy into the M$ justify it on the consistency of supply where
recent history would indicate the opposite
What I love about OS dev products is changes are total demand driven
with no subtext
n
David Brennan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">It is a danger with .NET. Compare with Internet Explorer. IE got mega
</pre>
</blockquote>
<pre wrap=""><!---->bucks
</pre>
<blockquote type="cite">
<pre wrap="">thrown at it by Microsoft because they perceived a threat that Netscape
could eventually provide an alternative to the Windows platform by having
</pre>
</blockquote>
<pre wrap=""><!---->a
</pre>
<blockquote type="cite">
<pre wrap="">multi-platform rich interface web browser.
Once Microsoft had strangled Netscape and ensure market dominance they
suddenly killed IE development. Almost all of the new technologies which
</pre>
</blockquote>
<pre wrap=""><!---->had
</pre>
<blockquote type="cite">
<pre wrap="">been under development for a richer browser environment were effectively
</pre>
</blockquote>
<pre wrap=""><!---->put
</pre>
<blockquote type="cite">
<pre wrap="">on hold at the same time... which was probably Microsoft's plan from the
start.
I see some parallels here. Java was getting too much popularity behind it
and it's cross platform nature and rich interface potential was/is a
</pre>
</blockquote>
<pre wrap=""><!---->serious
</pre>
<blockquote type="cite">
<pre wrap="">threat. So .NET is unleashed upon the world.
The difference is that Java isn't likely to die like Netscape did. So
Microsoft may end up having to push .NET as their long term solution
</pre>
</blockquote>
<pre wrap=""><!---->rather
</pre>
<blockquote type="cite">
<pre wrap="">than just using it for a single battle. Only time will tell I guess.
David.-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:delphi-bounces@ns3.123.co.nz">delphi-bounces@ns3.123.co.nz</a> [<a class="moz-txt-link-freetext" href="mailto:delphi-bounces@ns3.123.co.nz">mailto:delphi-bounces@ns3.123.co.nz</a>]
</pre>
</blockquote>
<pre wrap=""><!---->On
</pre>
<blockquote type="cite">
<pre wrap="">Behalf Of Neven MacEwan
Sent: Friday, 15 July 2005 1:06 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Skill shortage?
RE:
</pre>
<blockquote type="cite">
<pre wrap="">There are some big shops still using as far as I can tell, but a lot have
moved to .NET over the last 2 years.
</pre>
</blockquote>
<pre wrap="">
Now that M$ have sucessfully used .net to restrict Java in the
middleware area, will they focus on the UI again and push XAML
In which case these guys will have to move again
bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah,
bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah,
bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah,
bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah, bah,
bah, bah, bah, bah, bah, bah, bah, bah, bah, bah..
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>