It can be satisfying to feel like there is potential to realise a successful idea no matter how realistic the feeling is. This is a very counter productive mental state as not only does it not help in delivering the potential it also means that you are probably comfortable and perhaps don't want to leave the state.

Thoughts are not easily categorized, however as it might be helpful in deciding (to whatever extent we do decide) which thoughts to act upon and how, I will define three broad groups which thoughts could be sorted into.

1. Thoughts on past experience, something like how your memory is realized.
2. Thoughts about how potential events could play out, be it due to your intervention or not (like a plan or prediction).
3. 'What if' thoughts, could be regret or something less emotionally charged.

Thoughts from all groups appear to invoke emotion, so a memory of a nice event or promising plan could invoke a feeling of happiness and/or satisfaction but emotion could also be genesis of the thoughts. Although the genesis of a thought never seems clear to me.

In Inadequate-Equilibria Eliezer Yudkowsky argues that the efficiency of the economic system and the number of people in the world means that there isn't any low hanging fruit when it comes to converting an idea into something profitable.

Although things are in a state of Nash Equilibrium everywhere the incentive structure in place means that these states can't be resolved in a way that makes money otherwise it probably would have happened already and it wouldn't really be in Nash Equilibrium. Or something like that.

It would be nice to be able to reference previous thoughts when writing new ones.

There are two approaches that initially come to mind to tackle the presentation of referenceable thoughts.

1. Provide links to the referenced thoughts and referencing thoughts along with the current thought.
2. Present all referenced thoughts along with the current thought and make the referenced thoughts collapsable.

Some processes I perform during the day that I might be able to improve on are:

1. Making coffee
2. Exercising
3. Reading
4. Making dinner
5. Programming
6. Managing projects
7. Betting

Improvements could entail

1. Making the process faster to perform
2. Making the result of the process better
3. Achieving more enjoyment from the process

For each process one type of improvement may be more desirable than another. For example, I don't want to speed up my coffee making as I use it as a chance to take a break from looking at the computer screen but I do want to speed up project management as it would give me more time to do something I enjoy.

Although I believe a more liberated engineer (free from excess social, bureaucratic and traditional processes) generally makes for a more for-filled and ultimately more productive engineer it can also be helpful to use self imposed mechanisms to guide behavior where human tendencies can lead us down unproductive paths.

An example of this is a widget I created for android which connects with my Trello boards, sits on my home screen and has the following features:

1. A Doing section, (scrollable) Today/This Week section and Clocked off section which track corresponding lists on all Trello boards and present the cards present in these lists.
2. Ability to move the cards between lists as well as into the 'Todo' and 'Done' lists which are present in Trello but not presented in the widget.
3. Triggers notifications and alarms when amongst other events the following happens
   1. A card sits in 'Today' after the day is complete
   2. A card sits in 'This Week' after the week is complete
   3. A card sits in 'Doing' outside work hours
   4. There is no card in 'Doing' during work hours

The alarms and notifications have a pavlovian effect and can be made to quite unpleasant by adjusting vibration length and sound thus increasing the effectiveness.

The most effective solution to a mental process problem isn't always the cleanest solution. The model that is built in the head as part of the solution needs to resonate in a way that it is remembered and lends itself to being used when such a problem arrises.

Think two crocodiles facing each other.

A couple of thoughts regarding the PocketLab UI.

1. The collection of data across different data sources should be more closely integrated so the user can easily select between different graphs from different sources on the same screen. This would be similar to how post collection data is reviewed across sources.
2. The revision of data (post collection) should be more distinct from the collection of the data.

More ideas around accounting.

1. Find a way to introduce small business to accounting processes currently aimed at only bigger companies due to cost limitations.
2. An invoice generator which hooks into the tax system and can work as a plugin to existing project management tools.

Writing thoughts where it is assumed I am the consumer seems to be more satisfying.