6 ms·

Please don't let things like "Apple makes $1.8MM per employee" get to you. It leads to stupid decision-making. Yes, the company is making more money on your eff

Please don't let things like "Apple makes $1.8MM per employee" get to you. It leads to stupid decision-making. Yes, the company is making more money on your efforts than it is paying you. It's called business, you take inputs and add value to them and sell them to other people who will turn around and do the same thing. If you had capital to throw into a business venture then you'd do it too. I met a guy a few weeks ago who'd moved over from California. He wanted to learn how to code, and told me his story. He was a business sort who went into business with a software developer. The dev did good work, and the business guy managed to get it funded. Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise. He wanted to learn how to code so that this wouldn't happen to him again. So I'm giving him an hour or so a week to show him how web development works so that he can code a prototype himself. Then he can get funded and hire employees rather than deal with the emotional vagaries of software developers. I don't blame him at all. Business guys are typically going to make more money than the coders are, it's pointless to fight this. The better route is to go into business yourself and capture the value yourself. The reason is that the business side is the human side, and humans are harder to deal with, ultimately, than computers are. Also, humans have money and computers do not.

cheez 11y ago
Just as much as the business guy wants to avoid the vagaries of a software dev bailing, he's going to have a hard time understanding how good software is created at one hour a week. It was worth it for the business guy to give up a bigger piece of the pie in order to ensure that the business survives. That he is unable to see that, is either because he is unreasonably greedy or short sighted. Now he is delayed for X months or years because he let his greed get the better of him. Once a business is well into money making machine territory, the impact that a single good engineer is going to make is dramatically reduced. At that point, the leverage is much lower and the business person can make decisions like you described.
_pmf_ 11y ago
> Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed This story probably has two sides.
- vinceguidry 11y ago
  The dev's reasons can't mitigate his actions.
  - gaius 11y ago
    Really? There's no reason that you can think of? Is this business bro a relative of yours perchance?
  - GFK_of_xmaspast 11y ago
    No-one has an obligation to continue working in a bad situation.
amelius 11y ago
> and humans are harder to deal with, ultimately, than computers are I cannot imagine this to be true. Take for example the Paxos algorithm. There are few people who can fully understand it. Yet you are saying that some businessperson is doing work that is more difficult than dealing with the intricacies of distributed computing? The only reason the businessperson is making more money is because he has maneuvered himself into a better position.
- whatshisface 11y ago
  The "business guy's" job is exactly to manuver things into positions. He specializes in making more money! You hire him to do that for the company, but the good ones have side projects.
- jasode 11y ago
  >Take for example the Paxos algorithm. There are few people who can fully understand it. Yet you are saying that some businessperson is doing work that is more difficult than dealing with the intricacies of distributed computing? Coincidentally, I just went through the Paxos and Raft algorithms last week. Yes, they are complicated but a lot of the complexity is the proof that covers every possible edge case for conflicts and failures. I'm also currently working on populating a multi-threaded Merkle hash tree and the complexity is hitting the limits of what my brain can manage. Nevertheless, I'll eventually make it all work. Humans, on the other hand are much more difficult. When I was fresh out of school, I definitely thought of the business guys as "the useless suits" and the programmers as the real value-added employees. But since I've tried running my own business and not made much money at it, I've come to appreciate that a few business people out there really have talent for juggling the incentives and motivations of team members. Whereas moving computer code around in Paxos and multi-threaded hash trees will have an eventual solution, dealing with humans to solve a business problem seems like the social version of trying to prove P=NP.
  - amelius 11y ago
    I think you are biased because you are currently putting (for the sake of the argument) 100% of brain power into your programming work, and 0% of brainpower into business decisions. If you are like me, you think about your Paxos implementation even when in the shower, and while commuting. Now imagine that you didn't have to do that programming. You would have 100% of your time to make business decisions, talk to people, etcetera. Suddenly, what the businessperson does is not so hugely impressive anymore. Or at least, that is how I look at it.
