EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS


Fiduciary Technology: Why It’s Often Impermissible to Use Microsoft (But It’s Done Anyway)

Posted in Apple, GNU/Linux, Microsoft at 11:10 pm by Dr. Roy Schestowitz

Original by Mitchel Lewis at Medium (reproduced with permission)

Drake Microsoft

Summary: “As such and if your CTO isn’t actively moving tooling out of the Microsoft ecosystem like bailing water out of a sinking ship, then you should probably be looking for a new CTO.”

Leadership of public companies have one job: maximize shareholder value. Although the roles and governance of executives can vary wildly, CEOs, CFOs, CIOs, CSOs, and CTOs all operate in capacities that serve as a means to maximize value in their own way. Try as they might to muddy the waters and minimize this objective with discussions of ethically grounded missions and humanitarian causes, this is all done for PR purposes and executives of major corporations could be fired, fined, and possibly even thrown in jail for placing anything above shareholder value. It is their fiduciary duty; their modus operandi; their north star; their prime directive; their alpha and omega; their mecca; their great white buffalo; their holiest of holies; etc etc.

Since competitive trade is a form of war that is won with efficiency, CTOs, in particular, are tasked primarily with outfitting their company with the most efficient, secure, and reliable (dare I say best?) tools available in an effort to give their company a competitive advantage against their market competition. Quality isn’t cheap nor is it very objective in a world dominated by pervasive marketing where everyone markets themselves as the best, so a bevy of experience, tact, and research is required to navigate these waters successfully. In their world, minor insights can save millions while minor mistakes can cost millions just the same. Put simply, it’s the CTOs job to maximize shareholder value by constantly optimizing their tooling in favor of efficiency and revenue per employee metrics.

Ironically, the IT solutions that are the most complex, least secure, most unreliable, and most expensive over their lifespan, the worst solutions if you will, tend to be inexpensive upfront while the best solutions tend to be their inverse in that they are the simplest, most secure, most reliable, and least expensive over time tend to have higher financial burdens for entry. In comparison to the worst solutions, the best solutions also tend to be more agreeable for end users which maximizes revenue per employee while also minimizing downtime, the #1 IT expense for most organizations, along with reducing the labor required to maintain said technology to prevent downtime which is the #2 IT expense for most organizations; the initial cost of hardware and software licensing is a distant 3rd.

Based on this alone, one might expect that executive decision-makers in IT to be keeping companies on the simplest, most secure, and most reliable solutions available but this is hardly the case. Despite sparing no expense on IT and having grizzled veterans at the helm, anyone working in corporate America can confirm that the opposite often appears to be true. Almost as if they have pedestrians at the helm, most corporations can be found locked into a complicated hellscape of poorly implemented and virtually unsupportable IT solutions with a hodgepodge of cloud solutions that barely work while paying 3–5x more than they should be for their IT infrastructure as a consequence of all of this. In turn, this artificially limits user productivity and requires them to employ more people than they would otherwise have to if they were standardized on more efficient tooling; better tooling, less labor.

For example and even though both Apple and Linux solutions have been humbling Microsoft solutions for decades by generating anywhere from 1/2 to 1/3 of their ownership costs over their lifespan, you can still find that most major corporations and small-medium businesses are standardized on Microsoft solutions as if the opposite were true. In most scenarios, Microsoft solutions create more downtime, require more labor to implement and maintain, and are generally more complicated and more expensive than their market competition. In fact and when remembering that the majority of IT expenses occur after purchase, there is so much of a quality disparity between Microsoft solutions and their market competition that they often still wouldn’t financially competitive even if their licensing costs were free.

“Put simply, the implementation of Microsoft solutions puts any company at a significant competitive disadvantage from the perspectives of productivity and reliability while leaving them vulnerable to security breaches in comparison to competitors in the same market that are standardized on more efficient and secure Linux and/or Apple solutions.”Oddly enough, even when comparing Microsoft and Apple, both of which are standardized on their products, you’ll find that Apple generates 2–3x more revenue per employee on an enterprise scale. Although purely a coincidence, when IBM made the move over to the Apple ecosystem in 2016, they noticed their total ownership costs reduce to 1/3 that of their PC infrastructure. In doing this, support cases along with the requisite labor, downtime, and degraded productivity associated with them dropped dramatically as well when compared to their PC infrastructure. As far as CTOs are concerned, this is

