Live data from Hacker News

How Software Companies Die (1995)

zoion.com

11–19 of 19 posts

Re: How Software Companies Die (1995)

#11
post #9

Other previous discussion. This one is 120 days ago http://news.ycombinator.com/item?id=4776844 Personally I don't see why this resonates so much with the HN community. Its a great example of the worst attitude to take to work every day.

Personally I don't see why this resonates so much with the HN community.

Really? This is like a nerd mantra, it hits so many stereotypes in so few words. Orson talked about it at BayCon once when it came up.

I don't have a clear memory of exactly what he said but I took away from it that smart, introverted, people have a terrible time seeing anything outside their pool of influence, like looking at your shoes in a crowd and saying "everyone is crowding around me because I'm the coolest" when if you looked up you would see a pack of wolves circling the crowd. So all of their evaluation in their environment is about them and how people around them are responding.

An artifact of that inward looking view is to construct an internally consistent explanation for why things suck now but didn't before. That always targets people who are not like them (the introvert) and for whom the introvert cannot understand their motivations or values. (and more often than not in a software company that is "suits", aka business people or managers)

You combine that with a changing market place, and the thing that made the software successful before isn't valid any more, but if the programmers don't know why the software was successful in the first place they can't understand what changed or how to fix it. Imagine an artist who paints with charcoal, gets discovered, people buy their works, and then fashion moves on, and the artist goes broke. To an external viewer, fashion simply moved on, the artist was there (and fashionable for a time) and then they weren't. But internally the artist may have no concept of how briefly they were fashionable and now they weren't. Instead they construct an externalization of "discovery" where suddenly people begin to understand what it is they are doing with their art, and when they move on it is always some external force which has corrupted the minds of people seeing it or modified their vision. To accept the alternative, that their success was luck and fashion, rather than some deeper meaning, may be too harsh to think.

People cling to sense of destiny and purpose rather than consider themselves the random connection of ova and zygote and circumstance. Where is the meaning in that?

Orson captured this tension wonderfully in his essay, it resonates both with the bees who desperately want to be special and with the bee keepers who want productive bees without understanding that the bee's production is a byproduct of flowers and normal bee activity, it's a side effect of where the hive is and where the flowers are. Many software companies are fashion objects, successful ones are constantly producing new concepts and new ideas to stay in the limelight. Unsuccessful ones take a single success and assume they are done, nothing left to do but iterate. But fashion doesn't work like that.

Re: How Software Companies Die (1995)

#12
This is the most classic conversation with an India nigger.

Me, "Sorry, that's not how it works."

India nigger, "Don't be sorry."

----

They are stupid, stubborn and arrogant. Not much to like.

It's wrong to pick on the handycapped but I giggle laughing at explaining scaling working both ways. Global variables work in small scale. "This is not how you must do it. You do not understand programming." Knuth wanted 32-bit pointers on 64-bit systems. My boss Pete considered 16-bit on a 32-bit system back in 1993. This is simply not comprehensible by an India nigger.

Re: How Software Companies Die (1995)

#13
post #9

Other previous discussion. This one is 120 days ago http://news.ycombinator.com/item?id=4776844 Personally I don't see why this resonates so much with the HN community. Its a great example of the worst attitude to take to work every day.

Personally I don't see why this resonates so much with the HN community. Really? This is like a nerd mantra, it hits so many stereotypes in so few words. Orson talked about it at BayCon once when it came up. I don't have a clear memory of exactly what he said but I took away from it that smart, introverted, people have a terrible time seeing anything outside their pool of influence, like looking at your shoes in a cr…

Fashion is never finished.

Re: How Software Companies Die (1995)

#14
Short and to the point. I have lived this reality more than once. And its truer now than it was when it was written. One thing that seems certain, we careerist engineers will never stand up for our values. On that they can count.

Re: How Software Companies Die (1995)

#15
came from a big company, escaped to start-up world but also a marketer. take offense that marketers are the problem here. coders aren't the only ones who get the life blood sucked out of them by too much management. good marketers love to work with good coders and relish in creativity and risk-taking.

