interaction
Up and Down the Ladder of Abstraction
A Brief Rant
Stop Drawing Dead Fish
The Future of Programming
How I Build
Intelligent arrows
Website Response Times
Now I get it
Like, just a post complaining that screens should be better
An Article by Matt WebbIt’s been 19 years since Pixar released Monsters, Inc. with all that CGI hair. Where are my hairy icons? Ones that get all long and knotted as the notifications number goes up.
Why can’t I feel my phone? I found that paper from 2010 (when I was complaining about keyboards) about using precision electrostatics to make artificial textures on touchscreens.
I should be able to run my thumb over my phone while it’s in my pocket and feel bumps for apps that want my attention. Touching an active element should feel rough. A scrollbar should *slip. Imagine the accessibility gains. But honestly I don’t even care if it’s useful: 1.5 billion smartphone screens are manufactured every year. For that number, I expect bells. I expect whistles.
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Deliver early and continuously
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Self-organizing teams
The best architectures, requirements, and designs emerge from self-organizing teams.
Technical excellence and good design
Continuous attention to technical excellence and good design enhances agility.
Agility and sustainability
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
The amount of work not done
Simplicity—the art of maximizing the amount of work not done—is essential.
The primary measure of progress
Working software is the primary measure of progress.
Build projects around motivated individuals
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Deliver working software frequently
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers
Business people and developers must work together daily throughout the project.
Face-to-face conversations
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Reflect, tune, adjust
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.