About chocolate, the internet, usability and development

    Introduction



    In the world (in particular in IT), you probably come across difficulties too often, sometimes you don’t even pay attention to it, difficulties have already become routine and are not perceived consciously. However, I had a desire to give a short overview of the difficulties.

    Chocolate



    I really like dairy products. In particular, I like to drink a glass of milk with several slices of dark chocolate. Today this once again repeated. But he didn’t go through usually (maybe this is somehow connected with the fact that the day before yesterday I started a new life;)), but this case was noted by the fact that I very carefully approached the issue of opening chocolates:

    gork_franz [1]





    Have you ever eaten chocolates in this series ? The trick is that when you open it, you don’t have to think about how to do it, because everything is written and painted on the package, and it is made so that few people can go the other way. It's great!

    the Internet



    Now about the Internet, he abounds with various delights on the subject: if you can understand me in a few seconds, not everyone succeeds. My opinion is that you need to adhere to healthy minimalism, bring your resources to such a state that each page allows you to do only what it is intended for, but on the other hand to cover all related needs.

    I will give the simplest example:

    I write a message in some RTE (rich-text editor) editor, and suddenly I get the thought that it would be nice to insert a picture, my eyes look for the corresponding button and it’s good if I find it, or instead To continue pouring my creative energy into the editor, I will start pouring it to the authors of the site, or criticize it on various information resources.


    For example, tagging, categories, quoting, spelling, and so on could be added.

    However, in all these related functions, there is a slight nuisance associated with a complete lack of usability and oversaturation of the interface. So you should be very careful and have an idea of ​​the golden ratio :

    It is generally accepted that objects containing a "golden section" are perceived by people as the most harmonious. The proportions of the Cheops pyramid, temples, bas-reliefs, household items and jewelry from the tomb of Tutankhamun allegedly indicate that Egyptian masters used the golden ratio in their creation. The architect Le Corbusier “found” that in the relief from the temple of Pharaoh Seti I in Abydos and in the relief depicting Pharaoh Ramses, the proportions of the figures correspond to the golden ratio. The architect Khesira, depicted on the relief of a wooden board from the tomb of his name, holds measuring instruments in which the proportions of the golden section are fixed. In the facade of the ancient Greek temple of the Parthenon there are golden proportions. During his excavations, compasses were discovered, which were used by architects and sculptors of the ancient world.


    I would like to give an example of a resource that I started to work actively with recently, this is Twitter.

    image
    It is insanely popular, and this is not surprising, due to the fact that it:

    1. Implements a complete idea
    2. Provides interesting and comprehensive functionality.
    3. Simple and easy to use.


    Software development



    All of the above can be safely reflected on the development of which I do almost every day. It should be understood that the software is not written for a successful interpretation of the hardware component of a computer, but for people, therefore it is necessary to adhere to the principles of simplicity and convenience, clarity and ease.

    In order not to be unfounded I want to give an example of an analysis of a certain out-of-box engine for an online store.

    When developing such an engine, the following should be understood:

    1. A client who will be interested in buying this solution (we do not sell products, we sell solutions;)) will not be interested in organizing his support (if he buys a box, he will not want to hire specialists to work with it).
    2. The engine should be as simple as possible and provide the main function - the deployment and support of the online store, it is desirable that this happens by pressing a few buttons


    The same principles should apply to the process of writing software:

    • There should be no solutions pulled over the ears. If something goes wrong, it means you are using the wrong technology, the wrong environment, you do not have sufficient qualifications.
    • There should not be hard-to-read, confusing, scary code. If this happens, then you need to arm yourself with tools such as refactoring, design patterns, an experienced architect can help.
    • The code should work at any stage. If at the end of the period (day, 2 days, week) you are unable to make a functioning instance, then you need to review the development mode necessary for the solution to be functional.
    • Each line of code should have an idea, a thought. If your code is boring to read, if it is just a set of letters and numbers, try to write a short story (at least in your mind) about what your method is currently doing, I assure you that it will only benefit, and it will also bring clarity.
    • Writing a code should give positive emotions. If this is not so, you may be tired for today, I advise you to take a break. If this repeats tomorrow, it means that you are just in a state of “good weather”, if possible, try to do some other work at this time. If this constantly accompanies you, think about whether you are devoting your precious time to this activity.


    Conclusion



    I wanted to try to pee about the development a little abstractly, a little not from the technical side of the issue, I want my experience to be useful not only to .NET - developers.

    Also popular now: