I enjoyed the article - is this too strong a look in the mirror for most folks? My ideal job now is one where I can live in the bush, have boring but steady work, and otherwise not care about programming after 5pm and feel OK with myself for it.
I enjoyed the article - is this too strong a look in the mirror for most folks? My ideal job now is one where I can live in the bush, have boring but steady work, and otherwise not care about programming after 5pm and feel OK with myself for it.
I've been around since Bubble 1.0; I started working in San Francisco in 1997. The thing I find horrifying about this article is the way Vision Critical apparently takes the worst aspects of startups and amplifies them, while taking the best aspects and perverting them.
As example, I was an early Agile person; I went to the main US Agile conferences 2001 to 2008 or so. The whole point of things like sprints and standups was to control schedule pressure and keep our work lives sane. The point of agility was not to increase risk and fear, but to make it safe to take risks so that we could be both bold and serene. If you had focused on "maximizing productivity", you would have received stern talkings-to about "outcome, not output." The point was not to put on a show of working hard; it was to radically increase effectiveness.
The sales-bro culture of competition and aggression is also nightmarish to me. It's inevitably short-sighted. I'm sure it works to generate rapid growth, but at what cost to the people and the long-term prospects of the company? It's a sign to me that they definitely aren't changing the world, but instead are likely pushing a mediocre-or-worse product on the world. As if that's new.
For what it's worth, I have the impression that this sort of awfulness is is more common in tech startups that aren't in SF/SV. I take it as classic cargo culting: instead of adopting the important parts, they adopt the visible parts. So maybe some of the saltiness here is just where people are working.
This is the most succinct description of cargo cutting I have come across. Thanks, will use it :)
... which has exactly zero concrete advantages if there's only one implementation of the class.
Edit: of course it is up to individual judgement on a case by case basis, and there are instances were it is obvious that no other concrete implementation of an interface will be required. But otherwise, writing an interface is good practice because it helps safeguard against time consuming future refactoring.
Also, people pretend like refactoring is hard. My experience is that refactoring is only hard on the ends of the spectrum, where someone has added all the wrong abstractions, or no abstractions at all. Of the two, I'd prefer the latter, but obviously anything in the middle is usually better.
The comment above said the opposite, that the future was irrelevant.
These days there are tools that can help in a lot of languages; it's not a time consuming operation to press the Resharper "extract into abstract interface" button.
Because their bosses tell them to and because it looks better on their resume, not because the code they have suddenly stops working.
Chances are you're not gonna need it. Chances are you don't even need most what you do have.
And in environments like that, YAGNI makes even more sense. Overbuilding now in hopes it will pay off later is never a great idea. But it can only ever pay off if you correctly predict your business and technological future accurately. When you guess wrong, it's just waste.
Of course not, because they aren't really hiring 10x programmers (whatever that is), they are just hiring low self-esteem people, slap the 10xer label on them, strap them on the hamster wheel and work them to death.
It's a bit like the series "The Good Place" -- "heeeyyyy we only hire 10xers, you're a 10xer, aren't you proud? Right, now go prove you're a 10xer by working your butt off".
On the other hand these startups are voluntary organizations. You choose to work there or not. I don't see anything wrong with a company deciding on a culture/work enviornment which attracts people who are very dedicated to the company (and hope to be rewarded in the long term as such) and are willing to sacrifice personal time more than typically expected at a usual company.
Some people love working and solving hard problems (and having tens/hundreds of thousands of people use their software) more than going to restaurants or night clubs or having family - at that point in their lives.
It's one thing to work obsessively and to the detriment of your health. But that doesn't mean a small team of "10xers" is necessarily a toxic/abusive arrangement that people are forced to engage with.
There will always be plenty of 9-5, no nighttime/weekend type jobs for software developers. You just won't find them as often at high-growth/high-risk+high-reward type startups.
That said, not all high risk/reward agencies require an obsessive/super hard worker type either. But that type of commitment isn't necessarily a bad thing either (unless they do it to the point of hurting their own health, which hurts the intellectual/physical ability and ultimately their contribution to the company).
I know for a fact it's possible to put above average commitment into a company, while still being entirely health. But it's certainly not for everyone, nor should it be. That also doesn't mean you should feel bad for getting fired or pushed out of such a company because it's not for you.
Healthy or not, if the employee does not get above average renumeration for their above average efforts they are being ripped off. That's what the financial pathology here is - if everyone is working with an above average output, but thei pay is average, from the point of view of the company the cost of labour for above average output is less than the market rate, and it's harder to get fair compensation.
I don't think there is anything wrong in working ones ass off, but if the worker is just an employee they should make sure their compensation is fair, versus the market rate.
People often imagine that they will get a fair compensation for their work, while generally actually they get only the compensation which they ask for.
That's why this 'work hard party hard' culture can be detrimental IMO - it easily blinds people to the financial realities of their situation.
That's not to say that professional 10x operations would not exist where labour is rewarded faiy, but that the employee must be aware of what the unspoken gameplan actually is. Is it cultish razzle dazzle to get cheap labour or actual 'entrepreneurial spec ops' type activity.
That’s OK in theory but in practice it’s almost always a bait-and-switch relying on the marks not knowing the difference between preferred and common stock, or what dilution is.
Easy test: do they say “10,000” shares but don’t tell you how many shares there are?
In the absence of a basic income guarantee, the decision to take a job is a long way from truly voluntary. As long as people are obliged to take jobs, these exploitative jobs have to be illegal (in the same way that e.g. conventionally unsafe working conditions are illegal, even if the employee might "voluntarily" agree to them).
I think this sounds good in theory and is very shaky in practice.
For example, look at indentured servitude [1], where people can sell themselves into time-limited slavery. Once common, it has been banned. You will find people suggesting we bring it back while waving the banner of "freedom".
It's especially erroneous here. This whole article is about how he thought he was getting into one thing based on the hype, but that the reality was deeply different. He talks about it as cult-like, cults being organizations that take advantage of flaws in human cognition to manipulate people.
If free choice is to mean anything, it must be a choice that was honestly informed and unmanipulated. To use it as an excuse in a situation like this is just victim-blaming.
Here in particular he makes clear it's a veneer: "Six months in, I started to see through the acronyms and the carefully maintained optimism of my teammates. For all the talk of agility and disruption and 10X, there was a deep fear of fucking up."
Real cults regularly use reasonable-sounding religious jargon and performative optimism to paper over deep flaws. So I think he correctly describes this as cultish. And that's before we even get into the other cult-ish signs. You can do your own scoring here: http://www.neopagan.net/ABCDEF.html
If it were shaky, a court of law somewhere would find a comparable employment arrangement fraudulent and ultimately non-voluntary.
Social activists appealing to the court of public opinion, where under-informed people can be swayed with appeals to emotion, to change how interactions are governed, instead of a court of law, where a jury of one's peers have the opportunity to deliberate on the evidence presented, reveals them as disingenuous.
If a position has never been corroborated by court rulings, despite incentives existing to argue that position, then it's almost certainly not factually sound.
If you're going to make outrageous claims of the courts using an alternate definition of "voluntary", that is inconsistent with the correct or generally accepted definition, you need to provide evidence of that, and no, your own sweeping generalizations about a vast array of complex interactions is not evidence of anything except your own opinion.
Another time I interviewed at a company that I found cool and I was interested in their product. I asked, "How is work life balance here" and they answered "we have many projects in the pipeline". I told them their salary was too low. I left and my recruiter called me upset that I changed my salary expectations during the interview.
Some companies are shitty.
I enjoyed the article but I do think it's very wrong as a general claim. I like my job (is that so wrong?) and don't want to see it smeared by association with two badly-behaved companies that happen to be in the same broad category.
Plenty of startups won't expect you to work after 5pm - I never did, across several companies. Plenty of staid non-tech companies expect unreasonable hours.
How come when he interviewed at a dozen more start ups at the end of the story, he didn't find himself in an interview where he could discuss the 10x-start-up culture downfalls?
Or maybe that middle road is extremely rare.
Maybe they didn’t want to? They tried a few tech startups and didn’t like the experience; it seems natural to then say “I think I’ll do something else instead”.
It's classic, "I know more than you" mentality, where the author believes the people who buy into the culture are being duped, and he's the only one who can see clearly.
I'm so sick of being told to be less optimistic and positive about the company I work for, because my optimism is just me subscribing to the "cult". It reeks of that classic teenage "it's cool to hate/dislike/criticize stuff" attitude that I'd expect my colleagues to have grown out of by now.
Would love to find such a job, but sadly they don't seem to exist. It's either startups like described in the article, or major companies cheating the system and building startups within so they can hire contractors instead of employees and pay start-up rates. Every company in Toronto does it, even the large ones (hello banks, telcos)
We're still in the EU and I've no idea why you think we are anything like the US in terms of overworking. I've never had a job that required me to work overtime really, sometimes I've stayed behind in my latest job as I got lost in the moment and lost track of time, but usually someone will ask me "Why are you still here?". My manager even told me not to work overtime, as it often hid problems more than anything else.
In fact I don't know anyone in Web Development in the UK that does work overtime. Maybe it's different in London though...
If companies instead genuinely tried to care for their employees, I think the sentiment would be very different.
Expectations quickly rose to time on weekends, responsiveness to emails and requests at all hours of the day, and job duties ranging from DevOps and app development, to customer and client support for all issues after they let go of their customer support team.
I'm about ready for a bush somewhere.