lsd5you 11y ago
Typically for a business person, everything is a financial decision and calculation. They will out negotiate the typical engineer. Getting 'into business' might just mean properly valuing ones own contribution. That said I do see a lot of expressions of engineer entitlement on this site(I assume normative reasons).
- MCRed 11y ago
  I have seen an astounding amount of "biz guy" entitlement in this industry. It can't tell you how many times I've talked to potential co-founders who were a pair of frat boy types who had business school degrees. They pitch their idea as if it were a company, but all they have are some powerpoint and a few phone calls under their belt. They wanted to be CEO and "VP Sales" and would be happy to let me be CTO, they just want the to build the product and engineering team and for that-- because they liked me so much-- they'd let me have %5 of the company! (Vesting of course, one year cliff.) They don't understand when I laugh at them... and I think its because there are too many suckers out there and they soon find one.
  - dasil003 11y ago
    The flip side of this is the incompetent developer who produces hunks of irretrievably flawed spaghetti code which works just well enough to get paid, but is a technical dead end that will never work well enough for the company to derive long-term value. Granted, it's easier to be a useless biz guy than it is to be a useless developer since there's no litmus test for the former, but it's absolutely true that both exist. Your goal is to steer far clear of them.
    - pbh101 11y ago
      While I agree with you, I want to note that long-term value is often not what these businesses want or need: the work required to get LTV is often perceived as delaying time to market, and sometimes the right choice is to optimize time to market over correctness or soundness. In my experience this is frequently an unstated source of contention and unaligned expectations between engineering and business sides of the organization and one that is very useful (and liberating!) to get aligned on from the outset of a venture. And frequently, compensation structure is a useful part of that alignment: if you will also benefit from the time to market, that tradeoff feels less like someone asking you to make more work for yourself or others down the road (in the form of ops or rewriting)
