Re: It's not dead.
yeah well at some point in the project it seemed that swiss cheese unmaintainable spaghetti code might actually kill the project (and I would have to find a different engineering gig). So the guy originally tasked with the device control side (me) ends up taking over the whole project so that it does not DIE (missing customer commitments is a good way to kill it, for sure). Had I been in on the design phase for the web interface I would have directed it AWAY from such things but "that guy" shmoozed everyone into believing he was competent and 'talked a good game' and *I* was busy making motors spin and lights blink (then writing my own 'test' web interface pages because the "real" ones were not even CLOSE to being done, and handing them off to the web guy with 'well here is what *I* did to test it' like a *HINT* but without being too blatant (i.e. presenting him as a FOOL to the boss and being insulting about it).
Something like that, anyway.
Small companies really cannot afford engineering projects to be killed by "THAT kind of web "developer".
This swiss cheese spaghetti code was written using 3 things that need to be avoided: 1) JQuery, 2) Google "materialize" (bloatware, monolithic) style sheets, and 3) obvious copy/pasta from stack overflow and various 3rd party "solutions". And, "circling back" to I.E., this sort of 'thing' first became possible around 1997, and I.E. was right at the forefront of it, with the beginnings of DOM, script, and dynamic HTML (for good or ill). But I.E. had VBScript and ActiveX, whereas the others did NOT. Fortunately, neither of those two things survived the test of time. UNfortunately the use of bloatware javascript libraries and (later on) style sheets has NOT gone away... (and has unfortunately been given a new HIGHLY OVERRATED term to describe it, 'Material Design')
Biting the hand that feeds IT
