> 1960s: "COBOL will let non-programmers make the software!" > 1980s: "4GLs will let non-programmers make the software!" > 2000s: "UML will let non-programmers make the software!" > 2020s: "AI will let non-programmers make the software!"
> I started work on Tcl when I returned from my sabbatical early in 1988, and I began using the first version of Tcl in a graphical text editor in the spring of 1988.
Crafty kid found a solution though: With Steam Link the screen can be mirrored on the tablet! So I can patiently find a replacement rather than rush out and buy one.
@lnxw48a1 One other thing that people forget/don't know is that most everything medical related can be traced back to the raw materials and everybody that was involved along the way.
A standard LHR (Lot History Record) from former $EMPLOYER for a "simple" part run of 100 parts could be 50-60 pages between all the tracking of "raw" materials (materials purchased for the product), incoming inspection reports for raw materials, who did what in the process's to get to the final part, who did in process inspections and who did final inspections, usually a sterilization report and final packaging inspection report, labeling report and final quality sign off. This is all before the product gets sent to the customer or distributor with a copy included as well as a pdf emailed. I have seen LHR's get up to 100-200 mb in size as a pdf for large lots of complex parts.
I am not saying this is an excuse for high prices but the $8 aspirin at the hospital has a long paper/history trail that is required to be kept.
@geniusmusing This brings something to mind. Two of my younger brothers (and zero of my older brothers) became the site "IT guy" at earlier employments because (in both cases) the real IT people worked at a different site and weren't willing to drive over and take care of problems.
I suspect there's a dividing line in which few people born before year X had this experience, but many people born after year X had this experience, but with no random and mass observation data, it is just a suspicion.
Not at all. After many years as being the "IT" guy for $EMPLOYER and the first question I would ask about an issue a user was having was "Have you rebooted?", many of the calls/emails I would get about an issue with their computer would start with "I have an issue and I just rebooted and it is still there".
As we replace more and more software creation use cases with tooling, it's possible that we at some time reach some turning point where software developers would be less sought for, but I don't see it any time soon.
ChatGTP and Copilot are not it. The unreliable output we have seen from ChatGTP and Copilot are not indicators that they are generic tools that can replace hand-crafted tools for specific programming scenarios. We can't leave them unsupervised any time soon. You'll need an expert to check their work, even if that expert might (or might not) be faster with the large language model assisting.
Relevant comic (I made a repost with image caption, will find):
♲ @nixCraft@mastodon.social: ChatGTP and coding problem 😅