Hack day

September 2015

I surrendered my dev day to fix ticket bugs

The aim

Build

• one way FWD
• one way swap
• time options
• two way FWD
• two way swap

tickets

Is that achievable in 24 hours?

No.

Cut scope

Don't implement any of the domain logic or data logic.

Build purely the view of a ticket with

no binding to any business logic.

Tools of the job

Demo

What could have been better

• Made more, smaller components

What went well

• Hot module reloading is actually useful.
• Building the view with no coupling makes it easier to work with, allows stakeholders to provide quicker feedback.

Parallelize

a.k.a Fewer heroes, higher productivity.

Sometimes components are built by one 80 hour week working dev.

By decoupling the different layers we can build components as teams.

Simplify

Build components in separate layers.

Build view as dumb functions of domain model state.

Build small, single purpose components.

view = f(data)

...

newView = f(newData)