Re: How Software Companies Die (1995)

#17
post #9

Other previous discussion. This one is 120 days ago http://news.ycombinator.com/item?id=4776844 Personally I don't see why this resonates so much with the HN community. Its a great example of the worst attitude to take to work every day.

This resonates because it is a perennial problem that anyone that works in a technical or hacker role is going to face. It is not an "attitude", it is a business reality rooted in economics. There is a direct conflict between people who want to innovate and people who want to simply streamline existing money making enterprises. Streamlining wins because it is lower risk. Innovation dies and then no more streamlining can be done. The innovators leave, one way or another. The business either becomes a cash cow or new innovative competitors kill it off.

Re: How Software Companies Die (1995)

#18
post #2

Previous discussion on HN https://news.ycombinator.com/item?id=552821

1435 days ago- that's almost 4 years. I wonder if one day in 2034 someone will post a "done that" link with a conversation over 10k days old?

FWIW I found that helpful as the old discussion made some interesting points that are not made invalid by the passing of a few years.

Re: How Software Companies Die (1995)

#19
This is a good start, but ultimately doesn't have much insight into why companies die. Venkat Rao opened this discussion with his Gervais Principle series, which is very good: http://www.ribbonfarm.com/2009/10/07/the-gervais-principle-o...

I continued it with my (ongoing) series on my blog (8 parts and counting, will take a while to read): http://michaelochurch.wordpress.com/2013/02/19/gervais-princ...

Companies start out as a risk transfer. Those who can tolerate financial volatility and change and social upheaval (MacLeod Sociopaths) start to trade risk with those who don't want it (MacLeod Losers). The risk-seekers become the entrepreneurs; the risk-averse become workers. This is benign for a while, but as the company becomes stable, the upper class becomes entitled, established, and complacent. They want to keep the perceived risk trade going, but the business is actually de-risked, so now they're just grabbing for unjustified or legacy superiority. They've won, and now they want to stay where they are. In order to keep the risk-transfer between them and the (expectancy-sacrificing) Losers, they have to create a middling buffer class of Clueless. This style of organization becomes resistant to change, systemically underperforming, and bland, but it's extremely stable on its own terms. People don't want the jobs above them enough to break the rules. Losers (who value comfort and stability) see the ranks above them as being harder, riskier, and are happy to stay put. Clueless are oblivious to the Effort Thermocline (the point in an organization where jobs become easier-- but also more political-- with ascending rank instead of harder) and run the organizational day-to-day while oblivious to the agendas of the Sociopaths above them.

The most common end state of this is the organization with the full MacLeod hierarchy: Losers at the bottom, Clueless in the middle, Sociopaths at the top. It's a mature rank culture where position and subordinacy matter more than creative excellence and technical improvement. But why?

The process is complex, but the truth is that this form of organizational corruption was, for a long time, harmless from a business perspective. When you're providing commodity products or services, the MacLeod rank culture works. It does the job.

What's changing (first in software, increasingly in other areas of business) is the convexity switch. Concave work is work on which the difference between excellence and mediocrity is insignificant compared to that between mediocrity and zero. It's "get-it-done" commodity work where creativity isn't necessary or even useful. Convex work is that in which the difference between excellence and mediocrity is huge, and mediocrity is close to (or might be) zero.

The difference between the (winding down) industrial and (soon to come) technological eras is the convexity of the work that the world needs. In the industrial era, most needed work was concave and the hierarchical MacLeod organization worked well. In the technological era in which the commodity work has been given to machines (who do it far more reliably and cheaply than any human) what's left is convex work. Traditional industrial management, though successful for 200 years, just falls down. The reason why is that it's all about reducing variance. For concave work, variation is mostly to the downside, and variance-reduction (the goal of most management) improves expectancy. For concave work, variance is mostly to the upside, and variance-reducing management drives expectancy to zero.

Post reply on HN