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.
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.More Like This
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.More Like This
Another option for how to link up 'thoughts' is to use something similar to suggested stories on a news site. These suggested thoughts would be related to the current thought using an configurable algorithm. This would reduce the amount of friction when adding thoughts and encourage me to do it more.
Rather than complicating the UI the 'suggested thoughts', which from now on I will call 'related thoughts' because the verb suggest doesn't fit in this context, can fit in to the existing stream of thoughts, above and below the current thought depending on the creation date. This is where 'infinite scroll' would be very useful.More Like This
To improve the utility of the Doing widget I should start using it more for personal tasks. I think the task description, which for work items I currently don't read very often, would be more useful and I would engage with the actual content on the widget rather than the colours and the notifications.
To encourage we to use it for personal tasks I think the following improvements might help.
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:
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.More Like This
The main motivation for using Elasticsearch is the 'More Like This' feature which link thoughts together automatically.More Like This
Some processes I perform during the day that I might be able to improve on are:
Improvements could entail
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.More Like This
I find the lifecycle of angular services to be quite anti-intuitive when down in the weeds with lazy loaded modules.
If I have a service declared in a lazy loaded child module and that module is loaded the service is instantiated and according to the documentation and pretty much everyone who has wrote on the subject should live for as long as the associated injector (and thus module) lives unlike a module directly imported which I understand shares the injector and thus the services will be available app wide for the lifecycle of the entire app.
I have found that if a lazy loaded module accessed through a router outlet is navigated to from the same lazy loaded module through a different router outlet which effectively wipes the previous base component of the module, the component is redrawn but the service from the previous module and assumably the actual module itself sticks around. The question then is for how long?More Like This
I recently implemented a 'context service' for the PocketLab web app which has proven to be very useful for multiple reasons.
The service, which is part of an angular web app although assumably could be used in most front end web frameworks
In the web app I am working on the context consists of the object currently being viewed and the hierarchy it exists in as well as some more broader information such as login status and PocketLab device in use.
Amongst other things this is useful for providing information to UI components that help the user orientate themselves within the app and for sending a lot of rich data to Google Tag Manager.More Like This
A couple of ideas on how to use the skills of accounting and programming in the same company.