FitNesse Refactorings
Posted by Lars Vonk mid-afternoon: August 25th, 2007
Podcast Episode 10 online: EJAPP Performance Top 10, 2 and 1
Posted by Robert van Loghem mid-morning: August 17th, 2007
Yes we have finally reached to numbers 2 and 1 in this Performance Top 10 by Vincent Partington and Jeroen Borgers.
Discussed are numbers 2-Unnecessary remoting.
More information about number 2 can be found here.
and for number 1-Incorrect database usage see; here.
So download the podcast here or better yet! subscribe to one of our rss feeds on podcast.xebia.com
If it looks like XML…
Posted by Jeroen van Erp in the early morning: August 17th, 2007
And walks and talks like XML, it surely must be XML. Yes, well how wrong you can be about assumptions is once more shown in this blog.
One of our clients has an application through which videos are streamed. They do this by providing a browser embedded player, or your stand-alone Windows Media Player with an ASX file. The ASX file tends to look like this:
<asx Version="3"> <entry> <ref HREF="http://www.somecompany.com/videos/video.wmv"/> </entry> </asx>
Best of Xebia tech list August 2007: Magic number 28232
Posted by Erwin van der Koogh around lunchtime: August 15th, 2007
We have had a number of very interesting discussions on our techlist in the last week or so, so I thought it best to get started as soon as possible. The reason I choose this particular thread is that it is a very technical thread, but it's very hard to find any information about it online. Oh, and it's not about Java or Agile for a change!
This thread quickly rose to about 20 mails, so I have made a selection to keep it readable. (more...)
Hastily urgency is hardly ever right
Posted by Erwin van der Koogh in the wee hours: August 15th, 2007
Oh yes, I remember why you should never directly translate sayings from one language to another. The non-Dutch speakers will have to take my word for it that "Haastige spoed is zelden goed" has a lot better ring to it. The meaning of the saying is fairly obvious of course "Don't rush things, they usually come back to haunt you."
We all know this and it's even more true in IT, where small mistakes can have dire consequences. But we too often fall for it because with today's complex systems it is hard to oversee what can go wrong. And it is even harder to estimate what it will cost you if things do go wrong. I would like to share a case with you in which I will explain what went wrong and try to give an overview at what it has cost us and our client. (more...)
Scrum resourcing woes
Posted by Cesario Ramos at around evening time: August 14th, 2007
I ran into some interesting problems when implementing some Scrummaging practices. One problem that I faced had to do with idle time of projects members.
The company I'm currently working for does its projects using the waterfall approach. The structure of the company supports the waterfall, the way of working of
the individual departments, their geographical locations, the strict separation of roles etc are all optimized for the 'throw over the wall' culture.
After some evangelism some managers got convinced to give Scrum a try on their projects. The projects had started about a year ago, but in that year they
had been working on architecture and requirement documents. So everything up till now was waterfall oriented. Funding was 'fixed', functionality was 'fixed', release date was 'fixed' etc. Now that we had the architecture and requirements we 'only' needed to build the system.
New! Video Podcast Episode 1 – Eclipse Tips; Links directory
Posted by Robert van Loghem in the late afternoon: August 8th, 2007
Well we have a new addition to our podcasts! Video! and we start off with Serge giving you an Eclipse tip; Links directory.
Serge shows how to use a "links directory" in Eclipse and how to easily manage plugins across installations.
So head on over to our podcast page here or download or subscribe to our new podcast.xebia.com.
Best of Xebia tech list July 2007: Accuracy of System.getCurrentTimeMillis()
Posted by Erwin van der Koogh in the early afternoon: August 3rd, 2007
At Xebia we have an internal mailing list where a lot of interesting technical discussions take place. Because we have a passion for knowledge sharing, we thought we'd give you a glimpse of some recent topics. This is the first of a series we plan to do.
We choose this particular mail thread because it answers a technical question a lot of people might have. And it also introduces a little known feature of Java 5.
| From | Jan Vermeir |
|---|---|
| Subject | Accuracy of System.getCurrentTimeMillis() |
| Date | Mon 23/07/2007 15:51 |
|
Hi, we're measuring elapsed time for processing a message. each measured operation takes a couple of milliseconds, so I was wondering what the accuracy of System.getCurrentTimeMillis() is. I have some vague recollection about accuracy not actually being milliseconds, as the name would suggest, and that it may vary with platform and JVM vendor. Does anyone know for sure? Jan. |
|
Archives
Xebia Sites
Categories
- Java (282)
- Agile (109)
- General (50)
- Testing (42)
- Performance (42)
- Hibernate (36)
- Scrum (33)
- Podcast (31)
- Architecture (31)
- Spring (28)
- SOA (24)
- Maven (22)
- Project Management (22)
- Middleware (23)
- Deployment (14)
- Flex (17)
- JPA (17)
- Eclipse (15)
- Xebia Labs (15)
- Quality Assurance (14)