On top of the added costs from downtime and labor inherent to standardizing on Windows, 99% of all ransomware attacks occur on Windows while half of all of their users in their vulnerable cloud services are actively being poked and prodded by various exploits and attacks at any given time. Microsoft solutions are also the most exploited in the industry and require more ancillary services and layers of defense to fortify their integrity which introduces even more complexity into the environment while reducing convenience and driving costs even higher. Put simply, the implementation of Microsoft solutions puts any company at a significant competitive disadvantage from the perspectives of productivity and reliability while leaving them vulnerable to security breaches in comparison to competitors in the same market that are standardized on more efficient and secure Linux and/or Apple solutions.

Drake not Microsoft

When considering the fiduciary duty of CTOs along with the the financial and operational shortcomings of Microsoft solutions in today’s market, one might think that a large component of a CTOs role is to avoid Microsoft solutions altogether as if they were sitting in a box labeled “COVID-19 Mucus Samples” or at the very least keeping their implementation to a minimum, and they would be right to some degree. But Microsoft’s market position indicates that this is clearly not happening and Microsoft PCs along with their sketchy suites of productivity and server software persist as the industry standard when no objective measure can merit such a reception.

From another angle, it seems as if the vast supermajority of CTOs are failing miserably at fulfilling their fiduciary duty by continuing to militantly implement Microsoft solutions to the point of them being the status quo throughout industry. There could be several potential reasons for this, sheer ignorance possibly being one of them.

At the level of CTO, one might think that an aptitude with the philosophy of technology, IT architecture, and IT finance is skills is must, but as is the case elsewhere in life, it’s often more of a question of who you know, how loyal you are, and how well they tow the company line in these positions. As such, many of those being paid to be experts in IT architecture and finance as a CTO is may not be as polished as they’d like you to believe. Although it may be news to people who don’t live and breathe IT finance and architecture that the majority of IT expenses occur after purchase and that focusing on initial price alone is a fool’s game, such understanding is fundamental in the realms of accounting and architecting information technology.

Alternatively, it could also be a simple case of bygones in leadership positions and old habits dying hard. To their credit, there was a time when the above was not true about Microsoft solutions and their dominant market position was earned but those days are gone. Despite working in technology, a word that is almost synonymous with change, anyone in the industry can recall instances with people with a devout preference for the status quo and an overt fear of change; especially among leadership; regardless of how sound the math is. CTO or not, like it or not, we tend to become bygones as we age and the continued prominence of Microsoft products could be a consequence of the tendency of CTOs to be of an older demographic *cough* boomers *cough*.

Another possibility is that they could also be conflicted. Rather than having to learn new technology and architecture, decision-makers can also ensure both their relevance and necessity by continuing to deploy solutions that require their expertise. Those with decades of experience in the Microsoft ecosystem can ensure both their continued relevance and necessity by continuing to implement these products while embracing newer technologies that they’re unfamiliar with can put them at a competitive disadvantage. Just as consultants recommend solutions that generate further necessity for their services, CTOs could be doing the same.

To be fair, CTOs are humans prone to error and technical change is also hard. In the world of enterprise change, it can often feel as if users are so change-averse that they will hate you regardless of whether you deliver them a better solution or a worse one just the same and this is often true. Over time, the pushback one can get from employees and execs by simply trying to improve employee and company efficiency can be astounding. In turn, this pushback can wear on the best of us and suffocate the ambition of entire IT departments.

“…it’s foolish to expect an unambitious CTO to radically change both their mindset and philosophy towards technology at the pinnacle of their career, let alone at their average senior age.”After all, why try to make things better when people resent you for it and potentially jeopardize your job when you can instead safely maintain the status quo and have people praise you for fixing the same problem on a daily basis like some nerdy version of Groundhogs Day? However, mitigating this kind of change apathy is part of the job and those that fail to do so consequently fail to do their job effectively. Although enterprise change is difficult and not for the faint of heart, no one said it was easy, this is why they make the big bucks, and they can always quit if they don’t like it.

Regardless of their reasoning, it isn’t difficult to determine which category your CTO falls into though; it’s just a career limiting move. For example and if your CTO can’t even tell you the proper order of IT expenses, then they’re most likely ignorant; chances are they won’t even be able to tell you what technology is. If they’re spouting off old debunked rhetoric about Apple or Linux solutions not having a place in the enterprise in response to the mere notion of implementing Apple or Linux solutions, then they’re most likely a bygone. And if they’re compromised, then they’ll likely avoid this conversation altogether or become incredibly petulant when cornered on the subject.

But whether they’re some combination of an ignorant, jaded, and compromised bygone is of little consequence as the result is still the same regardless of the road they travel on. That said, CTOs are seemingly failing to fulfill their fiduciary duties throughout industry by continuing to implement Microsoft and other antiquated solutions as if they were everything that they clearly are not. Few seem to have the chutzpah to adhere to their fiduciary duty to the point of obsoleting themselves and jeopardizing their relevance by implementing better solutions beyond their expertise.

