Great, two of my collegues at Computas and me got accepted each our talk for the JavaZone-conference in Oslo 8-9. september. The three of us will contribute with these presentations:
Geir A. Lund:
Erfaring med konvertering fra CVS til Mercurial i stort Javaprosjekt
Filip van Laenen:
Why We Should Start Tagging Our Code
Harald Søvik:
Enhance your Maven plugins with Groovy
Along with a small army of other experts and geeks, we will fill the venue with experience, knowledge and pure java-happiness for two entire days. Don't miss out on this event - it's probably the best java conference in this part of the galaxy :)
Sporadic rant on java, maven, enterprise application integration, patterns, testing, people, legacy, people and so forth. And some cooking.
fredag 2. juli 2010
onsdag 16. juni 2010
NDC2010 material
Here are some material that will be referred to in Mortens and my talk at NDC2010:
The slides for Modularization, testing and technical debt (in a large agile project) is available at http://www.slideshare.net/harals/modularization-testing-and-technical-debt-in-a-large-agile-project
A whitepaper on the same topic (from the proceedings of the XP2010-conference) can be found at http://www.slideshare.net/harals/cou
The slides for Modularization, testing and technical debt (in a large agile project) is available at http://www.slideshare.net/harals/modularization-testing-and-technical-debt-in-a-large-agile-project
A whitepaper on the same topic (from the proceedings of the XP2010-conference) can be found at http://www.slideshare.net/harals/cou
Etiketter:
cx,
modularization,
ndc2010,
scrum,
technical debt,
testing,
xp2010
tirsdag 25. mai 2010
XP2010 accept
The 11th International Conference on Agile Software Development is coming up (June 1-4 in Trondheim). Unfortunately, I will not be able to be there. But I have been authoring and co-authoring some material for the conference.
First, Morten's and my experience report "Tech Challenges in a Large-Scale Agile Project" was accepted, and will be both presented and included in the conference proceedings:
This experience reports focuses on the major technical challenges that arose during the project, especially those challenges that we think can be attributed to the SCRUM methodology. For each of them, we try to identify the consequence and the cause, and then follow up with any solutions we tried, and an analysis of whether the problem was successfully solved or not. The session paper lists three major examples of such problems.
Then, I got accepted a lightening talk as well: "Agile Methods may Discourage Quality". However, since I have to be attending a customer at the time, Morten will be presenting this instead of me.
Agile methods, and in particular scrum, have a very strong focus on productivity and immediate business value. The developers are encouraged to complete their tasks in due time, and this may lead to quick and dirty solutions. Thus, a quality assurance system is required to ensure that technical quality is within required bounds. This system may be implemented through pair programming, code review, design review etc. It is crucial that whatever QA systems one choose, it has strong enough authority to inflict a decrease in focus factor, or even a postponed deadline.
Cheers and good luck to you all in Trondheim! See http://xp2010.org/
First, Morten's and my experience report "Tech Challenges in a Large-Scale Agile Project" was accepted, and will be both presented and included in the conference proceedings:
This experience reports focuses on the major technical challenges that arose during the project, especially those challenges that we think can be attributed to the SCRUM methodology. For each of them, we try to identify the consequence and the cause, and then follow up with any solutions we tried, and an analysis of whether the problem was successfully solved or not. The session paper lists three major examples of such problems.
Then, I got accepted a lightening talk as well: "Agile Methods may Discourage Quality". However, since I have to be attending a customer at the time, Morten will be presenting this instead of me.
Agile methods, and in particular scrum, have a very strong focus on productivity and immediate business value. The developers are encouraged to complete their tasks in due time, and this may lead to quick and dirty solutions. Thus, a quality assurance system is required to ensure that technical quality is within required bounds. This system may be implemented through pair programming, code review, design review etc. It is crucial that whatever QA systems one choose, it has strong enough authority to inflict a decrease in focus factor, or even a postponed deadline.
Cheers and good luck to you all in Trondheim! See http://xp2010.org/
mandag 10. mai 2010
Technical debt in agile projects
I'll be presenting my opinions on technical debt in agile projects at Communities in Action 2010 tonight.
The presentation can be found at slideshare but I'll let you in on my three "lemmas" as a tech lead:
The presentation can be found at slideshare but I'll let you in on my three "lemmas" as a tech lead:
make it simple and easy to report a technical shortcoming
don't let it backfire on the whistleblower
decide the matter in a setting with both technical expertise and executive power
torsdag 22. april 2010
Java Microbenchmarking
Working late on preparing a performance test tomorrow, I stumbled over something called microbenchmarking. The idea is to put small performance tests within you code to evalute the system. This gives you the liberty of extracting performance measurements regardless of what environment the platform runs in (i.e. your development desktop vs. testing vs. production).
There are an awful lot of obvious (and perhaps not so obvious) things not to do while microbenchmarking. Consider e.g. if you should invoke any large or small load, what layer to stress, when to do this ..
I'm implementing this as a JBoss MBean, which will let me invoke a test suite with a HTTP request, and get a "ping"-style timer response.
I'll post my results later if this happens to be an interesting feature.
There are an awful lot of obvious (and perhaps not so obvious) things not to do while microbenchmarking. Consider e.g. if you should invoke any large or small load, what layer to stress, when to do this ..
I'm implementing this as a JBoss MBean, which will let me invoke a test suite with a HTTP request, and get a "ping"-style timer response.
I'll post my results later if this happens to be an interesting feature.
Etiketter:
benchmark,
java,
jboss,
microbenchmarking
mandag 5. april 2010
NDC 2010 accept
Against all odds (?) - Mortens and my paper ("Modularization, Testing & Technical Debt in a Large Agile Project") was accepted for the Nordic Developer Conference 2010. Well then, even though it's experiences from a Java project presented at a .Net conference, both sides has the agile dimension in common.
But it's still somewhat comical to present in "the dragon's lair". The presentations is scheduled for day 2, track 2 at 11:40 - in parallel to Eric Evans .. yikes.
The abstract reads:
In addition, my colleague Filip van Laenen was accepted with his presentation "Distributed Computing 2.0". See http://www.ndc2010.no
But it's still somewhat comical to present in "the dragon's lair". The presentations is scheduled for day 2, track 2 at 11:40 - in parallel to Eric Evans .. yikes.
The abstract reads:
This experience reports focuses on the major scrum–related technical challenges that arose during a 120 000 hour scrum controlled project. For each of them, we try to identify the cause and the consequence, and then follow up with any solutions we tried. Finally we sum up and assess whether the problem was successfully solved or not.
In addition, my colleague Filip van Laenen was accepted with his presentation "Distributed Computing 2.0". See http://www.ndc2010.no
Etiketter:
agile,
conference,
cx,
experience report,
java,
presentation,
scrum
mandag 8. mars 2010
Wannabe Linux "#¤(=¤/"!?%/¤
For some reason, we are using Cygwin at work to ease our scripting burden. It's a great tool for using bash-ish scripting power. Lately, my find command has behaved in strange ways. Whatever flags I pass, the result is always the same:
After about 3 days this problem became unbearable, and I dedicated myself to hunt down the cause. Neither a cygwin upgrade, nor my configurations files was to blame. Windows stole my find !
Note that even though I remove the bogus find, some devil puts it back after a few seconds! Very strange indeed.
Anyway, I decided to get rid of the entire system32-thingy. I didn't want the break the fragile windows PATH variable, so I decided to handle the problem in .bashrc.
And that was just another nail in the windows/cygwin/hybrid coffin.
[/usr/bin] hasov@HKS-ADAMSTUA300 $ find
FIND: Parameter format not correct
After about 3 days this problem became unbearable, and I dedicated myself to hunt down the cause. Neither a cygwin upgrade, nor my configurations files was to blame. Windows stole my find !
[/usr/bin] hasov@HKS-ADAMSTUA300 $ which find
/cygdrive/c/WINDOWS/system32/find
[/usr/bin] hasov@HKS-ADAMSTUA300 $ rm `which find`
[/usr/bin] hasov@HKS-ADAMSTUA300 $ which find
/usr/bin/find
[/usr/bin] hasov@HKS-ADAMSTUA300 $ sleep 10s
[/usr/bin] hasov@HKS-ADAMSTUA300 $ which find
/cygdrive/c/WINDOWS/system32/find
Note that even though I remove the bogus find, some devil puts it back after a few seconds! Very strange indeed.
Anyway, I decided to get rid of the entire system32-thingy. I didn't want the break the fragile windows PATH variable, so I decided to handle the problem in .bashrc.
export PATH=`echo $PATH | sed -e 's/:\/cygdrive\/c\/WINDOWS\/system32:/:/'`
And that was just another nail in the windows/cygwin/hybrid coffin.
Abonner på:
Innlegg (Atom)