performance
If it could save a person's life, would you find a way to make it faster?
Why aim small?
The Website Obesity Crisis
A Management Maturity Model for Performance
Reflections on Software Performance
Add Less
Site performance is potentially the most important metric
Website Response Times
Fast Software, the Best Software
Finda
A Plea for Lean Software
Speed is a feature
Performance and people
Why Software is Slow and Shitty
The Taft Test
Page weight matters
An Article by Chris ZachariasMany of us are fortunate to live in high bandwidth regions, but there are still large portions of the world that do not. By keeping your client side code small and lightweight, you can literally open your product up to new markets.
Trees and graphs
A tree is a kind of graph, but a graph can be considerably more complex than a tree.
I have reason to believe, which for brevity’s sake I will treat elsewhere, that the most complex class of processes and structures we humans can consciously prescribe, reduces mathematically to a tree. A tree has a top, bottom, left and right. Its branches fan out from the trunk and they don’t intersect with one another. They are discrete, contiguous, identifiable objects which persist across time. Trees are Things.
Software and websites, however, reduce to arbitrarily more complex structures: they are graphs. A graph has no meaningful orientation whatsoever. No sequence, no obvious start or end—at least none that we can intuit. It is better considered not as one Thing, but as a federation of Things, like the brain or a fungus network, or perhaps a composite artifact left behind from an ongoing process, like an ant colony or human city.