> The entire world runs on SaaS tools which cannot / do not run locally.
Some of us have made different choices and therefore have different exposure to these kinds of failures. Yes, sometimes those choices mean higher costs or fewer features, but a lower probability of getting kneecapped by others' problems is a pretty good feature.
Engineering mostly isn't building either. AEs don't build the planes, they design them. EEs may prototype some boards, but as a profession it's also mostly design (intended for manufacture). Unless you're an EE working primarily on one-offs, and small ones at that, you don't build most of the products of your mind. MEs don't build the cars. CEs don't build the dams or bridges.
Engineering is principally a design discipline, with a small fraction actually doing the hands-on building of their designs at least once they hit a certain scale of manufacture or get past prototyping. Technicians, skilled and unskilled labor, and machines do the vast majority of the building of those designs.
The toolchain does the detailed design work too. The job is more like driving a train — engineering, if you will. The toolchain can do its thing, but it can go off the rails, so you still have to know when to hit the breaks.
I think the closer analog is developing schematics for circuitry, where one might design in terms of existing ICs or adhere to a specification about input and output signals. Turning the schematic into a real device would then involve a host of processes, of varying degrees of automation.
In the case of software engineering, source code occupies roughly the same position as a schematic, with all the "production" completely automated and highly reproducible. Yes, the toolchain can make decisions about the emitted machine code, but we expect the output to be stable, in all consequential ways, for a given input and constant optimization settings. (Even in manufacturing, there is allowance for variation due to process, and untold money has been spent variously trying to exorcise or neutralize it. We have it easy.) Importantly, while no single person can know everything about the operation of modern toolchains, we know that there exist people with the education and the inclination to understand anything about them. Compilers and linkers and analyzers are not mysterious black boxes that defy investigation.
> In the case of software engineering, source code occupies roughly the same position as a schematic
That is a reasonable take, but software engineers don't work at such a low level. They start the agent and their job is to make sure that the agent doesn't go off the rails. It is like driving a train. Hence why we call them engineers.
Yes it is, brick layers in this analogy are those that are only coders.
Then we have the whole team of engineers, architects, solution architects, that lay down the work for the coders, more often than not, some offshoring team.
Please, stop with the building metaphors. Source code is a design document interpreted by a toolchain to produce the product people actually care about.
The inconvenience of implementing correct safety measures is part of the cost of undertaking certain activities. When an activity's ratio of cost versus benefit is too high, there's no way to juice the benefit, and the last place to cost-cut is in safety measures, the responsible thing is to refrain from the activity in the first place.
Suppose I do something myself. I reap all the benefits, but it takes a lot of
time, I may not have the expertise to do a good job, and I get all the blame if
something goes wrong.
Suppose I go to the park and find one of several guys who would do it for free.
I get all the of benefits, he might do an excellent job, but, because there's no
contract, I still take all the blame.
Suppose I actually hire a professional to do it. I receive fewer of the
benefits. However, he's much more likely to do a good job, and the legal system
provides a variety of ways to hold him accountable for the work.
Suppose I hire a professional, but then insist that he use legions of guys from
the park to do the actual work, since that's going to be some much faster and
cheaper per quantum of work. I also tell him that if he's unwilling to do that,
I'll find someone who will. I also tell him that, since he has so much more
unoccupied time now that the original work is in the hands of all those other dudes,
he gets to supervise still more work done by other swarms of guys from the park.
At this point it should be clear that I'm not interested in quality work, but in
having someone poised to absorb blame. I want a patsy.
Now replace "guys at the park" with LLMs, and replace "free" with "nearly free,
but with no warranty."
My phone is turned off for roughly half my waking hours. The remaining waking hours, I have access to a real computer, or I have reason to not touch a phone or computer at all. A smartphone would be pointless.
That's cute. Your records are yours. Barring some agreement to the contrary, I have no right to mess with them or inspect them, even if they contain information about me.
Some of us have made different choices and therefore have different exposure to these kinds of failures. Yes, sometimes those choices mean higher costs or fewer features, but a lower probability of getting kneecapped by others' problems is a pretty good feature.
Life is tradeoffs.
reply