@prologic@twtxt.net Hmm, yeah, hmm, I’m not sure. 😅 It all appears very subjective to me. Is 2k lines of code a lot or not?

I mean, I’m all for reducing complexity. 😅 I just have a hard time defining it and arguing about it. What I call “too complex”, others might think of as “just fine”. 🤔

@movq@www.uninformativ.de well that depends on what this 2000 lines of coat does right does the 2000 lines of code basically amount to a linear set of instructions with no branching? Or is that 2000 lines of Covid include lots of conditional branching that make understanding what the program does, difficult and hard to maintain?

I feel like complexity is measured differently at different levels of a project..

• at the function level you use cyclomatic complexity or how many branches internally and how much you need to keep in mind as it calls out to other functions.
  
• at a file/module level is a balance of the module doing too much against being so granular that you have cross dependency across modules. I have trouble with keeping things dry at this level because it can lead to parts being so abstract or generalized that it adds complexity.
  
• at a project level i suppose its a matter of how coupled things are across sub-modules.

@xuu I think you’re onto something here. I tend to agree that there are different measures of complexity to apply to different things. The only downside I see here is we start to get into the realms of hierarchy and bureaucracy right, as a means to “simplify” the complexity, or abstract it away. I mean we tend to do this in software too, hide the complexity in an abstraction. The problem with this is this also becomes a measure of “complexity” too right and can potentially suffer from a point where it has become “too complex”.