March 22nd, 2010 • Comments Off on Leaving Sun – Kick butt and have fun!
I decided to leave Sun Microsystems/Oracle and move on to a new position which start 1st of May. I was looking around for a while and reached out to some people and decided that moving on is the best bet for me.
Don’t get me wrong: Working for Sun has been great! I met very bright, great, important, impressive and most of all innovative people – and the company supported me in creating things like OCCI. It was a great experience! Most certainly I’m a bit saddish about this. Sun was a dream-come-true when I started and I’m extremely happy that I had the chance to be part of this history.
Now I move on for various reasons which I might explain to you while having a beer…I will continue to work on Grids and Clouds and hopefully I can push OCCI even more! I will keep on blogging on my blog. My blog at blogs.sun.com/intheclouds will probably vanish sometime (*sniff*) but you can find me using the known website: tmetsch.org. But for now: Kick Butt and Have Fun!
February 21st, 2010 • Comments Off on Striking Lufthansa Pilots??
Okay the Lufthansa pilots are going on strike starting tomorrow for 4 days. I’m flying Lufthansa…But that is no issue. I fly with Augsburg Airways which is part of the Lufthansa organization. Weird is that Lufthansa uses the Augsburg Airways brand to pay pilots less then they have to when they would work for Lufthansa. Now guess what: The Lufthansa pilots (salaries between 60.000 and 240000 Euro annually) are going on strike. Those pilots working for Augsburg Airways whom earn less are not going to strike…something is wrong here…
It doesn’t mater which programming language you are using Java, Python, or something else. Writing cool kick-ass Unittests is a must. So here are some thoughts and Ideas:
Design first & design to test. But do not add extra methods juts for testing!
Always write your unittest first! It will start small (jsut checking the public methods and eventually grow with your code)
Design and spend time writing test environments with Mocks etc.
Each method should be at least tested by 3 test methods in your unittest:
test for success – Test if the method behaves correctly when given parameters in range
test for failure – Test if the method behaves correctly when given invalid parameters, wrong environment etc.
test for sanity – Test with a set of input parameters and compare results with expected output parameters.
Next to this I would encourage all developers to use Agile development methodologies like Scrum or similar. And also: please tweet and blog to give your users an insight of what is going on with your product/software.