LittleAlex on Nostr: nprofile1q…p0804 Don't forget vendor lock in. Manufacturers love it. On the other ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqtlxplnm3h69fx47r50fz0h9rn5mkxx5v95kfddk8489vez8wpfssyp0804 (nprofile…0804) Don't forget vendor lock in. Manufacturers love it.
On the other side it didn't improve the quality of the products, more the opposide. Since more and more stuff is software defined, done by copy&paste-code, you add complexity and bugs.
Before a discussion inside the development department was like this:
Boss: What's the status?
Engineer: We figured out if we bend this lever by 1.5° the operation is smoother and wear and tear is much lower. We can also make it lighter this way, but wen need some more testing.
Boss: How long?
Engineer: Two week,s maybe four.
Boss: Ok, you have two weeks and I want a report every week on the progress.
Today it goes like this:
Boss: What's the status?
Engineer: We found some actuators on the market 10% cheaper, but the software of the controller needs to be adapted.
Boss: Can we reuse some code we wrote before?
Engineer: Yes, but is has to be adapted, too and it would be slower than what would be optimal.
Boss: Do it, it's good enough.
Engineer: We also found the new actuators will get a little too hot sometimes, drastically reducing the MBF.
Boss: Not a problem. What about the updater?
Engineer: It works, but it still has a bug and doesn't work on Fridays.
Boss: Ship the product. We will update only on Mondays and tweek out everything via customer feedback.
The result are crappy products with reduced lifetime and annoyed customers. While engineers tested analoge engineering they found a lot of problems and fixed it before it went into production. It wasts a lot of ressources, the products are often not made to be recycled and end up in landfills. Best for profit, bad for everything else.
On the other side it didn't improve the quality of the products, more the opposide. Since more and more stuff is software defined, done by copy&paste-code, you add complexity and bugs.
Before a discussion inside the development department was like this:
Boss: What's the status?
Engineer: We figured out if we bend this lever by 1.5° the operation is smoother and wear and tear is much lower. We can also make it lighter this way, but wen need some more testing.
Boss: How long?
Engineer: Two week,s maybe four.
Boss: Ok, you have two weeks and I want a report every week on the progress.
Today it goes like this:
Boss: What's the status?
Engineer: We found some actuators on the market 10% cheaper, but the software of the controller needs to be adapted.
Boss: Can we reuse some code we wrote before?
Engineer: Yes, but is has to be adapted, too and it would be slower than what would be optimal.
Boss: Do it, it's good enough.
Engineer: We also found the new actuators will get a little too hot sometimes, drastically reducing the MBF.
Boss: Not a problem. What about the updater?
Engineer: It works, but it still has a bug and doesn't work on Fridays.
Boss: Ship the product. We will update only on Mondays and tweek out everything via customer feedback.
The result are crappy products with reduced lifetime and annoyed customers. While engineers tested analoge engineering they found a lot of problems and fixed it before it went into production. It wasts a lot of ressources, the products are often not made to be recycled and end up in landfills. Best for profit, bad for everything else.