jasode 11y ago
>Apple: $1,865,306 per employee Also, that Business Insider article is an inadvertent IQ test for people who want to regurgitate their figures. That $1.8 million number is revenue/#employees and not profit/#employees. Using profit calculation of $53B/98k is ~$500k. Since, a fully-loaded FTE in Silicon Valley is ~$250k, the ~$500k doesn't look that insane. If a writer copy&pastes stuff like that into their own essay without critical thought, don't be surprised if it taints the rest of his essay. For example, the "you are not a commodity" is not fully reasoned out. In the essay, it's just an empty platitude/affirmation instead of explaining why some programmers are treated as commodities and how to differentiate themselves to avoid that categorization.
- mistersquid 11y ago
  These numbers are provided in a different context (to measure Twitter's loss against profits of other well-known highly-valued technology companies: https://twitter.com/dcurtis/status/694586397588467712 https://twitter.com/dcurtis/status/694586397588467712 I don't know the source of Curtis's data.
- carboncopy 11y ago
  If you use profit/#employees, then you're double-counting. The employees' salaries are already taken out of profit. That's why it's not fully disingenuous to consider revenue instead. $500k of profit generated per employee sounds excellent, but it's also omitting other capital costs made by the business. Essentially, none of these benchmarks can give you the complete picture.
MCRed 11y ago
Business guys make more money, only because they convince developers to take less than they are worth. Your friend hired a developer who, by your account, was doing all the work, and then the business failed because your friend was too greedy. Now he thinks he's going to learn to be a developer and then not need any developers. Good luck with that. By the way "getting it funded" is not success. Making it profitable is success. PS- the word "coders" is like the n word. Use it and we know you don't respect us.
- abawany 11y ago
  Not that I am comparing software development to entertainment but in my perception, software developers today are in a similar position as Elvis was with his fake-Colonel "business guy" throughout his career: exploited and treated like a replaceable widget. The one person I credit with providing me this insight is patio11 whose articles on negotiation are gold.
- louprado 11y ago
  coda please.
  - 50CNT 11y ago
    I believe the politically correct nomenclature is "Technican-american", though some also call us dork skinned people. Still missin' my /home/boy, they got him up in Redmond after an IPO gone bad, heard he's vestin' for another 3 years up in there.
wcummings 11y ago
>Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise. >rather than deal with the emotional vagaries of software developers. Negotiating compensation you're comfortable with isn't an "emotional vagary". Sounds like the programmer was working for a measly amount equity in something that will most likely be worth nothing in a couple of years.
- vinceguidry 11y ago
  He should have realized it before he made the deal and negotiated a better one for him. Also, he almost certainly bailed on this deal without having an alternative lined up, so all he did was destroy momentum. I've been in this situation before, and bailed before any real work got done. That's when you need to realize these things, not after you get funding.
  - 67726e 11y ago
    Sometimes the right solution is to walk away, regardless if it destroys something. Maybe the businessman was unwilling to renegotiate or was a prick. I have no obligation to stick with a job that isn't doing it for me. Maybe it's the businessman's fault for not finding a replacement? As an aside, you seem awfully defensive of the businessman despite not having the full story.
gaius 11y ago
Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise This story is meaningless without some numbers attached. The developer was obviously a crucial part of the company - did he own 50% or 0.1%?
- vinceguidry 11y ago
  It's not. He made an agreement, and bailed on it later, for no other reason than that he didn't like the agreement he had made. Doesn't matter what the numbers are.
  - cheez 11y ago
    Agreements can be remade when circumstances change. Again, your business guy sounds pretty dumb when his solution is to learn it himself.
  - mistersquid 11y ago
    Your analysis is too rigid and could use the nuance numbers might provide. If the developer executing the idea was paid a low sum in exchange for low equity (say, 75K + 0.1%) and market analysis revealed a much smaller market than anticipated, the developer may have rationally understood the situation to be exploitative. In such a case, the numbers might reveal that higher equity (say, 75K + 20%) might make the situation would not only be equitable but potentially profitable. You're right to say that the developer breached the contract, sure. However, having numbers might contextualize that breach of contract so that it could be read as a poorly-considered evasion of responsibility or a rational decision to leave a financially abusive and career-limiting contract. EDIT: Readability. Add conjunctive adverb to last paragraph.
  - gaius 11y ago
    Depends if it was a "right to work" situation where no notice period was necessary - another crucial piece of the story omitted.
  - RobertDeNiro 11y ago
    It's his life. People change, and he probably found something better elsewhere. Why would someone who's paid less than 0.1%(assuming the worst case) be forever loyal to a business? Loyalty has a price and it's much higher than most people seem to think.
crdoconnor 11y ago
>Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise. >deal with the emotional vagaries of software developers This is a human trait, not a software developer trait: https://www.psychologicalscience.org/index.php/news/releases/are-humans-hardwired-for-fairness.html https://www.psychologicalscience.org/index.php/news/releases... He would do better to learn to temper his greed rather than to learn programming.
gizi 11y ago
> ... the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise ... Business guys are typically going to make more money than the coders are, it's pointless to fight this. The dev apparently fought this and won ;-) > ... humans are harder to deal with, ultimately, than computers are. Especially devs are ;-)
mangahero 11y ago
This statement is false. This man stands to benefit from the businessman in terms of a fairer deal in the future. Such is business.
- vinceguidry 11y ago
  Well, now the businessman won't deal with him in the future. So he burned a bridge.
  - gaius 11y ago
    Or dodged a bullet.
  - 67726e 11y ago
    Maybe the businessman fucked the developer and burned a bridge. You're obviously wedded to your narrative.
jsight 11y ago
> Business guys are typically going to make more money than the coders are, it's pointless to fight this. Negotiating a better deal is pointless? What? I thought you were in favor of business. > The reason is that the business side is the human side, and humans are harder to deal with, ultimately, than computers are. I will not get into an argument about whether humans are harder or easier to deal with. I also will not get into an argument about whether software development is fraught with the same types of issues with dealing with people. Instead I will just point out that pay is not directly related to the difficulty of the work. It is a function of the value derived from the work, the availability of labor, the negotiating skill of the various parties involved, and many other factors (all to varying degrees). I agree with everything else that you said, especially the part about $$$/employee figures and their misleading nature. In general whenever you see $/(some arbitrary unit) in the financial press, be wary. It is sometimes a useful way to look at things, but it is incredibly easy to manipulate so that it ends up being a completely useless figure. I see it happen all the time, and these are often the most quotable lines as well (sadly).
beachstartup 11y ago
uh, okay. sounds like the 'business guy' wasn't so good at business. if you choose a partner and he bails, that's your problem. one of the key tenets of business is keeping people properly incentivized, and he clearly failed at that. and that software guy was also a business guy, by definition. sounds like he did some intense businessing and got the hell out of that business after realizing he was making a terrible business decision. part of being a 'business' person is dealing with reality as it exists, not making up narratives that suit your ego.
deleted 11y ago
[deleted]
UK-AL 11y ago
I agree with the idea that you shouldnt care companies making more money of you than you cost. That's because capital, marketing and teams are multipliers. They use you plus these things to make more money than you could by yourself. Completely disagree with the rest of it though. You should neogiate the best deal possible, you should walk away if deal isn't good for you, you should treat it as business. You need to be an engineer and a business person and make sure your getting the best deal.
YZF 11y ago
It would be interesting to hear that story from the developer side of things. I'm sure there's more to it. I also got a few stories. Maybe a bit of a rant but bear with me ;) I have the technical know-how and the idea and I bring in a business person to help try and make a business from it. Before I know it the business person is putting me in a position where I lose control over the product and the business and essentially have to work for free on faith and lose all my intellectual property. I quit, sooner rather than later. Just to be clear very little effort was invested at this point and I was clear about my expectations from the beginning. I go work for a startup and take stock options as part of my compensation. The company IPOs. All business types including fairly recent hires make a ton of money. Most technical types made almost nothing. The shares keep declining, the company gets bought out, more money for business types. End of story? I did get an OK salary as well but I invested a lot of heart in this so it left me with a bad taste. What's at the core of this? No one is looking for win-win situations. We have too much competition and too little cooperation. When you have a CEO who is solely motivated by how much money he is going to make this is bad for employees, shareholders, the company and everyone else. Just because the way this CEO will make money is making the company look good doesn't mean he actually cares about anything beyond how it looks. Not all companies are like that but too many are. What we have is lose-lose, companies and shareholders lose from high churn, lack of loyalty, lack of motivation, lack of investment, bad CEOs. Employees for the most part lose as well. Tragedy of the commons. Specifically with Apple they're hoarding cash, not investing it, not paying it out to employees or shareholders. They're buying back their shares at inflated prices. How is that something that benefits the company or anyone else? They're sucking money out of the economy. I'm sure there are worse examples...
- nickpsecurity 11y ago
  Great counterpoint that describes and gives anecdote to what I described in my own reply: https://news.ycombinator.com/item?id=11095689 https://news.ycombinator.com/item?id=11095689
