| General > General Technical Chat |
| I hope some smart phone manufacturer/designer would understand this |
| << < (8/8) |
| Rick Law:
--- Quote from: ejeffrey on August 17, 2021, 03:25:19 am ---... Because if you get hacked it's not just your problem and the fact that you don't understand that is exactly why these policies exist. It is your obligation to keep any device you connect to the public internet up to date. ... --- End quote --- These policies exist because software manufacturers lost their ability to do good software. The software makers failed their obligation in delivering a secured and fully functional product. They "remedy" their mistake by shifting the burden and cost of that failure for the end user to bare. As a result, huge amount of productivity is lost. Computer programmers are not the only ones using computers for sure, but lets look at just them for a gauge. According to DAXX.COM, 4.2 million programmers in the USA in 2019. Average programmer salary ranges from 42K to 100K (PayScale.com), 42K to 94K (ZipRecruiter), 49K to 82K (Salary.com). So, let pick a middle number, say 70K/year. About 40hr/week, 50week/yr, that is $35 per hour. If a patch causes each programmer to loose 12 minutes, that is 1/5 of an hour. That is $7 each for 4.2 million programmers in the USA alone. Just in the computer programming industry alone, almost $30 million dollar worth of productivity gone down the drain. Now you add the receptionist, the accounting people, the sales folks... even the factory workers. Even if they don't do the patch themselves, they may need retraining because of UI change or changes in operations due to the software changed. 160 million people working in the USA averaging $31.1K/yr. Figure 1 in 4 use a computer, that would make it 40 million users. Say the computer users are above average at 40K/yr, that would be $20/hr or $4 for 12 minutes. 40 million user at $4 each. That cost of patch balloons to $160 million USD for USA alone. $160 million is a lot of productivity lost. This mess that we are in is because the software industry failed their obligation in putting out a working and a secure product. Don't blame it on the users. |
| AaronD:
--- Quote from: Rick Law on August 17, 2021, 05:04:52 am --- --- Quote from: ejeffrey on August 17, 2021, 03:25:19 am ---... Because if you get hacked it's not just your problem and the fact that you don't understand that is exactly why these policies exist. It is your obligation to keep any device you connect to the public internet up to date. ... --- End quote --- These policies exist because software manufacturers lost their ability to do good software. The software makers failed their obligation in delivering a secured and fully functional product. They "remedy" their mistake by shifting the burden and cost of that failure for the end user to bare. As a result, huge amount of productivity is lost. Computer programmers are not the only ones using computers for sure, but lets look at just them for a gauge. According to DAXX.COM, 4.2 million programmers in the USA in 2019. Average programmer salary ranges from 42K to 100K (PayScale.com), 42K to 94K (ZipRecruiter), 49K to 82K (Salary.com). So, let pick a middle number, say 70K/year. About 40hr/week, 50week/yr, that is $35 per hour. If a patch causes each programmer to loose 12 minutes, that is 1/5 of an hour. That is $7 each for 4.2 million programmers in the USA alone. Just in the computer programming industry alone, almost $30 million dollar worth of productivity gone down the drain. Now you add the receptionist, the accounting people, the sales folks... even the factory workers. Even if they don't do the patch themselves, they may need retraining because of UI change or changes in operations due to the software changed. 160 million people working in the USA averaging $31.1K/yr. Figure 1 in 4 use a computer, that would make it 40 million users. Say the computer users are above average at 40K/yr, that would be $20/hr or $4 for 12 minutes. 40 million user at $4 each. That cost of patch balloons to $160 million USD for USA alone. $160 million is a lot of productivity lost. This mess that we are in is because the software industry failed their obligation in putting out a working and a secure product. Don't blame it on the users. --- End quote --- The silicon valley mentality: "Move fast, break things, fix them later." That's awesome for getting and keeping the public's excitement for new features and capabilities, and is perhaps 90% responsible for what our technology can do in such a short time since it was invented in the first place. But it also causes the problem that you describe. These people are not engineers, regardless of what their titles might say. They're kids in a playground. --- But, if you're losing productivity because of a forced update, it means that you're not updating during your downtime. That puts the fault back on the user for poor maintenance. Likewise if you get hacked because you found a way to disable them entirely, which leaves you wide open to someone who studies them to see what vulnerabilities they fix. |
| Rick Law:
--- Quote from: AaronD on August 17, 2021, 02:21:18 pm ---... But, if you're losing productivity because of a forced update, it means that you're not updating during your downtime. That puts the fault back on the user for poor maintenance. Likewise if you get hacked because you found a way to disable them entirely, which leaves you wide open to someone who studies them to see what vulnerabilities they fix. ... --- End quote --- With exaggeration to make a point... down time only exists in the comforts of a software/hardware development office. In some lines of business, the most expensive part is the capital investment that makes the business. It is foolish to keep the expensive machinery idle and paid for empty spaces all night. Paying for overnight staff at 1.5x salary or more to keep the place going 24x7 instead of 8 hours a day is common. That 3x increase in productivity for the capital is what made the business viable. A manufacturer I worked at, downtime was once a year for annual cleaning. Restarting and warming up the machine to thermo-stability will take up a full day on a good day. Any interruption in an operating line costs thousands as the clock ticks. Yeah, many of the line machines run regular windows with network connections. Part of the network is entirely internal only. Yeah they receive updates only as needed - the operating environment is tested then locked down prior to rollout, expecting no further change for the next 360 days. To understand our sales environment and learn how can I best support them, I attended their sales meeting regularly. I actually took a few days to tag on to a sales guy or two on the road. Sales staff prefer to take most of the downtime smooching with customers. Their getting from one customer to the next is when they take a breather. Dealing with updates is the last thing they want to do. By the time they really reach their downtime, they are too "poop out" to do anything that requires the brain power to add 1+1. So I ship them lock-down machines (or pretend lock-down by disabling certain things) they ship their machines back for regular maintenance. Upgrading what works is part of the budget that bring no real benefit to the operation of the company. Around 2000, I was in the warm and fussy software development environment. I attended an IT seminar. One of the speakers was a senior IT person formerly at FAA (Federal Aviation Admin). He shared with us that his system's annual downtime budget is 3 seconds. He can use this 3 seconds whichever way he wants, but 3 seconds is the limit! You can bet any update is very expensive event in that environment. Yeah, a lot of people would like to switch places with others who do have "downtime". Outsourcing and off-shoring changed the picture a lot, but I believe most of affected would prefer to have no downtime than having downtime 24/7/365. |
| AaronD:
Seems like everyone has bought into the idea of having no stock at all, no spares, no anything except for what's actually in production *right now this minute*. Buy today to use tomorrow, nothing sits idle for more than a few hours. That's great when the entire world is operating stably, but how's that going this year? :-DD --- Likewise for downtime-sensitive things. Have a hot spare anyway, in case the main one fails - maybe not a whole 'nother manufacturing plant, but enough that you can switch a run over to another machine while you fix the original - and then an update simply counts as a "failure" of that machine. Bring it back up, test it, and voila! It's "fixed"! Then do it again with another machine that needs updating, etc. Your advertised capability takes that into account: you technically have more capacity that what you advertise, but that extra is reserved for exactly this purpose. |
| Navigation |
| Message Index |
| Previous page |