|
|
|
|
|
by EliRivers
2307 days ago
|
|
So if a crippled person needs somebody to go to the bank and withdraw $1,000 for them, and they figure they can hire somebody trustworthy for $50 to do the errand, is that person not being paid what they’re worth, because they added $1,000 dollars of value? This is a terrible example. Moving something is not the same as creating that something. Moving $1000 could be worth nothing. It could have negative value. It could be worth millions. |
|
If you’re in the business of creating useful objects out of basically nothing, you don’t even need a company. Maybe you hire somebody to sell your objects for commission, or maybe you sell them yourself.
If you’re looking for a closer analogy, try the shove analogy. Why is it that despite the fact that the shovel makers are creating an object, even out of nothing, that they aren’t worth what is dug up with them? Software engineers are a lot like the shovel makers. Sometimes the shovels we make are used in extraordinarily profitable ventures. But their value is still determined by how hard it was to make them, and to learn the skills to make them. Not what the company uses them for.
I think it becomes hard to see when all the shovels being made are bespoke. Lots of software is written to fill one role for one client. That client will often use that particular thing to make lots of money. So maybe it appears like that thing bit of software created all the value? But this is clearly false. The fact that some part of a system is essential to the whole system’s success does not imply that the worth of every piece of the system is equivalent to the worth of the whole system.