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

Python and Access-Control-Allow-Origin

Ok, here is something that probably happens a lot: You are trying to do some .js (if not you should get started), and write some code in your favorite ide, save it, load it in your favorite browser and everything is ok. You are a good developer and start making packages and loading your files when you need them: lazy . You don't want to overdo things, and manage to put stuff into a bunch of .js and .html. You load them into your browser and BAM: Access-Control-Allow-Origin   Failed to load resource: Resource failed to load   So now you are all WTF, right? You Google (some would Bing ) it and sure enough, what you were thinking is the ugly true and by now you get angry as a bird. Why? Ok, for those that didn't know there is a thing called Same Origin Policy , that forbids you from loading stuff across different domains and bla bla bla... So what does it has to do we you? You sure enough are not trying do load across domains, your are loading a file... you may think, but no...
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...
Kommentar veröffentlichen
Next »