Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 5
    Not a downvoter, but your analogy is a bit lost on me. Are you saying it's better to spread your code over multiple lines, and have less words on each line? Commented Apr 11, 2019 at 23:51
  • 1
    Spread code and helper over multiple lines and files as much as you can. Focus on readability. Don't throw 8 or 9 classes in a single file. It makes the code hard to read and harder to maintain. If you have a large condition code or loops. Turn them into utilities. Avoid heavy nesting. Please let me know if this helps explain it. Commented Apr 13, 2019 at 1:15
  • 1
    I used the script for Jackie Brown as a yardstick for modular z/OS COBOL programs. You know, for cocktail party banter... Commented Apr 30, 2019 at 6:11
  • 2
    It's all about perspective. Most solutions to real world problems are simple. As humans we tend to over complicate simple things. Most calculus is dirived from basic simple math analyzed in a different perspective. Commented May 24, 2019 at 0:07
  • 1
    @whatsisname There's a difference between something being impossible and something being a bad goal. Even though making sense to a 5 year old is rarely achievable, by adopting that goal to the greatest degree possible, the result tends to be far, far better than the result of not adopting the goal, even if the goal is never quite achieved Commented Aug 31, 2020 at 13:08