5 ms·
I don't really understand why Patreon needs so many employees. We're talking about almost 300 people to just supervise a fully automated process. The tech has a
by Nextgrid 7y ago
I don't really understand why Patreon needs so many employees. We're talking about almost 300 people to just supervise a fully automated process. The tech has already been built almost a decade ago and hasn't changed much, so it can't require that much engineering work. It's also an easy problem (take X amount of money, divide it between Y people, pay them out) and they ironed out any potential issues over the years.
For what it's worth I've stopped using Patreon when they included some Facebook tracking (among others) on the membership management page that when blocked will crash the entire front-end and make the entire page unusable.
- jackson1442 7y ago>take X amount of money, divide it between Y people, pay them out What's astounding to me is they don't even do _that_! It's a many-to-one payer-payee scheme... essentially a pretty wrapper for Stripe.
- rasz 7y agoBecause they took VC money and need to show fake growth.
- Trasmatta 7y ago* Product is successful * Hire lots of people because that's what successful companies do * Product development slows way down, because you hired too fast (Mythical Man Month stuff kicks in, where adding more people to a team can slow development down, if not done carefully and thoughtfully) * Notice that development is slow, so you hire even more people to try and speed it up At least that's been my experience at 3 different companies.
- mrnobody_67 7y ago100% correct. I love the Carta philosophy on hiring - every person you need means you've failed to execute: https://carta.com/blog/how-to-hire/ https://carta.com/blog/how-to-hire/ Unfortunately they didn't heed their own philosophy given their layoffs with simultaneous massive fundraise.
- deleted 7y ago[deleted]
- whatshisface 7y agoA healthier dynamic with the same result: - Value of a 1% improvement at $100/week revenue: $104 of developer time. - Value of a 1% improvement at $1M/week revenue: $1,040,000 of developer time.
- sk5t 7y agoHiring too much is a problem, but also bear in mind that having customers sort of gums up the works--you can't go changing stuff on a whim without communication, more careful assessment of impact, migration plans on customers' schedule--it's easier to be nimble when there's nothing to conserve.
- nikanj 7y ago* Product isn't that complicated at heart, so new hires busy themselves with complicating it, to justify their paychecks * Your easy to manage monolith is now seventy-three microservices, in case you need to serve Google levels of traffic without any further engineering. You're hopelessly understaffed to keep the monstrosity stable, so now you've got to grow your engineering corps to Google scale.
- eganist 7y agoSome of the services Patreon offers bring them dangerously close to being regulated as a lender, or even a bank. Wouldn't surprise me if some number of their staff are retained to meet any such compliance needs.
- SpelingBeeChamp 7y agoSuch as?
- eganist 7y agohttps://www.theverge.com/2020/2/18/21142306/patreon-capital-loans-jack-conte-cash-advances https://www.theverge.com/2020/2/18/21142306/patreon-capital-... tl;dr: payday loans
- rtpg 7y agoI feel like this sort of comment can only come from somebody who's never had to deal with operations. When you have a lot of users (especially when they rely on you to get money from you!) even 0.1% of them asking questions and having difficulties is a huge work generator! It's not "oh it's easy to write a for loop". It's "my for loop now has 20 non-orthogonal options, and a user is saying we emptied their bank account and now we gotta make sure if we did". Also a content host, a CMS, and reporting software for taxes and the like. I mean I bet you could get away with 100 people or something for this but there's _so much_ that can go wrong and would require lots of intervention.
- crazygringo 7y agoExactly this. A lot of people don't seem to realize, when you're dealing with communities -- especially communities that involve money flying around -- there's tons of work in managing it. You've got employees trying to grow the community in different areas (genres?) and different geographies, reaching out to people, giving advice to get them on board. You've got employees giving support. You've got employees looking for irregularities and fraud among all the finances. Sales, marketing and operation are huge parts of businesses that many engineers don't often think about.
- imtringued 7y agoThat argument makes sense when you are Reddit which has 400 employees. Patreon has no excuse.
- TylerE 7y agoIf 0.1% of your customers cause 80% of your effort maybe rethink that retention?
- baron_harkonnen 7y ago> I don't know why X needs N people This statement can be made about almost any company in the US right now. There is some serious systemic risk in the surreal number of people working whose jobs do not matter at all. Even for productive software engineers, think back on how many projects in your career really shipped, how many of those then made any money, and then how many of those companies are still thriving. For me nearly all of the work in my career has amounted to surprisingly little and I have always been on the front lines of creating products in my roles. So why are there so many people at every company that don't really create value? What does it mean when an economy depends on those people being employeed, well paid and consuming goods?
- kyuudou 7y agoIt's the Jack Welch algorithm
- danans 7y ago> There is some serious systemic risk in the surreal number of people working whose jobs do not matter at all. There is perhaps greater systematic risk in not having backups. Too much efficiency can equal a lot of fragility.
- imtringued 7y agoI've once read a HN comment that said that Aboriginees are economically useless and should work in a major city so that they can be useful. This completely ignores systematic risk posed by nuclear weapons or viruses like covid-19. Those Aboriginees have much better survival skills than the average NYC resident and they are far away so they are more likely to survive global disasters.
- danans 7y agoMy comment was about the fragility created by running organizations too lean from # of employees perspective. I have no issue with Aborigines' life choices and don't consider them economically useless at all, so I'm not sure what that has to do with the subject.
- miguelmota 7y agoI was at a consumer facing startup where about 70% of employees were in-house customer support representatives, so even though a product may appear simple, it can have a lot of non-programmer employees.
- jacobsenscott 7y agoNothing is fully automated. At their scale even if a small fraction of their users need manual intervention that's a lot of work. I'm sure they didn't freeze their feature set 10 years ago - they have a feature backlog for sure. On top of that they appear to have an ios, android, and web app. At their scale they need an infrastructure team just to keep the plumbing working. Their administrative back end is at least as complex as their user facing front end, and probably is also constantly generating feature requests. We are easily up to 30 engineers and more support people. That means accounting, HR, managers, payroll. The beast grows.
- Hoasi 7y ago> I don't really understand why Patreon needs so many employees. Good question, I am curious about how it compares with how Gumroad operates.
- Kye 7y agoGumroad's open board meetings might give some insight into this: https://www.youtube.com/playlist?list=PL_DfN-mKCGNuswqERc6sIA8urYAKARc6s https://www.youtube.com/playlist?list=PL_DfN-mKCGNuswqERc6sI...