nickpsecurity 11y ago
As with others, the morality of this situation depends on details we don't know. What always trips me out is the double standards in posts like yours. People are fine with the capitalist notion of starting a business, giving most people in it almost nothing, often collecting any I.P. produced rather than a license, and having goal of selling out in a way that will likely cost the employees their jobs. Almost all value goes to investors or a few founders while almost all work is done by employees. The process is often supported by false promises or emotional manipulation to keep workers loyal & with a tiny part of the pie. This is default in Silicon Valley from what I read here and in other media. Then, an employee decides to do what's best for him or her in a way that negatively impacts the founding business person or investor. This is seen as unethical: such employees, upon some agreement or context, cannot possess the ability to make other choices that damage founder or VC goals. They don't possess the trait that founders and investors wield with nary a thought over employees like we're starting to see with more layoffs. The employees are, instead of rationally selfish, being Evil and called out for it. A double standard that serves captains of industry and startup founders very well at everyone else's expense. In reality, capitalism says that everyone, including employees, should act in their own self interest externalizing all costs of such actions. So, per capitalism, the founder did the right thing by trying to screw the employee out of lots of net worth and the employee did the right thing screwing the founder by taking another path. Naturally, being utilitarian, I oppose such capitalism in favor of stakeholder-focused models with rules reducing opportunities for each party to screw the other. The market goes the other way, though, so everyone continues to help or screw everyone to heart's content. And I get to read nonsense like this where people cry "But that's not right and fair!" while simultaneously... "Business guys are typically going to make more money than the coders are, it's pointless to fight this. The better route is to go into business yourself and capture the value yourself. " ...supporting amoral, selfish practices of capitalists on founder or VC side. It's just also what the developers were following: do whatever provides most perceived value for themselves. It is really good advice, though. Keep preaching it while system works as it does given that's where money is at. It's just that making an exception for one party but not others seems unfair and irrational. Thanks for the entertainment though. :)

