Steve Barnett SteveBarnett

**Learn to code or level up with RailsBridge. **

Our events are targeted at groups of people that are underrepresented in tech. The workshops teach practical skills useful to those investigating new career paths, looking to compliment their current skill set, or simply interested in gaining a better understanding of software.

We’ll be running the Intro to Rails course. You’ll learn to use both Ruby and Rails to build and publish a web application. You’ll be given sufficient background and confidence to continue developing your Rails skills independently.

We’ll also be running the Job Board course. If you've completed the InstallFest and Intro to Rails courses and would like to stretch your Ruby on Rails skills a bit more, this one is for you.

—

Pick a new notebook and use it just for retros. Write down your answers to each question. Ideally keep a separate, visible, list of your SMART goals so that you can see them add up over the weeks.

What went well?

What should I do differently?
What did I learn?
Make a SMART goal.

A SMART goal is Specific, Measurable, Achievable, Realistic, Time-bound.

Subject

Is your RSVP still correct?

Body

We hope you can still make the talk on Wednesday 7th September. To get you thinking about the topic, please reply with an answer to the question below, by 6pm on Friday 2nd September.

What's one of your "go to" CSS tricks?

Images unoptimised and take up 2.8MB of 4.5MB total size.
- Smaller is better.
PageSpeed: 36 / 100
- 90 and up is good.
WebPageTest: SpeedIndex of 21142 (7722 on repeat view)
5000 is okay, but lower is better.

Why do we need to talk to users a lot?

Summary: to give a project the best chance of success (good work, happy users), we need frequent access to the users of the software. Without it, we run the risk of making incorrect assumptions and spending time and money building something that doesn't solve their problems.

When we make software there are two things that we try and keep in mind: build the thing right and build the right thing.

By build the thing right we mean use development best practices (often following agile ways of doing things, using Test-Drive Development, writing clean code, doing code reviews).

By build the right thing we mean doing User Experience stuff, usually with a User-Centered Design flavour.

Intro - 5m

Who I am
What we're doing
Not testing you, testing the app
"Be selfish, self-centred, honest, brave. Think out loud. If you get stuck, that's great."

Warm up - 5m

What do you do?

From http://www.statssa.gov.za/publications/P0318/P03182015.pdf

General household survey 2015

Statistical release P0318


	# Explain that BEM thing to me again..?

	## Block

	The root of your CSS component. eg: `.c-header` or `.c-flash`. (I'm namespacing all my classes with a `c-` to denote they're components, but that's optional. Namespace away to your own preference. Or don't. Whatever.)

	## Element

	Classes that are used inside the component block, and are instrumental to the structure - eg: the links inside a header: `.c-header__link`, or a dismiss button inside a flash notice: `.c-flash__dismiss`.

	body {

	// set your base
	font-family: sans-serif;
	line-height: 1.25;

	// .wf-loading means js is running and the webfont is loading,
	// so adjust the base font to minimise the jank when the switch happens
	.wf-loading & {
	font-size: 0.935em;

	<?php
	function disable_wp_unwanted_stuff() {
	// remove emoji js junk
	remove_action( 'wp_head', 'print_emoji_detection_script', 7 );
	remove_action( 'wp_print_styles', 'print_emoji_styles' );
	wp_deregister_script( 'wp-embed' );

	// Remove the REST API endpoint.
	remove_action('rest_api_init', 'wp_oembed_register_route');