> So here i [sic] was selling my self to a j2ee [sic] consulting company hoping they
> would hire me. And while i [sic] was lucky to hit the jackpot, meaning
[quoted text clipped - 3 lines]
> sql [sic] more then using a orm [sic] layer. You can imagine this was starting to
> look more like a battlefield then a job interview :)
I agree with some of what you say, with reservations.
> I could defend my self on all grounds except for two things
>
> 1) everybody is using struts and hibernate
Not everybody, and not always well, and never without difficulty.
The trouble is that people use these tools *without understanding the
paradigm* behind them. For Struts, it's the Model-View-Controller (MVC)
pattern. I've worked on teams where people knew the Struts API cold but
didn't understand the MVC architecture. Sad.
ORM layers are for people ign'ant of SQL. The new stuff, OTOH, with the Java
Persistence API (JPA) annotations, is actually useful. Try writing a good
data-access layer yourself; it's not trivial.
> 2) he said making a jndi [sic] connecting pool was slow.
Can he prove that? Has he ever measured it?
Somehow I doubt it.
> Can any one explain to me why jndi [sic]/jdbc [sic] is slow and whats the
> alternative ?
I'd be curious to know *if* it's "slow", what "slow" means in that context,
and compared to what. Somehow I doubt it.
It is not always good interview technique to inform the interviewer that he
has his head up his a.s, particularly if you prove it.

Signature
Lew
gert - 20 Oct 2007 20:38 GMT
> It is not always good interview technique to inform the interviewer that he
> has his head up his a.s, particularly if you prove it.
I brought some nuclear weapons of sample code to show him (expecting
FBI any minute now :)
Man, I suck at naming 3 positive and 3 negative points of my self. Who
likes to talk about himself anyway? Next time someone ask me, I am
going to answer: the positive thing is I like elephants and birds.
Negative thing is I don't like hot dogs.
In the end he still got me shot with AOP, because I never made
programs that where complex enough to make use of AOP or some advanced
annotations styles.
PS What time in English history did they decide to write I in
uppercase?
Lew - 21 Oct 2007 00:59 GMT
> PS What time in English history did they decide to write I in
> uppercase?
By the mid-thirteenth century certainly.
<http://dictionary.reference.com/browse/I> has it "bef. 900".

Signature
Lew
gert - 21 Oct 2007 02:33 GMT
> > PS What time in English history did they decide to write I in
> > uppercase?
>
> By the mid-thirteenth century certainly.
> <http://dictionary.reference.com/browse/I> has it "bef. 900".
And why didn't they write me like Me in mid-thirteenth old school?
Lew - 21 Oct 2007 03:34 GMT
>>> PS What time in English history did they decide to write I in
>>> uppercase?
Lew wrote:
>> By the mid-thirteenth century certainly.
>> <http://dictionary.reference.com/browse/I> has it "bef. 900".
> And why didn't they write me like Me in mid-thirteenth old school?
GIYF. That's how I found out the answer to your first question. How about
you do the research and tell us this time?
I suspect that ultimately the answer is, "Because language is a psycho-social
phenomenon, and people aren't utterly rational." I do think I remember
something about making it easier to read the word.
I'm not sure. Your research will get to the heart of it, of that I am sure.

Signature
Lew
gert - 21 Oct 2007 05:38 GMT
> >>> PS What time in English history did they decide to write I in
> >>> uppercase?
[quoted text clipped - 11 lines]
>
> I'm not sure. Your research will get to the heart of it, of that I am sure.
Yep i came to a conclusion Chines is the superior language for a java
programmer :)
http://www.apa.org/monitor/apr99/english.html
John W. Kennedy - 24 Oct 2007 22:52 GMT
>>> PS What time in English history did they decide to write I in
>>> uppercase?
>> By the mid-thirteenth century certainly.
>> <http://dictionary.reference.com/browse/I> has it "bef. 900".
>
> And why didn't they write me like Me in mid-thirteenth old school?
Because "i" is a little tiny letter that easily gets lost in
thirteenth-century handwriting. Simple as that.

Signature
John W. Kennedy
"Though a Rothschild you may be
In your own capacity,
As a Company you've come to utter sorrow--
But the Liquidators say,
'Never mind--you needn't pay,'
So you start another company to-morrow!"
-- Sir William S. Gilbert. "Utopia Limited"
Roedy Green - 21 Oct 2007 09:00 GMT
>PS What time in English history did they decide to write I in
>uppercase?
The Romans used all upper case. Some 7th century Celtic monks invented
lower case to speed transcription of books.
http://patentpending.blogs.com/patent_pending_blog/2005/07/lower_case_writ.html

Signature
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com
Roedy Green - 21 Oct 2007 09:04 GMT
>PS What time in English history did they decide to write I in
>uppercase?
Certainly when I started using computers, everything was all upper
case. In perhaps the mid seventies you could get lower case documents
printed by special request. They had to change the print band on the
printer which made it much slower.
I think in was around 1977 when personal computers and word processors
took off that lower case became ubiquitous. It came with dot matrix
and daisy wheel printers.
Mainframes flipped to laser printers, which made lower case feasible.

Signature
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com