Revert to the Last Known Working State

First published:

Last Edited:

Number of edits:

Initial considerations based on a personal experience at Dispertech

When working on projects for extended periods of time, it may happen that we depart from what was supposed to be the path to our goals. After all, decisions have a compounding effect . Borrowing ideas from version control systems, when we find ourselves in that position, we must return to the last known working state of our path.

This idea works for projects of various nature and also for life in general. The biggest challenge is understanding what points actually belong to the path we want to follow and which ones don't. It is also impossible to go to the past and forget about the relative future trajectory.

However, we can capitalize on whatever it is we have learned in our own process. But it is of utmost importance to clarify what was the first decision that made us depart from what we were expecting. It is likely that this point is much earlier in time than what we anticipated.


These are the other notes that link to this one.

Nothing links here, how did you reach this page then?


Share your thoughts on this note
Aquiles Carattino
Aquiles Carattino
This note you are reading is part of my digital garden. Follow the links to learn more, and remember that these notes evolve over time. After all, this website is not a blog.
© 2021 Aquiles Carattino
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License
Privacy Policy