Function, Functionality, Functionalism
The requirements of economy
Useless work on useful things
The minimum condition
Form eschews function
Feeble and ugly
Functionalism can be a kind of religion
Each element performs many functions
The informing idea of functionalism
Same name in the same basket
The plan must anticipate all that is needed
The element becomes a sign
Classical absurdity
205. Structure Follows Social Spaces
Roaming and capricious
What are those borders made of?
Presentable
A strangely negative character
Sine qua non
The contribution that something in them yet compelled them to make
Something more is required
Mechanisms and organisms
The center of the way
The Evolution of Useful Things
The usages of life
Form follows function
Against form follows function
UI and Capability
Embracing design constraints
An Article by Adrian RoselliConstraints have been shown to generally improve innovation. Giving targets and parameters helps ensure a team is working in unison. Identifying what is out of bounds can further focus that team.
A Plea for Lean Software
An Essay by Niklaus WirthSoftware's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
Beauty in flight
A QuoteAll of us had been trained by Kelly Johnson and believed fanatically in his insistence that an airplane that looked beautiful would fly the same way.
— Ben Rich, Skunk Works
Agile as Trauma
The Agile Manifesto is an immune response on the part of programmers to bad management.
Many a corner office
I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome.
Intramural brownie points
Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product
A
have featureX
?" then the answer is yes either way.Feature factories
We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise.
The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it.