In summary, it’s the primary role of a CTO to give their company a competitive advantage by ensuring that it has the most efficient tooling which many in these roles are failing at presently. Given Microsoft’s market stance and prominence throughout industry and since the name Microsoft is effectively anti-correlated with word quality while their products lack a competitive advantage or value proposition, a large component of a modern CTOs job is naturally to reduce Microsoft’s footprint within their infrastructure as much as possible and replace their tools with better alternatives from Apple, Linux, and the like; which again, many are failing at. Reasons such as this are why Microsoft has had to resort to the lock-in and anti-competitive tactics that they became notorious for

As such and if your CTO isn’t actively moving tooling out of the Microsoft ecosystem like bailing water out of a sinking ship, then you should probably be looking for a new CTO. Just as it’s a fool’s game to emphasize on initial price instead of the total cost of ownership or to expect the tired solutions produced by a tired monopoly propped up by the same tired lawyers to magically get better by several orders of magnitude any time soon, it’s foolish to expect an unambitious CTO to radically change both their mindset and philosophy towards technology at the pinnacle of their career, let alone at their average senior age. Many have generous exit packages while countless people under their employment have been let go under similar performance-related circumstances, so they shouldn’t take it personally.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

Leave a Comment

You must be logged in to post a comment.

What Else is New

  1. Burning the House That Richard Stallman (RMS) Built: An Open Letter to GNU Maintainers Who Opposed RMS

    An open letter to people who petitioned RMS to step down and who outsource GNU projects to Microsoft (GitHub)

  2. Links 30/5/2020: Godot Editor Under Web Browsers, Alpine Linux 3.12.0 and EasyOS 2.3

    Links for the day

  3. EPO's Illegal Patents and Massive Corruption Go Unnoticed by Corporate Media and Sites That Cover Patent News

    Very major corruption scandals still emerge in Europe's second-largest institution and illegal patents get granted as well as promoted; somehow, perhaps miraculously, this no longer seems to bother anybody in the media (corruption and radical policies have been gradually 'normalised')

  4. Never Mind If GNU/Linux Works Better Inside Hospitals and Free Software Not Only Safer But Vastly More Efficient...

    With lives on the line one might expect hospitals to choose what's most secure and generally works best; but in practice there seems to be a leaning towards what bribes best

  5. Sick Alexander Ramsey is Using a Public Health Crisis to Lie About the Unitary Patent, Whose Fall Made Him Redundant and/or Obsolete

    Weaponised media continues to manufacture utterly ridiculous puff pieces for Team UPC, containing intentional lies from beginning to end

  6. IRC Proceedings: Friday, May 29, 2020

    IRC logs for Friday, May 29, 2020

  7. They Came, They Saw, He Died

    Microsoft is an inherently sociopathic company; today's story of AppGet is an important reminder that Microsoft has not changed and isn't changing (Maui is another week-old example of trademark-hijacking tactics by Microsoft)

  8. Microsoft-Connected CloudGuru Doesn't Care About GNU/Linux and Now It's Gradually Killing the BSD/Linux-Centric Jupiter Broadcasting (Bought by Linux Academy)

    Assuming Docker is being 'killed' by Microsoft (or at least hijacked to push Windows, Azure and so on) while the GitHub-hosted (Microsoft) CloudGuru, whose co-founder comes from Microsoft, ‘finishes the job’ with Linux Academy and its assets, it’s time to take stock of a pattern/trend that ruins the media too

  9. What Happened to Docker is a Cautionary Tale About the Not-So-New Microsoft

    It’s hardly shocking that Docker collapsed (mass-scale layoffs) after the company had gotten close to Microsoft and got rid of its very own founder (a Red Hat veteran) while the software is being killed off/co-opted by Microsoft (all over the news this week; we’ve omitted links by intention as it’s only puff pieces, no investigative journalism anywhere); we only ask one thing: is anyone paying attention and, if so, what are the lessons learned?

  10. If You Want to Support and Follow Us 'Properly', Really Simple Syndication (RSS) is Most Reliable and Robust to Censorship

    Our longstanding position on social control media (we reject it and don't participate in it) is only proven ever more justified now that the mere idea of fact-checking is seen as controversial if not illegal

  11. Links 29/5/2020: Genode OS 20.05 and FSF Video Conferencing Service

    Links for the day

  12. IRC Proceedings: Thursday, May 28, 2020

    IRC logs for Thursday, May 28, 2020

  13. Weaponised Media Promoting an Illegal Patent System (UPC), Exploiting Major Pandemic in the Process

    The whole 'unitary' scam/ploy (merely a Trojan horse for litigation and low-quality/invalid patents) is being promoted by Thierry Breton as EU Internal Market Commissioner (in spite of illegalities and constitutional issues), merely reinforcing the view that the EU is rather complicit in the abuses perpetrated by Team Battistelli; the media in the pockets of oligarchs and litigation firms (fronting for these oligarchs) plays along, as usual

  14. Links 28/5/2020: OpenSSH 8.3, New Mesa Release, Raspberry Pi 4 News, Fedora 32 Elections

    Links for the day

  15. The EPO Became a Very Radical Institution

    Projection tactics are doomed to say more about the people who utilise them than about anybody else; the EPO has become so autocratic and corrupt that corruption is seen as normal and workers who explain this corruption are framed as "irrational" or "crazy" or "radical"

  16. IRC Proceedings: Wednesday, May 27, 2020

    IRC logs for Wednesday, May 27, 2020

  17. Allegations That Microsoft Will Ruin Besieged Clinics and Hospitals to Retaliate Against Those Who Name the Culprit

    With a broader picture coming into view, as per the above index, we're starting to wrap up the series while issuing a call for more stories and eyewitness testimonies, exposing the nature of attacks on hospitals (those almost always target Microsoft and others' proprietary software, which is technically unfit for purpose)

  18. Microsoft Has Ideas...

    Based on the pattern of media coverage, composed by Microsoft MVPs and Microsoft-affiliated blogs/sites, confusing the public about the meaning of GNU/Linux is reminiscent of an "Extend" phase

  19. ZDNet Proves Our Point by Doing Not a Single Article About Linux (RC7), Only About Linus and Windows Clickbait Junk

    It seems abundantly clear that nobody wants to cover the actual news about Linux and instead it’s all about which PC Linus Torvalds is using (gossip/tabloid); ZDNet‘s latest two articles are an example of this…

  20. UPC Lies That Make One Laugh...

    IP Kat and Bristows (overlaps exist) are still pretending that the UPC is coming because reality doesn’t seem to matter anymore, only self-serving agenda

  21. Canonical Continues to Help Promote Windows Instead of GNU/Linux or Ubuntu

    Thrice in the past week alone Canonical used the official “Ubuntu Blog” to help Microsoft instead of GNU/Linux and it is part of a disturbing trend which lends credibility to jokes or rumours about a Microsoft takeover; it's not like many people use this thing, either (Canonical helps Microsoft shore up a dying/languishing EEE attempt)

  22. Links 27/5/2020: CoreOS Container Linux Reaches Its End-Of-Life, 2020 GNOME Foundation Elections Coming

    Links for the day

  23. IRC Proceedings: Tuesday, May 26, 2020

    IRC logs for Tuesday, May 26, 2020

  24. GNEW Seedlings vs. Free Software Deforestation

    “The idea of the GNEW Project really is about keeping the goals of the GNU Project alive — hopefully, they won’t destroy or co-opt too much of the GNU Project, that people like the Hyperbola devs can’t fix it with BSD.”

  25. Joi Ito Already Admitted on the Record That Bill Gates Had Paid MIT Through Jeffrey Epstein

    An important exhibit for the accurate historical record (because MIT has been trying to deny truth itself)

  26. It's Convenient to Call All Your Critics Nuts and/or Jealous

    Bill Gates antagonists are not motivated by hatred or jealousy but a sense of injustice; spoiled brats who break the law aren’t a source of envy any more than mass murderers are subject of admiration

  27. Real History of Microsoft and How It Became 'Successful'

    New video that contains a portion about the history of Microsoft -- the part paid-for 'journalists' (paid by Microsoft and Bill Gates) rarely or never speak about

  28. Hostility and Aggression Towards Staff That Does Not Use Windows After Windows Takes Entire Hospital Down

    Microsoft Windows, with NSA back doors, continues to take hospitals offline (with records copied by criminals if not stolen by effectively locking the originals out of reach for ransom money); but guess who’s being punished for it…

  29. They Came, They Saw, We Died...

    It cannot be overstated that we're under attack (or a "Jihad" against Linux as Bill Gates himself put it) and failing to act upon it will be costly as time may be running out and our groups are being 'bought off' by Microsoft in rapid succession, as per the plan/strategy

  30. The GitHub Takeover Was an Extension of Microsoft's War on GPL/Copyleft (Because Sharing Code to Anyone But Microsoft is 'Piracy')

    Licences that make it easier for Microsoft to 'steal' (or a lot harder for Free software to compete against proprietary software) are still being promoted by Microsoft; its GitHub tentacles (see GitHub's logo) further contribute to this agenda

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts