You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nelsonic opened this issue
Dec 21, 2018
· 3 comments
Assignees
Labels
epicA feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues.mtstarterA beginner-friendly issue that is a good starting point for a new person
Please Ignore This! It's (Probably) Crazy and "Will Never Work"!
I've been consistently writing down and sharing the technical knowledge I've accumulated over the last 5 years of my "career" as a software developer. (before then I only stored it in my brain ... until ...)
I realised that writing down the knowledge was by far the best way of testing my own understanding. And by making it freely available for anyone else to read, comment on and improve I have succeeded in both maintaining my knowledge and enhancing/extending it with the help of thousands of other people! I did not intend to create a "collaborative learning social experiment", I just wanted to remove the excuse my co-workers/team-mates (or members of the wider tech community) had for not "understanding" a given topic e.g: Test Driven Development, Continuous Integration, DevOps or Lambda Functions ...
Most of the repositories for that knowledge have been "donated" to @dwyl to help other people find them: https://github.com/dwyl?q=learn many of them have gained a life of their own in the form of questions and contributions from complete strangers who then become members of the @dwyl community.
The learn-... knowledge accumulation and sharing was the visible part of "phase zero" of my life, where I relentlessly worked to accumulate the knowledge, skills and cash I need to build my dream(s). I have tried to maintain a consistent work ethic of "showing up every day and single-mindedly chipping away at the mountain".
So I'm confident I can execute on my plans.
Reading! 🤓 📚
I've been (not so) secretly reading hundreds of books on many more subjects than just "tech" and programming. I've had the habit of reading every day for the past 15 years and have accumulated lots of knowledge which I have not yet captured and shared.
So my plan is to systematically capture and condense what I have learned from reading hundreds of the best books on several topics and share it with the world! I will be reading 100more books over the next 2 years according to the topics listed below such that the resulting book that I write will contain the cumulative knowledge of all the most well respected authors on each subject.
Why a "Book"? 📘❓
This question is worthy of a few paragraphs ...
But the short version is: a book requires focus from the reader.
That focus is something people need to develop/practice.
So helping them to read is a good thing!
I may very well end up turning each topic into a "video essay" for easy dissemination.
But that will not be my focus until the reading, writing and initial feedback is complete.
Topics / Outline 📝
This is the outline of the areas the book is going to cover:
Communication: Listening, Empathy, (More) Reading+Writing, Using Video & Emojis! 💬
Music, Art and Creativity 🎨
Mathematics! (practical applications that make your life better!) ➕
Science! applying the scientific method to your life and learning about Biology, Chemistry and Physics! ☣️
Technology, Computing, Coding, Crypto & A.I 💻 📱🤖
Design thinking 📝
Tools!
Entrepreneurship, Investing & Financial Freedom 💰
Follower-ship and Leadership 🐺
Scheduling: how to fit more/less into a day/life ⏳ 📆
Teamwork: Trust, Cooperation and Delegation 👥
Love ❤️ 💔 💍 🏡
Family: Parents, Spouses, Children & Bonus Members! 🚸
Community
Failure 😞
Playing, Winning & Losing 🏁
General Knowledge/Ignorance ❓
Travelling 🚗 🚂 🛩 🚀
Retirement? 🌴
Death 💀
I estimate that I will dedicate roughly 10 pages to each topic. Some will require less others more.
But my goal is to avoid any kind of "fluff" and just focus on exactly what the person needs to know
and give a practical "checklist" they can follow.
If I spend 1 month on each topic it will take me over 2 years to write this. ⏳❗️
That is a perfectly reasonable amount of time for a book that I expect will be the most dense volume of human knowledge/wisdom ever published! 😮😉 (not really, but certainly in the top 1%!) However rather than waiting till the whole book is written, I intend to start publishing the initial version of the book as soon as there is something worth reading.
More on how I will be writing and publishing the content later ...!
Alternative Titles 💡
Obviously I plan to dedicate a sub-project (10+ hours of research, testing and analysis)
to determine the "perfect" name for the published version of the book.
I'm actually informally referring to it as "The First Book" in my mind ... because
(a) it's the first book I'm going to publish and
(b) I think it's the first book people should read if they want to get a massive head start in life.
But I'm not going dwell on the name as it's something I can do after I've invested the time in the content.
However ... here are a few alternative book names:
As you can probably tell, I've spent a decent amount of time thinking about this ... ⏳🙄😉
But it's not the thought that counts, it's the action. 🏃
And I have a plan to publish the first draft of my book in 6 months. 😮
So that I can start collecting feedback and reviews while writing the rest. ⭐️
The text was updated successfully, but these errors were encountered:
nelsonic
changed the title
Automatic Effortless Instantaneous Success
FAQ
Dec 22, 2018
nelsonic
added
mt
starter
A beginner-friendly issue that is a good starting point for a new person
epic
A feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues.
labels
Dec 28, 2018
epicA feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues.mtstarterA beginner-friendly issue that is a good starting point for a new person
Please Ignore This!
It's (Probably) Crazy
and "Will Never Work"!
I've been consistently writing down and sharing the technical knowledge I've accumulated over the last 5 years of my "career" as a software developer. (before then I only stored it in my brain ... until ...)
I realised that writing down the knowledge was by far the best way of testing my own understanding. And by making it freely available for anyone else to read, comment on and improve I have succeeded in both maintaining my knowledge and enhancing/extending it with the help of thousands of other people! I did not intend to create a "collaborative learning social experiment", I just wanted to remove the excuse my co-workers/team-mates (or members of the wider tech community) had for not "understanding" a given topic e.g: Test Driven Development, Continuous Integration, DevOps or Lambda Functions ...
Most of the repositories for that knowledge have been "donated" to @dwyl to help other people find them: https://github.com/dwyl?q=learn many of them have gained a life of their own in the form of questions and contributions from complete strangers who then become members of the @dwyl community.
The
learn-...
knowledge accumulation and sharing was the visible part of "phase zero" of my life, where I relentlessly worked to accumulate the knowledge, skills and cash I need to build my dream(s). Ihave tried tomaintain a consistent work ethic of "showing up every day and single-mindedly chipping away at the mountain".So I'm confident I can execute on my plans.
Reading! 🤓 📚
I've been (not so) secretly reading hundreds of books on many more subjects than just "tech" and programming. I've had the habit of reading every day for the past 15 years and have accumulated lots of knowledge which I have not yet captured and shared.
So my plan is to systematically capture and condense what I have learned from reading hundreds of the best books on several topics and share it with the world! I will be reading 100 more books over the next 2 years according to the topics listed below such that the resulting book that I write will contain the cumulative knowledge of all the most well respected authors on each subject.
Why a "Book"? 📘❓
This question is worthy of a few paragraphs ...
But the short version is: a book requires focus from the reader.
That focus is something people need to develop/practice.
So helping them to read is a good thing!
Topics / Outline 📝
This is the outline of the areas the book is going to cover:
I estimate that I will dedicate roughly 10 pages to each topic. Some will require less others more.
But my goal is to avoid any kind of "fluff" and just focus on exactly what the person needs to know
and give a practical "checklist" they can follow.
If I spend 1 month on each topic it will take me over 2 years to write this. ⏳❗️
That is a perfectly reasonable amount of time for a book that I expect will be the most dense volume of human knowledge/wisdom ever published! 😮😉 (not really, but certainly in the top 1%!)
However rather than waiting till the whole book is written, I intend to start publishing the initial version of the book as soon as there is something worth reading.
Alternative Titles 💡
Obviously I plan to dedicate a sub-project (10+ hours of research, testing and analysis)
to determine the "perfect" name for the published version of the book.
I'm actually informally referring to it as "The First Book" in my mind ... because
(a) it's the first book I'm going to publish and
(b) I think it's the first book people should read if they want to get a massive head start in life.
But I'm not going dwell on the name as it's something I can do after I've invested the time in the content.
However ... here are a few alternative book names:
As you can probably tell, I've spent a decent amount of time thinking about this ... ⏳🙄😉
But it's not the thought that counts, it's the action. 🏃
And I have a plan to publish the first draft of my book in 6 months. 😮
So that I can start collecting feedback and reviews while writing the rest. ⭐️
The text was updated successfully, but these errors were encountered: