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

Learning: Learn Tech + Onboarding Mentoring #200

merged 1 commit into from Nov 20, 2018
Changes from all commits
File filter...
Filter file types
Jump to…
Jump to file or symbol
Failed to load files and symbols.


Just for now

@@ -28,6 +28,7 @@ We're a company that moves fast, so we're going to need everyone to help us keep

* [About Made Tech](company/
* [Welcome Pack](company/
* [Learning](learning/ (Engineering)

### Roles

@@ -0,0 +1,40 @@
# Learning (Engineering roles)

## Onboarding

Before joining a delivery team, you will spend some time with a mentor focussing on skills relevant to delivery teams.

This comment has been minimized.

Copy link

craigjbass Nov 19, 2018

Author Member

To come in future

  • Clear learning outcomes
  • How long you spend with a mentor
  • Alignment with Core Skills

As a high level summary, we will cover the following -

1. Watch the [introduction to TDD screencast](
2. (Pair or mob with a mentor on) [code katas]( using [Test Driven Development]( discipline.
3. (Pair or mob with a mentor on) subcutaneous acceptance testing, and ATDD discipline.
4. Explore with a mentor the central architectural concepts of Clean Architecture
5. Discuss the SOLID principles with a mentor, with reference to Clean Architecture and (A)TDD.
6. Be introduced to the [Tic Tac Toe sparring exercise](

## Core Skills

Our Engineering team has built some Core Skills, which are courses around topics valuable to Made Tech.

Currently, each Core Skill is comprised of 3 levels, with acompanying stickers (which you will see on people's laptops).

You earn these stickers by doing coursework, or by passing an assessment, set by members of the Engineering team with expertise in that skill.

### Learn Tech

Every Friday between 13:30 and 17:00 the team come together to focus on Core Skills.

There are two teams, each with their own standup. Details can be found in [this spreadsheet]( along with a record of assessments.

This comment has been minimized.

Copy link

StevenLeighton21 Nov 19, 2018

Is including an internal spreadsheet necessary? Is it useful in the open source handbook to do so? Suggest replacing with something like 'Full details can be found in the topic of #learntech on Slack'

This comment has been minimized.

Copy link

craigjbass Nov 19, 2018

Author Member

Tis private obv, (you need a login). Elsewhere in the handbook we link to private sheets

This comment has been minimized.

Copy link

StevenLeighton21 Nov 19, 2018

Fair enough - I wasn't really considering the handbook as an internal 'resource' but I can see the logic.

* All Permanent Engineers are expected to attend and be on time.
* The time should be focussed on attaining, or be defining and/or improving Core Skills.

### Show & Tell

Show & Tell is more freeform - between 16:30 and 17:00 there is an opportunity to present to the team.

Use this as an opportunity to share with the wider group something of interest.

This could be, for example, how you applied TDD discipline on your delivery team, or it could be how you approached infrastructure as code at your previous company.

ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.