-2000 Lines Of Code An Article by Andy Hertzfeld www.folklore.org Bill Atkinson...who was by far the most important Lisa implementor, thought that lines of code was a silly measure of software productivity. He thought his goal was to write as small and fast a program as possible, and that the lines of code metric only encouraged writing sloppy, bloated, broken code. ...He was just putting the finishing touches on the optimization when it was time to fill out the management form for the first time. When he got to the lines of code part, he thought about it for a second, and then wrote in the number: -2,000. I'm not sure how the managers reacted to that, but I do know that after a couple more weeks, they stopped asking Bill to fill out the form, and he gladly complied. The amount of work not done metricscodemanagementproductivity
Baumol’s cost disease Baumol's cost disease (or the Baumol effect) is the rise of salaries in jobs that have experienced no or low increase of labor productivity, in response to rising salaries in other jobs that have experienced higher labor productivity growth. The rise of wages in jobs without productivity gains derives from the requirement to compete for employees with jobs that have experienced gains and so can naturally pay higher salaries, just as classical economics predicts. For instance, if the retail sector pays its managers 19th-century-style salaries, the managers may decide to quit to get a job at an automobile factory, where salaries are higher because of high labor productivity. Thus, managers' salaries are increased not by labor productivity increases in the retail sector but by productivity and corresponding wage increases in other industries. Wikipedia en.wikipedia.org economicsproductivitywork
Parkinson's Law Work expands so as to fill the time available for its completion. Wikipedia en.wikipedia.org Hofstadter's Law worktimeproductivity
The urge to be done "Flow" is often a synonym for ignorance and laziness. It's also a sign of haste, the urge to be done. Verlyn Klinkenborg, Several Short Sentences About Writing productivity
The absent-minded professor There are three variants of procrastination, depending on what you do instead of working on something: you could work on (a) nothing, (b) something less important, or (c) something more important. That last type, I'd argue, is good procrastination. That's the "absent-minded professor," who forgets to shave, or eat, or even perhaps look where he's going while he's thinking about some interesting question. His mind is absent from the everyday world because it's hard at work in another. Paul Graham, Good and bad procrastination procrastinationproductivity
Always produce "Always produce" is also a heuristic for finding the work you love. If you subject yourself to that constraint, it will automatically push you away from things you think you're supposed to work on, toward things you actually like. "Always produce" will discover your life's work the way water, with the aid of gravity, finds the hole in your roof. Paul Graham, How to do what you love Flow interesting (The Meander) productivity
Background textures of work An Article by Lucy Keer lucykeer.com One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it. ...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun. workproductivitymaking
Efficiency is the Enemy An Article fs.blog Many of us have come to expect work to involve no slack time because of the negative way we perceive it. In a world of manic efficiency, slack often comes across as laziness or a lack of initiative. Without slack time, however, we know we won’t be able to get through new tasks straight away, and if someone insists we should, we have to drop whatever we were previously doing. One way or another, something gets delayed. The increase in busyness may well be futile. It’s Time to Embrace Slow Productivity efficiencyproductivitywork
It’s Time to Embrace Slow Productivity An Article by Cal Newport www.newyorker.com The central goal of Slow Productivity is to keep an individual worker’s volume at a sustainable level. A natural fear is that by reducing the amount of work each employee tackles at any given time, it might reduce the total amount of work an organization is able to complete, making it less competitive. This fear is unfounded. As argued, when an individual’s work volume increases, so does the accompanying overhead and stress, reducing both the time remaining to actually execute the tasks and the quality of the results. If you instead enable the individual to work more sequentially, focussing on a small number of things at a time, waiting until she is done before bringing on new obligations, the rate at which she completes tasks might actually increase. Efficiency is the Enemy productivity
Beyond 10× An Article by Matthew Ström matthewstrom.com Forget 10×. With a focus on outcomes and an eye towards the border between net-positive and net-negative work, any team can push their productivity beyond their previous limits. ...If you can perform one task better than most people, you might be a 10× designer or developer or product manager (or whatever you are). But if your team can find small ways to make many of their tasks net-positive, 10× is just the start. productivity
Touch the keys An Article by Rach Smith rachsmith.com In his course Being Productive: Simple Steps to Calm Focus, Kourosh Dini emphasises the importance of taking a moment to “be with” the work every day (or however frequently you need to tackle a project). “Being with” your work is to be fully present and intentional about that activity and doing nothing else. This idea was inspired by Dini’s piano teacher, who encouraged him to sit at his piano and touch the keys every day. Even on the days that he felt he had no time or inclination to practice. Sometimes touching the keys would lead to a good practice session, even when he didn’t feel like it would before he actually gave it a go. Just like Dini, I find that once I give the task my full attention and be present, the actual doing of it turns out to be much easier and more enjoyable than my mind had been expecting. As usual, the resistance to getting started is far more uncomfortable than actually doing the thing. To pick up my pen productivityworkcreativitypractice
Nobody gives a hoot about groupthink An Article by Baldur Bjarnason www.baldurbjarnason.com Two relatively common ‘fashions’ today are real-time collaboration and shared data repositories of one kind or another. Both increase productivity in the naive sense. We work more; everybody is more active; the group feels more cohesive. The downside is that they also both tend to reduce the quality of the work and increase busywork. On that of the highest authorityPersonal Information Management (PIM) productivitycollaborationinformation
Winning by Design: The Methods of Gordon Murray A Research Paper by Nigel Cross & Anita Clayburn Cross A case study of the working methods of one particularly successful designer in a highly competitive design domain - Formula One racing car design. Gordon Murray was chief designer for the very successful Brabham and McLaren racing car teams in the 1970s and 1980s. His record of success is characterised by innovative breakthroughs, often arising as sudden illuminations, based on considering the task from first principles and from a systemic viewpoint. His working methods are highly personal, and include intensive use of drawings. Personality factors and team management abilities also appear to be relevant. There are some evident similarities with some other successful, innovative designers You need to make the step forwardDrawing the bitsLike designing things for the first timeWonder PlotsI never have engineers that aren't designers+7 More design
You need to make the step forward Throughout a racing season there is constant, relentless pressure on the designer to keep making design improvements. But there is a limit to what can be achieved with any car design, before a jump has to be made to basically a new design, an innovation. As Gordon Murray says, ‘Given the situation and the pressure at any one time, you do get to the brick wall...I mean you're doing all these normal modifications, you know you can't go any quicker, you need to make the step forward.’ In the midst of the pressure, the fervour, the panic, he ‘used to get breakthroughs, I mean I used to get like suddenly a mental block's lifted.’ Gordon Murray The Structure of Scientific RevolutionsMediocratopia progress
Drawing the bits That's what is great about race car design, because even though you've had the big idea - the “light bulb” thing, which is fun - the real fun is actually taking these individual things, that nobody's every done before, and in no time at all try and think of a way of designing them. And not only think of a way of doing them, but drawing the bits, having them made and testing them. Gordon Murray
Like designing things for the first time Gordon Murray insists on keeping experience 'at the back of your mind, not the front' and to work from first principles when designing. For instance, in designing a component such as a suspension wishbone, 'it's all too easy - and the longer you're in design the easier it is - to say, I know all about wishbones, this is how it's going to look because that's what wishbones look like.' But if you want to make a step forward, if you're looking for ways of making it much better and much lighter, than you have to go right back to load path analysis. It is like designing things for the first time, rather than the nth time. The eyes of a travelerZen Mind, Beginner's MindTotal collaboration experience
Wonder Plots Working from first principles, and working in a highly organized way seem to come naturally to him, but his personal design process is much less structured than the results might suggest. Although he can tightly organize his team and run a complex racing organisation, his personal ways of designing are relatively unstructured, based on annotated, thumb-nail sketches. ‘I don't sit down and say, OK, now I've had the idea, let's see, this is a solution, these are the different ways to go, if I do this, and do that; I do lots of scribbles just to save it, before I forget.’ Gordon’s design process is based on starting with a quick sketch of a whole idea, which is then developed through many different refinements. ‘I do a quick sketch of the whole idea, and then if there's one bit that looks good, instead of rubbing other bits out, I'd put that bit to one side; I'd do it again and expand on the good bit, and drop out the bad bit, and keep doing it, doing it; and end up with all these sketches, and eventually you end up throwing ninety percent of these away.’ He also talks to himself - or rather, writes notes to himself on the sketches; notes such as ‘rubbish’, ‘too heavy’ or ‘move it this way 30mm.’ Eventually he gets to the stage of more formal, orthographic drawings, but still drawing annotated plans, elevations and sections all together, ‘Until at the end of the day the guys at Brabham used to call them “Wonder Plots”, because they used to say “It's a wonder anybody could see what was on them”!’ The Design Squiggle
I never have engineers that aren't designers Although Gordon Murray carried immense personal responsibility for the design work of his racing cars, inevitably it involved a lot of teamwork. Clearly he has been successful in inspiring others to work with him. He likes to involve team members in the design problems, and for that reason prefers to recruit all-rounders to his team; ‘I never have engineers that aren't designers.’ Designing with code
The problem with CAD He also likes to work collectively, standing around a drawing board discussing problems and trying ideas. For this kind of teamwork, and especially for conceptual design work, he finds computer aided design systems too restrictive. For the McLaren F1 super-car, he installed a five-metre long drawing board in the design office, so that the car could be drawn full size. ‘The problem with CAD for this sort of stuff is that you can never have a full-size drawing, unless you do a print, and by the time you do a print it's out of date in the concept stage.’ He also does not like the one-person emphasis of CAD screens; ‘You can only ever talk to one person at once - you stand behind and look over somebody's shoulder, which is not very good for a boss-designer relationship anyway, to have somebody standing behind you is never a good thing. To look over somebody's shoulder at a tiny little screen, it's just wrong, it's totally wrong.’ (On the other hand, he fully acknowledges that tasks like a complex suspension plot to determine the wheel envelope are ideal for CAD.) collaboration
Drawing as a means of thinking Two-dimensional plans or sections can be seen with sketches and more diagrammatic marks all on the same piece of paper in what appears a confusing jumble.’ These sound like Gordon’s ‘wonder plots’. The architects also use their drawings as a means of thinking ‘aloud’, or ‘talking to themselves’, as Gordon put it. For example, Lawson reports the architect Richard MacCormac as saying, ‘I use drawing as a process of criticism and discovery’; and the engineer-architect Santiago Calatrava as saying, ‘To start with you see the thing in your mind and it doesn’t exist on paper and then you start making simple sketches and organizing things and then you start doing layer after layer.... it is very much a dialogue.’ The common elements in these similar descriptions are the use of drawing not only as a means of externalising cognitive images but also of actively ‘thinking by drawing’, and of responding, layer after layer and view after view, to the design as it emerges in the drawings. These observations also confirm Schön’s observation of designing as a ‘reflective conversation’ between the designer and the emerging design. It is the reliance on drawing, and the preference for the immediacy of the interaction and feedback that manual drawing gives, that makes the architects, like Gordon Murray, unenthusiastic about CAD as a conceptual design tool. Section-perspective drawingThe situation talks backWhen we make a model and realize it's rubbish drawing
A new gestalt The innovator has a systems mind, one that sees things in terms of how they relate to each other in producing a result, a new gestalt that to some degree changes the world. Michael Maccoby innovationsystems
Intense activity, then relaxation The working style is based on periods of intense activity, coupled with other periods of more relaxed, reflective contemplation. This working style may not be a reflection of a particular personality trait, but a necessary aspect of creative work, which requires alternating intense effort with relaxation. creativity
Strategic, not tactical The working methods of the innovative designer are, for the most part, not systematic; there is little or no evidence of the use of systematic methods of creative thinking, for example. The innovative designer seems to be too involved with the urgent necessity of problem solving to want, or to need, to stand back and consider their working methods. Their design approach is strategic, not tactical. strategy
Drawing for parallel design thinking An important feature of their strategy is parallel working - keeping design activity going at many levels simultaneously. The best cognitive aid for supporting and maintaining parallel design thinking is drawing. Drawing with the conventional tools of paper and pencil gives the flexibility to shift levels of detail instantaneously; allows partial, different views at different levels of detail to be developed side by side, or above and below and overlapping; keeps records of previous views, ideas and notes that can be accessed relatively quickly and inserted into the current frame of reference; permits and encourages the simultaneous, non-hierarchical participation of co-workers, using a common representation. The drawing of partial solutions or representations also aids the designer’s thinking processes, and provides some ‘talk-back’. As well as drawing, innovative designers frequently like to undertake practical work related to the design solution, such as building models or mock-ups, or participating in construction. Back to the Drawing Board drawing
A small team of committed coworkers The innovative designer also likes, perhaps needs, to work with a small team of committed co-workers who share the same passions and dedication. On Talent teamwork