Discussion on: How do you order your functions?

View post

Uncle Bob says we should order our functions by abstraction level and I've found that I like that approach best, as the code reads like a book.


function doSomething() {
    readInput()
    writeOutput()
}

function readInput() { 
   lowLevelImplementation()
}

function writeOutput() {}

function lowLevelImplementation() {
    ...
}

Aral Roca • Jul 26 '20

Yep! I like it. This is clear to read

Ben Halpern • Jul 27 '20

This is how I do things

Deepak Vishwakarma • Jul 27 '20

I really like what is suggested . It's one of the key concepts of functional programming too.

Pacharapol Withayasakpunt • Jul 27 '20 • Edited

About Uncle Bob, it seems that he is quite famous -- duckduckgo.com/?q=Uncle+Bob (the search engine suggested it correctly, without any programming-related keywords)

Konstantin Klima • Jul 27 '20

He is considered THE authority on clean code and best practices by a lot of developers and computer scientists and his books constantly appear on must-read lists for developers.
AFAIK, he is the one who originally put together the SOLID principle rules and is one of the creators of agile development.
I also love his writing style, very enjoyable to read ^^

𒎏Wii 🏳️‍⚧️ • Aug 6 '20

Yes, he even wrote one of the things in "97 Things Every Programmer Should KNow", which is probably the book title I throw around by far the most (It really is a gold mine though)

Etienne Burdet • Jul 27 '20

This is what suits the most to. It's much easier to read lower-order functions once you know where they will be called, while most of the time it's fairly easy to infer what they do by their name.

nilia1972 • Jul 27 '20

Yes, it is clear and simple.