Dreldev

    Good code there is an exact tk. For example, “make a tool with a long sting and a handle that allows you to tighten screws with a longitudinal groove of 1.5 mm wide with your hand” ... well, or something like that. Take and make a screwdriver.

    But when a creative person is at the helm, tk mutates into something terrible.
    Stage 1: “make a twist”
    Stage 2: “what if the screw’s head is hexagonal”
    Stage 3: “I thought that the user would break it myself”
    , etc.
    As a result, after 3 iterations we get an electric screwdriver. It's not bad. It is wonderful. An electric screwdriver is much more convenient than a screwdriver (since I bought it, I have not used a screwdriver).
    But! We spent 3 times more time, because we first made a screwdriver, then threw out the sting and made replaceable nozzles, then threw out the handle and made a handle with power supply. As a result, nothing was left of the screwdriver. A competent tk would save us from making the initial screwdriver.

    But the most achtung occurs when the programmer’s brain tries to logically build a scheme of interaction with a creative person who is at the helm. A programmer is by nature a lazy and narcissistic creature, and does not like to rewrite his code. Therefore, when the development of a new spinner begins, he tries to predict the train of thought of a creative person based on his own experience gained from other users. The result is not even a screwdriver but an electric drill with a flashlight and a folding butt. But no one guarantees that the creative person did not want this time a screwdriver for an hour.

    Here we have such a drill!
    And how are you?

    Also popular now: