This shows how important it is to learn about a company, it's culture, philosophy, and values before joining. I can see how some people operate like this, and I don't want to work with them.
For anyone reading this who thinks all companies are like the one that parent described, I want to share that it is not true. There are plenty of companies who based their collaboration with their workers on other mental models than cogs-in-the-machine.
I may sound dumb, but how does one do this? What question would you ask in an interview in order to determine whether the management are apathetic to their users or employees?
The three interviews I did at my current company gave me a glimpse into the culture, but only a surface-level "first impression" kind of knowledge. With that said, I think I successfully ascertained the company's vision with the product I'm working on, but that's way easier to learn than culture IMO.
Open-ended questions like that.
If the CEO can tell you about how engineering changed the product, but the dev can't, then your experience is going to match the dev's. And the part of "engineering" that changed the product was almost certainly not a dev.
Besides, it is common for CEOs to think that they are more responsive than they really are. And they are generally better at marketing than truth. So for both reasons, I would not trust their answer unless it is backed up by the rank and file.
There is no single approach. It's a soft skill. I don't think there is a single magic question you can ask and you'll get a black-and-white answer.
Here are some ideas:
- read about the company on glassdoor. Try to read between the lines. Are the reviews fluff? Are there any veiled criticisms. Read the high praises and the vulgar criticisms with a grain of salt. They are a signal, but people often have an agenda or are led by emotion when they post like that. Pay attention to the mixed reviews who give you the good and some bad. See if there are any patterns between reviews.
- I hope you will have an interview with either the hiring manager, or one or more peers. Ask them questions about how it is to work there. Find way to ask without asking "How is it working there?" directly. Some ideas:
- Am I joining because the team is growing, or am I replacing someone? If replacing, why did the person before me leave?
- How long have the people on the team I am joining been there? You're looking to get a feel for tenure and seniority.
- How often do you speak with your manager? Their manager? The CTO? The CEO? In general, the more often, and the more approachable leadership is, the less likely you're thought of as a cog and seen more as a human.
- Ask if they could give a concrete example of how their values or principles have been used in practice recently. Make sure you read these ahead of time. If they can't tell, then their values might be bullet points on a glossy brochure that have no application in reality. If they don't know their values, that means no one cares about them.
- How often do you have to work overtime? Is it normal? Is it occasional? How is that recognized? How is that seen?
- Ask how they define and recognize excellence on their team. Listen to the story they tell. Is it mechanical? Do you get a non-answer? A blank stare?
Draw your own conclusions. This is not a set of checkboxes. The best companies are not perfect. The worst companies do some things right (I would hope). It gets easier with time, as you get more experiences under your belt, you'll understand where you fit and where you don't. You'll build a gut feeling for this.Read reviews on Glassdoor.com. Take them with a grain of salt, but if you see a lot of reviews all saying similar things about the management, it's probably true.
Because otherwise you are always fighting an uphill battle and get boiled like a frog when things inevitably start to go south.
Every tech company I know of grants workers options/stock. What more is fair? What is it about worker status that should grant them outsized influence on a company and not, say, customers?
Of course a joint-stock company allows customers to put skin in the game too (which a worker does not simply by being a worker) and giving them influence in addition to their ability to “vote with their wallet”.
It solves all these problems and avoids the adversarial relationship issues.
It's even more complex. While top management might give a rough direction, even within a single company different managers may create way different environments.
I can't recall the exact quote so paraphrasing here, I recall the gist of someone saying:
> When deciding whether or not to join a group of people, take a long hard look at people already there, how they work, how they think, and if there's something that you see and don't want to turn into, bail out. Because you're going to join a group of, say, 10 people, and in all likelihood these 10 people will change you, whereas the chances of a single individual changing 10 people are slim at best, and more realistically and bluntly put, nonexistent. So the three choices are a) run away, b) join and embrace (or cave in, depending on how you put it, which may or may not be toxic for you), and c) join but resist (which will be toxic for everyone)
While a talented and motivated individual can indeed create a lot of value, this will inevitably also create a lot of dependency on said person. Now this person has become a liability, and HR doesn't like liabilities.
Not exactly. I do agreed about the value destroying part. But unless the knowledge mentioned is standardized, it's not really easy to transfer them to the succeeding team members.
Some highly successful products (or features in these products) was created because the effort from one or two employees who got the idea based on their knowledge from life. Without these key employees, the product/features will never be implemented, and the success will never happen (and nobody will know it's possible).
It's the same way how CEO/CTO works, really. Some CEO lead the company to success while others failed, not because they're incompetent, but because the knowledge is not there, which lead to (for example) the lack of imagination and growth.
But unlike the leaders, employees usually don't receive nearly enough reward for their insight, if their effort is noticed at all. That's the dilemma.
It’s capitalism for any business / platform that gets big
And has shareholders that want profits
Mark Z was an open source bro who turned down M$ in High School and ended up open sourcing Synapse. He built Facemash and Facebook and was going to build an open-source, decentralized file sharing network (“Wirehog”) but the Venture Capitalists proudly “put a bullet in that thing”. Gotta extract them rents!
I heard Sean Parker myself on stage at TechCrunch Disrupt 2010 telling the story. Sean likewise tried to make a file sharing economy (Napster), and got nailed for it by another set of really big monopoly-like organizations, in the music and movie industries. He learned his lesson of capitalism: don’t mess with the centralized control!
Peter Thiel, the first investor in Facebook, says like you: “competition is for losers, build a monopoly”. That’s not hyperbole, that’s the actual title of his talk at Google, that I listened to.
With such investors it is no wonder that Mark Z went from an open source bro to corporate golden boy who buys up the competition, makes unilateral decisions — moves fast, break things — and then says “calm down, breathe, we hear you.”
Society has become like this (lonely, angry, addicted) not by accident. It is the end result of the system where shareholders and venture capitalists and the profit motive shape our platforms.
The best is a gift economy with no profit motive. It creates more value for the world than its capitalist counterparts:
1) Wikipedia vs Britannica, Encarta, et al
2) VoIP vs Telcos
3) Linux vs closed systems like Sun, etc.
4) World Wide Web based on open protocols vs AOL, MSN, Compuserve
They beat them within a decade. Gopher was good but started trying to use the government to control its licensing. It lost.
Now, if you need an accounting system, that rewards ecosystem participants for storage, hosting, uptime/availability, computation, security, translating, moderating, whatever, then use decentralized crypto utility tokens based on open protocols. Micropayments can be done peer to peer via trustlines.
It’s the proper use case for crypto. And it beats the current system of financing projects because the end result is more like
1) Ethereum for business logic
2) IPFS for storage
etc.
vs Facebook, Twitter, Reddit and other centralized things.
The rest — realtime chats, video, endless doomscrolling feeds it’s all gimmicks designed to get you addicted to centralized control. It’s not good for healthy society.
Frankly, neither are celebrities who can tweet to 5 million followers at 3 in the morning. In true gift economies like Science, Wikipedia, Open Source software etc. people actually have to run the gauntlet of peer review for the privilege of having their ideas reach the public. That’s how it should be. Not polluting the public with mindless advertisement and smut and one sided news stories radicalizing them to hate and wars.
Think about it. https://rational.app also goes into more detail on the economics of how we got here and how to get out.
>Science
There's a reason for the saying "science moves forward one funeral at a time." Those with power block those who do not have power from competing with them until they literally die of old age.
It’s simple. The profit motive ruins everything as things get big. Usually because shareholders demand to extract rents from the ecosystem. Even while externalizing the cost to society and the environment
Open source gift economies are a far better alternative for society and don’t have that problem. But they require the productive participants to enjoy financial independence or some disposable free time, and universal basic income isn’t coming from daddy government anytime soon.
If you want to attract infrastructure providers and fund development for your project in an economically sustainable way, don’t sell shares in your corporation - release a utility token for your platform, and make it available worldwide. Heck, peg it to a USDC if you’re worried about speculators or complying with securities laws (although there are tons of exemptions from registration, like Reg D and Reg S and Reg CF etc). Issuing and managing them with smart contracts is super easy, and permissionless. You can do it in a minute. People have their own choice of how to store them. And micropayments for infrastructure can be implemented via trustlines in a free market pretty easily.
The utility token holders — even the people who hoard them — have a far better set of incentives than corporate shareholders do. Ether or Filecoin HODLers aren’t trying to ruin it for everyone using the network, nor are they even trying to assert central control over what people can do with IPFS or Ethereum!
Sadly, many people on HN have it completely backwards with what’s good for society. They hate Web3 with a passion and claim it has no use cases even though utility tokens would lead to a far superior set of incentives, wifh no parasitic shareholder class insisting on centralized control and rent extraction — essentially forever. They see what happens at Reddit, Twitter, Facebook, with a few people at the top making decisions, but they don’t put two-and-two together because the cargo-cult of anti-Web3 is strong in 2023. (But not next year, when the halving event happens and lots of innovation gets released again.)
Meanwhile they are in love with generative AI, the new kid on the block, despite most of its own most prominent inventors screaming about a large chance of catastrophe and running to the governmebf.
By the way, the reaction of those who were used to centralized control has always been priceless… this is the earliest moment when they were confronted with the possibility of everyone empowered to do their own thing on their own personal computers:
The committee meeting where the team first presented the Gopher protocol was a disaster, “literally the worst meeting I’ve ever seen,” says Alberti. “I still remember a woman in pumps jumping up and down and shouting, ‘You can’t do that!’ ”
Among the team's offenses: Gopher didn’t use a mainframe computer and its server-client setup empowered anyone with a PC, not a central authority. While it did everything the U required and then some, to the committee it felt like a middle finger. “You’re not supposed to have written this!” Alberti says of the group’s reaction. “This is some lark, never do this again!” The Gopher team was forbidden from further work on the protocol. (https://www.minnpost.com/business/2016/08/rise-and-fall-goph...)
Times change, the hilarity of resisting decentralization stays the same…
But then, you have on top of this "hyper-capitalism". Peter Thiel says "competition is for losers, build a monopoly", making many capitalists blush. Venture Capitalists prop up money-losing unit economics for years (they call it "reducing friction") and then dump the equity on the public. The public then pushes the team to extract rents from all sides from the marketplace forever. Who needs these shareholders? That's hyper-capitalism.
In fact, I would even go so far as to say that your utility token shouldn't be freely available to everyone. Only the actual participants should be buying it. Otherwise a hyper-capitalist whale like Goldman Sachs can pump and dump it, hurting people: https://foreignpolicy.com/2011/04/27/how-goldman-sachs-creat...
It might even be designed to undergo demurrage, so that if you don't use it, you gradually lose it. This was done in Worgl and defied the depression all around it, even the Mises institute had to gradully agree it worked: https://mises.org/library/free-money-miracle
In fact incentive structure matters.
So for example people in a co-op or volunteer org can be bad for reasons other than profit, like power or the illusion of regard instead.
But then a few days ago at a family gathering a guy asked what I do, and as part of that I was explaining what open source is, and he on his own started telling me how much he loved the vlc media player. Everything he loved about it was the result of the fact that no one working on it has any reason to mistreat the user.
There are examples of open source software that makes decicions I don't like, but even the worst of those are someone else's legitimate best idea how to do the best possible for the user.
Yes, Reddit's current actions are squarely the result of capitalism, not "people".
For me that's as capitalistic as it gets.
It's the same frame of thought geared towards employees.
What else could it be?
And I added an edit to point out that if the profit motive was true, they would have accepted the money offered by the API users who agreed to the price hike. They went ignored for two out of the four weeks notice Reddit gave.
Yes, signing a few API users would "increase profit" but not as much as the profit they can (or perceive they can) generate by having control over their platform/clients.
With control they can employ whatever dark patterns they want to extract as much value as they can from ads. Some suggest ads by API but still that's nowhere near the same type of control/guarantee.
Ultimately this even strengthens my point. They want profits above all else. They are choosing the highest potential profit over the less profitable API deal that could be a nice middle ground.
In capitalism it doesn't matter if a better alternative costs a single cent more. If there is a choice, it will be to save that cent.
Disclaimer: I am all for criticizing capitalism, but using the cliché is not well argued imo.
Saying it's not "the capitalism" is a bit of a true scotsman argument. There is only really one capitalism: the one we're living in today. There's no other version of this as far as I can tell. Maybe before we had different variations of it but with globalization, it's one to rule them all.
> it's not necessarily in their interest to get tunnel-vision and seek short-term profits
I wish I shared your hopeful vision because looking at history and current affairs, there's no indication that short term gains are ever going to be replaced by long term ones. The climate change issue is the prime example for that. Everyone knows long term it's bad, but who cares? We need those stocks to go up! [1]
[1]: https://www.derekchristensen.com/wp-content/uploads/2014/12/...
The statement I answered was making the worst case the norm. That's why I said that it is not representative for capitalism ("not the capitalism"). Short-term-profiteering is just a part of it - that is usually eliminated, if that's all that is to it.
> I wish I shared your hopeful vision because looking at history and current affairs, there's no indication that short term gains are ever going to be replaced by long term ones. The climate change issue is the prime example for that. Everyone knows long term it's bad, but who cares? We need those stocks to go up!
Now you're shifting the goal post. I specifically speak about profit not about some other arbitrary goal. Capitalism (like any economical system) isn't going to magically fix everything (i.e. climate).
edit: clarify
That was not my intention. Climate change was just an example but the point is still about profits. It doesn't matter if you find that in 25 years profits will be better for everyone if we do X. Unless you get growth next quarter, stocks plummet.
Hence why I said I don't share your optimistic vision. With capitalism there is only the next quarter.
Even if you look at some of the longer plays like venture capitalism, it's the same mindset focusing on an exit that is a bit delayed. Swap profit at all costs with growth at all costs for a while in hopes you then profit later with monopolies.
Sure as you state short-term profiteering might not be all there is to capitalism, but I never claimed that in the first place. The issue is not the short-term part, it's seeking profit above all else. You can't really fix that within capitalism since it's what defines it.
Shrugging at shitty practices and saying "capitalism" is at best reductive and unhelpful.
The most far-reaching and complex of human problems are compressed into brief, highly reductive, definitive-sounding phrases, easily memorized, and easily expressed. They become the start and finish of any ideological analysis.
* https://en.wikipedia.org/wiki/Thought-terminating_clich%C3%A...
Yes, I'm currently working for such a client (not as a dev though) and it's amazing how absolutely convinced even so-called "technical" people think developers are like interchangeable factory workers (which are themselves also probably a myth).
Apparently, the inability to code is some badge of honor, and proof that one is a "thinker"(?!?).
This view seems to be more pervasive in Europe than in the US... Maybe it's an artifact of social classes / hierarchical societies, and more egalitarian societies have an edge to overcome those prejudices.
I'm not sure. I don't really know.
What I know is that it's terrible.
This being said, companies that really do provide added value and grow are usually the ones valuing their engineering staff highly.
As for myself, I outright refuse to work with traditionally structured French companies.
Less than a year after this guy started, a lot of the best people in the company have left the company. I still have several good contacts there and it is really bad. The company had good revenues and a lot of potential, but they are really struggling right now and they already had to let a lot of people go that they actually needed. There is one very good developer left who basically built most of the company's software and who is still performing like crazy because he really identifies with the company and he tries to keep it alive, even though it is literally destroying his health and family. Guess what, the CTO wants to get rid of him because he "doesn't like his attitude". He tried to force the previous Head Of Software Development to get rid of this guy until he quit himself, now he is trying to get the new Head of (one of the Iranian guys) to find a way to get rid of him. It is not easy to fire someone in Germany btw. You either need a good reason (like validated documentation that they violated the terms of their contract) or get the person to quit themselves. The Head Of knows that this guy leaving would be the worst thing to happen to this company, so he is basically just stalling.
Of course the CTO gets more than triple the money of the best paid developer, plus bonuses like a car that's worth ~140k.
Which is quite weird, since at every Not Software engineering company I've interacted with in Europe, the majority of the top management are experienced senior engineers who have worked their way up from 'the floor' as it where.
They build the machines that sit in the factory and churn out the product/service
After I worked a few years in the industry, I came to the following conclusion: The main difference between a factory and a knowledge business is that in a factory, the smartest, most knowledgable people are at the top (not completely the case, but mostly). In knowledge work, the smartest (=experts) are at the bottom. If you move up as a smart person, you will for sure lose up-to-date knowledge.
This has a few consequences of course. In knowledge work, managers should not say "First do this, then do that". Managers should be at the service of their team, making sure they get the focus and freedom to work on their stuff.
Now back to the factories: I'm no expert, but one of the key elements of Lean Manufacturing is that the people on the floor are able to provide feedback to the upper layers. Why them? Because they have the hands-on knowledge and see things management can't. So even in factories, either you listen to the lowest level employees or you're not optimising your process.
And finally, if users and employees can be replaced, so can companies, products and services. The thing is that having great retention in users saves you a lot of investment on acquiring new ones. And having great retention in employees saves you a lot of investment in hiring and training. The leaders that realise this will outperform anyone that doesn't.
The personality of the leadership will determine whether they think of workers as self-motivated (will actively look for work) or externally motivated (will wait for work and try to avoid it). Those who don’t think workers are self-motivated will build management structures where people are discouraged from thinking beyond their station and have all kinds of reporting and incentives to make them do their work.
I was for a long time hard in the self-motivated camp, but eventually realized that’s me and not everyone, and maybe not even most people. A multi-modal management approach that leaves room for both works better but is harder to pin down.
Thanks for the info, fellow Flemish guy (your name gave it away :D)
My experience tells me you should just assume everyone is going to need the external carrot/stick arrangement.
You'll save a lot of pain by realizing that no one cares about the product as much as the people spending 14 hours a day on it.
If this communication goes wrong it can result in deaths and giant profit leaks until eventual bankruptcy.
Programming can fail much harder.
If you listen to programmers, the app has technical debt, and needs to be rewritten on [next tech stack needed on the developer’s resume]. I’ve hear that on a 6-month-old app written in SpringBoot/React in 2020.
Leader-blaming is a nice sport, but actually working together with full responsibility on both sides is a much rarer skill. Including being fired with damages if you summon KubernPyKafka in Scala and your team doesn’t produce features during 6 months.
Getting flashbacks from my own time working on what I like to call Cthulhu Architecture. KubernPyKafka in Scala is probably the most reasonable part of it.
The parts that needed to be fast were in python. The parts that could afford to be slow were in Go or LuaJIT. Ops in C++. And the parts that required well defined carefully controlled business logic to be encoded were in JavaScript if you were lucky, but more likely embedded in a DSL constructed over YAML. ACID built over top of NoSQL. Still only scratching the surface of the insanity. I’m sure there are many of us carrying these scars; some of the intent on bringing this dysfunction into their next organization.
> And finally, if users and employees can be replaced, so can companies, products and services.
Yep.
And now maybe reddit's number is up, and it's time for it join Myspace, Friendster and Twitter?!Now ask the same CTO (or, hell, most HN users) what they think of tech support.
Developers are like gods in the pecking order compared to tech support.
The very definition of a factory is that it manufactures the same thing, or a limited range, of items over and over and over again.
That's not software development: you're either doing something new, or working on an existing codebase but, of course, because each part of that codebase is quite different to the others, there's no real uniformity to what you're building. Sure, there are processes that are similar (writing tests, debugging), etc., but it's much more like the design and testing phase of engineering a product rather than the manufacturing phase.
Overall, "factory" is an incredibly vapid analogy that simply needs to die in our industry.
You can pay someone to work but you can’t pay them to care and the difference between a product where people cared and one where they did not is extremely tangible.
pg says there's probably no one who understands reddit's userbase better than Huffman... https://twitter.com/paulg/status/1654769759399845888
so, there's hope? /s
The entire industry is infected with management (CXO, VP, Directors, Managers) that think engineers can be pushed to produce "more". And they do this without any idea what "more" is, and how the "more" will bring revenue.
At least in a factory, producing "more" units is likely to return more income. But engineering is not like that at all. There is a creative aspect to it and there is a maintenance aspect to it.
But management ignores it to protect their own stock awards.
I've worked in tech with a lot of people like this. They will tell you straight up they don't care about users or employees. CTO I've worked with said that developers are like "machines working in a factory" that they shouldn't think above their level and should just do the same thing over and over.
I'll tell you one thing you'll never change the reddit managements minds, never ever ever. Same as I was never able to change any of these other peoples minds.