Long time, no blog..

Well, were to begin. It’s been a long time since my last post; this is because my server blew up (not literary though, only the motherboard, psu and both of the drives in the RAID1 set). Since I had my ass full both work wise and private it took a lot of weekends and nights to restore everything. Well, what have I been up to since my last post?

It’s good to be back

Wise word

Great article by Michael Feathers about being a professional. Interesting reading, and many wise words.

Task-application for small teams?

I am looking for a simple application to track task in a small team environment, the requirements are quite simple.

Nothing fancy really, and I could probably roll my own pretty fast (by example leveraging appfuse or equinox), but I rather reuse some existing piece of software.

Any suggestions??

Learning from OSS projects?

The O’Reilly website onlamp.com has a really interesting article out about what “corporate” projects can learn from open source dittos, I found the article really interesting and there are allot of recognition-points in there. Worth reading, and I immediately ordered the book which the article reefers to.

It all boils down to five important point, namely.

  • Tell the truth all the time
  • Trust the team
  • Review everything, test everything
  • All developers are created equal
  • The fastest way through the project is to do it right

    I know I will try to integrate more of the tips into my projects, and definitely try to stand up against the “management” more.

    The article

    Going to JavaOne..

    I just registered for this years JavaOne, should be a nice experience as usual.

    The voes of multi-IDE projects.

    At my current gig we use multiple IDE’s for different tasks (of historic reasons as well as pure productive reasons). Today the team uses Borland JBuilder, Intellij IDEA and Eclipse.

    The suggested/preferred choice is JBuilder, but the project has decided to be IDE independent, and today JBuilder is almost exclusively used by the EJB-developers (team is split between EJB, Web/Frontend and Persistence/Hibernate). The Hibernate Team uses Eclipse, since it makes a lot of sense to use some of the rich plugins available for this IDE.

    The project has a directory structucture set up, an ant file for building/deploying etc. The problem is that JBuilder seems to spread a lot of files around the whole repository, ad hoc META-INF directories, .class files in strange places and some other arbitrary files.

    I must say that I am no JBuilder fan, but it has some really nice features for those not that into “code” (i.e. WYSIWYG/Code generation for e.g. EJB’s). But I highly dislike it spreading it’s files all around it, as said before Eclipse & IDEA has no problem with a predefined directory structure, but JBuilder really insist on rolling it’s own, highly annoying. For the time being I believe I got it under control by hacking strange JBuilder xml-files, and heavy usage of .cvsignore .. I only wish it were easier.

    SCEA – 1

    Cleared SCEA part 1

    After a slow start I took the plunge and booked a time for part one of SCEA (Sun Certified Enterprise Architect). For those of you not familiar with SCEA the exam is made up of three parts, where the first one is a standard multiple choice exam. Once you have completed part 1 you can continue to the “guts” of the certification which is architecture based on the requirements you receive.

    I have started the analysis work of part 2, and I must say that the requirements are as fuzzy as real world requirements often are.

    Posting Disclaimer

    Posting disclaimer!

    The guidelines I follow for publishing anything are:

    • It’s publicly available info (i.e., I never post anything you can’t fi
      nd on the net by yourself)
    • It’s useful to me, right now or in the future
    • It has something to do with my work, hobbies or the general “tech-world”
    • It’s not directly related to work – I never post anything directly related t
      o my work, projects, company or suppliers, except if it’s out in the public alre
      ady.

    Finally, in case the above does not make it absolutely clear, my views do not re
    flect that of my past, present, or future employers. What I post is my opinion.
    This is, after all, my blog.

    10 most common answers from a developer

    The following is quite old by now, but still get its point through…

    10. ‘That’s weird…’
    9. ‘It’s never done that before.’
    8. ‘It worked yesterday.’
    7. ‘You must have the wrong version.’
    6. ‘It works, but it hasn’t been tested.’
    5. ‘Somebody must have changed my code.’
    4. ‘Did you check for a virus?’
    3. ‘Where were you when the program blew up?’
    2. ‘Why do you want to do it that way?’

    And finally…

    1. ‘I thought I fixed that.’

    ← Previous Page