Intuitively: (1) Excluding tests, software repositories should be LARGER in size than the artifacts they produce, or, (2) Excluding tests, software repositories should be SMALLER in size than the artifacts they produce.
-
-
You can include docs if you want since they tend not to have a significant impact on repo size.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
yeah there’s a lot collapsed here. a repo can produce related projects, books, careers, an entire community. even if you go super literal, the artifacts should be smaller if it’s embedded software and larger if you’re using code generation techniques
-
I wouldn't consider "a career" (or a book deal) to be an artifact of a software repository though. To be clear, the literal software CI pipeline sense.
-
ok, but even then, it’s kind of a very exact question paired with terms that could have multiple definitions. should like Trump should go to jail, or should like the train should arrive in the next ten to fifteen minutes?
-
if you can reduce the question to “is compilation more intuitive than code generation,” then compilation looks like an easy winner, but personally I find code generation more intuitive, and it again prompts questions as to what “intuitive” means here
-
but the question is not about code generation at all. It's literally file size and how we intuit input vs. output of data. Is the expectation of programming that we take <small data> to make <big data>, or do we take <big data> and chisel out <small data>? There's no 1 answer.
-
(that's why it's a poll)
End of conversation
New conversation -
-
-
Compiled? Debug? It's such a weird question.
-
The ones you ship.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.