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

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

ThreadLocal as an Enum - I'm not afraid to admit it!

Well, as disturbing as it might be, I am not afraid to at least admit it: I did not know about the elegance of the following construct: public enum TLData { INSTANCE; private final ThreadLocal< String > myData = new ThreadLocal< String >(); public String getMyData() { return myData.get(); } public void setMyData( final String myData) { this .myData.set(myData); } } Since you are using an Enum, nobody can create new members from outside, you don't have to care about privatizing any methods and you can access it as easy as: public class myClass { public void myMethod() { /** * setting the data */ TLData.INSTANCE.setMyData( "some data" ); /** * getting the data */ String myData = TLData.INSTANCE.getMyData(); } } Isn't that fancy? I had to admit I never thought of it myself. A colleague of mine had to put it under my nose.
Kommentar veröffentlichen
Next »

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 h
Kommentar veröffentlichen
Next »