Words of Java

Found this nice blog while searching for some log4j info the other day : http://veerasundar.com/blog/

Seems to have quite some other good pieces of info aswell that I might have to discover.

January 23rd, 2010 | Tags: log4j | Category: blogs, java | Leave a comment

Not much here lately due to time issues. Or prio issues one could say. So, posting in between meetings from My iPhone is only option right now. Hopefully I Will have time to look into Jee6 tjis year and some more about tdd

January 21st, 2010 | Category: java | Comments (1)

I started out to investigate TestNG to see if it has an advantage over JUnit 4 and first I thought so but along the way (reading about it) I found it to contain just a little to many setup files and configurations (XML). These are things you don’t see when running the combination JUnit 4 and Maven 2, but maybe there is another way to go to have the same easy run options with Maven / TestNG.

Sofar, groups are the biggest improvement here. Since JUnit 4 took quite a few things from TestNG when it took the step from JUnit 3 you would think that Junit 4 should be able to match TestNG. Well, if I get back into this investigation I’ll try to tell my story about it here.

August 3rd, 2009 | Tags: java, junit 4, testng | Category: Testing | Leave a comment

This book is a must have in a team of developers. It doesn’t really bring you much new stuff but it sure is a good collection of the tools you need at a dayly basis. I learned some new JUnit 4 and TestNG stuff today actually, the way test data can be set up in both these frameworks.  I still have half a book to read so I probably have a few more new things up my sleeve when done. This is a compile-one (read-one), run everywhere (use any day) book.

August 3rd, 2009 | Tags: java, junit, testng | Category: development, java | Leave a comment

but I find myself involved in firefighting most of the time at work. We are shortstaffed with a high maintenence burden and I don’t know how we will take ourselves out of this. I was not a part of creating this situation but I hope I will be a part of the solution.

First, learn to say no to changes as much as possible.

Priority one is quality improvements and I play the boyscout role whenever I get the chance.

Dig, dig, dig after all possible faults and make the visible - at last somebody in charge has to react.

“Powerpoint it” or “Excel it” to make the everyday quality loss understandable to whoever calls the shots.

May 20th, 2009 | Tags: development, quality | Category: development, quality | Leave a comment

We have a few things we would like to have done in and around the project. Should we spread the word that we would like to refactor other parties code (and maybe also do it) or should we just make some rumours appear that we are about to do something. I think the small difference here could really matter. Or?

April 16th, 2009 | Category: development | Leave a comment

This week I tried these two Eclipse plugins at work.

I wasn’t so happy with EclEmma but maybe I just didn’t get the settings right. Would have been nice to have see the result just by looking at a production code file. Running the coverage tests all the time is going out of the way to find it.

Find it you do with Findbugs. Yes, we had quite a few in the project but no too bad I think. I hope we have time to look into it. Or I should say the guts to demand it… I’ll do my best to be a good boy scout.

March 27th, 2009 | Tags: EclEmma, Findbugs | Category: agile, development, java | Leave a comment

I stated in some earlier post that this year was going to be all about quality. I have started the long road where the goal is mainly the quality of my own work, but I also aim to be a good force and try to help whoever needs it (even if they don’t express it

So today I joined the initiative Manifesto for Software Craftmanship at http://manifesto.softwarecraftsmanship.org/

Maybe it’s only a name on a list or maybe is it worth something.

March 20th, 2009 | Tags: Manifesto for Software Craftmanship, software quality | Category: agile, development | Leave a comment

In the last 6-9 month I have had a quaility thinking revival. Or atleast I have started the quest after a few years in the dark path of dirty delivery.

So, reading the book Clean Code is kind of a new start for me and I DO LIKE IT. I also try to act on it to maximize the gain of the book. I try to think in these terms. I try to be a pain in the ass for my collegues at work to push clean code. And TDD. And automated thingies. Thanks Pål btw for being the biggest pain in the ass ever.

March 13th, 2009 | Tags: clean code | Category: development | Leave a comment