Cognitive Load is what matters

1. cognitive-load

   1 33 12,518 8.7

   🧠 Cognitive load is what matters

   

   There's a chapter about mental models: https://github.com/zakirullin/cognitive-load?tab=readme-ov-f...

2. AppSignal

   www.appsignal.com sponsored

   AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.

   

3. aposd-vs-clean-code

   2 20 1,936 8.4

   A discussion between John Ousterhout and Robert Martin about differences between John's book "A Philosophy of Software Design" and Bob's book "Clean Code".

   

   I would also recommend A Philosophy of Software Design if you haven't read it, a very short and brilliant read with a similar approach.

   There is also a discussion between the author of Clean Code and APOSD:

   https://github.com/johnousterhout/aposd-vs-clean-code

4. gocyclo

   3 5 1,613 0.0 Go

   Calculate cyclomatic complexities of functions in Go source code.

   

   > Our coding standards require that functions have a fairly low cyclomatic complexity. The goal is to ensure that we never have a a function which is really hard to understand.

   https://github.com/fzipp/gocyclo

   > * We also require a properly descriptive header comment for each function and one of the main emphases in our code reviews is to evaluate the legibility and sensibility of each function signature very carefully. My thinking is the comment sort of describes "developer's intent" whereas the naming of everything in the signature should give you a strong indication of what the function really does.

   https://github.com/mgechev/revive

   > Now is this going to buy you good architecture for free, of course not.

   It's not architecture to tell people to comment on their functions.

   Also FTR, people confuse cyclomatic complexity for automagically making code confusing to the weirdest example I have ever had to deal with - a team had unilaterally decided that the 'else' keyword could never be used in code.

5. revive

   4 12 5,551 8.9 Go

   🔥 Fast, strict, configurable, extensible, and beautiful linter for Go

   

   > Our coding standards require that functions have a fairly low cyclomatic complexity. The goal is to ensure that we never have a a function which is really hard to understand.

   https://github.com/fzipp/gocyclo

   > * We also require a properly descriptive header comment for each function and one of the main emphases in our code reviews is to evaluate the legibility and sensibility of each function signature very carefully. My thinking is the comment sort of describes "developer's intent" whereas the naming of everything in the signature should give you a strong indication of what the function really does.

   https://github.com/mgechev/revive

   > Now is this going to buy you good architecture for free, of course not.

   It's not architecture to tell people to comment on their functions.

   Also FTR, people confuse cyclomatic complexity for automagically making code confusing to the weirdest example I have ever had to deal with - a team had unilaterally decided that the 'else' keyword could never be used in code.

6. rust

   5 3,000 119,545 10.0 Rust

   Empowering everyone to build reliable and efficient software.

   

   Visitors additionally allow you to decouple graph traversal from the processing. It is still needed even in the languages with pattern matching.

   There's also the question of exhaustiveness checking. With visitors, you can typically opt-in to either checking that you handle everything. Or use the default no-ops for anything that you're not interested in.

   So if you look at compilers for languages with pattern matching (e.g. Rust), you still see... visitors! E.g.: https://github.com/rust-lang/rust/blob/64a99db105f45ea330473...

7. SaaSHub

   www.saashub.com sponsored

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

Suggest a related project