Thoughts on a patching system

The team I work with was thinking about how to build a patching process for the software that we have inherited (which none of us like). So I quickly came up with the following solution and emailed it to the team (I changed some software and team names here...):

JAVA:
  1. public class Patcher {
  2.  
  3. public void patchIt() {
  4. try {
  5.  
  6. File repositoryDirectory = Software.getRepository();
  7. repositoryDirectory.backup( "/backup/repository" );
  8.  
  9. Software.uninstall();
  10. Software.wipeFromDrive();
  11.  
  12. Team.designApplicationFromScratch();
  13. Team.codeApplication();
  14.  
  15. AwesomeApplication app = Team.installApplication();
  16. app.importFromBackup( "/backup/repository" );
  17. app.start();
  18.  
  19. Team.celebrateInstallation();
  20. Team.patEachOtherOnBack();
  21. Team.revelInTheGloryOfBeautifulCode();
  22.  
  23. Team.maintainAppWithoutFrustration();
  24. }
  25. catch( ResistanceToDoingItRightException e ) {
  26. Team.cry();
  27. patchItAnyway();
  28. Team.eraseJunkSoftwareFromMemory();
  29. }
  30. }
  31. }



Don't miss anything, subscribe!

Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.

Comments

No comments yet.

Leave a comment

(required)

(required)