mirror of
https://github.com/MetaFam/TheGame.git
synced 2026-04-24 03:00:09 -04:00
Adding new playbooks for aug/sept: (#295)
- How to join a DAO community: written by & paired with @Techniciann9ne - Understanding Impostor Syndrome: written by & paired with @Gnomeski - How to Git on Github: written by & paired with @luxumbra Also tidied up sidebars.js & added `.vscode` dir to .gitignore
This commit is contained in:
Luxumbra
1
.gitignore
vendored
1
.gitignore
vendored
@@ -22,3 +22,4 @@ yarn-error.log*
|
||||
package-lock.json
|
||||
|
||||
.idea
|
||||
.vscode
|
||||
|
||||
246
docs/playbooks/how-to-git-on-github-non-builder.md
Normal file
246
docs/playbooks/how-to-git-on-github-non-builder.md
Normal file
@@ -0,0 +1,246 @@
|
||||
---
|
||||
title: 📚 How to Git on GitHub as a non-builder
|
||||
description: 'This Playbook focuses on contributing to the MetaGame wiki but the core concepts can be applied to any repository you want to contribute to and most DAOs & projects use similar set-ups for their wikis & documentation.'
|
||||
image: https://i.imgur.com/6abIIsy.png
|
||||
---
|
||||
|
||||
by @luxumbra
|
||||
|
||||
<details>
|
||||
<summary>🤔 Wait, WhoTF is @luxumbra!?</summary>
|
||||
<br />
|
||||
luxumbra is a builder and a community focused resident of MetaGame. He can be found in Discord or on Twitter as @bdgrdev.
|
||||
</details>
|
||||
|
||||
<br />
|
||||
|
||||
<details>
|
||||
<summary>WTF is Git?!</summary>
|
||||
<br />
|
||||
|
||||
Git is (pretty much) the industry standard software for tracking changes in any set of files. Usually used for coordinating work among developers who are collaboratively developing source code in the software development industry.
|
||||
|
||||
In MetaGame, we use it on the wiki (among other places) for updating the content and making updates to the code. The former is what we will be looking at here.
|
||||
</details>
|
||||
|
||||
<br />
|
||||
|
||||
<details>
|
||||
<summary>Git is not GitHub.</summary>
|
||||
<br />
|
||||
GitHub is the worlds biggest software development platform. 3 million organisations store their code and project files in Git repositories hosted by GitHub.
|
||||
|
||||
Developers and the more tech focused folk will reach for the GitHub Command Line Interface (CLI) but rest assured, there's other ways to use it without needing a degree in Computer Science. :smile:
|
||||
</details>
|
||||
|
||||
## Get your Git on
|
||||
As a non-builder you're unlikely to know WTF a 'terminal' or 'command line interface' is ([WTF even is 'terminal'?!](https://www.pcmag.com/encyclopedia/term/terminal-window)); let alone feel at ease running commands in one, so I won't go into that. Luckily for you, there's a handful of decent desktop applications that'll make using Git a lot less painful.
|
||||
|
||||
This Playbook focuses on contributing to the MetaGame wiki, but the core concepts can be applied to any repository you want to contribute to. Most DAOs & projects use similar set-ups for their wikis & documentation.
|
||||
|
||||
> If you're completely new to Git itself, it is recommended to get a bit of a grounding with that before you start contributing to projects and such. Here's a couple of handy articles on this very subject: [Basics of Git](https://docs.github.com/en/github/getting-started-with-github/using-git) & the [Git Book](https://git-scm.com/book/en/v2/Getting-Started-The-Command-Line)
|
||||
|
||||
> Also note: When contributing to MetaGame, to avoid potential gaming of XP please use the correct workflow for adding content. Write your post in Notion or [HackMD](https://hackmd.io/) and submit it for feedback & review. Once it has received the go ahead and requires no more edits, then you're good to submit it to GitHub. What we do not want is people making commits for small typos through the feedback phase and gaining XP for these micro edits.
|
||||
|
||||
With no further ado, here's How to Git on GitHub as a non-builder:
|
||||
|
||||
### 1. Go get an account on [GitHub](https://github.com/)
|
||||
It is free and takes a jiffy.
|
||||
|
||||
### 2. Get the required apps
|
||||
If you don't know the command line, download and install a desktop app for Git (this guide focuses on GitHub Desktop). If you do know Command line, there will be another playbook for you...soon:tm:
|
||||
|
||||
Recommended app for starters:
|
||||
[GitHub Desktop - Mac/Win](https://desktop.github.com/)
|
||||
|
||||
Alternatives to try:
|
||||
[GitKraken - Mac/Win/Linux](https://www.gitkraken.com/)(Free for basic use or $4.95p/m for the Pro)
|
||||
[Tower - Mac/Win](https://www.git-tower.com/)(Not free but a pretty UI for $69p/y)
|
||||
|
||||
|
||||
You will also need a text editor or ideally a free code editor like [VSCode](https://code.visualstudio.com/download) that will enable you to see all of the projects files and edit them with much clearer formatting than a simple text editor. *Word, Google Docs or other desktop publishing apps will not work for this purpose*.
|
||||
|
||||
> If you get stuck, hop into [#!?-ask-anything](https://discord.gg/5vhfXtZ9g2) on our Discord or DM myself and I will do my best to help.
|
||||
|
||||
So, once you've installed a desktop app for GitHub and for editing the files...move on the the next step. :point_down:
|
||||
|
||||
### 3. Login to GitHub via the GitHub Desktop app
|
||||
|
||||
|
||||
If this is your first time using the app, you will see the Welcome screen and the sign in button.
|
||||
|
||||
|
||||
|
||||
Once you've logged in and authorised the app, you will see the Configure screen. Select the email address you want to be associated with your Git activity and hit 'Finish'
|
||||
|
||||
### 4. Clone / Fork the repository
|
||||
Now you're signed in, you can copy (clone or fork) the repository you are going to be working on.
|
||||
> Copying a repository is called 'cloning' or 'forking'. Forking is used when we don't have full access to a repository.
|
||||
>
|
||||
For the purposes of this Playbook, we will be *forking* the [MetaFam wiki repository](https://github.com/MetaFam/metagame-wiki) and adding a new page.
|
||||
|
||||
|
||||
|
||||
#### Select "Clone a repository from the internet..."
|
||||
Wait, weren't we just *forking*?! Yes, but we *clone* initially and will set-up our *fork* a bit later. :smile:
|
||||
|
||||
|
||||
|
||||
Select the 'URL' tab, enter either the GitHub name of the repo or the URL of the repository you wish to work on (`metafam/metagame-wiki` or `https://github.com/MetaFam/metagame-wiki`), choose a local directory to download to and click 'Clone'.
|
||||
|
||||
*Don't forget where you selected, so you can find it later*.😆
|
||||
|
||||
|
||||
|
||||
This will 'clone' the project's repository to the folder you selected on your computer.
|
||||
|
||||
### 5. Create a new branch from `master`
|
||||
|
||||
Once the repo has finished downloading, make sure the 'Current branch' selected is `master` and go to `Branch > New Branch...` in the app menu.
|
||||
|
||||
|
||||
|
||||
Enter your branch name with a name like `content/adding-git-playbook` (using this format helps to organise all branches of a specific type in Git, a bit like folders) and hit 'Create branch'.
|
||||
|
||||
|
||||
### 6. Adding content
|
||||
Now you have a branch to work on you can open up the project in an application like VSCode to make your changes.
|
||||
|
||||
|
||||
|
||||
Go to `File > Open folder` and navigate to the location you selected earlier when we cloned the repo and open the folder in your editor. If in VSCode, you are safe to "Trust the authors" if it asks you.
|
||||
|
||||
|
||||
|
||||
As you can see in the image, there's a ton of folders & files here. Don't be intimidated, if you mess something up, there's no possible way you can mess up the original codebase. If you do accidentally delete everything, you can always checkout the `master` branch again and start over with a new branch or clone.
|
||||
|
||||
#### Creating a new page
|
||||
Navigate to `docs/playbooks` and take a look at the files already there. Open one. We will use this as a template.
|
||||
|
||||
Once opened, go to `File > Save as...` or you can use the shortcut `Ctrl+Shift+S` (Win) / `Cmd+Shift+S` (Mac) to save the file as a new file. A pop up will appear asking you to give your file a name.
|
||||
|
||||
|
||||
|
||||
Ensure you use 'kebab casing' when naming the file - use hyphens in place of spaces and *all lower case letters* eg: `how-to-git`. Make sure 'Markdown' is selected in the 'Save as type' field. You shouldn't need to add an extension but if you do, use `.md`. Click 'Save'.
|
||||
|
||||
> :warning: At this point, look at the files in VSCode and check the name of the file you just created has the `.md` extension at the end. If it doesn't, right click the file in VSCode and select 'Rename' in the context menu and add in the `.md`. Without it, the wiki build will fail.
|
||||
|
||||
|
||||
|
||||
Now, remove the contents of the file **except** for the 'Frontmatter' at the top, that is what is between and including the triple hyphens `---` and replace the title with your own, and for consistency's sake, use the 📚 emoji as in the example.
|
||||
|
||||
|
||||
|
||||
While you're in the Frontmatter, you can also add in image and description properties, which will be displayed as a preview when sharing the URL to your post in Discord, Twitter and other social networks.
|
||||
|
||||
|
||||
|
||||
Add your content using [markdown syntax](https://www.markdownguide.org/cheat-sheet/) or using basic HTML such as `<h2>, <h3>, <p>, <a>, <img/>`.
|
||||
|
||||
>Please do not use the `<h1> or #` level 1 headings in your post as there should only be one of those on the page and it will be generated automatically from the `title` property in the Frontmatter.
|
||||
|
||||
> ℹ️ If you press `Shift+Ctrl+P`/`Shift+Cmd+P` in VSCode and type 'preview', you will see 'Markdown: Open preview...'. That will give you a preview to check how your file looks when parsed - Handy for checking your links and images are not broken.
|
||||
|
||||
#### Edit `sidebars.js`
|
||||
Next, - this is critically important when working on the MG wiki! 😱 - You need to add a reference to your new file in the `sidebars.js` file in the root of the project. The sidebars file is used to create the main menu for the wiki and your page will not display correctly if it is not added.
|
||||
|
||||
|
||||
|
||||
Open `sidebars.js` and find where you need to place the reference to your page. For this example, we want to add to the 'Playbooks' section as highlighted in the image above.
|
||||
|
||||
|
||||
|
||||
Add your entry below the others - pay close attention to how you named your new file as it needs to match in the sidebar file. **Do not** include the file's `.md` extension in the sidebar. Make sure to leave a `,` at the end of the new line, eg; `"playbooks/how-to-git",`. Also check there is a `,` at the end of the line above or the wiki build will not work. :cry:
|
||||
|
||||
Once you are happy, save the file and return to the GitHub desktop app where you will see the changes you have just made. :smile:
|
||||
|
||||
### 7. Commit & publish to GitHub
|
||||
|
||||
|
||||
Here you see your changes - the green plus icon denotes a new file, and the amber dot an existing file with edits. The right hand pane shows you the edits that were made for the selected file.
|
||||
|
||||
#### Fork it
|
||||
|
||||
|
||||
|
||||
If you are not yet a member of the MetaFam organisation in GitHub, there will be a warning that you do not have access to the upstream repo - in this case the **metagame-wiki** repo - and a link to 'create a fork'. Click the 'create a fork' link. *Now we're forkin'!* :eyes:
|
||||
|
||||
> A fork is what we want because we will be using this branch to contribute to the original 'upstream' repository. As you may not be a member of the organisation in GitHub, you need to push your changes to your own GitHub account, and then create a Pull Request to be merged into the original, upstream `master` branch.
|
||||
|
||||
|
||||
|
||||
Next click the 'Fork this repository' button in the subsequent pop up.
|
||||
|
||||
|
||||
|
||||
On the next screen, Select 'To contribute to the parent project' and hit Continue.
|
||||
|
||||
|
||||
|
||||
Double check your changes and if happy, add a summary of your update and a longer description in the form at the bottom left of the screen. When done, hit the commit button.
|
||||
|
||||
Once committed, and before we publish (or 'push') our branch, we should check for and 'pull' the latest updates from the MetaFam repo (upstream) to ensure your branch is in sync and to reduce the chance of conflicts when we create our pull request.
|
||||
|
||||
|
||||
|
||||
Switch to the `master` branch and click 'Fetch origin'. This will update your repo with any updates from the MetaFam repo.
|
||||
|
||||
|
||||
|
||||
Next, we need to 'rebase' `upstream/master` onto our branch. So switch back to your branch and go to `Branch > Rebase curent branch...`
|
||||
|
||||
|
||||
|
||||
In the popup, type 'master' into the search field and select `upstream/master`, if there are updates, there will be a yellow dot as opposed to a green tick, if there are no updates. *The rebase button will be disabled if there are no changes*.
|
||||
|
||||
If you have updates, click the 'Rebase' button. If that goes smoothly, you're ready to publish and make a new pull request. :raised_hands:
|
||||
|
||||
#### Publish and make a PR
|
||||
|
||||
|
||||
|
||||
Hopefully, there won't be any issues and you are now OK to publish your branch and get a pull request underway. Click 'Publish branch'.
|
||||
|
||||
|
||||
|
||||
Once published, you will see 'Create pull request', so hit that and you will be taken to the GitHub website to continue the PR process.
|
||||
|
||||
|
||||
|
||||
Enter the details of the PR in the form, if not sufficiently covered by the commit message
|
||||
|
||||
|
||||
|
||||
Select the dropdown arrow in the green 'Create pull request' button. Select 'Draft pull request'.
|
||||
|
||||
|
||||
|
||||
We want it to be a draft initially so we can make sure the updates have no issues and check the deployed preview site *before* the PR is opened for review.
|
||||
|
||||
|
||||
|
||||
Once the draft is created, notice the checks that are running; displayed below your comments on the page. Pay particular attention to the 'Vercel' one. Vercel is where we host the wiki and it deploys a preview site on every PR and on any further updates to the PR, so we know our update won't break anything.
|
||||
|
||||
> If the tests fail, panic not. There will either be conflicts (shown at the bottom of the PR page), or an error in the page or sidebars file. If it is conflicts, make sure you have updated your branch with the latest from `master`, from within the GitHub desktop app, and then push the updated branch again. If it's not conflicts, double check the Frontmatter in the page you're adding is free of errors or check for a missing `,` or `"` in the `sidebars.js` file. If you get stuck, feel free to tag me (@luxumbra), @chair, or @baconaetor in the PR comments (or find us in Discord), and we will help you get it sorted.
|
||||
|
||||
|
||||
|
||||
Once Vercel has deployed your preview, you will see the tests turn green. You can view the preview by clicking the 'Details' link in the last item of the checks list. The one that ends with `/deploy-preview`. This will open up the preview site for you to check out your handiwork. :raised_hands:
|
||||
|
||||
#### The moment of truth
|
||||
|
||||
|
||||
|
||||
Navigate to the page you added via the wiki menu to ensure the sidebar item and the new page you added are both as you expect. :heavy_check_mark:
|
||||
|
||||
|
||||
|
||||
If all is well, return to GitHub and move the draft PR to an open PR ready for review, by clicking the 'Ready for review' button.
|
||||
|
||||
|
||||
|
||||
Your PR is now 'Open' and you will notice that the checks section now shows 'Review required' and below that, 'Merging is blocked' in red. This is because all PRs must be reviewed & approved by at least one team member before they can be merged into the `master` branch in the main repository.
|
||||
|
||||
> For MetaGame, the best way to notify of your PR is to hop into [our Discord](https://discord.gg/rMa8Ahtv5u) and post the URL for the PR in either the #writers-guild or #playbooks channels (For Player or Engaged Octos), #ask-anything if you're not yet onboarded. Someone will get to reviewing your PR. :pray: For other DAOs and projects, their Discord is probably a good place to let them know of your contributions.
|
||||
|
||||
...and you're done!! 🥳 Congratulations, you levelled up! :beers: Let's hope this is the first of many pull requests on your journey through the Metaverse. 🎉
|
||||
49
docs/playbooks/how-to-join-a-dao-community.md
Normal file
49
docs/playbooks/how-to-join-a-dao-community.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: 📚 How to Join DAO Community
|
||||
---
|
||||
|
||||
by @Techniciann9ne
|
||||
|
||||
|
||||
- How non developers can make an impact in the dao space
|
||||
|
||||
Find out where your DAO of choice meets the most.
|
||||
For example, some DAOs are most active on Telegram, some on Discord, and others on Github.
|
||||
|
||||
Learn the ins and outs and etiquette of that social media... or just sit back, say hi and hey great a lot, and get to know people and go from there.
|
||||
|
||||
If you identify a need, present a solution to people and ask for feedback. Oftentimes your ideas will trigger even better solutions from others who might be more familiar or have more experience with the situation. Always be ready to listen.
|
||||
|
||||
Some things you can just do. Sometimes useful data can be collected and shared.
|
||||
Some DAO's really need newsletters, or more newsletters, to keep people updated about projects and deployments and collaborations and such. In cases like this, provide a useful tool to the DAO without making a Big Deal about it. Everyone is busy, and you are appreciated.
|
||||
|
||||
Communicate with people in other DAOs and understand how things are done elsewhere. Share thoughts and ideas with the original DAO, strive to create networks.
|
||||
|
||||
**First of all**, if you don’t have basic knowledge of what DAOs are, quickly jump to the following link to gain it - [What are DAO’s?](https://ethereum.org/en/dao/#what-are-daos)
|
||||
|
||||
Now now, dear Anon, considering that you have gained knowledge and are interested in joining DAO as a community person, this playbook is written to bring ease to the steps you are to take in the process of joining.
|
||||
|
||||
DAO’s are open, decentralized communities of like-minded people who are willing to contribute to an idea and join forces in building a new decentralized and better world for all of us to enjoy. That being said, no one expects you to bring a hard set of skills when joining DAO’s, but in fact, what everyone expects from you is that you are willing to contribute and make new friends while doing so.
|
||||
|
||||
For a start, it is enough that you are willing to learn, add value to the community by contributing, and that you love people in general.
|
||||
|
||||
So having that said, let’s jump to that number of steps which lies in front of you anon!
|
||||
|
||||
1. You have heard about a DAO and decided that it is the right choice for you.
|
||||
2. Find out where your desired DAO resides and is most active, e.g., Telegram, Discord, GitHub, to name a few. Bare in mind that some DAO’s require you to fill out a membership proposal form. The forms can be on the DAO's website.
|
||||
3. At this point, you have joined a channel where your DAO operates or granted an invite based on your proposal, thus landed in the community chat.
|
||||
4. Greet the community, and don’t be shy to introduce yourself. Tell the community how you found out about it, what inspired you to join. In brief, let the community know what kind of person just joined, and do not hesitate to express yourself.
|
||||
5. The new people start their journey in most DAO’s by finding the role channel and assigning themselves the roles related to skills they can carry out.
|
||||
*E.g., considering that you are a community person, seek something that you can relate to, in most cases, that can be a Community moderator (Innkeeper-TaverKeeper), Writer, Shiller.
|
||||
**As a Community mod**. - you will be responsible for taking care of the community, welcoming, and helping new people to start their journey. Take care of community well-being and love people in general.
|
||||
**As a Writer,** you can write some cool content that will add value to the community, either to keep everyone inside on the same page or to provide something that can be shared over the Social Media channels.
|
||||
**As a Shiller** - seek interesting content about the community you are in. You can basically start with sharing, retweeting, and bumping other people’s threads, as your work is to spread word and awareness about your DAO.*
|
||||
6. Seek out the materials your DAO has made available for further knowledge expansion.
|
||||
7. Check/ask for the meeting calendar and make sure to attend meetings related to your role and community meetings that are very important and will let you connect with the community much faster.
|
||||
8. Start checking what’s happening inside the community, look at what's going well, and what might need improvement to benefit the community. Your ideas and feedback are valuable thus most welcomed. If the ideas and feedback can’t be implemented, they might trigger more experienced people in the DAO who will improve it, **so don’t hesitate to raise your voice.**
|
||||
9. Now you are probably wondering what should I do, as no one will tell you what to do, that is just how DAO’s work! All of the work you do and your contribution is based on your intuition. - *observe, notice, do, propose, implement, get the incentives.*
|
||||
Seek smaller quests/evergreen - those are usually there to help you start in the DAO space. However, as you have gone through the onboarding process, you can just do some things: jump to the welcoming channel and help other people get started, greet them, try to answer their questions, and be welcoming and communicative. See what kind of content is necessary for the DAO. Try writing something useful, whether it is a newsletter or playbook, something you have learned about, summarize it into a text so that others coming after you can learn from it.
|
||||
|
||||
*Pro tips: Be active, be responsive, communicate and connect with other members of DAO, attend meetings, provide ideas and feedback - don't forget to implement. NEVER STOP LEARNING, because the more we learn, the more we grow.*
|
||||
|
||||
If you identify a need, present a solution to people and ask for feedback. Oftentimes your ideas will trigger even better solutions from others who might be more familiar or have more experience with the situation. Always be ready to listen.
|
||||
114
docs/playbooks/understanding-impostor-syndrome.md
Normal file
114
docs/playbooks/understanding-impostor-syndrome.md
Normal file
@@ -0,0 +1,114 @@
|
||||
---
|
||||
title: 📚 Understanding Impostor Syndrome
|
||||
---
|
||||
|
||||
by @Gnomeski
|
||||
|
||||
## What is Impostor Syndrome (IS)? 🤔
|
||||
|
||||
The context here is that in the brave new world of Web3 DAOs, everything is new. People frequently find themselves doing new things, in a new context, and sometimes with unclear expectations of how something should be. Added to this, most work is carried out asynchronously and remotely, with limited forms of communication. All of this can add up to potentially higher chances of IS rearing its head. 🐍
|
||||
|
||||
IS is a common syndrome consisting largely of false self perception and insecurity. IS is an issue with projections of Self not matching ability.
|
||||
|
||||
Either
|
||||
|
||||
- Ability is below that which we believe it should be, and we feel bad about this dissonance. Although we fear our incapability is transparent, we work to live up to our aspiration and hope no one notices the difference.. all the while suspecting that they do. 😬
|
||||
|
||||
Or
|
||||
|
||||
- Our self perception is lower than our actual ability. Despite doing well at our tasks and receiving good feedback, we dismiss these acknowledgements as by-products of hard work (that anyone else could have done) or maybe as politeness, as encouragement to improve, or even a form of pity. We are, as a result, never satisfied and may suspect others are not being genuine with us.✋
|
||||
|
||||
These projections can come from ourselves, our histories and upbringing or from the culture we currently find ourselves in. This insecurity typically manifests in an ongoing ‘cup half empty’ feeling of inadequacy and quiet desperation. This can cause anxiety and low self-esteem and/or over working.
|
||||
|
||||
We will explore it further below by looking at signs, beliefs, cultural influences, aggravating factors and possible solutions. ✔️
|
||||
|
||||
Initial impressions of how it feels...
|
||||
|
||||
- You feel like a fraud.
|
||||
- You worry people will, or already do, see through your ‘charade’ and realise you are tricking them. You do not belong where you are really.
|
||||
- Any signs of success or appreciation come from dumb luck, hard work anyone could do, or charity/pity on the part of others.
|
||||
- Others perceive you as being more competent than you are and it is just a matter of time till disappointment and resentment arise from this sorry situation…
|
||||
|
||||
## Who is prone to IS? 🤷🏽♀️
|
||||
|
||||
Me, them, anyone! First thought to be associated with perfectionists and women more than men, research on imposter syndrome has since debunked these myths.
|
||||
|
||||
All of us humans experience times of doubt. In DAOs, freedom and lack of structure can be greater, creating extra room for anxiety and neurosis. Increased room for interpretation and individual choice can also give rise to greater self doubt. This is a flip side of the opportunities such community structures provide for us. ☯️
|
||||
|
||||
## Wait, are you actually an Impostor? 😱
|
||||
|
||||
Unless your aims are to secretly extract value unfairly from a situation, while offering little in return (think thief or parasite), then the answer is simply **NO**, YOU ARE NOT AN IMPOSTOR!
|
||||
|
||||
Easy to say and yet, the feeling can persist. It is often deeply rooted in the mind as conditioning— as the saying goes “what we resist, persists.” So let us look at how this can play out.
|
||||
|
||||
Here is a [basic 10 minute test](http://impostortest.nickol.as/) for Impostor Syndrome to maybe help get some idea.
|
||||
|
||||
### Signs of IS 👩⚕️
|
||||
|
||||
- You attribute successes to forces outside your own control.
|
||||
- You criticise your own mistakes to the point of minute detail but are very sensitive to any outside criticism even if it is helpful.
|
||||
- You self deprecate frequently.
|
||||
- You often question whether you are capable.
|
||||
- You fear being discovered as ultimately ‘no good’.
|
||||
- You have trouble feeling that you belong.
|
||||
- You often compare your performance to that of others.
|
||||
- You see seeking support as incompetence and burdensome weakness.
|
||||
- You believe things should be perfect, and this can only be achieved by putting massive pressure on yourself. You must always focus on the negatives or risk becoming complacent. “Contentment is mediocrity.”
|
||||
- You feel unconsciously inadequate and thus compelled to push yourself more and more into over working. “See! I cannot be an impostor, just look at how hard I work.”
|
||||
- No matter how well you are doing, it can always be improved upon… nothing brings lasting satisfaction.
|
||||
- You believe you should ‘know stuff’ naturally and already be able to do things excellently, that you should be innately gifted.
|
||||
- If you cannot sort something out by yourself, then you cannot count it as being a success of your own.
|
||||
- Not risking taking work on is better than being seen as a failure. “It must be perfect or not done at all”.
|
||||
|
||||
A few of the kinds of internal messages we might tell ourselves..
|
||||
|
||||
- ***Validation through achievement is what I need to be accepted and loved.*** 🙏🏿 This can become like an addiction. Workaholism may result from spending too much time on a job, never feeling it is complete and maybe even making a loss as a result of freelancing or self-employment.
|
||||
- ***I do not fit the model of a person that is successful, I am destined to be a loser. 😞*** In DAOs anyone can be of high value. Being white, male, comfy background and well educated, is no longer a measure of anything.. This is the beauty of these spaces, your value can increase, whoever you are. Minorities IRL may still carry some undermining conditioning and be more prone to these doubts, that they will always be held back. These doubts can then play out, sabotaging our self belief and fulfilling the neggy narrative in a vicious feedback loop of doom! DAO's typically operate both virtually and pseudonymously, so it's easy to contribute without other's possible biases playing out.
|
||||
- **I should be better than this, I have no excuse**. 😳 If you are from a ‘successful demographic’ you may feel greater pressure to know what you are doing and do it perfectly… this may have been projected onto you by family, teachers etc
|
||||
|
||||
If this is the case it is no surprise you feel under too much pressure or never good enough..
|
||||
|
||||
## What makes it worse? 🤕
|
||||
|
||||
Certain situations can spark IS more so.
|
||||
|
||||
- You have assumed a new role/undertaken an unfamiliar project recently (which often happens in DAO spaces).
|
||||
- Your online ‘Avatar Self’ projects your aspirations to others, rather than your current reality and the two do not match.
|
||||
- You have no belief in your ability to realistically assess your own abilities objectively, and it is hard for others to do so at a distance.
|
||||
- You have bouts of Social Anxiety.
|
||||
- Your expectations exceed your current abilities.
|
||||
- Worsened by competitive environments, feeling unsupported leads to fear of being a burden and a reluctance to be seen as vulnerable or struggling.
|
||||
|
||||
## Cultural Influences 🌍
|
||||
|
||||
Others may project onto us expectations or perceptions of us which are beyond where we currently are. We may accept these perceptions as a condition of belonging. This can be a collusive unconscious group dynamic enabling all participants to avoid honest and humble self acceptance that can actually cause systemic failures to occur due to the inaccuracy of this type of ‘group hallucination’. The event of systemic failures can make everyone feel like an impostor, which is highly uncomfortable and can begin a highly destructive blame game, eventual scapegoating and a return to the start of another cycle of denial, aspiration and quiet desperation…
|
||||
|
||||
Another factor would be if we were brought up with negative messages that we are not good enough etc
|
||||
|
||||
PLEASE REMEMBER YOU MAY WELL HAVE A PSYCHIC HANGOVER FROM COMPETITIVE, CAPITALIST, CONDITIONING! 💰💩💰
|
||||
|
||||
The Old World socio-economic demands and pressures to conquer through competitiveness and confidence can manifest as something called the Dunning-Kruger effect. Watch this [4 minute TED Talk](https://www.ted.com/talks/david_dunning_why_incompetent_people_think_they_re_amazing/transcript?language=en#t-244176) to see how this can play out in different ways. 👁️
|
||||
|
||||
1. People with little ability/knowledge in an area have an inability to acknowledge this lack (embarrassment, ignorance?) and bandage over the weakness with false positive, sometimes grossly inflated self perception. Realising part of you has been operating like this can cause IS to arise.
|
||||
2. People with moderate abilities/knowledge in an area are all too aware of just how much they do not know (a little knowledge is a dangerous thing, to the self). This will be the majority of us, our awareness of our own current limitations are seen as embarrassing inadequacies and character flaws which mean we are really ‘no good’.
|
||||
3. Experts in an area suffer Solipsism, that is, a belief that everyone else understands something as well as they do. This can encourage negative expression in the first 2 types.
|
||||
|
||||
## What to do about IS? 💊
|
||||
|
||||
- Do not judge yourself for feeling like an Impostor, just notice the feelings and allow/welcome them, so you can learn more where they come from. 👂
|
||||
- Share what you are feeling with someone you trust. 💞
|
||||
- Know that up to 70% of people are estimated to experience bouts of IS. 📈
|
||||
- Contemplate that people who do not experience IS are also not statistically any more successful than those that do and vice versa! 🤔
|
||||
- Create or find a culture that is warm and nurtures self knowledge, acceptance, honesty, openness and learning. 🏠
|
||||
- Learn to accept and ask for constructive criticism. 🎓
|
||||
- Developing skills and knowledge can help us realise where we formerly had something missing. This awareness itself can make us more accepting of the fact that we likely have more holes in our knowledge and abilities and this is OK and a normal part of learning and ‘being a work in progress’. 📚
|
||||
- If you are projecting an image that is ahead of your abilities, then dial it down to match where you actually are presently in your journey, get learning and levelling up. 🎭
|
||||
- If you suspect people who compliment your efforts or you downplay them frequently, then you may need to dial up your perception of your abilities and achievements. 👑
|
||||
- If you feel comfortable sharing your feelings more widely, this may help others struggling with the same issue. The more people share the less power these kinds of alienating complexes can isolate us and make us miserable. 📢
|
||||
- Return here and read this again if you are suffering; eventually the message might sink in! 🔁
|
||||
|
||||
The feelings of self sabotage and doubt of IS are isolating and while very common, if left unchecked they might, for some, be infectious to many different areas and relationships in your life. If they are serious and/or persistent, then Psychotherapy/Counselling is an excellent idea.
|
||||
|
||||
At the very least, reach out to someone you trust. Please be kind to yourself. 😇
|
||||
|
||||
|
||||
20
sidebars.js
20
sidebars.js
@@ -24,16 +24,12 @@ module.exports = {
|
||||
"enter-metagame/join-metagame",
|
||||
"enter-metagame/why-patron",
|
||||
"enter-metagame/how-to-become-a-player",
|
||||
// "enter-metagame/roles-in-metagame",
|
||||
"enter-metagame/navigation-board",
|
||||
"enter-metagame/leaderboard",
|
||||
//"enter-metagame/Chainlog",
|
||||
],
|
||||
'🤔 What we do': [
|
||||
"Guilding/metasys",
|
||||
"what-we-do/mymeta",
|
||||
// "what-we-do/events",
|
||||
// "what-we-do/metalibrary",
|
||||
],
|
||||
'🏡 The Great Houses': [
|
||||
'great-houses/how-to-house',
|
||||
@@ -41,10 +37,7 @@ module.exports = {
|
||||
'great-houses/house-of-daos',
|
||||
'great-houses/house-of-NFTs',
|
||||
'great-houses/house-of-dapps',
|
||||
// 'enter-metagame/guilds-of-metagame',
|
||||
'great-houses/house-of-defi',
|
||||
// 'great-houses/house-of-dapps',
|
||||
// 'great-houses/house-of-tokens',
|
||||
],
|
||||
"⚔️ Guilding": [
|
||||
"Guilding/meme-driven-organizations",
|
||||
@@ -54,20 +47,15 @@ module.exports = {
|
||||
"Guilding/building-successful-teams",
|
||||
],
|
||||
"📚 Playbooks": [
|
||||
"playbooks/browse",
|
||||
"playbooks/how-to-make-it-without-technical-skills",
|
||||
"playbooks/how-to-coach-eth",
|
||||
"playbooks/how-to-hackmd",
|
||||
"playbooks/entering-daos-as-a-writer",
|
||||
"playbooks/become-a-buidler-on-ethereum-by-austin-griffith",
|
||||
"playbooks/how-to-play-twitter-by-visa",
|
||||
// "playbooks/how-to-not-get-hacked",
|
||||
// {
|
||||
// type: "subcategory",
|
||||
// label: "The good books",
|
||||
// ids: ["playbooks/how-to-make-it-without-technical-skills"],
|
||||
// },
|
||||
// 'resources/alignment2021',
|
||||
"playbooks/understanding-impostor-syndrome",
|
||||
"playbooks/how-to-join-a-dao-community",
|
||||
"playbooks/how-to-git-on-github-non-builder",
|
||||
],
|
||||
"🌳 Other": [
|
||||
"resources/calendar",
|
||||
@@ -76,8 +64,6 @@ module.exports = {
|
||||
"resources/art",
|
||||
"resources/memes",
|
||||
"resources/talks",
|
||||
// 'resources/alignment2021',
|
||||
],
|
||||
// "About The Wiki": ["style-guide", "mdx"],
|
||||
},
|
||||
};
|
||||
|
||||
Reference in New Issue
Block a user