Answer the question
In order to leave comments, you need to log in
Is there a site where generally accepted programming practices are collected?
The bottom line is this: a person, after reading a textbook, begins to write something and only then accidentally finds out that it is customary to make a counter byte and not int. Or the user's gender in the database is not a string, but a boolean one. Or that it is necessary to compare not passwords during authorization, but hashes. Or when it's enough to sculpt methods and it's time to make inheritance. It's all here for the sake of example. Something like the advice of experienced fishermen, the nuances that Uncle Señor will tell a new june about, but about which they usually do not write in books. Like, for example, that a nail needs to be greased so that it enters hard wood more easily.
Answer the question
In order to leave comments, you need to log in
Naturally not, because everything you described is not some kind of secret knowledge that can only be remembered, but logical tricks that follow from knowledge of fundamental principles and analysis of product requirements. If you try to replace fundamental knowledge with such a collection of precedents, it will turn out to be gigantic and completely unsuitable for mastering - you simply cannot remember so much. The volume of fundamental knowledge is orders of magnitude less than the volume of details that are derived from them, but the complexity of this knowledge is higher. Whoever has not mastered the fundamental knowledge remains a shit coder until he masters it.
Such a site is years of practice, tons of rakes and love for your work.
Uploading to the brain, like Johnny the mnemonic, does not exist.
There is no such. All through conferences, articles and all that. How many projects - so many solutions
Hello.
If I understand the question correctly, then all this is called the word "specification". When a new version of the language comes out, for example, Microsoft releases the next version of c #, in which, say, the "$" operator appears, then along with this version of the language, a specification is also released - a recommendation on how to work with it correctly. Also in many (normal) companies there is a so-called code style, which usually consists of these very specifications and is filled with experience. It is in such documents that the rules are described, for example, in what order to declare variables, in what style different names should be written, if the class is inherited from IDisposable, then work with it only through using. Do not use First() if there should be one element in the database, but use Single(), for example, to edit one entity.
If you send me an email, I can send my document, which I stole from one good project. The banal implementation of the rules makes your code much clearer and more readable for other participants. But what can I say, before, when I looked at my code just six months ago, my eyes just ran out and I wanted to rewrite everything. This won't happen again.)
Do you need a site where ALL the life experience of a person is collected?
It is impossible in such a statement of the problem.
Let's say a couple of dozen patterns in one article - yes, it's possible.
Sites like Habr or StackOverflow - yes, it is possible.
But the way you put it, no.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question