Fast and Slow

When we think about quality attributes or criteria, we often see slow. It's easier to spot something when it's lagging. It causes us to look and investigate what the problem is.

But what about thinking about fast software and what that means to us?

Building fast...
- changes behaviour
- it means we can do more
- it can feels magical
- it elminates friction and gets things flywheeling
- means we may need to simplify
- strip away other features so that it speedy
- it therefore creates focus
- potential complexity behind the scenes
- fast can feel fun
- it can suprise and delight us
- fast is dependent, on you guessed it, many things

Questions to ask about fast software:
- How do we notice fast?
- Or how do we build for fast?
- Is it something we care about?
- Who is striving for it?
- If we are slow to begin with, will we always feel slow?
- How do we measure fast?
- How will fast create a difference?
- What's slowing us down? :)

This post was inspired by: https://www.catherinejue.com/fast

What other questions or ideas would you add to the ideas of fast software?