cheez 11y ago

Just as much as the business guy wants to avoid the vagaries of a software dev bailing, he's going to have a hard time understanding how good software is created at one hour a week. It was worth it for the business guy to give up a bigger piece of the pie in order to ensure that the business survives. That he is unable to see that, is either because he is unreasonably greedy or short sighted. Now he is delayed for X months or years because he let his greed get the better of him. Once a business is well into money making machine territory, the impact that a single good engineer is going to make is dramatically reduced. At that point, the leverage is much lower and the business person can make decisions like you described.

_pmf_ 11y ago

> Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed This story probably has two sides.

vinceguidry 11y ago
The dev's reasons can't mitigate his actions.
- gaius 11y ago
  Really? There's no reason that you can think of? Is this business bro a relative of yours perchance?
- GFK_of_xmaspast 11y ago
  No-one has an obligation to continue working in a bad situation.

amelius 11y ago

> and humans are harder to deal with, ultimately, than computers are I cannot imagine this to be true. Take for example the Paxos algorithm. There are few people who can fully understand it. Yet you are saying that some businessperson is doing work that is more difficult than dealing with the intricacies of distributed computing? The only reason the businessperson is making more money is because he has maneuvered himself into a better position.

whatshisface 11y ago
The "business guy's" job is exactly to manuver things into positions. He specializes in making more money! You hire him to do that for the company, but the good ones have side projects.
jasode 11y ago
>Take for example the Paxos algorithm. There are few people who can fully understand it. Yet you are saying that some businessperson is doing work that is more difficult than dealing with the intricacies of distributed computing? Coincidentally, I just went through the Paxos and Raft algorithms last week. Yes, they are complicated but a lot of the complexity is the proof that covers every possible edge case for conflicts and failures. I'm also currently working on populating a multi-threaded Merkle hash tree and the complexity is hitting the limits of what my brain can manage. Nevertheless, I'll eventually make it all work. Humans, on the other hand are much more difficult. When I was fresh out of school, I definitely thought of the business guys as "the useless suits" and the programmers as the real value-added employees. But since I've tried running my own business and not made much money at it, I've come to appreciate that a few business people out there really have talent for juggling the incentives and motivations of team members. Whereas moving computer code around in Paxos and multi-threaded hash trees will have an eventual solution, dealing with humans to solve a business problem seems like the social version of trying to prove P=NP.
- amelius 11y ago
  I think you are biased because you are currently putting (for the sake of the argument) 100% of brain power into your programming work, and 0% of brainpower into business decisions. If you are like me, you think about your Paxos implementation even when in the shower, and while commuting. Now imagine that you didn't have to do that programming. You would have 100% of your time to make business decisions, talk to people, etcetera. Suddenly, what the businessperson does is not so hugely impressive anymore. Or at least, that is how I look at it.

lsd5you 11y ago

Typically for a business person, everything is a financial decision and calculation. They will out negotiate the typical engineer. Getting 'into business' might just mean properly valuing ones own contribution. That said I do see a lot of expressions of engineer entitlement on this site(I assume normative reasons).

