3 ms·
Sorry though revenue per employee is still massive for a lot of companies. The folks who own the companies are even more overpaid. Also the insecurity really do
by taurath 3y ago
Sorry though revenue per employee is still massive for a lot of companies. The folks who own the companies are even more overpaid. Also the insecurity really does reduce quality when you have people performing what used to be 3 peoples roles and everyone who’s left is told to tighten their belts (read: burnout within a few years)
- austin-cheney 3y agoFor almost all large employers that make primary use of JavaScript as a core component of their business there are only two revenue streams: e-commerce and ad impressions. The margins and overhead per developer employee are dramatically lower in e-commerce than for business primarily reliant on ad revenue. The reason for that distinction is that developers are always a cost center while the money makers are always sales, but in ad revenue based businesses those lines are blurred and ad based business scale their revenue disproportionately to their headcount far more so than e-commerce. As a result developers in e-commerce type businesses tend to reach compensation caps faster than employees in ad revenue type businesses. What is counter-intuitive about that is that the user facing code from ad revenue type businesses tends to be extremely low quality compared to equivalent code from e-commerce type businesses, because that code more directly impacts user engagement on the e-commerce side and user engagement is more critical for sales conversion on the e-commerce side. I am not saying the code on the e-commerce side is great either.