If I'm writing some small tool, I often start with fictional workflow examples.. These get adjusted as I discover ways that the implementation can be made simpl

If I'm writing some small tool, I often start with fictional workflow examples.. These get adjusted as I discover ways that the implementation can be made simpler or easier without any significant changes to the workflow.. Other times I find that the workflow is annoying and that a larger complexity in the implementation is well worth it for a nicer workflow.. What I'm trying to convey is that it's often better to BOTH have a lose idea of how it should be used AND how to implement it, but be ready and able to change both implementation and workflow/documentation as new discoveries are made.. In the end, if you know the implementation AND workflow EXACTLY, it's because the program already exists and you should just use that instead..