Make complex code changes faster & more reliably with automatic working memory support
- Total 162
- Win 77
- Mac 51
- Linux 34
|May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3||May 2||May 1||Apr 30||Apr 29||Apr 28||Apr 27||Apr 26||Apr 25||Apr 24||Apr 23||Apr 22||Apr 21||Apr 20||Apr 19||Apr 18||Apr 17||Apr 16||Apr 15||Apr 14||Apr 13|
Cognitive science research shows that humans can only store a few things in our working memory at once. So what happens when programmers do tasks that are too big to fit in our working memory? You're debugging the frobnitz, and midway through you realize that the simplest fix involves refactoring the widget, which in turn requires reworking the widget factory. By the time you're back at the frobnitz, the frobnitz-related info that was in your working memory has been replaced. You waste time recovering that lost context, and you may introduce bugs if you misremember what's been done or forget something that needs to be done.
FlowTree is a Sublime Text 3 plugin designed to help with this problem. By automatically building a diagram of the files you open and why you open them, it can help you make complicated code changes faster and more reliably.
To install via Package Control, run the
Package Control: Install Package command and choose the FlowTree package. (If you aren't able to find it, maybe try updating Sublime Text to the latest version.)
To install manually, e.g. if you want to do development, clone the repository into the Packages directory in your Sublime Text 3 settings folder.
Open a file from a codebase you're working on and run the
FlowTree: Show FlowTree command. You should get a new buffer titled
Your FlowTree that tracks your editing workflow.
In this example, you're fixing a frobnitz-related bug that requires making changes to the frobnitz model, the frobnitz view, and the frobnitz controller. Because
frobnitz.py was the file that was open immediately before each of
frobnitz_view.py were opened, they are each displayed as children of
frobnitz.py. Midway through fixing
frobnitz_model.py, you realize the widget needs a refactor and search the repository for the string “widget”. Partway through editing
widget.py, you open
widget_factory.py to make some changes there. At each stage, it's possible to see where you are in the task as a whole and what still needs to be done.
As buffers get closed, the empty box ☐ turns into a checked box to indicate completion of that part of the task. In the above screenshot, you finished making modifications to
frobnitz_controller.py and closed the file, causing its box to become checked. When the top buffer gets closed, the entire FlowTree diagram disappears to get ready for the next task.
To provide further reminders about where you are in your editing workflow, if you leave text selected in a buffer, that text gets displayed next to the buffer in the FlowTree diagram. This can be used to leave hints for yourself about what you were doing.
I made this for a hackathon and there might be bugs. Please report issues here.
John Maxwell - maxwelljohn