2/ The word "Complex" sounds negative, but is not.
TfT tools enable new possibilities, but they require effort and commitment.
Is is not just about learning new software & features, but learning new things about ourselves.
We are the tool of thought, software is the helper.
3/ TfT tools are complex because we have to make changes to ourselves - the way we think, process & use knowledge. We have to be willing to invest time, energy & in some cases money to learn new techniques, processes & workflows.
We become the algorithm (or set of algorithms)
4/ We become the algorithm: tweaking our mind to have the mechanisms to successfully & consistently process & utilize information, to obtain value based results.
It hurts to change, habits are hard to break.
So we have to embrace the complexity. The gold is found in complexity
5/ It is understandable that new users want the tools to magically make them more creative, innovative and smarter.
It is understandable they want the perfect system from day one. Basically they want the "jack me into & pump with the knowledge"
It doesn't work that way.
6/ TfT is a journey of self-discovery and learning.
We start with the basics. Master the basics.
Then move on to the next feature, technique, workflow, etc. With each step we build on the foundation laid in prior steps.
We are an algorithm in the state of constant change.
7/ No one can have a perfect system from the beginning.
It would mean your mind perfectly knows what and how to accomplish its goals and the perfect tool exists to match.
We are not that prepared, and that tool does not exist.
8/ For those of us who have gained a level of proficiency, we need to help guide, yes shepherd new ones along the path.
We don't overwhelm, but we also don't hide that it is a journey.
Journey of time
Journey requires energy
There are obstacles to overcome.
9/ How do we help new ones?
We encourage them to move forward.
We show confidence in their ability to grow and learn new things. We did it, they can do it. You are not smarter than me, I am not smarter than you.
We did it. They can do it.
10/ Encourage them to be modest. Simple goals. One step at a time.
Teach them to iterate: iteration means trying something new, throwing away what doesn't work & retaining what does.
This is not a waste, because we do it in small steps with little to lose, but much to gain.
11/ As they progress, introduce advanced concepts & more detailed workflows.
Commending them with each step forward.
Help them see the journey is to be enjoyed and the value of their system will steadily increase with each small iteration.
Teach them to embrace the complexity!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Over last 2 weeks been playing with @craftdocsapp while working on my newest @obsdmd plugin. For all you #roamans, it is Roam42 workBench, but tailored to Obsidian. I am calling it Text Transporter (for you Star Trek fans) since there is already a plugin with workbench name.
2/ anyhow @craftdocsapp is beautiful. For those looking for excellent block centric authoring with export MD support, this is amazing.
Some of my #roaman friends (@beauhaan) preach the gospel of Blocks. And I agree, blocks are the best unit for work. Craft supports them natively
3/ While Craft is amazing, I still can't see it's future. It is a little between Roam and Obsidian, but not a totally fair comparison. It is simpler and easier to learn. Uses more standard UX metaphors, which makes it a snap to learn.
In 1980, @TheTedNelson in one of his books coined the phrase transclusion and even demonstrated it in his own Xanadu Project. Transclusion says you have a single document assembled dynamically from separate sources.
3/ It is good to educate yourself on the transclusion as it helps you better understand the goal of block refs. I suggest this Wikipedia article. It’s not a new idea, the concept of compound documents have been around for a long time.
The Opinionated Short Guide for Switching from Roam to Obsidian
1/ Many have asked for advice on making the switch. While there is no "one size fits all" approach, I will share some practical tips that should help you.
Other switchers - feel free to hop in with your advice
2/ -- Give yourself time --
Over time, we build complex workflows & techniques in a Tool for Thought like Roam. There is no button to instantly transfer you to a new tool. You need to give yourself time to make the transition. Some say 2 to 3 weeks, I gave myself 2 to 3 months.
3/ -- Export from Roam using Flat Markdown --
Export your Roam graph to flat markdown files using the export tool in the menu. This will give you a zip with all your pages in Roam, in markdown format and with all block refs resolved to pure text.
1/ I submitted my 1st plugin to Obsidian for review. The process is nice. Not only is the dev experience good & support via the forums helpful, but the process of submitting a plugin makes you feel confident in @obsdmd leadership.
Here is the feedback I got with needed fixes
2/ You develop your plugin and then you submit it to review. Obsidian tests the plugin and then does a code review. The review is looking for a number of things that will improve the quality, reliability and secure usage of the plugin.
3/ First they make sure you are consistent with their User Interface features. This makes sure the user experience is standardized.
1/ Hi folks, today I changed my twitter handle to @TfTHacker. Basically using Roam less than other tools and my bias is toward being tool neutral. So going to be discussing many tools and their benefits and not just Roam, also @obsdmd, @rem_note, @logseq.
2/ For those who have followed me because of Roam, I won’t be offended if you unfollow. Though I intend to continue to tweet on Tools for thought and PKM, including Roam. Someone has to keep them honest - assignment accepted.
3/ In my book, Roam is 2020, lots of other options out there worth exploring as they are delivering features we need today not some focus on 2060 or 2070 (40 or 50 year vision?)
I live in reality, your welcome to join me if you like.