RE: Remind me why we got rid of those nasty fax machines, clerk?
Because the beancounters said it would cut costs!!!
2263 posts • joined 6 Apr 2008
Considering that amount of cheaply1 produced tat flowing out of the Far East, is it a bad idea to allow only higher power levels for products that are certified to comply with the regs?
Cut too many corners, and that waiver can be revoked.
1 As in poorly engineered or manufactured. Current security of IoT tat is a prime example of this shove it out the door quickly and cheaply mentality.
<quote>The reason that one truly is forbidden, is because it let's us know the real truth about managers (who have their sense of humour surgically removed when they sign the contract to become manager).</quote>
The contractual lobotomy, the prime reason why I turned down a promotion to manglement.
Anyway, it is more """fun""" to take cheap shots at them, rather than having ones taken at you.
<quote>We should all hope the cash spigot is left wide open through lack of regulation so executive bonuses can trickle down.</quote>
Trickle down, MY ASS!!!
Do you honestly think the executives are going to share those bonuses???
There will be a giant sink stopper at the drain of the executive level preventing any such "trickle down".
<quote>And you tell me just what management tools he has at his disposal.</quote>
IF it is like a former mangler I had to endure, those tools are:
1) a big mouth, and
2) steel toed work boots.
If the use of tool #1 doesn't achieve the desired result, then judicious use of tool #2 to your ass usually does.
<quote> Does not take long to buy the hardware ... at $156/month.</quote>
You are right, it doesn't.
In the USofA, no thanks to the Tax Laws, you run into the old debate - CAPEX vs OPEX.
Buy it outright for (let's use a round figure of) $3700. That's $3700 straight out of your pocket (and possibly out of current profits), and you have to depreciate it over its expected lifespan. Assume a residual value of $100 at the end of a 36 month lifespan; you get to 'write down' the value by $100/monthly. Again, assume that you bought it in early January, and your first year writedown is only $1200. You have to carry the remaining $2400 as an asset, and can not depreciate it until year 2 and 3 before it no longer benefits from a depreciation schedule. If that $2400 came from profits, then guess what - you pay taxes on it! Only in year 2 and 3 do you get the benefit of the previous expenditure. That depreciation goes against profits from year 2 and 3.
Contrast that to a lease - leases and a straight expense, written off as a business expense as they are incurred. No taxes paid on those writeoffs.
Now you have some inkling as to why beancounters want to shift as much CAPEX into OPEX as they can get away with.
<quote>Plus, the beancounters prefer spending money on fixing tomorrow than on digging today because digging is more expensive in the short run and nobody knows what the long run is anymore.</quote>
Today's MBA induced mentality is to always think in short term objectives (e.g. next quarter), you will not be around to reap the rewards of any long term thinking, as it is likely you will be gone in 5 years.
Second, there is that good old debate over CAPEX vs OPEX.
<quote>I'm not sure if this is still the case, but in the US aren't mobiles charged for receiving calls as well as making them?</quote>
One word answer - YES!
And $DEITY help you if you are on a plan that provides X minutes per month because you do not need an """unlimited""" plan. Overages are a BITCH!
<quote>Over the 8 years I have had complete hell of updates and failures on some other Windows machines I unfortunately took responsibility for...</quote>
You should never take responsibility for any Windows machines, because you do not """own""" the operating system. Microsoft does. You only get to use it as Microsoft sees fit.
And Microsoft does not give a shit if you encounter 'problems'.
At my former employer - it was mandated that desktop machines be shut down at the end of the day.
If it isn't powered up, then it can not be pwned during the overnight/weekend hours.
This policy arose from an incident where an executive left his machine on, and it was infected with malware. Those behind the attack had the whole weekend to surf out or internal network. Cleaning up the mess was one of the reasons why we ditched Windows, and went to Linux. The other being a nastygram from the BSA that was quite costly.
I point to incidents like this one as reasons why you should not go to the cloud.
But penny pinching manglers never learn.
One mangler I once worked for bought that hype, hook line and sinker. So that company went off to the cloud against my advice. Cue one cloud failure, and people were sitting there unable to do their jobs, and said mangler starts screaming: "Do something!!!!!" I did. I handed him my letter of immediate resignation, packed up and walked out. A few days later he calls me up sheepishly wanting to know if I would 'come back'.
The answer was a terse: "FUCK YOU!!!" and I hung up. 'Fix it your own goddam self' was my attitude.
<quote>It's also possible that he's fighting a very private health battle with a
n uncertain foreboding prognosis.</quote>
He might be facing a situation where he has been told that you have X amount of time left; and he plans to step aside to enable his team to continue forward, and he can make the best of the time left.
In any regard, I hope I am wrong on that one.
Biting the hand that feeds IT © 1998–2019