Chore at Last is a little bit like tidy first but what with different approach. Chore at Last means, before you create a PR or go live with a new feature you chore your code. The idea is to improve the code around the new feature or bug fix to prevent it from going tech debt. This step also includes the usage of common code analyzer tools like PMD or Sonar.
OK, a real world example. I just update a lib to the latest version. The new lib version was improved and has a little bit changes interface. The quest was to update to latest lib version. At this point I could stop and "solve" the JIRA ticket. But I realize that a service class that hides the lib, was not needed anymore. My chore last action was to remove this needless class. It reduces the code complexity and prevent tech debt.
Or you can compare with a craftsman who is cleaning up the work desk and store all there tools. It's not part of the product but still needed.
Do you think this would be banal, I know it isn't.
No comments:
Post a Comment