Well, engineers are supposed to learn how to solve problems that haven't been solved before by turning them into a problem that they can solve.
Engineering is the application of science to produce a product to provide a required capability (service).
It's not to "solve" a problem or turn something into a problem.
To put it into DoD terminology, the consumer sees the need for something. You can refer to that as maybe solving their problem.
But the engineer doesn't create a problem, they analyze the request and determine what the user is really asking for, i.e. we develop a set of requirements, that when met would result in the solution the consumer is looking for.
The second part of this is what differentiates engineers from scientists, scientists can look at things, components, and determine if there is something new that can be tried. New technologies, but the engineer isn't supposed to invent a new technology, but rather use the best technology available to address the requirement. In short, the engineer has to deal with the practical side, while the scientist can deal in theory.
There is no shame in not reinventing the wheel. In fact, for cost and time, it's often preferred that you not reinvent the wheel.
As for the "pricks", there is something to be said for experience. Learn from the mistakes of the past, don't repeat them. Principles of science don't change. Sometimes the prick is telling you, Been there, Done that, please look at these common mistakes first.
When it comes to software, the difference between and engineer and a programmer is not just semantics.
Again, engineers think in terms of what is required. Not what tools they currently have in the box.
Programmers are all about the tools in their box, they have their expertise and what you find is that is their preferred method to address every problem even if it doesn't meet the requirement. They define the solution before they actually define the requirements.
This is why we see so many problems with systems that are heavily dependent on software.
So I don't know how we got here, but in terms of the schools, my opinion is they are driven by
their IT department
Emphasis on their. This is a much broader issue. At some point the schools step into the commercial world for the broadband connectivity.
They are going through the same internet the rest of us use. Did they work with their ISP to ensure they had the resources upstream to handle the additional bandwidth. Moving from a bulletin board / simple file upload / download to a more complex interactive environment, with many more people trying to simultaneously use the resources isn't simple.