Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions about apprenticeship structure #2

Open
ZooeyMiller opened this issue Jun 19, 2017 · 2 comments
Open

Questions about apprenticeship structure #2

ZooeyMiller opened this issue Jun 19, 2017 · 2 comments

Comments

@ZooeyMiller
Copy link
Collaborator

ZooeyMiller commented Jun 19, 2017

Both @finnhodgkin and I had a few things we weren't sure about and just wanted to clarify about the apprenticeship.

  • How long is a day? e.g. start and end times (seems start time is 9am but not sure of what time the day is ending)
  • How long is the apprenticeship? I was told 4 weeks by Joe but not had any input from anyone from dwyl on this.
  • How/when/how much do we get paid?
  • What is expected from us during the apprenticeship and what can we expect to get out of it?
@finnhodgkin
Copy link
Collaborator

How does the apprenticeship work with my week of teaching at Founders and Coders? I'm booked for the second week of the course (3rd July). Although the teaching isn't full time, it would take up a significant chunk of my week.

@nelsonic
Copy link
Member

nelsonic commented Jun 19, 2017

@ZooeyMiller good questions! (thanks for opening this!) I will respond in more detail in the README.md shortly, but in the interim:

  • Start: 09:00
  • Break: when you feel "unproductive".
  • End: When you're tired of looking at code / learning new things ... try not to focus on the clock while you are learning. if something is taking longer than you estimated communicate this in the issue. If you "finish early":
    • Re-read/Review your own work to ensure that it's as beginner-friendly as posible
    • Figure out what to do next by checking/opening issues (ask early if you need any help!)
  • How long? If you only have 4 weeks to "spare" that's cool!
    If you decide you enjoy working with dwyl we can discuss continuing for longer. We/I won't be "offended" if you decide to work with another team/company/org instead, provided you capture your apprenticeship experience in this repo for others to learn from. 👍
  • Getting Paid?
  • "What can we expect to get out of it?"
    • What you put in ... the more questions you ask and more your push yourself to learn and write more, the more you will get out of it. If at any point you are stuck/blocked/confused/bored open an issue immediately so we can help get you back on track!
    • Open Source Contributions
    • Experience working with people who have made way more mistakes than most (i.e. "experienced") and can answer questions in seconds/minutes that would take most "junior" technologists hours/days/weeks to discover!
    • Payment ... 💰
  • "What is expected?"
    • Learn how to build apps with outstanding UX
    • Document all-the-things you learn in the process
    • Help build features on dwyl's product roadmap: https://github.com/dwyl/product-roadmap#what
    • Work at a sustainable pace.
    • Follow dwyl's contributing workflow (describe the story, estimate, track efforts, document & PR)

@finnhodgkin if you want/need to take a break to teach @ F&C that's totally fine. 👍
If you are able to manage your time to continue working you could assign yourself a T2-4h story/task and work around your "classroom" commitments.

BTW: what are you teaching in "Week 2" ? I can't find it in https://github.com/foundersandcoders/london-curriculum
this it: https://github.com/foundersandcoders/master-reference/tree/master/coursebook/week-2 ?

@nelsonic nelsonic mentioned this issue Jun 22, 2017
Merged
nelsonic added a commit that referenced this issue Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants