“A good plan violently executed now is better than a perfect plan next week.” -General George S. Patton, Jr.
When what is defined as a "good pattern" is setup And it is sufficiently complex. Be mindful that there are probably ways to automate and simplify.
But for the time being you need others to execute that pattern. Find the person who knows the pattern best and can accomplish the task most efficiently and accurately
Have a meeting with them and note how long the meeting took. People at the meeting might also help resolve any quick issues that come up in the meeting with the goal to get it done as efficiently as possible.
One way to roll this out:
-
Have someone at the meeting outlining step by step the order of how they approach and solve the problem:
a. From the planning level
b. To the api level
c. To executing the problem
d. Until the point where the code is in a spot that can be code reviewed and merged.
e. Tickets should be broken into reviewable sections. -
Additionally deliver the overall diff. Of the change from the session.
Clock how long it took. The meeting may have been imperfect but now you have an idea of how long that takes.
Now have everyone implement that pattern
- Have them measure their own accuracy
- Have them measure the overall time.
- Have people report on the time it took them and if they felt good about how it went.
- As people get better they will come closer to the optimal persons time.
- Now you should have the most simple way to multiply the thing by x number of times people need to do that thing
Something that took the original creator 2 hours may take an experienced person who is prepared and just executing: 5 hours. And someone who gets stuck way longer.
Circle back from time to time on the fact that:
- there are probably ways to automate and simplify.
further reading: https://blog.codinghorror.com/the-noble-art-of-maintenance-programming/