4 ms·
... then before you know it your code-base is 10 million lines long and you have no idea where anything is, what the side-effects of calling X are, what's been
by louthy 4y ago
... then before you know it your code-base is 10 million lines long and you have no idea where anything is, what the side-effects of calling X are, what's been deprecated, onboarding is a nightmare, retention of staff is difficult, etc. You may be right for the smallest of applications, or whilst you're building an MVP, but if your application does anything substantial and has to live forever (a web app, for example), then you will have to get organised.
- worldsayshi 4y agoI think we are conflating (at least) two different issues here because we don't have a good way to deal with them separately. Closure on one hand and implicit logic on the other. Most of the time when I split out a method what I want is a closure that is clearly separated from the rest of the code. If I can have such closures, where input and output is clearly scoped, without defining a new method, that might be preferable. Lambdas could be one way to do it but they still inherit the surrounding closure so it's typically not as isolated as a method.
- louthy 4y ago> I think we are conflating (at least) two different issues For sure, I have absolutely no idea how your comment relates to what I wrote.
- worldsayshi 4y agoOops, it looks like I answered the wrong comment here. :/
- louthy 4y agoIt happens to the best of us! :)