
Hello! Today's review of the sandbox is unusual! And it is unusual in that me and the
kriptomen decided to write it together!
Over the past week we have gone through a lot of articles, and it’s hard to believe that people can write about such different topics and are not always compact. We tried to make this review really a review, somewhere with minuses, somewhere with recommendations. Please forgive us for a fair amount of sarcasm regarding some articles. Sometimes it's hard to resist. In the article, where required, the initials P - Roman (s), and A - Anton (
kriptomen ) are
indicated .
In general, we hope you enjoy it!
Algorithms
The author of the article invents a long arithmetic and gives an example of student laboratory programming.
Unfortunately, it looks that way.
R: author, do not allocate 10 megabytes per stack for one array.
A: i nikogda ne pishi transliton v kode. NIKOGDA!

The author, rushing off the bat, proposes to understand the algorithm for finding the smallest common divisor (GCD). A formalized description of the algorithm (very brainwashing, for my taste) and the implementation of the algorithm in different PL are given.
')
It is not entirely clear what the author wanted to say, the article could be replaced with a maximum of three links:
ru.wikipedia.org/wiki/Euglide_Algorithm_– a detailed description of the Euclidean algorithm
ru.wikipedia.org/wiki/Algorithm#.D0.9F.D1.80.D0.B8.D0.BC.D0.B5.D1.80 - write the algorithm in pseudocode in recursive version
ru.wikibooks.org/wiki/Example_execution_Algorithms_Euclidean - implementation of the algorithm in different PL
The author could describe in more detail the application of the algorithm, examples of its actual use.
Development
A: A bit of necromancy - an overview of a web application for creating applications for S40-based phones (Nokia Asha in particular). The article can learn how to know the rss address to create your application. In my opinion, about anything.
R: Quite a strange step on the part of Nokia, to launch a competition on such devices. Give Africa cheap mobile phones!
It is a decent article, in my opinion a worthy invite. The author gives an example of working with GitUm, a tool that facilitates working with git-repositories. Briefly and in the case.
A bit of code for Smarty from home bins. Quite classic tasks - the conclusion of the announcement and the conclusion of the correct endings of words. The author does not hide that the code of 2009, but still decided to share it. No, well, what if.
A: I think an invite almost to Habr for the article is provided. The author, the counterfeiter will not leave you, invite to png, size 24x24px
R: Already there were several articles how to generate pictures like invite to Habr
Automation
Guide for those who do not know how to use Google.
It is useful as an extended version of this guide.
developer.android.com/tools/building/building-cmdline.htmlI advise the author to also describe the “not for the lazy” method, or how to create the build.xml file via the console (terminal).
In general, the article was useful to me. But I am afraid that it can be comprehended by cons, like this article
habrahabr.ru/post/174425A useful article on how to perform SQL database queries with a “package” that differs from a transaction in higher performance in Java using JDBC.
I advise the author to make the code tag <source>, and not <code>. The author also made a grammatically incorrect title, I advise you to correct
The article is brief, background, specific.
Iron

R: The author makes a review of headphones whose model is listed in the title. Inserted specification and those. characteristics of the microphone (I do not know why, apparently, to increase the amount of text). (I would like to note that it was decorated ugly, without formatting. It’s worth paying attention to how reviews are written by experienced authors)
A: The review does not stand out as something special, the author's opinion is strongly condensed.
In principle, if you work on the design of the article (subtitles, text selection), then you can publish. But it’s too dry, I think. I would like to note the presence of spelling errors "Chinese prodovtsov." Even the browser stresses such errors, it seems to me in the review that is unacceptable (I hope we don’t have such errors).

R: A fascinating article, after which you ask yourself the question: “Is that all? Anything science is capable of striding by leaps and bounds? ”.
Of course, dry, but for the first article is quite suitable.
I would like to ask the author to correct the “memory effect” on the “memory effect” in several places and other minor errors (“cause the battery to burn” - “cause the battery to burn”).
A: And since the article is a compilation of information from other sources, it would be good to refer to the sources.
A call to notify about the past days and read about the Game Boy Pocket and see the analysis. I didn’t dream of such a thing in my childhood, for example, I didn’t even know about him, but even though it’s not the good old Dendy, it causes a smile (still, the first photo shows my favorite Mario and Castlevania running on the devices)

