Agile Design and Development
So that you can get feedback on it and make it better
The most rewarding iterations
Building is never a straight line
Product owner vs. product manager
A Product Owner is focused on output i.e. how quickly can we build these features?
Product Management, on the other hand, is focused on outcomes i.e. why are we building these features in the first place?
Good design is redesign
Good design is redesign. It's rare to get things right the first time. Experts expect to throw away some early work. They plan for plans to change.
It helps to have a medium that makes change easy. When oil paint replaced tempera in the fifteenth century, it helped painters to deal with difficult subjects like the human figure because, unlike tempera, oil can be blended and overpainted.
Finish designing as close to the end of a sprint as possible
The traditional process of delivering design, vs. delivering design just in time.
Designers are often working at least one sprint ahead of engineers. While one sprint might not seem like much of a lag, a typical product team learns a lot after the design hand-off. ...Instead of working ahead, we should finish designing as close to the end of a sprint as possible: just-in-time design.
We optimize what we measure
Scrum does not say “only focus on output”, but, unfortunately, humans will optimize for what they measure.
If you worry about story points & hitting your estimations, that’s what is going to consume your attention. That is what you and your team will optimize for.
And that is the core critique of Scrum as it is practiced: That it focuses a product team’s attention so heavily on delivery — on building lots of features quickly & efficiently — that teams fail to focus on spending time to discover what the right thing to build is.
How we can do better
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Manifesto for Agile Software Development
A DefinitionWe 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.
Agile Scrum is not working
The Agile founders had it right, one size doesn't fit all. What the founders perhaps didn’t foresee, or couldn’t agree on, is that in order for the world to scale and consume their wisdom, it had to be packaged as concrete practices, not as abstract classes with virtual methods to be defined in context. And to the proponents of Agile Scrum, give them their due, for their part, they made it concrete – Agile Scrum has been packaged and delivered. Yet much work remains to realize the promise of Agile, which in summary is, the realization of wise use of lightweight development practices and workflows that flexibly adapt to the changing and evolving needs of customers.
Driving engineers to an arbitrary date is a value destroying mistake
An Article by Gandalf HudlowWhat happens when you apply date pressure to software engineers working on high value software projects? The engineers will focus on delivering Something™ by the Date™! This fatal flaw results in delivery of a Something™ full of chaos and features that nobody really wants or needs.
Beware SAFe, an Unholy Incarnation of Darkness
An Article by Sean DexterThe Lean Portfolio Management function that controls funding, are given sole authority to approve which Portfolio Epics move into each stream. Epics are not explanations about a problem that needs to be solved. They are pre-formed ideas about how best to solve those problems.
Right away we can see signs of the old-school mindset of viewing teams as a “delivery” function instead of a strategic one. The high level thinkers come up with ideas, and the low level doers execute on those ideas. Ignored is the possibility that those closest to the work might be best equipped to make decisions about it. Escaping from this misguided mindset is a core goal of Agile thinking that SAFe fails to remotely accomplish.
Why Scrum is killing your product
An Article by Henry LathamDesign Systems, Agile, and Industrialization
An Article by Brad FrostI’ve come to the conclusion that “enterprise web development” is just regular web development, only stripped of any joy or creativity or autonomy. It’s plugging a bunch of smart people into the matrix and forcing them to crank out widgets and move the little cards to the right.
In these structures, people are stripped of their humanity as they’re fed into the machine. It becomes “a developer resource is needed” rather than “Oh, Samantha would be a great fit for this project.” And the effect of all this on individuals is depressing. When people’s primary motivation is to move tickets over a column, their ability to be creative or serve a higher purpose are almost completely quashed. Interaction with other humans seems to be relegated to yelling at others to tell them they’re blocked.
Reading “AS PER THE REQUIREMENTS” in tickets makes me dry heave. How did such sterile, shitty language seep into my everyday work?
The value-destroying effect of arbitrary date pressure on code
An Article by Gandalf HudlowThe mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.
Agile is Dead (Long Live Agility)
An Article by Dave ThomasThe word “agile” has been subverted to the point where it is effectively meaningless, and what passes for an agile community seems to be largely an arena for consultants and vendors to hawk services and products.
…Let’s abandon the word agile to the people who don’t do things. Instead, let’s use a word that describes what we do. Let’s develop with agility.
- You aren’t an agile programmer—you’re a programmer who programs with agility.
- You don’t work on an agile team—your team exhibits agility.
- You don’t use agile tools—you use tools that enhance your agility.
/
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation, and
Responding to Change over Following a PlanTraditional companies are losing because they mismanage software engineers
An Article by Emma WattersonInnovation is messy, and frankly Anti-Steve [Jobs] can’t figure out why you wouldn’t just tell people the right thing to build and skip all the trial and error that comes with innovation. Anti-Steve and his board of directors that keep him in place fundamentally believe that they know what needs to be built. Or at least that they can hire the messiah that will come down off the mountain and tell everyone what to build. There is no such messiah.
Why we stopped breaking down stories into tasks
An Article by Adam SilverThe Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint.
But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this:
- Breaking down stories into tasks is time consuming
- The tasks we came up with invariably would change as we worked on the stories
- Tasks are repetitive
- Tasks were often carried out in parallel
- Our estimates didn't improve
- It decluttered our task board
- It encouraged collaboration throughout the sprint
While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace.
Why We Don't Do Daily Stand-Ups at Supercede
An Article by Jezen ThomasYesterday I worked on the widget.
Today I will work on the widget.
I have no blockers.Are you asleep yet? The developers are. You promise them an intellectually stimulating work environment and what they end up with is drudgery.
What value can be had from these meetings anyway? Using “alignment” for justification is so nebulous that it is essentially meaningless. Engineers align themselves. They talk. Especially if you hire good ones (which, you know, you’ll struggle to if you have a culture of coercing them into this kind of busywork). Where does the real discussion happen? It’s written down.
Software that nobody wants
An Article by Gandalf HudlowFinding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
Making sense of MVP
An ArticleHenrik Kniberg:
The top scenario (delivering a front tire) sucks because we keep delivering stuff that the customer can’t use at all. If you know what you’re doing – your product has very little complexity and risk, perhaps you’ve built that type of thing hundreds of times before – then go ahead and just do big bang. Build the thing and deliver it when done.
Doing It Right
An Article by Brad FrostDoing it right requires a different pace of working and a much broader thought process than “ok, let’s get this thing out the door.” Which is super tough because most workplaces place a huge emphasis on getting things out the door, and fast. Little agile tickets that are expected to be completed in micro sprints to me seem to be antithetical to doing it right.
Planning doesn't make for better software
A Fragment by Robin RendleMy own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it.
Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me.
After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64.
Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way.
Agile as Trauma
An Essay by Dorian TaylorThe Agile Manifesto is an immune response on the part of programmers to bad management.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
The State of Agile Software in 2018
A Talk by Martin FowlerOn the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects).
Product vs. Feature Teams
An Article by Marty CaganThis article is certain to upset many people.
The Craftsman
The great teacher
The good teacher imparts a satisfying explanation; the great teacher unsettles, bequeaths disquiet, invites argument.
The categories of good
We need to turn to a fresh page. We can do so simply by asking—though the answers are anything but simple—what the process of making concrete things reveals to us about ourselves. Learning from things requires us to care about the qualities of cloth or the right way to poach fish; fine cloth or food cooked well enables us to imagine larger categories of 'good'.
For its own sake
'Craftsmanship' may suggest a way of life that waned with the advent of industrial society—but this is misleading. Craftsmanship names an enduring, basic human impulse, the desire to do a job well for its own sake.
The details of construction
The housing developments in the Moscow suburbs were built mostly in the decades after the Second World War. Laid out as enormous chessboards, the suburbs stretch to the horizon across flat land sparsely planted with birch and aspen. The architectural design of the suburban buildings was good, but the state had not been able to command good-quality work. The signs of poorly motivated workers appeared in the details of construction.
The technology shelf
Motorola developed what it called a 'technology shelf', created by a small group of engineers, on which were placed possible technical solutions that other teams might use in the future; rather than trying to solve the problem outright, it developed tools whose immediate value was not clear.
The lure of inspiration
The lure of inspiration lies in part in the conviction that raw talent can take the place of training.
I don't think you understand
The physicist Victor Weisskopf once said to his MIT students who worked exclusively with computerized experiments:
When you show me that result, the computer understands the answer, but I don't think you understand the answer.
Impossibly coherent
...what gets lost mentally when screen work replaces physical drawing.
Drawing in bricks by hand, tedious though the process is, prompts the designer to think about their materiality, to engage with their solidity as against the blank, unmarked space on paper of a window.
Computer-assisted design impedes the designer in thinking about scale, as opposed to sheet size. The object on-screen can indeed be manipulated so that it is presented, for instance, from the vantage point of someone on the ground, but in this regard CAD is frequently misused: what appears on-screen is impossibly coherent, framed in a unified way that physical sight never is.
Head and hand
The blueprint signaled a decisive disconnection between head and hand in design: the idea of a thing made complete in conception before it is constructed.
Bodily reality
To do good work means to be curious about, to investigate, and to learn from ambiguity.
In the Fordist model of medicine, there must be a specific illness to treat, the evaluation of a doctor's performance will then be made by counting the time required to treat as many livers as possible and the number of livers that get well. Because bodily reality doesn't fit well inside this classifying model, and because good treatment has to admit experiment, a not insignificant number of doctors create paper fictions to buy themselves time from the bureaucratic monitors. Doctors in the NHS often assign a patient a disease in order to justify the time spent on exploring a puzzling body.
Awareness and knowledge
In the higher stages of skill, there is a constant interplay between tacit knowledge and self-conscious awareness, the tacit knowledge serving as an anchor, the explicit awareness serving as critique and corrective.
The journeyman
The apprentice goldsmith was place-bound while learning how to smelt, purify, and weigh precious metals. These skills required hands-on instruction from his master. Once the apprentice had locally presented his chef d'oeuvre, however, he could move from city to city as a journeyman, responding to opportunities. The traveling goldsmith journeyman made his presentation élevé to the corporate body of master craftsmen in foreign cities. Through his managerial talents and moral behavior he had to convince these strangers that he could become one of them. This migratory dynamism was built into medieval goldsmithing.
Sedentary guilds, by contrast, appeared to him insert and 'corrupt'. The good master, in his words, "presides over a traveling house."
Building generations
How did the builders of Salisbury Cathedral achieve this astonishing construction? There was no one single architect; the masons had no blueprints. Rather, the gestures with which the building began evolved in principles and were collectively managed over three generations. Each event in building practice became absorbed into the fabric of instructing and regulating the next generation.
A thousand little moves
Missing in these analyses is a reconstruction of the workshops of the master—more precisely, one element that has irretrievably gone missing. This is the absorption into tacit knowledge, unspoken and uncodified in words, that occurred there and became a matter of habit, the thousand little everyday moves that add up in sum to a practice.
The most significant fact we know about Stradivari's workshop was that he was all over it, popping up unexpectedly everywhere, gathering in and processing those thousand bits of information that could not signify in the same way to assistants who were doing just one part.
Mirror tools
A mirror-tool is an implement that invites us to think about ourselves. There are two kinds of mirror-tools. These are the replicant and the robot.
A quiet and contented mind
The Encyclopedia sought to get its readers out of themselves and into the lives of artisan craftsmen in order to clarify good work itself. Throughout, the volumes illustrate people engaged sometimes in dull, sometimes in dangerous, sometimes in complicated labor; the expression on all the faces tends to the same serenity. About these plates the historian Adriano Tilgher remarks on the "sense of peace and calm which flows from all well-regulated, disciplined work done with a quiet and contented mind."
The limits of language
The question of human limits was posed to Diderot the moment he, as it were, rose from his armchair. His method for finding out how people worked was, like a modern anthropologist, to ask them:
We addressed ourselves to the most skilled workers in Paris and the kingdom at large. We took the trouble to visit their workshops, to interrogate them, to write under dictation from them, to follow out their ideas, to define, to identify the terms peculiar to their profession.
The research soon ran into difficulty, because much of the knowledge craftsmen possess is tacit knowledge—people know how to do something but they cannot put what they know into words. Diderot remarked of his investigations: "Among a thousand one will be lucky to find a dozen who are capable of explaining the tools or machinery they use, and the things they produce with any clarity."
What we can say in words may be more limited than what we can do with things. Language is not an adequate 'mirror-tool' for the physical movements of the human body.
The wisdom of the apprentice
Diderot's solution to the limits of language was to become himself a worker.
Become an apprentice and produce bad results so as to be able to teach people how to produce good ones.
This is how I lived
Rather than convey "be like me," better parental advice should be more indirect: "This is how I lived" invites the child to reason about that example. Such advice omits "Therefore you should..." Find your own way; innovate rather than imitate.
Entropy
Imperfect, handmade glass has virtues: these are irregularity, distinctiveness, and what the writer refers to vaguely as 'character'. The two sets of images for glassblowing are thus inseparable; only by understanding how something might be done perfectly is it possible to sense this alternative, an object possessing specificity and character. The bubble or the uneven surface of a piece of glass can be prized, whereas the standard of perfection allows no room either for experiment or for variation.
Against the claim of perfection
We should not compete against the machine. Rather, against the claim of perfection we can assert our own individuality.
Seven lamps
Ruskin's Seven Lamps of Architecture provided seven guides, or 'lamps', for the troubled craftsman, guides for anyone who works directly on material things. These seven are:
- The lamp of sacrifice: The willingness to do something well for its own sake.
- The lamp of truth: The truth that 'breaks and rents continually'; Ruskin's embrace of difficulty, resistance, and ambiguity.
- The lamp of power: Tempered power, guided standards other than blind will.
- The lamp of beauty: Which for Ruskin is found more in the detail, the ornament—hand-sized beauty—than in the large design.
- The lamp of life: Life equating with struggle and energy, death with deadly perfection.
- The lamp of memory: The guidance provided by the time before machinery ruled.
- The lamp of obedience: Obedience to the example set by a master's practice rather than by his particular works; otherwise put, strive to be like Stradivari but do not seek to copy his particular violins.
I am here
I am here, in this work.
A maker's mark is a peculiar sign. Ancient brickwork established presence through small details marking 'it': the detail itself.
The great historian of bricks, Alex Clifton-Taylor, observes that what most counts about them is their small size, which just suits the human hand laying a brick. A brick wall, he says, "is therefore an aggregation of small effects. This implies a human and intimate quality not present to the same extent in stone architecture."
Get a grip
The hand is the window on to the mind. — Immanuel Kant
American slang advises us to "get a grip"; more generally we speak of "coming to grips with an issue." Both figures reflect the evolutionary dialogue between the hand and the brain.
Focal awareness
The philosopher Maurice Merleau-Ponty describes what she experienced as "being as a thing." The philosopher Michael Polanyi calls it "focal awareness" and recurs to the act of hammering a nail:
When we bring down the hammer we do not feel that its handle has struck our palm but that its head has struck the nail.
We have become the things on which we are working.
Sublime tools
Getting better at using tools comes to us, in part, when the tools challenge us, and this challenge often occurs just because the tools are not fit-for-purpose. In both creation and repair, the challenge can be met by adapting the form of a tool, or improvising with it as it is, using it in ways it was not meant for.
The all-purpose tool seems a special case. In its sheer variety, a flat-edged screwdriver admits all manner of unfathomed possibilities; it, too, can expand our skills if only our imagination rises to the occasion. Without hesitation, the flat-edged screwdriver can be described as sublime—the word sublime standing, as it does in philosophy and the arts, for the potently strange.
Crafting repair
Repair is a neglected, poorly understood, but all-important aspect of technical craftsmanship. The sociologist Douglas Harper believes that making and repairing form a single whole; he writes of those who do both that they possess the "knowledge that allows them to see beyond the elements of a technique to its overall purpose and coherence. This knowledge is the 'live intelligence, fallibly attuned to the actual circumstances' of life. It is the knowledge in which making and fixing are parts of a continuum."
Put simply, it is by fixing things that we often get to understand how they work.
When history moves on
Much twentieth-century urban planning proceeded on the principle: demolish all you can, grade it flat, and then build from scratch. The existing environment has been seen as standing in the way of the planner's will. This aggressive recipe has frequently proved disastrous, destroying many viable buildings as well as ways of life bedded into urban fabric. The replacements for these destroyed buildings have also, too often, proved worse: big projects suffer from overdetermined, fit-for-purpose form; when history moves on, as it always does, tightly defined buildings can soon become obsolete.
Details first
The identification a good craftsman produces is selective, that of finding the most forgiving element in a difficult situation. Often this element is smaller, and so seems less important, than the larger challenge. It is an error in technical as in artistic work to deal first with the big difficulties and then clean up the details; good work often proceeds in just the opposite fashion.
Walls and membranes
All living things contain two sites of resistance. These are cell walls and cell membranes. The cell wall is more purely exclusionary – a boundary; the membrane permits more fluid and solid exchange – a border.
Most pervasive in the modern city is the inert boundary established by highway traffic, cutting off parts of the city from each other. Working with resistance means, in urbanism, converting boundaries into borders.
The ground plane
Whereas Corbusier relegated streets to traffic functions, the ground plane represented to Van Eyck the realm in which people 'learn' cities. The placement of benches and bollards, the height of stepping-stones, the ill-defined separations of sand, grass, and water are all tools in that learning, an education in ambiguity.
Most cities were mostly built by improvisation
In Architecture Without Architects, Bernard Rudofsky documented the ways in which most cities were mostly built by improvisation, following no consistent formal design. Building was added to building, street to street, their forms adapting to different site conditions in the process of extension.
Rudofsky thought that this hidden order is how most settlements of poor people develop and that the work of improvising street order attaches people to their communities, whereas 'renewal' projects, which may provide a cleaner street, pretty houses, and large shops, give the inhabitants no way to mark their presence on the space.
The aspiration for quality
To arouse the aspiration for quality and make good on it, the organization itself has to be well crafted in form. It needs, like Nokia, open information networks; it has to be willing to wait, as Apple is, to bring its products to market until they are really good.
Oddity and peculiarity
The experienced doctor, as one would expect, is a more accurate diagnostician. This is due in large part to the fact that he or she tends to be more open to oddity and peculiarity in patients, whereas the medical student is more likely to be a formalist, working by the book, rather rigidly applying general rules to particular cases.
Relentlessness deformed it
I am not interested in erecting a building, but in presenting to myself the foundations of all possible buildings. — Ludwig Wittgenstein.
But in a note of 1940 to himself he wrote that the building "lacks health" or "primordial life".
In the construction of a house for his sister in the Kundmangasse, Wittgenstein's striving for an ideal perfection rendered the object lifeless. Relentlessness deformed it.
Necessity
Loos's need to respond positively to the difficulties he encountered appeared in the errors that occurred during the construction of the Villa Moller. When the foundations were not laid as specified, he could not afford to dig them up and start again; instead, Loos thickened the form of one side wall to accommodate the mistake, making the thickened wall and emphatic side frame for the front. The formally pure properties of Villa Moller were achieved by working with many similar mistakes and impediments Loos had to take as facts on the ground; necessity stimulated his sense of form. Wittgenstein, knowing no financial necessity, had no such creative dialogue between form and error.
The narrative of its making
Getting things in perfect shape can mean removing the traces, erasing the evidence, of a work in progress. Once this evidence is eliminated, the object appears pristine. Perfection of this cleaned-up sort is a static condition; the object does not hint at the narrative of its making.
The good craftsman
The good craftsman...
...understands the importance of the sketch—that is, not knowing quite what you are about when you begin.
...places positive value on contingency and constraint.
...needs to avoid pursuing a problem relentlessly to the point that is becomes perfectly self-contained.
...avoids perfectionism that can degrade into a self-conscious demonstration.
...learns when it is time to stop.Your life adds up
Weber's German word for a vocation, Beruf, contains two resonances: the gradual accumulation of knowledge and skills and the ever-stronger conviction that one was meant to do this one particular thing in one's life.
An English locution roughly conveys what he meant: your life 'adds up'.
To do just one thing well
The skills society is bulldozing the career path; jobs in the old sense of random movement now prevail; people are meant to deploy a portfolio of skills rather than nurture a single ability in the course of their working histories; this succession of projects or tasks erodes belief that one is meant to do just one thing well.
Manual labor
Artisanal craftsmen have proved particularly promising subjects for job retraining. The discipline required for good manual labor serves them, as does their focus on concrete problems rather than on the flux of process-based, human relations work. For this very reason it has proved easier to train a plumber to become a computer programmer than to train a salesperson; the plumber has craft habit and material focus, which serve retraining. Employers don't often see this opportunity because they equate manual routine with mindless labor.
Multiple choice
Intuitive leaps that open up a problem are impossible to test using multiple-choice questions. These leaps are an exercise of associating unlikely elements. There is no correct answer to the question "Are city streets like arteries and veins?"
Hephaestus
The clubfooted Hephaestus, proud of his work if not of himself, is the most dignified person we can become.