Hey Nick,

If you're interested in more suggestions on making code human readable check out "Clean Code: A Handbook of Agile Software Craftsmanship" by Robert C. Martin (Uncle Bob). It has some really great advice for keeping code understandable and maintainable. Here's a few quotes on functions:

"The first rule of functions is that they should be small. The second rule of functions is that
they should be smaller than that."

"FUNCTIONS SHOULD DO ONE THING. THEY SHOULD DO IT WELL.
THEY SHOULD DO IT ONLY."

"So, another way to know that a function is doing more than “one thing” is if you can
extract another function from it with a name that is not merely a restatement of its implementation"

 

Hi Nick!

We might also add that most of the code written for one application should be in libraries that may be useful in building other applications.

Yes, it is possible! Although, unfortunately, this practice is unusual.

Greetings.

Al Gonzalez.

P.S. How do I change my avatar?

 

It depends.

Some software products should, while others should not.
If the software product, for instance, connects to the internet as part of its features(no, not updates ) then the installer should assume it, otherwise not.
Example of the former is a Facebook desktop client.
Example of the latter is a word processor.

Andrew

 

About 'Question of the day': Andrea Raimondi said exactly what I think about it.

I add that if it's updated frequently, you could include an update page on the installer asking to click a button if the user want to update it right now or at the first execution of the program.

 

Pingback from christian-rehn.de

www.christian-rehn.de   » Gefangen, nicht gefunden! #12