<aside>
For my eyes only. To display tasks, and for documenting anything technical about the project, such as tech stack, database schemas, diagrams, and more that other developers or users don’t need to see to use the extension.
</aside>
Break down the project into smaller tasks. Difficulty is measured in hours. Any task that exceeds 40 hours needs to be broken down further.
A detailed list of features that the application will provide. Features are split into ‘Required’, ‘Want’, and ‘Optional’ priorities.
Some key principles this extension is built on come from Atomic Habits by James Clear. That book carries a lot of wisdom to developing healthy habits and, most importantly, breaking bad habits. The laws of breaking a bad habit are:
Make It Invisible
Reduce exposure. Remove the cues of your bad habits from your environment.
Make It Unattractive
Reframe your mind-set. Highlight the benefits of avoiding your bad habits.
Make It Difficult
Increase friction. Increase the number of steps between you and your bad habits.
Use a commitment device. Restrict your future choices to the ones that benefit you.
Make It Unsatisfying
Get an accountability partner. Ask someone to watch your behavior.
Create a habit tracker. Make the costs of your bad habits public and painful.
Define the boundaries of your project. What will your project do and what will it not do.
It is a browser extension, built using Chrome API, React, Vite, and vanilla web languages. Whenever Chrome extensions are supported, this application will be able to function. As far as my knowledge goes, Chrome extensions are not usable on the Safari browsers and will require the extension to be redeveloped using Apple’s developer tools (which require a Mac computer).
What should be true after this project is implemented?