2/ Productivity isn’t solely dependent on having the right tool, rather Nick focuses on how negative self-talk can be disruptive to our focus & lead to procrastination.
Procrastination doesn’t have to be laziness, but can be a subtle avoidance to having to do difficult things.
3/ Its amazing how emotional state is directly connected with productivity. When full of self-doubt, or giving place to the internal critic, we can partially shutdown, lose flow and not get things done. Instead of letting our emotions fuel us forward, we allow them to disable us.
4/ Emotions are driven from our thoughts. Our emotions can be a strong motivator or demotivator in being productive and finding joy from our work.
So let’s break this down into a formula
thoughts -> emotions -> level of output
5/ Now reverse this formula. If you find you are less productive, or you are putting of some important task, or struggling with he task at hand:
Ask yourself: What emotions am I experiencing?
Examples: Lack of self-confidence? Confusion or lack of clarity? Fear of failure?
6/ We need to think about what emotions we are experiencing. Emotions don’t appear randomly, nor are they just byproducts of bodily processes.
Emotions are brought to life by our thoughts.
When we sense and identify an emotion, then we need to identify the thoughts behind them
7/ Once we understand what thoughts are derailing us emotionally, we can begin to address those thoughts.
In other words, we can’t change the emotion, rather the thought has to be changed.
This is not easily done.
8/ To change our emotions, we have to change our thoughts.
This means replacing a current thought with a helpful thought, or more likely to disprove to ourselves the so called “validity” of a harmful thought (example: feelings of worthlessness)
9/ In summary, our thoughts lead to emotions which affect our overall mental state which affect our ability to be productive.
What do you think, how have you found that your emotions affect your productivity?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Mobile apps are fundamental tools in our lives & we want our Tools for Thought to treat mobile devices as first class citizens, not some afterthought added later in the programs life span. @craftdocsapp handles this amazingly! Check out these gestures:
1/ So I have been deep diving on @logseq. Let me just say its brilliant and has so much potential. It really is a local @RoamResearch, but in some ways better (and in a few not so).
One thing I really like is this hybrid blend of a graph database with markdown under the hood.
2/ You really own your data and you can easily change your data in the markdown format and LogSeq crunches it into the graph database.
LogSeq is an outliner. Find out about the advantages outliners here, written for Roam but applies equally well to LogSeq
3/ Roam really deserves praise when I compare it to LogSeq.
+ Roam is cloud based, no setup, no local file management
+ Roam has fine tuned UX for many features. On surface it doesn’t look special, but it is all in the polish, yes in its nuances and finesse — Roam has this.
1/ Reviewing highlights in a smart way is one of the benefits of @readwise using their Daily Review feature. However, it is important to understand what the review buttons do, so as to efficiency of the process. For example, what does the "Discard" button do during a review?
2/ Some might think it is designed to ignore it in the reviews. But in fact it does something different.
You use this when you decide a highlight doesn't have value to you.
Consider it a friendly delete. It removes the highlight from being reviewed and not to appear elsewhere.
2/ This was also an interesting comparison of the use of block references in other systems and how they slowly become a standard way to do translusion.
1/ Readwise Tip - Use highlight_id in your exports
The @readwiseio export feature allows you to export your highlights to various tools like @obsdmd, @RoamResearch, @NotionHQ and more. The export can be configured to export these highlights in a format that works best for you.
2/ One possible issue when exporting highlights is that you can lose context of where they come from. Each TfT tools might have their own way of creating references to a source (example: block references).
How can we connect our TfT back to its source consistently?
3/ Readwise’s highlight_id to the rescue.
Use highlight_id in your export configurations.
It is Readwise’s internal identifier for that highlight. This means that every highlight you create gets its own unique identifier and is globally unique to the Readwise system.
1/ Today I to start officially cover @craftdocsapp. Craft is a beautifully “crafted” app for iOS, Mac & the Web. They define themselves as “a fresh take on writing & collaboration”for the modern era of digital devices that brings back the joy of writing. craft.do
2/ It isn’t necessarily a PKM or TfT tool, so a bit outside my focus area, but has many of the core features in place to compete in this space over time.
I have to thank @calhistorian for brining this app to my attention last year.
So what do I like?
3/ It is block based. So very natural experience for Roam and Logseq users.
It supports backlinks. Who doesn’t? But crucial!!!
Excellent collaboration features - multi-user editing
A beautiful WYSIWIG experience with great markdown support (import/export)