Skip to content

Instantly share code, notes, and snippets.

@dearshrewdwit
Last active June 29, 2020 13:49
Show Gist options
  • Select an option

  • Save dearshrewdwit/728d08d9607f044e629e8166a9bf70c4 to your computer and use it in GitHub Desktop.

Select an option

Save dearshrewdwit/728d08d9607f044e629e8166a9bf70c4 to your computer and use it in GitHub Desktop.
Makers Part time - Course Outline

July2020 (Pilot)

  • Fundamentals: Monday 6th July - Saturday 1st August
  • Software Craft: Sunday 2nd August - Saturday 12th September*
  • 1 week break
  • Modern Web Development: Sunday 20th September - Saturday 28th November
  • 1 week break
  • Team Professional: Sunday 6th December - Monday 8th February 2021**

* Summer bank holiday: 31st Aug

** Winter break: Friday 25th December - Sunday 3rd January 2021

** Demo Day will be on the Monday evening from 6:30pm (TBC)

What is the Application Process?

Application process

During the pairing session I’ll be looking for you to demonstrate a problem solving mindset. It will help to have some awareness of simple programming concepts like variable assignment and method definitions, but the best indications of success on the course are your enjoyment of programming and the way you approach problems - so don’t worry too much about learning lots of syntax, I’ll help you there.

There is no downside to booking more than 1 pairing session - so don’t wait! In every session I’ll give you things to work on, until and even when you’re accepted!

Here are some resources (though by no means exhaustive) to have a go at:

  • Complete a language track with codeacademy (eg: Ruby)
  • Get 100pts solving problems with codewars (any languages)

What is the curriculum outline?

1. Fundamentals (4 Weeks)

By the end of this module all developers can:

  • Pair using the driver-navigator style
  • Set up and navigate development environments
  • Solve simple problems procedurally
  • Follow an effective debugging process
  • Plan and meet learning goals based on learning needs.

2. Software Craft (6 Weeks)

By the end of this module all developers can:

  • Explain and apply a development process to convert requirements into software
  • Test-drive modular programs using objects and methods
  • Describe OO principles like encapsulation, SRP
  • Explain techniques they use to keep their code clean
  • Peer review code

3. Modern Web Development (10 Weeks)

By the end of the module all developers can:

  • Build a simple web app with a database and follow an effective debugging process across the stack
  • Explain the basics of how the web works (e.g. request/response, HTTP, HTML, CSS)
  • Explain the MVC pattern
  • Explain the basics of how databases work (e.g. tables, SQL, basic relationships)
  • Test drive a simple front-end web app with Javascript
  • Follow an effective process for learning a new language
  • Build an API and a front-end app in Javascript that consumes it
  • Work competently in Javascript *
  • Reason about asynchronous behaviour in Javascript

4. Team Professional (8 Weeks)

By the end of the module all developers can build tested, easy-to-change software in a team using these processes

  • Break down projects into tasks and allocate them to pairs
  • Build applications to a specification (rather than challenges)
  • Continuously integrate and deploy new code
  • Run stand-ups and retrospectives
  • Use a branch/PR/merge git workflow
  • Give and receive meaningful code review

What is the schedule like?

Here's a calendar airtable view For the Team Professional module - rather than Challenges in pairs you'll be doing project work and there'll be fewer coach-led sessions.

Sunday

  • 9.00-11.45: Coach-led sessions Coaches will be running workshops, mini projects, 1:1s, and you'll work on the topics in a pair. After the sessions you might continue work on them, or work on the unit challenges with your pair partner.
  • 11.45-12.00: Meditation. Programming is extremely challenging. Meditation helps keep a lid on things, keeps you grounded, and helps keep your brain sharp.
  • 12.00-14.00: Challenges in pairs You'll work on a different set of challenges every unit and with a different person each time. These form the main thread of the course and ensure everyone comes out with common important skills like debugging, pair programming, and web development.

Monday, Wednesday

  • 18.00-18.15: Meditation. Balancing your commitments and a part time intensive software engineering course is challenging. Meditation helps keep a lid on things, keeps you grounded, and helps keep your brain sharp.
  • 18:15-18.30: Peer group check in
  • 18.30-21.00: Challenges in pairs You'll work on a different set of challenges every unit and with a different person each time. These form the main thread of the course and ensure everyone comes out with common important skills like debugging, pair programming, and web development.

Tuesday, Thursday

  • 17.00–18.00: Yoga. Remote, availabe to all current Makers students
  • 18.00-18:15: Meditation. Balancing your commitments and a part time intensive software engineering course is challenging. Meditation helps keep a lid on things, keeps you grounded, and helps keep your brain sharp.
  • 18:15-18.30: Peer group check in You'll be in a small group of 3 or 4 cohort members to check in and share your goals for the evening.
  • 18.30-21.00: Coach-led sessions. Coaches will be running workshops, mini projects, 1:1s, and you'll work on the topics in a pair. After the sessions you might continue work on them, or work on the unit challenges with your pair partner.

Friday & Saturday

  • Flexible hours. There are no scheduled events on Fridays and Saturdays. (4 Fridays will be a cohort retrospective) You're empowered to use this time as much as you'd like during any part of the week. You might want to spend an hour in the morning Monday - Thursday, to keep every Saturday free, for example. You might want to take a Wednesday evening off, and do more work on the weekend, or during one of the week-breaks.

  • Friday Retros When a module ends, We'll meet that Friday to look back and discuss how the learning has gone in order to make adjustments for the upcoming unit.

  • Otherwise, you'll work independently on projects to achieve goals. You’ll use your own way of tracking your goals to self-assign projects and assess your progress

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment