universal subgoaling
Table of Contents
Breaking a goal into smaller subgoals.
1. example
You want to get to Sydney from the North Pole, that’s your first goal. You decide the best way to do it is to get to an airport and take an airplane. Then you need to get to the airport. Get to the airport is a subgoal of you big goal of going to Sydney. To get to the airport, you decided that you best took a
Backlinks
General Problem Solver
Assume a current state \(C\) and goal state \(S\), define a difference/distance between the 2 states \(d\). With previously known operator \(o\), a transition can be made from \(C\) to an intermediate state \(I\).
self-collaboration
(Key component)
For self-collaboration to happen, in what you produced in each work session, there has to be all 3 of the following components:
- Documentation
Description of the whole project.
For a program project, how to install, what are modules are designed to be there, how they work…
This will be how you imagine the project, and you need that picture intact and consistent across sessions.
- Log
What happened in the session, what have you done.
Did you wrote a bunch of function for a feature? you may forgot about them if you don’t log you have written them and read those logs. I would.
In a single session this will conveniently be in your working memory and something you look back a lot on, as you localize yourself on your process. This is part of your perception of your progress and part of the whole schedule.
- Agenda
What you planned to do.
An example would be, you wrote a converter, your wote a predicate, and you plan to write a filter using the predicate, then use the filter in another function to collect eligible items.
In a single session this will also naturally be in your working memory, not only with the big stages “this feature then that feature, this module then that module”, but also with the details in implementation where you do the universal subgoaling on the job