A question for Java developers... how wide are your skills?

[swamp]

A good Java contract developer is one who gets his timesheet signed, who gets renewals and who gets rate rises.

The End.

There are people in this world who like to fanny around with decompiling class files and playing with stack traces. Good for them. But such things have no bearing on being a good Java contract developer.

[BarbarianAtTheDoor]

Yes, competence is the new incompetence, black is the new white and we've always been at war with Eurasia.

If I was interviewing you guys for a contract role, you wouldn't get the nod from me unless you can tell me precisely what the stack, the heap, the frame and signatures are. If you know these, you also understand bytecode. If you don't, you're a tulip developer.

[minestrone]

Yes, competence is the new incompetence, black is the new white and we've always been at war with Eurasia.

If I was interviewing you guys for a contract role, you wouldn't get the nod from me unless you can tell me precisely what the stack, the heap, the frame and signatures are. If you know these, you also understand bytecode. If you don't, you're a tulip developer.

You are my java hero.

[d000hg]

If I was interviewing you guys for a contract role, you wouldn't get the nod from me unless you can tell me precisely what the stack, the heap, the frame and signatures are. If you know these, you also understand bytecode. If you don't, you're a tulip developer.

Good luck then. You'll get people who can hack into the 'assembly' but don't understand 'new fangled' ideas like XML, design patterns, then... "I don't believe in unit tests. There are unlikely to be bugs".

Who is this BATD? I never saw him before this thread... is he a techy troll?

[Joe Bloque]

A good Java contract developer is one who gets his timesheet signed, who gets renewals and who gets rate rises.

The End.

There are people in this world who like to fanny around with decompiling class files and playing with stack traces. Good for them. But such things have no bearing on being a good Java contract developer.

WHS.

There are Java bods out there who have a different meaning alltogether for stack,heap, frame, thread etc and currently in contracts, raking in lots of dosh.

[nomadd]

If I was interviewing you guys for a contract role, you wouldn't get the nod from me unless you can tell me precisely what the stack, the heap, the frame and signatures are. If you know these, you also understand bytecode. If you don't, you're a tulip developer.

I've been developing software for 30 years. Started in assembler (Zilog Z80, MOS 6502/6510, Motorola 68000, etc.). I've about 30 years worth of C (and later C++), and I've a solid 10 years worth of Java - both core and EE. I've also a string of successful Java projects under my belt for some of the world's largest companies.

Therefore I have a question for you: Do you actually get any work done during the day, or do you just spend your time fanny'ing around like you listed above?

Nomadd

[minestrone]

Who is this BATD? I never saw him before this thread... is he a techy troll?

I think it is someone's long time sleeper sp.

[d000hg]

A good Java contract developer is one who gets his timesheet signed, who gets renewals and who gets rate rises.

The End.

I don't agree with that. There is such a thing as professional dignity in my book. I'm sure some contractors flit from contract to contract, getting paid until their lack of skills are discovered and they move elsewhere.

http://thedailywtf.com/Articles/Long..._0x24_ing.aspx
http://thedailywtf.com/articles/ill-be-back.aspx
http://thedailywtf.com/Articles/The_...aula_Bean.aspx

[thunderlizard]

A good Java contract developer is one who gets his timesheet signed, who gets renewals and who gets rate rises.

The End.

There are people in this world who like to fanny around with decompiling class files and playing with stack traces. Good for them. But such things have no bearing on being a good Java contract developer.

This is one argument that Plato puts into the mouth of Thrasymachus in Republic I. Socrates' response is that you need to separate off the Java developer's responsibility qua money-maker from his responsibility qua Java developer.
It makes for fine reading I assure you.

[nomadd]

This is one argument that Plato puts into the mouth of Thrasymachus in Republic I. Socrates' response is that you need to separate off the Java developer's responsibility qua money-maker from his responsibility qua Java developer.
It makes for fine reading I assure you.

Ah, Socrates. A contractors philosopher if ever there was one. An entire lifetime of work, none of which he ever committed to paper. Documentation? I don't do documentation - I'm a contractor!

Nomadd