MCRed 11y ago
I have seen an astounding amount of "biz guy" entitlement in this industry. It can't tell you how many times I've talked to potential co-founders who were a pair of frat boy types who had business school degrees. They pitch their idea as if it were a company, but all they have are some powerpoint and a few phone calls under their belt. They wanted to be CEO and "VP Sales" and would be happy to let me be CTO, they just want the to build the product and engineering team and for that-- because they liked me so much-- they'd let me have %5 of the company! (Vesting of course, one year cliff.) They don't understand when I laugh at them... and I think its because there are too many suckers out there and they soon find one.
- dasil003 11y ago
  The flip side of this is the incompetent developer who produces hunks of irretrievably flawed spaghetti code which works just well enough to get paid, but is a technical dead end that will never work well enough for the company to derive long-term value. Granted, it's easier to be a useless biz guy than it is to be a useless developer since there's no litmus test for the former, but it's absolutely true that both exist. Your goal is to steer far clear of them.
  - pbh101 11y ago
    While I agree with you, I want to note that long-term value is often not what these businesses want or need: the work required to get LTV is often perceived as delaying time to market, and sometimes the right choice is to optimize time to market over correctness or soundness. In my experience this is frequently an unstated source of contention and unaligned expectations between engineering and business sides of the organization and one that is very useful (and liberating!) to get aligned on from the outset of a venture. And frequently, compensation structure is a useful part of that alignment: if you will also benefit from the time to market, that tradeoff feels less like someone asking you to make more work for yourself or others down the road (in the form of ops or rewriting)

jasode 11y ago

>Apple: $1,865,306 per employee Also, that Business Insider article is an inadvertent IQ test for people who want to regurgitate their figures. That $1.8 million number is revenue/#employees and not profit/#employees. Using profit calculation of $53B/98k is ~$500k. Since, a fully-loaded FTE in Silicon Valley is ~$250k, the ~$500k doesn't look that insane. If a writer copy&pastes stuff like that into their own essay without critical thought, don't be surprised if it taints the rest of his essay. For example, the "you are not a commodity" is not fully reasoned out. In the essay, it's just an empty platitude/affirmation instead of explaining why some programmers are treated as commodities and how to differentiate themselves to avoid that categorization.

