| ▲ | DoctorOetker 2 days ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Precisely, cars are more-or-less identical copies, at each position along the assembly line its just one of a handful of variants of the step that needs to be executed. Software is less like an assembly line and more like plumbing: Some people design which type of pipe needs to be routed from here to there. The implementor actually pipes the outputs of one function, in a variable, and then taps it off as an argument to another function. Software development is like plumbing really, so a good manager of a pipeworks and plumbing company might actually make a good manager for software companies as well. This is also why its actually not so surprising that LLM's are mastering programming skills, it's essentially just being a plumber, and a lot of people are happy they no longer need to be a plumber. Physicists, engineers, scientists, ... they have much more complicated tasks compared to plumbers, programmers and code monkeys. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | AlotOfReading 2 days ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An assembly line is plumbing too. And just like software, while there are a finite number of variants at any specific time, the plumbing is constantly being rearranged for various reasons. A line won't look the same in 6 months as it does today. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | palmotea 2 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> Software development is like plumbing really, so a good manager of a pipeworks and plumbing company might actually make a good manager for software companies as well. No, wrong again. Some software development tasks are like plumbing, but that misses a lot. Your claim in sort of like saying since the Wendelstein_7-X has wiring, the manager an electrical contractor would be good to lead that project. Plumbers and electricians more or less solve the same problems over and over with slightly different parameters, and because of the repetitiveness, they can do a good job by following (a hefty number) of rules of thumb (the building code). A software developer isn't going to go far just throwing design patterns at a problem (though many bad ones try). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | QuercusMax 2 days ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The plumber who has a robot who can make perfectly measured custom one-off tools and specially constructed piping runs inside your walls is going to have super powers compared to somebody who has to go to home depot and assemble a bunch of PVC pipes or whatever. Just the other day I needed to make a calibration interface for a home automation app (pointing a dumb webcam at my washer and dryer so I can tell if they're done without running up and down two flights or stairs). I just wanted to be able to look at the whole scene and manually pick the ROI to extract and display on my home dashboard. So I asked the AI to build me a stupid little web UI where I can just click to select the ROI center, and what it built me in 10 seconds was perfect for my needs. Was it pretty? Not really. Was it what I would have built myself? Not quite - but it solved the problem I had without me needing to remember or look up how to do all the specifics. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||