A guide to getting started with embedded systems

Re:A guide to getting started with embedded systems by stackbutterflow on Friday May 13, 2022 @04:34AM (#31364825)

Pay has never been correlated to the difficulty of the job. It's simply how much money you can generate for the business. Software is but one part of an embedded system. Whereas it is the whole part of a pure software product.

[ Parent | on HN ]

Re:A guide to getting started with embedded systems by Dudeman112 on Friday May 13, 2022 @10:17AM (#31367950)

>It's simply how much money you can generate for the business

I find your excessive faith in businesses disturbing.

Markets aren't rational [1] and the wage-labour market isn't either. Sometimes there's no good reason for something, only a bunch of chain of consequences that don't necessarily have to make logical sense from an utility perspective.

[1] https://www.cnbc.com/2017/12/21/long-island-iced-tea-micro-c...

[ Parent | on HN ]

Re:A guide to getting started with embedded systems by GianFabien on Friday May 13, 2022 @07:44PM (#31373710)

You need to look at the business as a whole. Software only business are profitable because the per unit cost approaches zero as your volume increases past the development amortization cost. Say profits in the order of 80%+

Embedded systems are part of tangible products. They have an order of magnitude greater non-recurring engineering costs, then cost of components, manufacture, packaging, inventory, distribution and after-sales service and support. Due to the huge up front costs, volumes are generally limited by capital funds. So the net profits are likely to be 15% - 20% range.

When you look at the differences, it becomes clear why tangible product companies are unable / unwilling to pay like software-only companies.

[ Parent | on HN ]