No Huddle Offense

Open Solaris 2008.11

Okido, everyone is talking about our Q1results – for more info see jonathan’s blog. But for one second think about the upcoming new cool stuff – like opensolaris 2008.11 🙂 I just had a look at a release candidate, and it is worth a try. You might already know ZFS, Dtrace and the other good stuff which comes with solaris but new is the time slider? This new features is similar to the time machine of Mac OS X and shows some potentials of ZFS!

I hope I can add a screenshot tomorrow 🙂

Categories: Work • Tags: OpenSolaris, Tech • Permalink for this article

OSGi best practices

I’ve been working with OSGi for the past years – and I must admit I really like it. If you follow some best practices rules your applications are definitely going to perform better and look nicer. Therefor I remembered an presentation about best practices when using OSGi. I have almost nothing to add – See for yourself: OSGi Best Practices!

Categories: Work • Tags: OSGi, Software Engineering, Tech • Permalink for this article

OSGi dependencies

I like the OSGi platform, and I have been using it for quite a while. One of the most important things is to keep track of your dependencies (e.g. like preventing cycled dependencies). Auto-generated MANIFEST.MF files are most of the time not really optimized. Therefor I started writing some python code to check dependencies. 

 It reads in all the MANIFEST.MF files from the bundles and creates a dependency graph. It will look for unnecessary and unneeded imports and exports. Look for cyclus etc. It is written using the networkx library for python. Also useful is the zipfile extension in python 🙂 It can be used to extract the jar files of bundles.

Categories: Work • Tags: Software Engineering, Tech • Permalink for this article

Software engineering

So my personal opinion on software engineering is pretty straight forward. First of all it is important that the developers who write code are willing to improve themself by reading, blogs, articles, books (e.g. Code Craft or Beautiful Code – good reads).

The second idea is to restrict the work of the users. Provide coding guidelines and define processes. Everybody should know them by heart (and behave like they say). This will help that persons can work more and do not have to look up and ask many things (A knowledge base is always a good idea and even more important a todo/issue tracker so everybody knows what he is doing).

The next is to automate everything (another good tip from the Pragmatic Programmer book :-)). Last but not least do clear designs and document them (do not reinvent the wheel).

And if you behave work like this you can minimize the number of bugs you produce during development. You can also speed up your development! But always try to optimize (e.g. by tracking where you loose time…) your personal working behaviour and the global processses. Be Agile!

Categories: Work • Tags: Tech • Permalink for this article

Cloud Computing

Use Cloud Computing Services : http://www.nohardware.com/  🙂

Categories: Work • Tags: Cloud • Permalink for this article