Re:Response to “Literate programming considered harmful”
by andy_ppp on Wednesday August 31, 2016 @08:57AM
(#12397934)
My new checklist for making programs easy to understand and work with in the future.
- Make the program in complete slices of a functionality and put those into folders and files that are descriptive of what the code does: "web/login/facebook/always_ask_for_email.lang"
- Do repeat yourself in different functionality areas.
- Name your variables and functions as if they should never conflict/as specifically as you dare.
- Use a functional and immutable programming language or write pure functions as much as possible.
- Stop thinking that patterns are necessary to solve the problem of turning data from one form into another.
- Make the program in complete slices of a functionality and put those into folders and files that are descriptive of what the code does: "web/login/facebook/always_ask_for_email.lang"
- Do repeat yourself in different functionality areas.
- Name your variables and functions as if they should never conflict/as specifically as you dare.
- Use a functional and immutable programming language or write pure functions as much as possible.
- Stop thinking that patterns are necessary to solve the problem of turning data from one form into another.
I might be wrong.