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.More Like This
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.
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
Refining an earlier thought about improving some of my daily processes.
The combinations of process and improvement type which currently seem the most promising.
Apple triaged the app review for the latest PocketLab app due a bug that was introduced in the previous release.
I liked the process but even with the triage it took about 18 hours.More Like This
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
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
A couple of thoughts regarding the PocketLab UI.
I think I will start learning machine learningMore Like This