and see the review is quite interesting.
Another interesting fact is that 2 devices take part in the review: one of the Japanese, the second of the Chinese assembly - the devices are absolutely identical in appearance and quality of assembly / materials, and the devices themselves, despite their considerable age of 17 years, are well preserved.
Electronics, DIY
The article is more like:
1) the flow of thoughts electronic engineer
2) on a very big post for Q & A
The article is replete with abbreviations, technical terms. The article poses a problem, and does not solve it, but only creates questions. I would recommend the author with his problem to apply to the specialized electronics forum, and not to start the article with the words “Greetings to the community! We need the first post, “pretending to invite,” so it will be about what my head is crammed with. "

Another article on electronics. Read the article in one breath. Very intriguing, I would give an invite just to read the sequel.
Written in clear language, abbreviations are decrypted, the scheme is attached. In the article, the author briefly describes what an SDR system is, how, theoretically, it can be built, who uses it and for how long. The author also promises a series of articles on SDR systems.
Remarks:
1) fix “nhflbwbjyysvb” to “traditional”;
2) the article has only one subtitle, so it can be combined with the text, highlighting it in bold.
Collected the home server - write on Habr! The author apparently doubted for 2.5 years - whether to follow this rule, but in the end he decided. Seriously, I like such articles, and for a long time I have wanted to collect and hoist servacheks on the cabinet, but here ... The author was not too lazy to write the name of the flash card on which he transferred the system, but for some reason decided to conceal the name of the motherboard, and only lay it out picture. Not a final configuration, nor any interesting software solutions. There is not even a photo with a cat on a server.
Quote:
The topic was written in the workplace, for this lay out the pictures do not work.
No, well, I waited for 2.5 years, and here I had to write an article urgently at work! :)
Let's talk for life
“And let's see!” (In the voice of Grishkovets)
A rather sharp article in defense of the author of a recent article from the sandbox “Is it possible to travel in time” (the author has removed the article).
The article is a response to a recent post -
“How two weeks ?!” and comments on it. The author shows his vision of the implementation of a fuzzyly described TK from a customer who is not well versed in the web (in particular) technologies (“TK mortal”):
The customer wants to improve his site by adding a certain functionality, he knows what should come out in the end, but he doesn’t know how to describe it in the TK, he doesn’t know the pitfalls of development.
On the other hand, the performer, seeing a simple at first glance TK, is taken to execute it “in an hour,” and makes it clumsy as it is written.
We read - "who is to blame" and "what to do." Drama, gentlemen :)

God, what did I just read? Looks like a pseudoscientific fantasy on the topic ... on the topic of what? Unclear. Either I am tired today, or the author is a professional copywriter who earns money by composing texts from scientific terms. And it turns out whether he convincingly, or so-so.
A small excursion into the classifiers (methods for presenting custom ads by class, systematized). I hope the author did not steal it from anywhere, and did not copy it from another resource, because ...
In general, for me personally, the article seemed boring. It is not clear whether the author proposes to throw all the start-up forces into the category, or says that the market is already drunk, so you should know that there are such things.
The author did not lie, and really spoke a few words about the principles of design. I would like more. Less water, more principles. Author, let's more principles!
So far, not enough, and does not pull on a full article.
Failed articles
An article is not an article. After reading, I would like to say: “Thank you, Captain Obvious”. And yes, kep, why do you need a flash drive? I think most of the problems you could avoid using DropBox.
O God, Microsoft, help a man! Such a cry of the soul can not be left unnoticed. Why he can not write down the number of the machine in Outlook? What the ..?!
Although the article and, I will not hide, about anything, there is something to ponder. How often are products tested for similar problems? In particular, corporate decisions. And how often the products are written with the thoughts “well, it works here, it means everything is in order”.
quote: Pentest - imitation of real attackers (crackers, hackers, etc.)
And again the article is the answer. This time, based on “Myths of our time: genetically modified organisms. Is the devil so terrible?”. I would like to note that the original article was quite clearly argued, it’s more like a stuffing in order to discuss the Evil Corporation.
No offense to everyone, but sometimes it seems to me that Habr will turn from day to day into a community of gardeners who are fond of space (I myself really like this topic) and occasionally program in Excel.
What the hell? :) The article is clearly not for Habr, although it may deserve 3 minutes to read it.
Habr is not for esoteric.
the end
This is our review. Perhaps we missed a couple of articles (laziness or inattention? Somewhere in the middle). But in general, they tried to give an objective picture of the sandbox: the authors want to use Habr, and it does not matter in what ways.
The following is a list of articles in reverse chronological order.