3 ms·
Basically nothing here is specific to software. You can talk about a piece of writing exactly the same way. Even the part about patching; lots of books have r
by Dylan16807 2y ago
Basically nothing here is specific to software. You can talk about a piece of writing exactly the same way. Even the part about patching; lots of books have revisions.
I don't really see the point of focusing on software in particular before answering the general question. It's not being used to bring any special insight, and to my eye it's a false narrowing that makes it harder to answer.
> What this means of course is that programs are eternal unchanging things. We don't create programs as much as discover them.
This is a hell of a claim to pull out of nowhere.
I disagree that sentence 1 implies sentence 2.
And calling it a "fact" in the next sentence is bold!
- namaria 2y agoI feel like this is a rehash of the very old conversation "what is math? is it invented or discovered". Note to the author: repeating trivial questions isn't the same as asking deeper questions.
- Koshkin 2y agoIn physics research, things are discovered. In engineering, things are (mostly) invented. Mathematics can be thought of as a combination of those. There are “physical” parts (think of facts of Euclidean geometry) and “engineering” parts (e.g. proofs).
- Dylan16807 2y agoI think that's a legitimate question with math, but not for highly creative/subjective works. And software overwhelmingly goes in the latter category.
- guappa 2y agoUh? Math is highly creative. Probably not school algebra, but what mathematicians do.
- Terr_ 2y agoPerhaps a softer but less-brittle version of this might be: 1. It is possible to define "programs" as an immutable abstraction, much like how "123+456" exists even if I decide not to do the calculation. In this view, we don't mutate our programs so much as we pick a different one to execute instead. 2. We create formal programs in code in response to discovering informal "programs" implemented in people.
- Dylan16807 2y agoNumber 1 is just a library of babel argument. Every sentence that could ever exist can be enumerated in a giant list. That doesn't mean that creation ceases to exist and everything is actually discovery. Number 2 seems overly dismissive of the work of crafting the informal version.
- Terr_ 2y ago> > in response to discovering > overly dismissive of the work of crafting the informal version I disagree, if anything it's the opposite and "we made new program X in-response-to existing process Y" is downright meek. It never suggests that anyone is capable of fully replicating or even understanding Y, nor does it say X is even good enough to partially replace it... it's simply why they started a project.
- schiffern 2y ago>Basically nothing here is specific to software. You can talk about a piece of writing exactly the same way. Even the part about patching; lots of books have revisions. >I don't really see the point of focusing on software in particular before answering the general question. It's not being used to bring any special insight, and to my eye it's a false narrowing that makes it harder to answer. I agree with the substance of this remark (the OP is indeed a general information-theoretic observation), except for the part where it's framed as a negative value judgement against the initial work. It seems like this feedback could be trivially recopywritten in a way that elevates, rather than denigrates. -- One thing that would seem to bear mentioning is that software seems to be highly compressible. Indeed, good software seems better represented by the path, rather than the current state. An analogy here would be chess, where a state can be represented by the sequence of moves or the current board state. The analogy isn't perfect, eg since in chess the board state tends to reduce information over time. I would expect, for software, when the (dead-end pruned) sequence representation exceeds the information content of the current 'board' state, that's when you know it's time for a refactor.
- Dylan16807 2y agoHow do you turn "you are coming at this from the wrong angle and that's causing problems" into praise? If you cut my comment down to "This touches on fundamental philosophy." you could turn it into minor praise but you'd have to throw out the rest.
- schiffern 2y ago>How do you turn "you are coming at this from the wrong angle and that's causing problems" into praise? By eliminating those judgement words "wrong" and "problem," of course. ;-) A more positive-focused process might be, "that's an interesting perspective, and here's a generalization that might unlock new avenues for thinking further." Anyway, see my edit above where I offer an elaboration on your (IMO excellent) observation.
- kortilla 2y ago