4 ms·
which is really a good way to do it. you design it to be so many pounds, when you get it all together you should be there (or close to it).
by 9659 3y ago
which is really a good way to do it.
you design it to be so many pounds, when you get it all together you should be there (or close to it).
- conductr 3y agoYou start a project knowing how many LOC it will take? I want to assume you’re being sarcastic but it really doesn’t sound like it
- drekipus 3y agoIt's responding to the analogy.
- 9659 3y agonot knowing exactly, but with an estimate of the software size. sure. how else do you reliably estimate the projects cost and schedule. "engineering" not "programming"
- heyoni 3y agoDifficulty of the problem you’re trying to solve. Just like it could take 5 hours to come up with 5 lines of code, it could also take 5 minutes to produce another 5 lines. All depends on how complicated the task is.
- 9659 3y agoyep. and when you need to write 300K SLOC, the average takes care of the outliers.
- conductr 3y agoInteresting. I can estimate time by gauging complexity but LOC (for me) is usually not exactly correlated to time or complexity
- sokoloff 3y ago“This airplane design will be done much faster if we use lead and tungsten in key places.”
- riwsky 3y agoIf I had to name one design pattern that really helped my org’s codebase scale into the million LOC range, it would be replacing our database with in-repo json files.