377 karma · joined January 17, 2015
"Contrary to what we would like to believe, there is no such thing as a structureless group. Any group of people of whatever nature that comes together for any length of time for any purpose will inevitably structure itself in some fashion. The structure may be flexible; it may vary over time; it may evenly or unevenly distribute tasks, power and resources over the members of the group. But it will be formed regardless of the abilities, personalities, or intentions of the people involved. The very fact that we are individuals, with different talents, predispositions, and backgrounds makes this inevitable. Only if we refused to relate or interact on any basis whatsoever could we approximate structurelessness -- and that is not the nature of a human group. This means that to strive for a structureless group is as useful, and as deceptive, as to aim at an "objective" news story, "value-free" social science, or a "free" economy. A "laissez faire" group is about as realistic as a "laissez faire" society; the idea becomes a smokescreen for the strong or the lucky to establish unquestioned hegemony over others. This hegemony can be so easily established because the idea of "structurelessness" does not prevent the formation of informal structures, only formal ones. Similarly "laissez faire" philosophy did not prevent the economically powerful from establishing control over wages, prices, and distribution of goods; it only prevented the government from doing so. Thus structurelessness becomes a way of masking power, and within the women's movement is usually most strongly advocated by those who are the most powerful (whether they are conscious of their power or not). As long as the structure of the group is informal, the rules of how decisions are made are known only to a few and awareness of power is limited to those who know the rules. Those who do not know the rules and are not chosen for initiation must remain in confusion, or suffer from paranoid delusions that something is happening of which they are not quite aware."
Her comments were aimed at the feminist movement of the 1970s, but her essay is universal and everyone can gain from reading it:
The Tyranny Of Structurelessness
Software Runaways: Monumental Software Disasters.
Anyone with an interest in the management of software projects should read it.
The worst of these project failures, the most expensive and the most ambitious, was the attempt made by the Federal Aviation Authority to modernize the computer system it uses to keep track of what planes are in the air. The effort began in 1981 and ended in complete failure in 1994. The government hired IBM to do the actual work, and over the course of 14 years, IBM burned through $3.7 billion dollars. Nothing was accomplished. The project was finally shut down by Congress. Nothing came out of the project, not a single piece of software, nor even a line of code, was ever used for anything.
From the book:
It has been noted by everyone from the New York Times to the Vice-President of the United States that the main problem on the Advanced Automation System was "changing requirements". For those involved in large-scale computer systems, that is nothing new. No one can perfectly surmise the shape and feel of a system years in advance. Even replacing some aspect of a system you know by heart is not immune from thinking twice about it. ... [But] the requirements churn (it was called) on the Advanced Automation System was not normal. It was the result of our enchantment with the computer-human interface, the CHI. The new controller workstation, fronted by a 20" by 20" color display, because it was capable of seemingly endles variety of presentations, mesmerized the population of AAS like the O.J. Simpson trial mesmerized the nation...
The project was handed over to human factor pundits, who then drove the design. Requirements became synonymous with preferences. Thousands of labor-months were spent designing, discussing, and demonstrating the possibilities: colors, fonts, overlays, reversals, serpentine lists, toggling, zooming, opaque windows, the list is huge. It was something to see. (Virtually all of the marketing brochures - produced prematurely and in large numbers - sparkled with some rendition or other of the new controller console.) It just wasn\'t usable...
Rummaging through one of the closets at the far end of the hall on the fifth floor one day, looking for some standards document, I found an envelope left by someone who left the company - as many did after so many years advancing against stone, while the wheels of commerce were accelerating on what everyone referred to as "the outside". It contained "A Brief History Of The Advanced Automation System". It was printed by hand and left, perhaps inadvertantly, or perhaps with the hope that some anthropologist might some day discover it and make a pronouncement. In every important way, it is the truth:
"A young man, recently hired, devotes years to a specification written to the bit level for programs that will never be coded. Another, to a specification that will be replaced. Programmers marry one another, then divorce and marry someone in another subsystem. Program designs are written to severe formats, then forgotten. The formats endure. A man decides to become a woman and succeeds before system testing starts. As testing approaches, she begins a second career on local television, hosting a show on witchcraft. An architect chases a new technology, then another, then changes his mind and goes into management. A veteran programmer writes the same program a dozen times, then transfers. The price of money increases eight times. Programmers sleep in the halls. Committees convene for years to discuss keystroking. An ambitious training manager builds an encyclopedia of manuals no one will ever use. Decisions are scheduled weeks in advance. Workers sit in the hallways. Notions of computing begin in the epoch of A, edge toward B, then come down hard on A + B. Human factors experts achieve Olympian status. The Berlin Wall collapses. The map of Europe is redrawn. Everything is counted. Quality becomes mixed with quantity. Morale is reduced to a quotient, then counted. Dozens of men and women argue for thousands of hours: What is a requirement? A generation of workers retire. The very mission changes and only a few notice. Programming theories come and go. Managers cling to expectations, like a child to a blanket. Presentations are polished to create an impression, then curbed to cut costs. Then they are studied. The work spikes and spikes again. Offices are changed a dozen times. Management retires and returns. The contractor is sold. Software is blamed. Executives are promoted. The years rip by with no end in sight. A company president gets an idea: make large small. Turn methods over to each programmer. Dress down. Count on the inscrutability of programming. Promote good news. Turn a leaf away from the sun. Maybe start over.
"I am from Tennessee and love that I have a very real business reason to spend more time there and shine a spotlight on some of the creativity that lives outside the coasts. And yet, it’s been made abundantly clear to me over the last year or so that a small, but influential group of men in the city do not want me or Pando there. One story that makes the point: As last year’s event was drawing to a close, one male attendee, apparently a Nashville local, stopped Pando reporter James Robinson to share his thoughts on the conference. Specifically, he wanted to share his opinion of me, or as he called me “That Pando lady.” “I can’t believe you let her leave the house,” said the man. James was left speechless. Some were bold enough to tell me to my face that my personality made them uncomfortable: I was told I “have a mouth on me.” I was even warned to “watch myself.” And, best of all, I was told that my occasional use of profanity on-stage is unbecoming for a mother (never mind that most everyone on stage at Southland swore except Al Gore and Christy Turlington, and we raised hundreds of dollars for charity through a swear jar.) The male attendees were expected to curse, but when I do it it’s just plain unladylike. Won’t somebody think of my children!
I did make good money during those years (2002 to 2009) but what I recall most fondly is how much fun all of it was.
I think that world has now largely died out, as even the earliest stage startups now belong to a scene that is somewhat professionalizing. But the earlier web was unprofessional, and that was the best thing about it.
Still I find, even now, even in New York City, there is some of the same energy among those dreaming about doing very early stage startups. Certainly the creativity and excitement is still there. The problem I've run into lately is the large number of people who are so sure that their idea will someday be worth billions that they do not want to pay cash right now, they only want to pay in equity. And that kills all of the fun for me.
Because they are so thoughtful and talented, whenever they see a flaw in a 3rd party library, they give up on that library, and they try to write their own.
So for instance:
They tried using Chef for configuration, but they didn't like Ruby. Then they tried Ansible, but they found it immature. The tried Puppet, but didn't like that it had a central daemon. So they started writing their build/config system, which they released as open source. Their system has some unusual ideas, a heavy reliance on bash, and an emphasis on supporting a polyglot system. However, this took a lot of time that could have been directed at the specific needs of the startup.
They decided they would need a system of dependency injection. In Python it is common to configure some variables at the level of the module, but they felt this lead to tight coupling. They did not like any existing system for dependency injection for Python, so they wrote their own. They released this as open source. Their DI system borrows a lot of ideas from Angular. It is clever and they have long debates about how to make it better. But this also took time that could have gone to the specific needs of the startup.
They needed a framework that would allow them to serve a website out over Nginx. They reviewed all of the existing Python web/application servers. They found flaws in all of them: Zope, Pylons, Flask, etc. They decided to build their own. They based their work on Flask but they added a lot of their own unique ideas. They released it as open source. It has been a big effort and it is still missing certain features. For instance, they started off assuming that all of the pages of their site would require a login. When they eventually had to add in some pages that did not require a login, they had to re-work the way they were handling security and authorization. All of this has taken time away from the specific needs of the startup. And, of course, their software may have security flaws which they have not yet discovered. Although it is open source, I don't believe anyone else is using their software.
They decided they needed a way to enforce contracts on the structure of the documents moving through their system, and they wanted a system that could work almost exactly the same in Python and in Angular. So they built their own library for validating the structure of documents. They built out a whole vocabulary for the "types" in their system, using types which were generic enough that they could work in both Python and Javascript. It is an interesting system, but it takes at least 25% of the time of the most senior engineer. If they did not write their own system, he would have at least an extra 10 hours a week to put toward tasks that are specific to the needs of the startup.
They wanted to store JSON but they did not like any of the JSON document stores that were available in 2011/2012. They love PostGres. This was before PostGres had a JSON column type. So they decided they would store JSON in PostGres as a string in a TEXT column. They wrote a library that serializes and deserializes the string. They built this as a layer on top of SqlAlchemy. Their code is very clever: you can query the database with their ORM and you always get back objects, you never have to think about JSON as a string. In some ways, they have reinvented the idea of an "object database" that was popular in the late 1980s and early to mid 1990s. These are clever ideas, though it took time away from the actual needs of the startup.
I could go on. They wrote their own cache system, their own system for transforming data structures, etc.
They are thoughtful. When adding a new feature to one of their libraries, they have respectful debates that sometimes last 2 or 3 or even 4 hours. They release everything as open source. They are trying to help the Python community. But it adds up to a huge tax on their time, and it takes them away from the needs of the startup. The founder/CEO is not technical, and I think they often wonder why things take so much time.
With startups, it is especially true that "the perfect is the enemy of the good." Their perfectionist streak takes them away from the needs of the company. They pursue an ideal of absolute brilliance, though they often don't have the time they need to make their libraries as good as what they dream of.
Having worked with them, I've gained a new respect for the idea that startups should, as much as possible, just use what libraries they can find. All libraries have their quirks, but it is an illusion to think it is cost effective to spend your time re-inventing what's out there.
If we focus, for a moment, on those jobs that are available to those who have college degrees, many women become teachers, but teaching is not high prestige.
There is little risk that the USA will outsource all the hospitals to China, so women go into medicine. There is little risk that the USA will outsource all the lawyers to China, so women become lawyers. There is little risk that the USA will outsource all the teachers to China, so women become teachers.
But there is a possibility that most of the engineering jobs will move to China. And I think women are wary of investing 10 years of their life learning a skill that might get sent overseas.
There are a large number of people living in China who would like to get around the nation's currency controls. There are a large number of people living in Russia that want to move money without being tracked. There are a large number of people living in Latin America who want to avoid taxes in their own countries. This is what drives the use of Bitcoin. The only large scale need for Bitcoin is criminal activity, in China, Russia, Latin America and elsewhere.
Currency regulated by the government is a classic "good enough" product. It might lack some features that would be nice, but 99% of the public doesn't seem to care. Rather, they want more money, but they don't want to change money. If they had real doubts about the currency, they would dump it in exchange for real goods. But instead, most people work hard to acquire more money, and they show no real concern with the standard proxies for currency (credit cards, checks, etc).
"Could regulation be increasing barriers to entry, raising the costs of reallocation, and slowing the diffusion of productivity innovations? To test the hypothesis that regulation is reducing dynamism Nathan Goldschlag and I combined data on dynamism with an industry level measure of regulation. Our measure of regulation is produced by an innovative technique that combs the Code of Federal Regulations (CFR) for restrictive terms or phrases such as “shall,” “must,” “may not,” “prohibited,” and “required”. The count of restrictive words in each section is then associated to industries via a machine learning algorithm that recognizes similarities between the language in that CFR section and industry language (e.g. a section of the text with words such as “pipeline” would be associated with the oil and gas industry). In this way, we can associate each industry with an index of regulation derived from the entire CFR."
That's mostly true for people who descend from people living in Europe and parts of Asia. Less so for anyone who primarily descends from Africa or Australian aborigines.
http://www.zephoria.org/thoughts/archives/2014/10/08/framewo...
danah boyd works in Microsoft Research
They plan to grow for 5 years and then sell for something between $25 to $100 million, depending on how much growth they get.
I was offered $90,000 and 1% of the company. This is a startup where the risks are fairly low, considering that they already have customers who love them, and they are cash flow positive, and they are growing quickly.
For a risky startup, I would have asked for 4%.
"Admittedly, the dynamism of Western capitalism depends upon people who work with missionary zeal, who refuse to accept that a job is merely a job."
Is it the "the dynamism of Western capitalism" that causes people to pretend to like their job, or is it the scarcity of good jobs, which forces workers to engage in an exaggerated pantomime of missionary zeal?
http://www.cdc.gov/measles/vaccination.html
"Measles can be prevented with the MMR (measles, mumps, and rubella) vaccine. One dose of MMR vaccine is about 93% effective at preventing measles if exposed to the virus, and two doses are about 97% effective. In the United States, widespread use of measles vaccine has led to a greater than 99% reduction in measles cases compared with the pre-vaccine era. "
And most people are vaccinated:
http://articles.latimes.com/2013/sep/12/science/la-sci-sn-cd...
"The federal government targets 90% childhood vaccination rates. Nationwide, Americans are hitting or exceeding that goal for measles, mumps and rubella; for polio; for hepatitis B; and for varicella (the virus that causes chicken pox). Americans missed targets for diphtheria, tetanus and pertussis, and for Hib and PCV vaccines."
However, there is something strange happening among the affluent in California, and so a great many children are vulnerable:
http://www.wired.com/2015/02/tech-companies-and-vaccines/
"We selected more than 20 large technology and health companies in the Bay Area and researched their day care offerings. Of 12 day care facilities affiliated with tech companies, six—that’s half—have below-average vaccination rates, according to the state’s data. And those six have a level of measles vaccination that does not provide the “herd immunity” critical to the spread of the disease. Now, this data has limitations—most critically, it might not be current. But it also suggests an incursion of anti-science, anti-vaccine thinking in one of the smartest regions on Earth."
'Daddy's job in video games was no longer a cool thing they liked to brag about'
That is a story that everyone should read. It is emotionally intense, and I think it says a lot about the difficulties that families face due to the instability in some industries, notably the video game industry.
I'm posting some of it here. I'm struck by how much the family tried to roll with the punches, but the punches just kept coming:
-----------------------------
We found some possibilities and, after interviewing, he received a great offer from a wonderful and stable company, in a state where we already had friends and family. We purchased a home and relocated our (now) family of six, leaving California for good. This was a really exciting move for us. Each child had their own room (they had to share in California), and they could paint or decorate their rooms however they liked. Our in-laws were in a position to buy a second home in the area, so they could be closer to the grandchildren. It was a ranch, and the kids loved to explore it. Life was looking very good, and we were all very excited about the future.21
The following summer was when we experienced our first layoff. It was devastating and extremely scary. My income wasn't enough to cover the mortgage, even with the unemployment. We received no severance, and our health benefits would run out at the end of the month.
We tried applying for positions at numerous gaming companies (and non-gaming companies) in the area, but no one was looking for my husband's skillset at that time (in addition to there being a mass layoff and the market being flooded with great talent of all levels). In the end, we were forced to relocate. We chose a studio that had been around for many years and had survived through releases of games both good and bad. We had friends in that area, and the entire situation looked like a pretty good fit for us.
We continued paying for the house while it was on the market, and we were once again put up in temporary housing. This time, the six of us had to stay in a hotel for a month, until an apartment that would fit us all became available. Once we moved into the temporary apartment, it was time for the children to start school again. We registered them knowing they would only be in the school for a month or so, and then they would move to a more permanent school once we found our own apartment to rent.
This time, our stay in temporary housing was extended due to the amount of overtime my husband had to work, and we were not able to transfer the children to their new school until they were between semesters. As was inevitable, they had begun making friendships and establishing roots, even though they knew they wouldn't be staying. It wasn't easy for them, but we had prepared them well from the start, and they knew they could keep in contact with their friends and maintain those friendships if they wanted to. I think that made it a little bit easier on them.
After we were settled and a couple of years had passed, I received notice that my appeal for in-state tuition was being granted and that I was able to register for classes at the local college. My son had been very sick for the past few months, and our family pediatrician told us that he felt our next step was surgery. He said it was probably best to do it sooner rather than later. We got him scheduled and started preparing for it. My husband requested some time off so he could be there. It was approved and we were all set.
This rarely changes anyone's mind (few people ever change their minds about issues regarding money) but I hope I can at least raise the contradiction to the top of their minds. All currencies are backed by our willingness to accept them, and that is the only backing that any currency ever needs.
"Contrary to what we would like to believe, there is no such thing as a structureless group. Any group of people of whatever nature that comes together for any length of time for any purpose will inevitably structure itself in some fashion. The structure may be flexible; it may vary over time; it may evenly or unevenly distribute tasks, power and resources over the members of the group. But it will be formed regardless of the abilities, personalities, or intentions of the people involved. The very fact that we are individuals, with different talents, predispositions, and backgrounds makes this inevitable. Only if we refused to relate or interact on any basis whatsoever could we approximate structurelessness -- and that is not the nature of a human group. This means that to strive for a structureless group is as useful, and as deceptive, as to aim at an "objective" news story, "value-free" social science, or a "free" economy. A "laissez faire" group is about as realistic as a "laissez faire" society; the idea becomes a smokescreen for the strong or the lucky to establish unquestioned hegemony over others. This hegemony can be so easily established because the idea of "structurelessness" does not prevent the formation of informal structures, only formal ones. Similarly "laissez faire" philosophy did not prevent the economically powerful from establishing control over wages, prices, and distribution of goods; it only prevented the government from doing so. Thus structurelessness becomes a way of masking power, and within the women's movement is usually most strongly advocated by those who are the most powerful (whether they are conscious of their power or not). As long as the structure of the group is informal, the rules of how decisions are made are known only to a few and awareness of power is limited to those who know the rules. Those who do not know the rules and are not chosen for initiation must remain in confusion, or suffer from paranoid delusions that something is happening of which they are not quite aware."
Her comments were aimed at the feminist movement of the 1970s, but her essay is universal and everyone can gain from reading it:
The Tyranny Of Structurelessness
I can imagine a "less likely" and "more likely" way this might play out:
1.) "less likely" would be something bordering on blatant theft -- perhaps the contract specifies options or bonuses, but the parent company, after the acquisition, no longer wants to pay. That would be fairly blatant, though not impossible.
2.) "more likely" would, I think, be issues regarding copyright, which, with software, allows something of a fudge factor, since software is always changing, and no one programmer writes the whole of a large system. I'm thinking of my own startup here: during the years 2000 to 2002 I created a content management system, which then became the basis of a company that was formed in 2002. But the founding documents of that company gave me the right to specific royalty payments for the CMS, even if we eventually agreed to dissolve the company (which we did in 2008). But suppose the company was acquired, and then the acquiring company declared that the requirement to pay royalties was null and void? This is very similar to what apparently happened with Gravity.
Worrisome.
Also, although interest rates for the national governments of some countries have reached 0%, or even negative numbers, commercial interest rates are still slightly positive.
"When Cowboy Ventures founder Aileen Lee coined the term unicorn as a label for such corporate creatures in a November 2013 TechCrunch blog post, just 39 of the past decade’s VC-backed U.S. software startups had topped the $1 billion valuation mark. Now, casting a wider net, Fortune counts more than 80 startups that have been valued at $1 billion or more by venture capitalists."
Again, this is because interests rate, in general, are very low, much lower now than they were during the original Dot Com boom, which is why valuations are higher. The math on this is simple.
Suppose you have a company that makes $1 million in profits. The question then is, at what point does it make sense to invest in something else? When prevailing interest rates are 10%, then $1 million is 10% of $10,000,000, so the company is worth $10,000,000 (excluding a million other factors for the sake of a simple model). If the company demands more than $10,000,000 to buy it, then it makes sense to invest in something else instead. If a company wants less than $10,000,000 for ownership, then it is a hot deal.
But when prevailing interest rates drop to 1%, as now, and since $1 million is 1% of $100,000,000, then for same level of profit, the value of the company has gone from $10,000,000 to to $100,000,000.
Again, there are a million other factors you could consider (do you trust the management, can they scale, how fast are they growing) but I'm going with a simple model here to demonstrate the basic driving force of modern valuations: when interest rates go down, valuations go up.
Of course, that doesn't explain why a web startup with no profits would be valued more than, say, a mature company like GE, which has known profits. Some of the wilder valuations are obviously being driven by speculation about wild growth rates.
"We used a combination of lexical features (e.g., variable name choices), layout features (e.g., spacing), and syntactic features (i.e., grammatical structure of source code)"
In particular, "layout features" is a huge issue in some languages, and not at all in others. For instance, a language like Javascript, or PHP, give great flexibility about layout, so in those languages I can see each developer having a unique style (and I have been involved in style debates regarding those languages), however, a language like Python has a fairly fixed layout, since the whitespace is significant. And also, in Clojure, I think most programmers use Emacs and accept the Emacs clojure-mode indenting as the default.
Variable name choices is another where some environments encourage similarity, and others allow for unpredictability and unique styles. Within the Ruby On Rails framework, for instance, there are norms about the creation of variable names.
I would guess that syntactic features is perhaps the one characteristic that shows a great deal of uniqueness in every language. I am often surprised at the choices my fellow co-workers make, when it comes to how to solve a problem.
"I’m talking about at Dr. Nic’s talk at RubyConf 2011, a little more than a year ago. Dr. Nic had a fairly simple message: when performance matters, build multithreaded programs on JRuby (also: stop using EventMachine). Now granted he was working the company that was subsidizing JRuby development at the time, but I didn’t, and I for one strongly agreed with him. Not many other people in the room did. The talk seemed to be met with a lot of incredulity."
So even among Rubyists, there has been growing interest in Ruby beyond the MRI, and if that is happening in the land of Ruby, then the argument for Groovy is that much weaker.
At the same time, the growing interest in dealing with concurrency certainly helped increase interest in Scala and Clojure, and furthermore, functional programming in general. If you are a developer who wants to harness the power of concurrency for greater speed, Scala and (especially) Clojure are full of interesting ideas for how to do that. Groovy, meanwhile, feels off-topic.
"Online and off, some teams consistently worked smarter than others. More surprisingly, the most important ingredients for a smart team remained constant regardless of its mode of interaction: members who communicated a lot, participated equally and possessed good emotion-reading skills."
can be read as a variation on John Boyd's OODA loop. Boyd made the point, repeatedly, that in war and sometimes in business, victory typically goes to whoever can iterate through ideas more quickly, as new information comes in. The winners are not necessarily smarter, they simply iterate faster based on the information they have. And the same seems to be true of the teams being described here.