5 ms·
A few unfortunate things about software development practice lately being mostly plugging together components: * People make huge things out of often poorly-ch
by neilv 4y ago
A few unfortunate things about software development practice lately being mostly plugging together components:
* People make huge things out of often poorly-chosen components and frameworks.
* People 'engineering' the system don't actually understand how it works.
* Much/most of your time is spent figuring out a pile of library/framework bureaucracy that someone else created. Not even useful concepts that you are smarter for learning, just figuring out some muddled version of an old model, the particular forms of made-up incantations around, and discovering and working around the shortcomings of their design and implementation. Often you find the thing you're using is actually poor design and implementation, and you might feel stupider for having learned its bureaucracy.
* This plugging together of components can be done well, and sometimes is, but it's also a little too convenient for developers who think software engineering is like turning in homework assignments in school. In which the goal is to get your homework (sprint task) past the grader (PR approved), and that's the end of it (what's analysis, planning, and architecture?). So you do Web searches of Stack Overflow (and maybe some Copilot open source laundering), to slap together some components, and no one even seems to expect you to know how it works. Where's the pressure to do software engineering?
* Perhaps some of the churn of these components is due not to technical/business merit, but to the fact that putting the latest possibly-rising component on your resume can improve your marketability in an employment environment oriented around frequent job-hopping. It's a symbiotic relationship between people who spit out "new" components to plug together, and people who twist projects to put the new thing on their resume.
That's not exhaustive; just a few off-the-cuff that are annoying this weekend. :)
- klodolph 4y ago> People 'engineering' the system don't actually understand how it works. The problem is that the complexity of systems is growing beyond the capacity for people to understand in the first place, and the solution is to make it possible to do meaningful work in systems where people only understand a part of it at a time. In a way, software engineering is catching up with the rest of the world, which already operates that way. When you build a skyscraper or a bridge, maybe you have a structural engineer who understands how concrete and steel work, and you have a geotechnical engineer who understands how soil and sand work. My personal observation is that programming has long attracted people who like the kind of absolute certainty that you can have in smaller programs, where the behavior of programs is known to a mathematical certainty. If you're careful, you can build larger and larger programs this way... but at some point, the program or system is too large, and you are forced to think about things in statistical terms. You have to accept that your program has bugs in it. Some people who are otherwise brilliant programmers are simply too uncomfortable with the jump from the certainty you have in small programs to the known uncertainty you have in large programs & systems. It used to be you could make a decent living working within the certainty of small programs, but nowadays you are going to have to plug things together.
- zozbot234 4y agoProgramming in the large does not necessarily involve uncertainty. A CPU microarchitecture or an OS are large, complex systems, but we expect them to perform reliably. Well-understood modularity boundaries are of course quite important for this. It's only when we expect systems to do things that they weren't designed for at the outset (such as keeping private data from being accessed via side-channels, if you're designing a modern CPU) that real problems exist.
- klodolph 4y ago> Programming in the large does not necessarily involve uncertainty. Can you provide some reasoning to support this, or elaborate? This seems obviously false to me, maybe I don't understand what you're trying to say here. When we have goals like wanting to keep private data from being accessed via side-channels, there are some major problems preventing you from being certain about it. You are probably not going to be certain that you know which data is private and which data is not private. You are probably not going to be able to enumerate all possible side-channels--new ones keep getting discovered. Then, suppose you've found a way to mathematically express what data is private and what side channels are and what it means to leak data, do you expect to somehow apply formal methods to the entire damn system? Maybe someday. Not today. Today, you apply defense-in-depth strategies. Mitigations upon mitigations upon mitigations. You try to keep any one bug from bringing down the whole system. You do analyses of different types of bugs and see how they affected the system, and figure out ways to make the system more resilient.
- inimino 4y agoThere is a radical idea discovered in the 70s, that you can just buy computers and run your own code on your own machines. Rumour has it that some still practice this ancient art.
- klodolph 4y agoIf you're happy with the experience of using computers in the 1970s and 1980s, you are of course free to continue using computers that way. Meanwhile, all the people who want to build a "quick web app" are building on top of an enormous tech stack which they don't understand. Your application will be affected by everything from the way that your TCP packets get routed around the world, to the arcane rules which your browser uses to decide when to repaint the page, to the byzantine rules for text segmentation and script-specific shaping engines used to let end-users interact with "plain text" content.
- sirsinsalot 4y agoI think this is, and bare with me, because of the infiltration of radical individualism since the 1960s. Donald Trump can fake his way to president, anyone can build a SaaS and fake their way to money with a loose collection of APIs. Hustle culture outweighs solid fundamentals and rigor. Superficial, yet effective. Lacking rigor but marketable. Become a developer in 4 weeks (seen lots of that on YouTube). Go to a boot camp and learn Javascript. Fake it until you don't need to make it. Don't learn about weights and activation, just load it off HuggingFace and make an amazing landing page that ignores accuracy. It's not a world where SICP fits. This makes me sad.
- lgas 4y agoI don't know... LLMs are just functions from text to text. Seems like the same skillset is still valuable. You just have more amazing functions at your disposal.
- hgsgm 4y agoSICP was cancelled 15 years ago near when Obama was elected. The people who build the powerful functional apps you use every day are nothing like Donald Trump.
- sirsinsalot 4y agoYou totally missed the point
- kilgnad 4y ago>* People 'engineering' the system don't actually understand how it works. This is not unfortunate. This is literally the only way to manage complexity. You cannot hope to understand everything. I think the course in its old form is good. But what sussman says is legit. Software engineering is now more of a scientific exercise of testing existing structures then it is an axiomatic construction from primitives. In fact this is how ALL of society works. Specialists each construct their own universe and nobody truly understands everything as a whole.
- thfuran 4y agoWell, theoretically one could instead expand the engineers' capacity for understanding, but that seems to be harder.
- kilgnad 4y agoWhat do you mean expand? All brains have a upper limit in memory and capacity to understand things. If you exceed this limit, there's nothing that can be done short of science fiction cybernetic brain augmentation.
- inimino 4y agoDo you think that, as an industry, we're in danger of hitting this theoretical limit?
- kilgnad 4y agoIn danger? We already hit the limit, and we're waay past it. Tons of software we produce is so complex it already has no hope of being fully understood by one man. Look at the operating system you're using to read this! It's not even a software thing. Society itself is segmented into specialists. Carpenters specialize in wood, they don't need to understand blacksmiths and vice versa for blacksmiths. Why did society segment itself this way? Because the body of knowledge and skills of each trade is so complex that few can fully master more then a single trade.... This occurs simply because our brains aren't smart enough.
- jameshart 4y agoI hear this kind of complaint a lot, but in general it seems to be railing against a strawman. Which systems, specifically, do you see being built in these ways?
- deleted 4y ago[deleted]