Direkt zum Hauptbereich

Release Plan

Mario: is of course the developer trying to save the princess
Princess: is the release
Barrels: are either feature requests or bugs
Hammer: reconsider / won't fix
Kong: release manager

Story: Mario starts at the wrong end. He is actually done developing at the time the release comes into action, but has to run his way up through the plan to make the release on time and help the princess. On the way up, there are all kind of features and bugs rolling down wanting to hurt Mario. He has no possibility whatsoever to get them done faster. However, it is in his power to keep some of them from getting done before he reaches the princess.

Kommentare

Beliebte Posts aus diesem Blog

JUnit testing services and clients with javax.xml.ws.Endpoint

Following situation: you have written some generic stub to use in your projects that creates a client for a service. Your client is smart and does some magic for connections (proxy, cache or other kind of magic). Or maybe you just have written a service for that matter. Anyway, you now want to test it. Unit testing the functionality of your methods is a must. But you still want to reach 100% coverage and need to test the service as it would run in real life. Then you can use the javax.xml.ws.Endpoint class. If you prefer figuring it out yourself, you can find the code (as a project for netbeans) -- here -- To follow the code examples as html click   --here-- So here is how you do it: If you've coded nothing fancy, then you probably have a class like this: This is a generic client for opening connections to services. It gives you back a port of the type of your service where you can call your operation as a method of the port. It is very...

Stop the software / car analogy

I can understand that making analogies is a very powerful form of explaining a hard concept, but you should be aware of the demons you might be unleashing.  I like analogies, as much as anyone. I do the Einstein-Train-Thing to convince my self that I understand relativity like the next man. But everybody is careful talking about relativity and nobody would walk outside the framing without considering it very carefully. Software on the other hand is not so respected, and I ask you: does the next man really get it? Everybody can relate to cars, right? So that is a good reason to use the analogy, you would think , but here is where I have to disagree: Thinking you know about the domain, sells, production lines, marketing, resourcing, electronics, hydraulics and all the engineering that has been put into the car is the first mistake. The second mistake is assuming other people do (unless they work for BMW or something like that).  You think you are making the ...