As we go along with the years, information and even old articles have remained, perhaps giving deprecated information, this seems to me a risk, you are not always careful about the date of what you read, but it can also be that it is valid, and can be confusing.
What do you think about it? Or do you know any site that publishes articles (in the field of software development / data science), which has the courage to delete its own old articles because it considers deprecated or modifying them properly?
An example can be courses about windows form

--

--

I’m thinking about this conventions, tell me what you think about that:

  1. Use LBYL when you can, EAFP when you must.
  2. In every function you can throw exceptions in order to explicit software bugs.
  3. Error labels in the user interface only to explicit user errors, included in the software working domain.
  4. One or some optional very big try catch in order to save log data, and then crash.
  5. Logs must be divided in two types: standard logs, and warning logs. (software errors are explicited only from exceptions)

--

--

Do not write:

func () {
if (something)
return true;
return false;
}

Instead write:

func () {
if (something)
return true;
else
return false;
}

Do not write:

func () {
while (somehing)
if (somethingelse)
break;
}

Instead write:

func () {
while (somehing)
if (somethingelse)
return;
}

These are my current best practices, what do you think?

--

--

Lorenzo Tinfena

Lorenzo Tinfena

Computer science student - Artificial intelligence enthusiast. https://github.com/lorenzotinfena