Direkt zum Hauptbereich

12 steps for software development


  1. We admitted we were powerless over planing—that our time had become unmanageable. 
  2. Came to believe that a Power greater than ourselves could restore us to sanity. 
  3. Made a decision to turn our will and our lives over to the care of The Team. 
  4. Made a searching and fearless moral inventory of ourselves. 
  5. Admitted to The Team, and to managers the exact nature of our wrongs. 
  6. Were entirely ready to have The Team remove all these defects of character. 
  7. Humbly asked The Team to remove our shortcomings. 
  8. Made a list of all projects we had harmed, and became willing to fix them all. 
  9. Made direct bug fixes to such projects wherever possible, except when to do so would injure them or others. 
  10. Continued to take personal inventory and when we were wrong promptly admitted it. 
  11. Sought through code review and automation to improve our conscious contact with The Team, committing only tested features. 
  12. Having had a spiritual awakening as the result of these steps, we tried to carry this message to other developers and to practice these principles in all our affairs.
(no sarcastic undertone intended)

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 convenient if you have to do some nasty network-conne…

My language skills over time... update

Skills, as everything else, develop over time. Some get rusty though. I was once a very skilled c programmer, now I dread to manage memory myself. I suppose with time the tools change and the languages change with it. I don't think there is A Best Language for coding. They have different objectives, some are good in some context, some even fun, some are not fun but they do the thing they are suppose to best. It took me a long time to realise, that the language I choose is not strictly to communicate with the computer but with the next developer (including myself). The computer will interpret and run the code once it works, but the next developer is in charge of understanding the code, the Why and How, so she/he can maintain it, use it, or even learn from it.