“Do you know what?” Or Stackoverflow, on the contrary

Currently, there are already resources on the Internet where you can talk about your problem and get a solution to it with high probability, however, sometimes, having found a solution to a complex issue, I want to share it with others . One of the practiced options was to create a stackflowflow question and answer it yourself.

There are well-known resources on the Internet dedicated to bad code, very bad code . Their reading certainly raises self-esteem and mood, but very little implies professionalism and level of knowledge.

Personally, I really did not have enough resources where I can neatly fold the “particles of gold” sown from the pile of the very thing that was mentioned several lines above. You can say: “Well, get yourself a blog.” What for? Why would I store notes for myself? As if this is a map with the location of the Grail. I want to share what I learned, and I also want to learn something new from you, from my colleagues and completely strangers to me.
')
Thus, I bring to your attention my new project “And you mean what?”: Doyouknowthat.ru .



As for this site, I am a rather impatient person and not able to lick a month for a project that actually did for myself. In general, I must say that I took this site, like trackmypost.ru two years ago, quite spontaneously, on a day off, and by the evening I performed exactly 80% of the planned functionality. Another week a couple of hours a day was spent on decorations, ryushechki, buttons and everything else.

I want to say to all developers who read this message: share information and always write logs . These are the 2 key things the developer must follow. For me, it is always funny when programmers sit next to each other and talk about everything except programming, of course, they talk about coding, but at the level of solving current problems. Everyone seems afraid to seem stupid, saying: “Guys, I recognized a cool chip in mongo / php / redis / python / c ++ ...” because it may turn out that for everyone this “chip” is a truth read 7 years ago in paper tutorial. Tell each other what you learn, knowledge is not gold, they cannot be lost, but it can and should be multiplied.

And about the logs: always parallel development, log your code, everywhere, and obvious and potentially problematic places. Writing tests is cool, but the simplest and most accessible for everyone is the logs. Do this:

DEBUG && Log('...'); 

and you can always enable / disable logs in one simple motion, you do not have to randomly enter echo, etc. Think over what parameters you need to log in and try to make a prefix tag for logs that are close in meaning, for example: USER_AUTH, CHAT_MESSAGE, SHOP_ORDER, thus using only tail and grep you with 99% probability of localizing the bug in the first minute of analysis.

For those who could read it to the end and eager to find out the technical details I inform:
nginx + php-fpm + mongodb
Exactly the kit that allows you to quickly throw a working project.

After authorization, and there OAuth to popular mailers and social networks, you will already be automatically subscribed to all service updates (facts and comments), i.e. totally subscribed to everything. This can be disabled in the profile settings and subscribe separately to tags (receipt of new facts on these tags) and facts (new comments on a specific fact).

New facts appear only after moderation, while I’m alone moderator, so please do not kick if you slow down a bit. Comments to the facts on the site will appear immediately, but the notification will be sent again, only after viewing the comment, so that you do not cuss the mat and other garbage.