Eliminate spaces, learn Android

It's not about the gaps in knowledge, but more on that later.

By old habit, I still read books on paper programming. In particular, about the development for Android. Several years ago, with the literature on this subject on the great and mighty was intense. Now the situation has improved a little. I bought and read, probably, 99% of all released books. There are two problems with books. The first is that they are of the same type in their mass and tell about the same thing. The second problem is a significant delay in the release of the publication. As a rule, the delay occurs on version 1-2, which is quite critical. For example, when versions of Android 3.0 and 4.0 appeared with fragments, reading examples of creating applications for Android 2.3 was stupid.

Back in 2011, the Android book came out in 24 hours , which, in my opinion, was one of the best. I liked the approach to the disclosure of the topic - one was taken through the project and gradually became more complicated from hour to hour. Along the way, explained the fundamental things on one project. It was clear where and when to apply these or other opportunities.
Last week, I accidentally stumbled upon a message on the Internet that a new edition had appeared with a longer title Creating Android Applications in 24 hours with the same authors. And immediately drank bought.

When buying, I was a little embarrassed that there was an inscription on the cover of the 3rd edition . Apparently, the countdown comes from foreign publications. Okay, let's not quibble.
')
This time, the authors abandoned the previous approach and began to write like everyone else. One hour, one topic, one project. Then everything is new. In the middle of the book, they temporarily returned to the old way, when for 4 lessons they explained new topics using the example of one project.

Began to read. Already by the fortieth page there were two typos:



Gone are the days when it was possible to put a "party card on the table for the same." I talked to people who worked in publishing during the Soviet era and I know this firsthand. Now you won't surprise anyone with misprints, and in computer literature they have met very often.
But further my amazement grew more and more.
My eyes were presented with a sentence written without a single space. Immediately I remembered school German, where long words were not uncommon:



If you think that there was an accident, then you have another example:



In fact, the lack of spaces occurs constantly. As if someone decided to save on paper and save the forest. Sometimes, the proposal lacks one space, sometimes two. Sometimes they do not exist as a class.



Let's leave the gaps alone for now. Refer to the code. By the way, the font for the code I did not like, some kind of narrow and not too readable. But I'm not a type designer, maybe I do not understand something.

We look at this code:



How do you? Two variables with the same name are practically near. And the principle of the name of one character? What a sin to conceal, I myself wrote about fifteen years ago in Visual Basic in the same style for myself. Now this approach is justified, probably, only in js-libraries to reduce the size.

Then the authors corrected and began to give the buttons more meaningful names. But horseradish radish is not sweeter.



In my opinion, in all modern languages ​​there is an unspoken rule to use verbs for function methods.
But only in this case.



Formatting code without indentation (dealing with spaces, you remember):



Okay, indents. So removed the space between the name of the class and the variable.
Accident? I do not think.



Error-free code is fantastic. The programmer must not blindly copy the text.

Again, the "successful name of the button."



The design of the text.
Methods in Java are written in small letters. Well, this is such a small thing. But when Word formatted replaced them with large, Word can not be wrong (one of the versions, why it happened).



But sometimes you can make an exception and leave one item with a small one. Indeed, what I find fault with.



Tables are decorated with love, spaces will not pass!



If we steal gaps slowly, then let's populate the reader with single quotes.



Surprisingly, the pages of the book are excerpts from the code, and where to see the full source code is not written anywhere. No references in the book found. On the website of the Russian publishing house, too. I had to search for the website of a foreign publisher, and only there I found a link to the archive.

On the pages of the book there was a remark that this work was written in June 2013. Remember, I talked about lagging at the beginning of the article. This means that here you will not find material about the Material (pun), as well as mentions about Android Studio. Many novice developers see Eclipse and Android Studio as different and incompatible programming languages ​​(!). I have often met such statements on forums where people refused to learn an example, if the word Eclipse met there, with the statement: “After all, everything is different there and I won’t work”.

The book left a dual impression. On the one hand, interesting topics are covered there using the Flickr and Facebook APIs.

With all the parties, all of these prints are worn completely without any problem.

Happy programming!