3 ms·
The first few, I don't fully agree with. I think the numbers are exagerated. But these 2 have more truth: "Although most software is made by teams, it is not
by wccrawford 16y ago
The first few, I don't fully agree with. I think the numbers are exagerated. But these 2 have more truth:
"Although most software is made by teams, it is not a democratic activity. Usually, just one person is responsible for the design, and the rest of the team fills in the details."
When things are designed by 1 person (IME) they work better and have a more flowing work flow. Designing in a committee has been a freaking nightmare.
"Programming is hard work. It’s an intense mental activity. Good programmers think about their work 24/7. They write their most important code in the shower and in their dreams. Because the most important work is done away from a keyboard, software projects cannot be accelerated by spending more time in the office or adding more people to a project."
While I don't 'code in the shower', I do think about my projects constantly. An 'ah hah!' moment can come at any time. Just the other day I left for lunch and in the car on the way I thought of a possible reason for an issue we were experiencing. I was getting nothing while staring at it.
- kranner 16y agoI agree with you - I believe that, in most cases, the whole industry suffers from too many cooks spoiling the broth.
- cagey 16y ago"When things are designed by 1 person (IME) they work better and have a more flowing work flow. Designing in a committee has been a freaking nightmare." I completely agree. Yet in industry, being that one person (like I am) leads to great management consternation to the tune of "what if you're hit by the proverbial bus?" which leads to "you need an understudy", which leads to expending 2x the resources to achieve <2x results (the time spent selecting, training and guiding an understudy is definitely nowhere near 0, even when the choice of understudy turns out to have been a good one), and there can't help but be some feeling of "training your replacement". Industry loves interchangeable parts (people), and a one-man-band (domain expert or similar) grates against that ethos.
- mseebach 16y agoI hate the proverbial bus. It seems to assume that central employees should be completely dispensible. If a key employee, being the architect or even the CEO, is hit by a bus, the company will take a hit. If employees are a central, strategic assets, you can't go around killing them off and expecting no impact on your business. Deal with it. The important metric is whether the company/project can recover, if it is resilient. Just because one guy drives the decisions, it doesn't mean that the team filling in the details don't know the code and the motivations behind it, and there can't be a guy from that team who could take a promotion, or that the team couldn't be reasonably productive for a while, while a new architect is brought on.
- noblethrasher 16y agoIn short, stakeholders should always be concerned with the potential discontinuity of (especially high) performance. But it's rather like technical debt (or any other kind); something that should be managed rather than avoided at all cost.
- skybrian 16y agoThat's a bad way to think about it. You probably don't want to work on the same project forever anyway, and if you're so smart, teaching other people what you know is the most important thing you should be doing. The bottleneck on many projects (especially those that are either poorly defined or particularly novel) is not coding speed, but rather learning speed. The faster the team learns about the problem it's really solving, the environment the solution has to live in, the people who will have to use the software, and what the possible solutions are, the faster you're done.
- hga 16y agoApropos of the 1 person design thesis, the Antipatterns book said that only 1 in 5 programmers "get" abstraction. That's why democratic design processes tend to fail: the ones who get it are outvoted by the ones who don't. And that certainly matched my quarter century experience in the field, and boy was it frustrating to watch teams try to build frankly impossible systems. Heck, I'd be happy if more people got and could use big O notation. In one particularly unhappy case my peers just couldn't grok that the design would vastly outstrip the database's maximum transaction rate in normal customer configurations (number of client workstations).
- makmanalp 16y agoThat's like saying only 1 in n people have food, shelter and education. The ones that do have this property are likely to be with their peers (or close), as are the ones that don't.