mistersquid 11y ago
These numbers are provided in a different context (to measure Twitter's loss against profits of other well-known highly-valued technology companies: https://twitter.com/dcurtis/status/694586397588467712 https://twitter.com/dcurtis/status/694586397588467712 I don't know the source of Curtis's data.
carboncopy 11y ago
If you use profit/#employees, then you're double-counting. The employees' salaries are already taken out of profit. That's why it's not fully disingenuous to consider revenue instead. $500k of profit generated per employee sounds excellent, but it's also omitting other capital costs made by the business. Essentially, none of these benchmarks can give you the complete picture.

MCRed 11y ago

Business guys make more money, only because they convince developers to take less than they are worth. Your friend hired a developer who, by your account, was doing all the work, and then the business failed because your friend was too greedy. Now he thinks he's going to learn to be a developer and then not need any developers. Good luck with that. By the way "getting it funded" is not success. Making it profitable is success. PS- the word "coders" is like the n word. Use it and we know you don't respect us.

abawany 11y ago
Not that I am comparing software development to entertainment but in my perception, software developers today are in a similar position as Elvis was with his fake-Colonel "business guy" throughout his career: exploited and treated like a replaceable widget. The one person I credit with providing me this insight is patio11 whose articles on negotiation are gold.
louprado 11y ago
coda please.
- 50CNT 11y ago
  I believe the politically correct nomenclature is "Technican-american", though some also call us dork skinned people. Still missin' my /home/boy, they got him up in Redmond after an IPO gone bad, heard he's vestin' for another 3 years up in there.

wcummings 11y ago

>Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise. >rather than deal with the emotional vagaries of software developers. Negotiating compensation you're comfortable with isn't an "emotional vagary". Sounds like the programmer was working for a measly amount equity in something that will most likely be worth nothing in a couple of years.

vinceguidry 11y ago
He should have realized it before he made the deal and negotiated a better one for him. Also, he almost certainly bailed on this deal without having an alternative lined up, so all he did was destroy momentum. I've been in this situation before, and bailed before any real work got done. That's when you need to realize these things, not after you get funding.
- 67726e 11y ago
  Sometimes the right solution is to walk away, regardless if it destroys something. Maybe the businessman was unwilling to renegotiate or was a prick. I have no obligation to stick with a job that isn't doing it for me. Maybe it's the businessman's fault for not finding a replacement? As an aside, you seem awfully defensive of the businessman despite not having the full story.

gaius 11y ago

Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise This story is meaningless without some numbers attached. The developer was obviously a crucial part of the company - did he own 50% or 0.1%?

vinceguidry 11y ago
It's not. He made an agreement, and bailed on it later, for no other reason than that he didn't like the agreement he had made. Doesn't matter what the numbers are.
- cheez 11y ago
  Agreements can be remade when circumstances change. Again, your business guy sounds pretty dumb when his solution is to learn it himself.
- mistersquid 11y ago
  Your analysis is too rigid and could use the nuance numbers might provide. If the developer executing the idea was paid a low sum in exchange for low equity (say, 75K + 0.1%) and market analysis revealed a much smaller market than anticipated, the developer may have rationally understood the situation to be exploitative. In such a case, the numbers might reveal that higher equity (say, 75K + 20%) might make the situation would not only be equitable but potentially profitable. You're right to say that the developer breached the contract, sure. However, having numbers might contextualize that breach of contract so that it could be read as a poorly-considered evasion of responsibility or a rational decision to leave a financially abusive and career-limiting contract. EDIT: Readability. Add conjunctive adverb to last paragraph.
- gaius 11y ago
  Depends if it was a "right to work" situation where no notice period was necessary - another crucial piece of the story omitted.
- RobertDeNiro 11y ago
  It's his life. People change, and he probably found something better elsewhere. Why would someone who's paid less than 0.1%(assuming the worst case) be forever loyal to a business? Loyalty has a price and it's much higher than most people seem to think.

crdoconnor 11y ago

>Just when things started picking up, the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise. >deal with the emotional vagaries of software developers This is a human trait, not a software developer trait: https://www.psychologicalscience.org/index.php/news/releases/are-humans-hardwired-for-fairness.html https://www.psychologicalscience.org/index.php/news/releases... He would do better to learn to temper his greed rather than to learn programming.

gizi 11y ago

> ... the dev decided he wasn't getting enough of the pie and bailed, destroying the entire enterprise ... Business guys are typically going to make more money than the coders are, it's pointless to fight this. The dev apparently fought this and won ;-) > ... humans are harder to deal with, ultimately, than computers are. Especially devs are ;-)

mangahero 11y ago

This statement is false. This man stands to benefit from the businessman in terms of a fairer deal in the future. Such is business.

vinceguidry 11y ago
Well, now the businessman won't deal with him in the future. So he burned a bridge.
- gaius 11y ago
  Or dodged a bullet.
- 67726e 11y ago
  Maybe the businessman fucked the developer and burned a bridge. You're obviously wedded to your narrative.

jsight 11y ago

> Business guys are typically going to make more money than the coders are, it's pointless to fight this. Negotiating a better deal is pointless? What? I thought you were in favor of business. > The reason is that the business side is the human side, and humans are harder to deal with, ultimately, than computers are. I will not get into an argument about whether humans are harder or easier to deal with. I also will not get into an argument about whether software development is fraught with the same types of issues with dealing with people. Instead I will just point out that pay is not directly related to the difficulty of the work. It is a function of the value derived from the work, the availability of labor, the negotiating skill of the various parties involved, and many other factors (all to varying degrees). I agree with everything else that you said, especially the part about $$$/employee figures and their misleading nature. In general whenever you see $/(some arbitrary unit) in the financial press, be wary. It is sometimes a useful way to look at things, but it is incredibly easy to manipulate so that it ends up being a completely useless figure. I see it happen all the time, and these are often the most quotable lines as well (sadly).

beachstartup 11y ago

uh, okay. sounds like the 'business guy' wasn't so good at business. if you choose a partner and he bails, that's your problem. one of the key tenets of business is keeping people properly incentivized, and he clearly failed at that. and that software guy was also a business guy, by definition. sounds like he did some intense businessing and got the hell out of that business after realizing he was making a terrible business decision. part of being a 'business' person is dealing with reality as it exists, not making up narratives that suit your ego.

