Need to hire someone

[BrilloPad]

Core Skills:

Java. Web Services. XML. Modern development practices (CI, TDD etc). Good design & problem solving skills.

Technical interview question #1:

You have a tree data structure that you need process, doing something different with each leaf in turn, and collating the results into another parallel tree. How would you go about that?

There is a question #2 for people who do well on #1.

You are asking the wrong question. Try "can you give an example where you have bribed the interviewer to get a role?".

[DimPrawn]

Well this is pretty much the first thing the guy who gets the gig is going to be working on, so it seems to prudent to ask how he'd go about it.

Can I ask how you end up with a system that relies on generating code at runtime driven by XML, with no schema support?

What in the business drives this requirement?

Sounds like a debugging/maintenance nighmare...

[aussielong]

I can now see why you lot are contractors. You have no choice. Too long in the tooth to get permie growth roles. Not big picture enough to get senior permie roles.

[EternalOptimist]

I can now see why you lot are contractors. You have no choice. Too long in the tooth to get permie growth roles. Not big picture enough to get senior permie roles.

pipe down, Im watching the ashes

[DimPrawn]

I can now see why you lot are contractors. You have no choice. Too long in the tooth to get permie growth roles. Not big picture enough to get senior permie roles.

It's a terrible price we pay, pocketing a six figure income for 30 years and then putting our feet up.

[tranceporter]

Anything that relies on reflection to emit types at runtime is going to be a maintenance nightmare in any case, because you cannot see what you are coding. It will just be a code with lots of GetType(), GetProperties(), GetBindingFlags() and the likes.

[fullyautomatix]

Anything that relies on reflection to emit types at runtime is going to be a maintenance nightmare in any case, because you cannot see what you are coding. It will just be a code with lots of GetType(), GetProperties(), GetBindingFlags() and the likes.

Only if Bobs code it, properly coded its actually maintainable. I just would not be able to do my work without reflection.

[minestrone]

Can I ask how you end up with a system that relies on generating code at runtime driven by XML, with no schema support?

What in the business drives this requirement?

Sounds like a debugging/maintenance nighmare...

A BA got me into a conversation last year asking if it was possible for a current production application to start creating tables, rows and then populate the tables with data as and when required.

It was battulip crazy ideas like that caused skynet to become aware.

[minestrone]

Worked on a few generic data applications, they usually start off quite innocent and well meaning but at some point people start concrete coding in the generic types ( usually quick hacks "For the business" ) then all hell breaks loose.

[doodab]

Can I ask how you end up with a system that relies on generating code at runtime driven by XML, with no schema support?

By hiring people who think that is a good idea. We didn't, so that isn't how we solved that particular problem.

What in the business drives this requirement?

Our customers want to be able to integrate our products with their other systems without the cost and complexity of coding from scratch. We will generally have schemas, but requiring our customers to preprocess them, compile, deploy the resulting code & glue it all together isn't an option.