The most sound advise I’ve heard regarding hiring developers, which I’d consider solid even outside the realm of Apache Wicket development:
Don’t hire Wicket programmers. Hire good OO programmers with real domain problem analysis skills. ? Jonathan Locke
We are in the middle of replacing old Ajax favorite Dojo with Wicket Ajax in our application. The dojo parts are a left over from our pre Wicket 1.2 days when Ajax was still in its infancy. We still have some places where Dojo is used, and this time it triggered a bug. A co-worker said:
“I thought dojos were extinct” ? Sverre
The Wicket team announces the last maintenance release of Wicket 1.2: Wicket 1.2.7.
This release fixes the remaining issues for Wicket 1.2. For future support we ask you to upgrade to Apache Wicket 1.3 or newer.
This release of the Wicket project is not endorsed or approved by the Apache Software Foundation. The Apache Software Foundation is in no way affiliated with this release.
Below are the release notes for Wicket 1.2.7.
- the Wicket team
Ted talks are really astounding: in less than 20 minutes each talk knows how to captivate you and change your world view. Each talk I’ve seen so far was remarkable and a true addition to my life’s experiences.
But even this highest category of talks has differences in the way a talk grabs you. The talk by Jill Bolte Taylor about her stroke of insight was funny, informative and touching in a way you can’t imagine. In her talk she explains how the two halves of the human brain work. She even grosses out the audience by displaying a real human brain. This is remarkable in itself, but when she starts talking about her stroke, the talk begins to gain a life of its own.
The way Jill visualizes her experience really struck me. I urge you to see it for yourself, it is one of the most touching talks I have seen. Garr Reynolds from Presentation Zen describes the way how this talk affected him while he watched. It had the same effect on me:
“A bit unexpectedly, I was floored. In fact I was moved to tears, as was the packed TED theatre which gave her a huge standing ovation. Take some time today and watch this 18-minute TED presentation. This is such a wonderful talk.”
So take your 18 minutes and start watching now:
Debugging JavaScript is always a problem, but even more so in IE. Things should be better in IE8 but today my focus was on IE6. The tip of the day is: when IE shows an error during loading, it will provide you with a line number. You can look for hours at the line number and not figure out what it means and where the error happened.
I found out after much puzzling that IE will show the line number where the error happened from the file. So if you load foo.js and an exception occurs on line 731, IE will tell you only the line number. You have to find out for yourself which file is the cause. Oh, and you should subtract 1 from the line number.
Why is it impossible for IE engineers to provide helpful error messages? Is it so hard to actually show the filename as well?