diff --git a/README.md b/README.md index 402304f..7ddb876 100644 --- a/README.md +++ b/README.md @@ -1,89 +1,489 @@ -# dwyl apprenticeship +
-Everything you need to know about -dwyl's creative technology apprenticeship! +# [@dwyl](https://github.com/dwyl) Apprenticeship in Creative Technologies -## Why? + + + + +Everything1 you need to know about +dwyl's Apprenticeship in Creative Technologies ("ACT"). + +> 1Our aim is to capture +the answers to _all_ questions +relating to the apprenticeship +in this repository.
+If you have any unanswered questions +or _anything_ is unclear, +_please_ open an [issue](https://github.com/dwyl/apprenticeship/issues)!
+We _know_ this repo not perfect and we _need_ your help to make it better. + +
+ + -_Most_ companies/organisations only (_want to_) hire -people who _already_ have "_years_" of experience -and not _invest_ in training `new` people. +## _Why_? + +_Most_ companies/organisations only (_want to_) hire +people who _already_ have _years_ of experience. +Managers rationalise +that it's too expensive and time-consuming +to _invest_ in training people +who have little or _zero_ work experience. On the _surface_ it can be _tempting_ to only -hire "_experienced_" people for technical teams; -after all someone _else_ has paid for their past "mistakes" -and they have practiced their craft for "_years_", -so they are more likely to get the work done faster, right? +hire _experienced_ people for technical teams; +after all someone _else_ has paid for their past mistakes (_learning_). +Experienced people have practiced their craft for _several years_, +so they are more likely to get the work done faster, _right_? +_Evidence_ suggests it makes a _lot more_ sense +to have a _mix_ of _both_ experienced +and people with a fresh perspective on a team. + + +The purpose of @dwyl's Apprenticeship +is to help people +gain real-world experience +while developing the skills +necessary to operate effectively in the +[creative industries](https://en.wikipedia.org/wiki/Creative_industries). +Our objective is to give people the _opportunity_ +to learn creativity, communication, +teamwork and technical skills in a real world environment. + -### Our + + + + +### Our Hypothesis At dwyl we hypothesize that it's _more effective_ to train people _from scratch_ -because of the following reasons: -+ Gives people who are new to the industry a start. -+ Avoids bad habits (_like un-tested or un-documented work!_) -+ Instills the habit of continuous learning _early_ +because: ++ It gives people who are new to creative tech a start +they would not otherwise get. + + Getting a _start_ in creative tech is the _hardest_ part. + @dwyl will help you _leap_ over the first barrier. ++ People who are `new` tend to have a +["beginners mind"](https://en.wikipedia.org/wiki/Shoshin) +and are more "_teachable_". ++ Avoids having to unlearn bad practices (_like un-tested or un-documented work!_). ++ Instills the _habit_ of continuous learning _early_ in the person's journey thus avoiding "_senior syndrome_" (_where people feel they already know everything!_) -+ New people tend to have a ["beginners mind"](https://en.wikipedia.org/wiki/Shoshin) -and are more "_teachable_" -+ more likely to pass on their knowledge to teammates (_whereas most "senior" people "hoard" their knowledge our of fear of being replaced!_) ++ They are more likely to pass on their knowledge to teammates +(_whereas most "senior" people "hoard" their +knowledge out of fear of being replaced +or as a bad habit!_) + + + +## _What_? + +An **apprenticeship** is a **system** of training people +who are **learning** how to do a job which needs **special skill**.
+see: +[wikipedia.org/wiki/Apprenticeship](https://simple.wikipedia.org/wiki/Apprenticeship) + +***ACT*** is an ***intensive learning*** program +covering several areas that are relevant +to working in the creative industries. +Some of the skills are "life skills" +that are _essential_ for operating effectively +both as an individual and as a member of a team in any organisation. +Other skills are technical and _specific_ to a particular role in a team. +We encourage _everyone_ to learn the fundamentals in _all_ skills +before choosing their preferred ones to _master_. + +Some of the skills include: + +### 1. Personal Effectiveness + +[@dwyl's mission](https://github.com/dwyl/start-here/blob/master/mission.md#what-is-dwyls-mission) +is to +"_Empower people to maximise effectiveness, creativity and happiness._"
+Maiximizing your personal effectiveness +is the _first_ step toward achieving your potential. +Our [App](https://github.com/dwyl/app) - +which you will _contribute_ to during your ACT - +is designed to help you build and track the habits +necessary for creative excellence. +There are _many_ ways you can contribute +way more than designing UX or writing code! +For now simply focus on the fact that you +will be improving your personal effectiveness +in a _systematic_ way. +You will be tracking and managing your time and energy +to ensure you are applying yourself +and working on the tasks that actually +move you toward your goal(s). + + + +### 2. Creativity + +Creativity is the use of imagination or ideas to create something. +https://en.wikipedia.org/wiki/Creativity
+Creativity is central to everything we do @dwyl +and we are all _constantly_ being creative. +There are _many_ ways of being creative, +the first step is simply to _think_ +that you _can_ be creative! +If you _already_ feel that you are creative +and want a chance to develop your ideas and creative skills, +please contact us! +We need creative people who want to _make_ things! + +If you are stuck thinking you are _not_ creative, +we suggest +[dwyl/**learn-creativity**](https://github.com/dwyl/learn-creativity/issues/7) +as a starting point. + +### 3. Communication + +One of the most valuable transferrable skills +anyone can learn and _apply_ to any area of their life/work +is _communication_. + + ++ [x] **Asking questions**! +If you _aren't_ asking questions you aren't learning. It's really _that_ simple. ++ [x] **Writing** - capturing _everything_ you learn. +Enhancing/improving/editing @dwyl's _extensive_ library +of learning guides and tutorials. ++ [x] **Sharing** what you are thinking +_especially_ when you see an area for improvement! ++ [x] ***Informing*** your teammates of what you are working on +by consistently updating the task tracker +(_e.g: with update comments on a GitHub issue_) +has multiple benefits which compound over time. ++ [x] **Visual** communication including graphics and ***video***. + +### 4. Collaboration + +
+ + + +
+ +How to work with other people in a team both in-person and remote. +This is an incredibly valuable transferrable life skill +that everyone should master. +See: https://github.com/dwyl/remote-working + + +### 5. UX/Design Thinking + + + +You don't have to _label_ yourself as a "designer" or go to college for 4 years +in order to _think_ like a designer. You just have to _observe_ the world +and think: "_is this **user-friendly**?_" + +![steve-jobs-design-is-how-it-works](https://user-images.githubusercontent.com/194400/72974694-5f026480-3dc7-11ea-9d82-e89165f48d49.jpg) + +There are plenty of examples of both good and bad design around us. +You have the _opportunity_ to improve the world +and the experience of your fellow humans through design. +What can be more _exciting_ than that? + +Read: ++ https://en.wikipedia.org/wiki/Design_thinking ++ https://en.wikipedia.org/wiki/User-centered_design ++ https://uxplanet.org/user-centered-design-process-and-benefits-fd9e431eb5a9 ++ https://99percentinvisible.org/article/norman-doors-dont-know-whether-push-pull-blame-design/ + + +### 6. Code + +#### _“Everybody should learn to program a computer,
because it teaches you how to think.”_ ~ Steve Jobs + +We think _everyone_ should learn how to (read/write/understand) code +because it teaches you to think systematically +and break down problems into small chunks. + +[![image](https://user-images.githubusercontent.com/194400/71601935-a6416080-2b4d-11ea-9ad9-70bd5ada490e.png "Photo by Kevin Ku")](https://unsplash.com/photos/w7ZyuGYNpRQ) + +@dwyl we write code to make useful things for real people.
+ +We do not expect _all_ the people +doing the Apprenticeship to write code for their _career_. +But technology and code are at the _centre of what we do @dwyl_ +(as well as the world we live in) and we have found that +knowing how to code is an ***essential skill*** +to **working effectively** here. + -## What +#### “_Whether you want to uncover the secrets of the universe, or you just want to pursue a career in the 21st century, basic computer programming is an essential skill to learn_.” ~ Stephen Hawking -**4 weeks** of ***intensive learning*** and ***building*** technology products -with _great_ UX and code quality! ## Who? -Anyone who has not worked as a "developer" before and wants to get started! +Anyone _**over 18** years old_2 +who has +***either*** not worked in creative tech before +and wants to get started, +***or*** people who have worked in tech +and want to explore a different path. + +The apprenticeship is for self-motivated people +who are eager to **learn _fast_ and _make_ things**!
+If you are _not already_ motivated +to learn _independently_, +please +[do _not_ apply](https://github.com/nelsonic/nelsonic.github.io/issues/318) +to ACT +until you learn to +[_apply_ yourself](https://english.stackexchange.com/questions/267667/apply-yourself). + + +> 2The reason for **minimum age** +for ACT is simple: +we don't want anyone quitting (regular) school, +[running](https://www.quora.com/Did-people-actually-used-to-run-away-and-join-the-circus-And-do-they-still-do-so-now) +[away](https://www.wikihow.com/Run-Away-With-the-Circus) +from home +and showing up on our doorstep! +We _encourage_ anyone/everyone +_under_ age 18 to start their creative tech learning journey +as soon as possible! +But _definitely_ "stay in school" +and learn everything you can, +because life is much easier +if you tick the box of "school" first and do it well. +If you are still in high school +and feel that your creativity +is _not_ being rewarded, +don't worry or lose hope, +it will be soon enough! + ## How? ### Prerequisites -+ Read (_and "star"_) `this` repo to show you have (_have read_) ++ **Read** (_and "star"_) `this` repo to show you have (_have read_) and are interested in the apprenticeship. -+ Read (_and "star"_) the dwyl contributing guide: ++ **Read** (_and "star"_) https://github.com/dwyl/start-here +to show you _agree_ with @dwyl's +[mission](https://github.com/dwyl/start-here/blob/master/mission.md#what-is-dwyls-mission), +[manifesto](https://github.com/dwyl/start-here/blob/master/manifesto.md) + and values. ++ ***Read*** (_and "star"_) the dwyl **contributing guide**: https://github.com/dwyl/contributing -to confirm that you have read and understood our "team workflow". -+ Previous contribution to a dwyl project -or tutorial(s): https://github.com/dwyl?utf8=%E2%9C%93&q=learn -(_a Pull Request with an improvement to the learning materials_) -+ Answer the "AMA" questions see: `/ama` +to confirm that you have read and understood our "**team workflow**". ++ ***Answer*** the questions see: +[start-here/**questions.md**](https://github.com/dwyl/start-here/blob/master/questions.md) ++ ***Contribute*** to a dwyl project +or tutorial(s) and show us you're putting your reading into practice with + https://github.com/dwyl?utf8=%E2%9C%93&q=learn +(_a Pull Request with an improvement to the learning materials_). +See: What is a "_Previous Contribution_" question/answer below. -


+### _Apply_! -## Way More Questions & Answers! +Send us an email: **hello@dwyl.com** with the subject: "Apprenticeship". +Describe _why_ you want to join our Apprenticeship program and +include a link to your GitHub profile. +We will take it from there. -### Q: What is a "Previous Contribution" to a @dwyl Project? +


+ +## Frequently Asked Questions & _Answers_! -Contribution to a dwyl project can range from: -+ asking a question (_seeking clarification_) in a GitHub Issue -+ reporting a bug/issue on one of our projects or tutorials -+ Creating a Pull Request that _fixes_ the bug/issue you reported -and or adds the question/answer to a relevant readme. ### Q: How long is a day? [asked by @ZooeyMiller in #2](https://github.com/dwyl/apprenticeship/issues/2) -Aim to start at 09:00. If you are prefer to start earlier, -just let someone know you are available/online! +You should aim to spend **6 hours** per day on _deep work_.1 +You are responsible for managing/tracking your time. +Divide your time between learning, researching, writing, coding, editing +and other creative work. +Aim to **start** your day no later than **08:50 GMT** +so that you are always "on time" +for the daily morning meeting. + +If you are prefer to start earlier, do it! +Some of us start our day at 06:00 so we get 3h +of focus time *before* 09:00! +Just let someone know you are available/online +and remember to track your time so you don't over-work. + +Six hours either sounds like _little_ +(_if you are used to working 12h per day at a minimum wage job_), +or a _lot_ if you have attempted to _focus_ without distractions for 6 hours. +You are _not_ expected to work _continuously_ for 6 hours. +You _are_ expected to keep _track_ of your time. + +> 1If you haven't yet read the book **Deep Work** by Cal Newport +make it a priority to read it and understand all the concepts +***before*** starting the ACT. + + +### Q: How to _Communicate_? + + +1. **GitHub** - GitHub is our +[single source of truth](https://en.wikipedia.org/wiki/Single_source_of_truth). +We have a _strong_ preference for communicating via GitHub. +This ensures that _anyone_ can see what everyone _else_ is learning +or working on and can _help_ when we get stuck. +If in doubt, open an issue in the repository you are working on. + + +2. Daily Standup Meetings - We have a +[daily standup meeting](https://en.wikipedia.org/wiki/Stand-up_meeting) +at **09:00** each day of the work week (_Monday - Friday_)
+_Everyone_ attends via **Zoom** video conference: +https://zoom.us/j/3371337133
+Join the call at **08:59**. + +> We keep our individual updates _brief_. +The point is just to describe in a few words what +you worked on the _previous_ day +and what your plan is for _today_. +We mention an issue number and project name e.g:
+"_Yesterday I worked on Autocomplete issue +[#224](https://github.com/dwyl/app/issues/224). +I realised that there is more work to do +before Autocomplete can work, +so today I am working on Basic tagging +[#245](https://github.com/dwyl/app/issues/224)_" + +> If you are _stuck_ with the task +you are _currently_ working on, +make that clear by writing a **comment** +in the issue you are working on +and draw people's attention to it in the standup. + +If for any reason you are _unable_ to attend the daily standup, +send a message with your update on the **@dwyl** Signal channel. + + +3. Signal - We use signal messenger https://signal.org +to _coordinate_ and ask "_logistical_" questions. +Signal is ephemeral so we _never_ use it +to ask technical questions, +those are _always_ asked/answered on GitHub +so that they're indexed by Google +and thus helpful to _everyone_. + + ### Q: How long is the apprenticeship? [asked by @ZooeyMiller in #2](https://github.com/dwyl/apprenticeship/issues/2) -Initially for 4 weeks. +Initially for **8 weeks**.
+Progress should be reviewed _weekly_. (_we need a system for this ..._)
+ +More details in the Apprenticeship Agreement. + + +### Q: What is a "Previous Contribution" to a @dwyl Project? + +Contribution to a dwyl project can range from: ++ **Asking** a question (_seeking clarification_) in a GitHub Issue + and **opening a PR** to add the answer/clarification to the relevant readme. ++ **Answering** a question on an _existing_ issue. ++ **Reporting** a bug/issue on one of our projects or tutorials _and_ ++ **Creating** a Pull Request that _fixes_ the bug/issue you reported +and or adds the question/answer to a relevant readme. + + + +### Q: What are the Potential _Outcomes_ of the Apprenticeship? + +There are four potential outcomes +ranging from disappointment to _delight_. + +1. ***`Nothing`*** - +people who do _not_ put in the _daily effort_ +will inevitably have _no outcome_.
+This is just a fact: “_Nothing will work unless you do_.” ~ Maya Angelou
+Do not fall into the trap of doing nothing and expecting miracles. +Ask questions every day. Learn continuously and _share_ your knowledge. +Trust that persistence is the key to success. + +2. **Job** with another org/company (_recommendation from @dwyl_) - +once you are confident in your skills and have a portfolio of work, +we _encourage_ everyone to _apply_ for a job that you _want_ to do. + +3. **Job** with @dwyl - +If you consistently go the extra mile to share what you learn, +ask/answer questions and contribute to the @dwyl projects/product, +you will be invited to become a core team member. +For now just focus on learning and sharing what you learn. + +4. **Start Up** - If you decide +that you want to work +on a particular idea/company/product, +discuss it with us! + + +### Got Questions? -> If you have _any_ questions which have _not_ -been answered here, [***please ask***!](https://github.com/dwyl/apprenticeship/issues) +If you have _any_ questions +which have _not_ been answered here, +[***please ask***!](https://github.com/dwyl/apprenticeship/issues) diff --git a/ama/README.md b/ama/README.md deleted file mode 100644 index 0819b02..0000000 --- a/ama/README.md +++ /dev/null @@ -1,22 +0,0 @@ -# Ask Me Anything! - -The purpose of the dwyl apprenticeship "AMA" -is for everyone in the team to get to know each other a bit. - -## Step 1: Clone the Repository & Create your Answers File: - -Please clone this repository, create a new file `{your-github-username}.md` -copy the contents of `TEMPLATE.md` - -in my case I ran the following: -``` -git clone https://github.com/dwyl/apprenticeship.git && cd apprenticeship -cp ama/TEMPLATE.md ama/nelsonic.md -``` -## Step 2: Answer the AMA Questions in your File - -Once you have created your own "ama" answers file, please answer the questions! - -## Create a Pull Request with your Answers File! - -Create a pull request! diff --git a/ama/TEMPLATE.md b/ama/TEMPLATE.md deleted file mode 100644 index fe40d11..0000000 --- a/ama/TEMPLATE.md +++ /dev/null @@ -1,26 +0,0 @@ - -## 1. ***Who*** are ***you***? - - -## 2. **What** is _your_ "***story***" (_or "journey"_) so far? - - -### 2.1 Where have you worked `before`? - - -### 2.2 What did you like/dislike about working there? - - -### 2.3 What did you learn (_both good and bad_!) while there? - - -## 3. ***What*** do you want to do with the next **2 years** of your **life**? - -### 3.1 ***Where*** do you want to live? - -## 4. Is there a "***Real World Problem***" you would like to solve? - -### 4.1 [ ] What is your _personal connection_ to the problem (_if any_)? - -## 5. ***Why*** do you ***want*** to **work** _with_ @dwyl ***specifically*** -(_as opposed to the **millions** of other options you have_) ?