Welcome to Technology Decisions, LLC

"Dr Phil of Technology"

There is no substitute for experience, formal & disciplined preparation & execution.

Technology Decisions, LLC specializes in the strategic planning, understanding, and the tactical bottom line benefits of technology to the enterprise for senior executives. 

We have practiced network design, security, management and performance optimization for over twenty-five years. 

Our principal, Matthew McCormick, has served as an expert witness on domestic and international patent infringement cases. His opinions have been sought out by major investment houses and consulting firms.  

We bring common sense analysis and solutions to business problems and efficiency.  Never endorsing technology for technology's sake, rather listening carefully to your business challenges, and only recommending and applying the right technology as and in a best practice way if it is the right tool for you at this time, bringing long term benefits.

"What you don't do nice..."

Too many networks are poorly designed, understood, underperform, managed, costing too much, and ultimately, failing to deliver service.  It's inevitable, if not done correctly.


The right way, the first time...

If you want it done right the first time, saving you time, pain, and money, hire us.

We have a problem w/the truth & questions....

We LIKE them TOO much!!!

CV

Click on a file to download.

What is cloud computing?

Click on a file to download.

Professional thoughts...

Big Data is dead.  Collecting a lot of data is literally useless, if the data is not properly utilized. The key is the systematic exploration of the data with a right set of questions. For instance, is the data uniform or irregular? Is there a significant amount of variation in the data set? Is it buried in a mass of other irrelevant information? Can it be easily extracted and transformed? Is it possible to load the data at a reasonable speed? Can it be thoroughly analyzed? Can powerful insights be garnered? Otherwise, Big Data alone in an old style is really obsolete.

DevOps is dead.

"IBM's Mustafa Kapadia says. "We needed to answer some basic questions and determine the problems we were trying to solve. That's where we failed," he said. "If you don't know how the work is actually done, you don't know which problems are worth solving. We were grasping at [imaginary] problems that came from vendor hype, not from seeing what was really slowing us down.""


"Too much accessibility -- not enough education...The second takeaway is to better educate developers on the workings of infrastructure. "Many of them have never been exposed to production infrastructure," Slideshare's Sylvain Kalache says. "Devops is based on a way of working, which obviously is more about human interaction. You can't expect everyone to naturally know ‘the hidden rules.' That's why onboarding is mandatory and critical.""


"A few weeks back, we had what amounted to a total system outage due to a hole in the monitoring," Nathaniel Rowe says. "A necessary third-party validation service had a network outage that brought their entire infrastructure down."


This shouldn't have been a problem, Rowe says. But due to the initial subpar construction of the software -- which was offshored for a bargain rate -- all the lease submissions processes were tightly linked to the service that went down. "In a company like this, that means the money stops flowing," he says.


""Unfortunately, devops cannot be implemented strictly with tools alone," he warns. "Devops requires equal attention to people or culture, process, and tools"....However, the agency largely ignored the people and process portion of devops, and failed to gain the buy-in from developers and other stakeholders that was needed to build a devops strategy that would actually be put to use.


"This meant that though we had a ‘devops platform' in place, it was effectively used to support the same old legacy practices," Dawson says. "Developers deferred commits, merges, and integration; automated QA [quality assurance] and release were never fully implemented; broken builds were no big deal, and production loads in production-like environments were never tested."

When the client released the web application it immediately experienced critical and very public failures, as it hadn't been regularly tested in a production environment or by real users. In addition, once the problems became apparent, it took the agency multiple, multi-week development cycles to fix the issues and get the site operational. The slow response times served to exaggerate the impact of the initial failures."


http://www.infoworld.com/article/3087447/devops/real-world-devops-failures-and-how-to-avoid-them.html


Data Science Nonsense

Click on a file to download.

KPMG:  60% of CEOs do not trust the conclusions from their data analytics.

IT Guy Becomes a Player

Click on a file to download.

Why Agile & Scrum are terrible

Click on a file to download.

More Professional Thoughts....

Our maxims:

Computers can just make dumb happen faster.

Wrong is not a service we offer.

Our Code of Ethics

  Technology Decisions, LLC abides by the following Code of Ethics, which we take most seriously:   

Professional responsibility of fair dealing toward the our clients, past and present, and the general public.  

Professional responsibility of adhering to generally accepted standards of accuracy, truth, and good taste at all times.  

Never to represent conflicting or competing interests, nor shall we be placed in a position where our interest is, or may be, in conflict with duty to the client.  

Safeguard the confidences of both present and former clients, and shall not accept retainers which may involve the disclosure or use of these confidences to the disadvantage or prejudice of such clients.  

Never intentionally disseminate false or misleading information, and we obligate ourselves to use as much care as is humanly possible to avoid dissemination of false or misleading information.  

Never intentionally or recklessly injure the professional reputation of others. 

In performing services for a client, never accept fees, commissions, or any other valuable consideration in connection with those services from anyone other than the client.  

Prior to the commencement of the services to be performed, make the client fully aware of the fee structure, and all associated costs.  

Never be in conflict by retaining ownership in any company selling or leasing products where such interest constitutes a conflict of interest.  

As soon as possible, sever the relationship with any organization when we know or should know that continued employment would require us to conduct ourselves contrary to the good conduct principles of this code.