• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2025

help-circle



  • Cyclomatic complexity is like trying to measure complexity of a mathematical formula by the counting penstrokes. Don’t mistake a metric’s ease of measurement for its correctness, see: productivity vs lines of code.

    Every point under “Why?” is too optimistic about forced deconstructions being good, that all the small pieces will be cut along the right seams.

    Breaking up a messy scribble in the wrong places just leaves you with the same messy knot, now as a shuffled jigsaw puzzle.

    If the code is written for humans, then excercise human judgement and use a relaxed “complexity metric”. If the code is written for agents, then this metric matters even less. If forced to pick a number, I’d use something like 50+ to only alert on the truly excessive.








  • Absolutely silly premise. Continuing the author’s analogy, how would pacing oneself in one marathon improve performance in the race tomorrow? What about next week (a race of indeterminate length)? Or next month (turns out will be a triathlon, but you don’t know it yet)?

    It doesn’t, and the “races” that engineering teams run are more like those latter examples than they are like performance during a single marathon.


  • In the short term, a small amount of duplication to prevent bad abstraction spaghetti is worth it

    In the medium term, true duplications are better extracted after the fact rather than correctly guessing future reusability.

    In the long term, total extraction into separate vertical or external package, as suggested by the author.

    Over time, this progression is natural and unforced. If you don’t need an abstraction to be de-deuplicated, then don’t. If you don’t need to promote an abstraction into its own vertical/package, then don’t.



  • IMO in the same way everyone learns arithmetic but doesn’t necessarily go into mathematics or finance, I think everyone should learn basic logic and coding, enough to basically use spreadsheet formulas, which is a half step away functional programming. (I’m pretty sure Excel even supports named functions and lambdas)


  • Consider the shell itself to be “the IDE”

    Everything is interoperable, extensible, scriptable, and more. CLI tools are designed to run fast/instant, have keyboard shortcuts for everything, and be deeply customizable. The openness and variety cannot be overstated, Google “CLI file explorer” and you’ll easily find at least 10. Nobody has the same exact setup because it gets molded to match how your brain works. Go for popular tools, niche setups, or both.

    Graphical IDEs could also run fast/instant and have keyboard shortcuts for everything, but their users don’t demand it. If you wished the file explorer/git integration/debugger/etc worked a bit differently, there might be a plugin, if you’re lucky. Many operations can only be invoked manually via sequence of dialog boxes or mouse clicks or both.