Yes and no. Speaking of bridges, you are IMHO a bit too extreme, a "double strength" bridge is definitely bad-engineering. Over-engineering is (as an example)

Yes and no. Speaking of bridges, you are IMHO a bit too extreme, a "double strength" bridge is definitely bad-engineering. Over-engineering is (as an example) using a modified asphalt to pave the bridge (very good for adherence when raining and on cold, snowy places) in a warm climate country where it rarely rains, and never snows. The good old definition of (construction) engineering norms is (maybe was) revolving around representing the reasonable cost for the society of reasonable levels of "safety" and "convenience" (both rather difficult to establish BTW). When it comes to computing (and similar) the problem is often what I call the "because I can" syndrome, on the web there is an over-complication (maybe more accurate than over-engineering) on an increasing number of sites, which as an example if you have poor connection or not the latest OS and browser, reduce the number of visitors (or the quality of their experience) and this is the "under-engineering", as the site (while possibly offering a superb experience to someone accessing it with a given connection/Os/browser) will be inaccessible or only partially working to a not-so-trifling number of potential customers, so the site does not deliver fully what is supposed to, so maybe more accurately, it is over-complication that makes the result be under-performing.