deleted 11y ago

[deleted]

UK-AL 11y ago

I agree with the idea that you shouldnt care companies making more money of you than you cost. That's because capital, marketing and teams are multipliers. They use you plus these things to make more money than you could by yourself. Completely disagree with the rest of it though. You should neogiate the best deal possible, you should walk away if deal isn't good for you, you should treat it as business. You need to be an engineer and a business person and make sure your getting the best deal.

YZF 11y ago

It would be interesting to hear that story from the developer side of things. I'm sure there's more to it. I also got a few stories. Maybe a bit of a rant but bear with me ;) I have the technical know-how and the idea and I bring in a business person to help try and make a business from it. Before I know it the business person is putting me in a position where I lose control over the product and the business and essentially have to work for free on faith and lose all my intellectual property. I quit, sooner rather than later. Just to be clear very little effort was invested at this point and I was clear about my expectations from the beginning. I go work for a startup and take stock options as part of my compensation. The company IPOs. All business types including fairly recent hires make a ton of money. Most technical types made almost nothing. The shares keep declining, the company gets bought out, more money for business types. End of story? I did get an OK salary as well but I invested a lot of heart in this so it left me with a bad taste. What's at the core of this? No one is looking for win-win situations. We have too much competition and too little cooperation. When you have a CEO who is solely motivated by how much money he is going to make this is bad for employees, shareholders, the company and everyone else. Just because the way this CEO will make money is making the company look good doesn't mean he actually cares about anything beyond how it looks. Not all companies are like that but too many are. What we have is lose-lose, companies and shareholders lose from high churn, lack of loyalty, lack of motivation, lack of investment, bad CEOs. Employees for the most part lose as well. Tragedy of the commons. Specifically with Apple they're hoarding cash, not investing it, not paying it out to employees or shareholders. They're buying back their shares at inflated prices. How is that something that benefits the company or anyone else? They're sucking money out of the economy. I'm sure there are worse examples...

nickpsecurity 11y ago
Great counterpoint that describes and gives anecdote to what I described in my own reply: https://news.ycombinator.com/item?id=11095689 https://news.ycombinator.com/item?id=11095689

nickpsecurity 11y ago

As with others, the morality of this situation depends on details we don't know. What always trips me out is the double standards in posts like yours. People are fine with the capitalist notion of starting a business, giving most people in it almost nothing, often collecting any I.P. produced rather than a license, and having goal of selling out in a way that will likely cost the employees their jobs. Almost all value goes to investors or a few founders while almost all work is done by employees. The process is often supported by false promises or emotional manipulation to keep workers loyal & with a tiny part of the pie. This is default in Silicon Valley from what I read here and in other media. Then, an employee decides to do what's best for him or her in a way that negatively impacts the founding business person or investor. This is seen as unethical: such employees, upon some agreement or context, cannot possess the ability to make other choices that damage founder or VC goals. They don't possess the trait that founders and investors wield with nary a thought over employees like we're starting to see with more layoffs. The employees are, instead of rationally selfish, being Evil and called out for it. A double standard that serves captains of industry and startup founders very well at everyone else's expense. In reality, capitalism says that everyone, including employees, should act in their own self interest externalizing all costs of such actions. So, per capitalism, the founder did the right thing by trying to screw the employee out of lots of net worth and the employee did the right thing screwing the founder by taking another path. Naturally, being utilitarian, I oppose such capitalism in favor of stakeholder-focused models with rules reducing opportunities for each party to screw the other. The market goes the other way, though, so everyone continues to help or screw everyone to heart's content. And I get to read nonsense like this where people cry "But that's not right and fair!" while simultaneously... "Business guys are typically going to make more money than the coders are, it's pointless to fight this. The better route is to go into business yourself and capture the value yourself. " ...supporting amoral, selfish practices of capitalists on founder or VC side. It's just also what the developers were following: do whatever provides most perceived value for themselves. It is really good advice, though. Keep preaching it while system works as it does given that's where money is at. It's just that making an exception for one party but not others seems unfair and irrational. Thanks for the entertainment though. :)