The last time I did any interviewing for developers, we ended up with some devs who really did not want to engage with WO on any level, no matter how they came across in the interview. Years of complaining about WO, misusing it in ways which hurt the performance of the system (as the last remaining experienced WO developer I often ended up wading in to sort it out) and then blaming it on WO without having made the least attempt to learn it properly...
If you hire good people they'll be willing to learn and engage with new things, but obviously that's easier said than done (and usually more expensive, too). I think our mistake was taking on experienced JEE types who have all the certs under the Sun, whereas what we perhaps should have been looking for are people with a variety of technologies under their belts. If I were looking right now and couldn't find someone with WO, I think I would look for some Java experience, some non-Java experience, and definitely some iOS experience. The latter might make people more open to Apple's favoured design patterns, and CoreData experience can't hurt.
Sadly, I am no longer using WO professionally and only maintain an interest for a side project. As for what happened on my last team, the new devs got their way and the system was ported to Hibernate. Amusingly, this is still not in production 8 months after it was declared complete because they have been unable to match the performance of the (still in production) WO version! Last I heard they were going to go cap in hand to our (internal) clients and explain that yes, it's going to be slower, but at least it's easier to hire new developers (if they had the cash to hire new developers)...
On 24 Sep 2011, at 19:38, Marius Soutier wrote:
> Hi there,
> I know this a difficult and opinionated topic, but I have been asked by a friend what technology to choose for a Lean Startup (= 3 months until the first minimum viable product). While he and I know WebObjects quite well, I think it's safe to say there are only few people here in Germany who know it at all. I'm personally convinced (and have seen this affirmed by the two WOWODC talks about Lean Startup and Fluffy Bunny, excellent talks by the way) that WO itself is a great technology to get things up and running very fast. However, what if the business grows and he needs to hire more people?
> My first question is - do you easily find skilled people who are willing to learn WebObjects? What's your experience on this?
> And the second question would be - how long does it take them to be productive, i.e. write working code without much help. I'm assuming here the person knows Java quite well and is eager to learn new stuff.
> The alternative would be Ruby on Rails, which seems quite popular in startups nowadays.
> Thanks for your insight!
> - Marius
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> This email sent to email@hidden
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden