Why we can train accountants, but not programmers

It seems that we are doing everything to write good code: we read books, listen to podcasts, go to conferences and study best practices. Why is the result poor? New languages ​​are learned slowly, the code turns into a hellish monster, and the Juns spend months learning to clearly name identifiers.

We called Grigory Petrov, DevRel Evrone.com (ex. Voximplant, Radmin, Digital October Center) and the inspirer of the Moscow Python community , to tell you how to write good code yourself and teach the team. We also discussed how to understand what mechanisms are holding us back, and how to look at neurophysiology through the prism of applied development and technical team leadership. The conversation turned out to be so interesting that they made an article in his footsteps.

Our guest calls himself a generalist. He writes in most mainstream development languages, except Haskell, and is interested in neurophysiology. At some point, he looked at his previous work experience and realized that he liked writing documentation, explaining complex things in simple language and communicating with developers, but not leading. Therefore, the position of DevRel (Developer Relations) turned out to be optimal for him.

Good code, what is this?

,   . ― ,   . , ,    ,      , -       . ,  IT 20–30,    ,       . . ― ,  «»    ,     .     .

― ,   , ,    ,   .

 , , ?

,   : - , , , , .   ―  . ― .      : , ,     .

 _{Bonkersworld.}

    .   ( , , ,   ,  -),   , .

 ,     .      —   .   ,     ?

   ,       .

,       ,   .  ,     ,     ,  .   (Reward system) ,  .  ,   , ,   . ,   «» ,   .

 , , , ,   . , (Attention Schema Theory) ,   .   .

_{.   . .   2015}

  ,      ( ) ― .

, .   ,     ,    , .   .  ,     : ,   ,   .

  ,   .   , ,   .   ,   .   - , . ,   ,  .

  : «» , . ,   ,     (FPS),    ,   ,   .

, ,   ,     ,  ,   .    , .

 ?    —

  : « »,   , ,  FPS, BFG  Doom    .  ,   : ,    .

  ,   .

,   Ruby.   « »,    ,   .    , , . Ruby,     , .

(Spaced repetition). Anki .  IDE , , hotkey,   ― - .   ―  .

  ,  :  ,  ,   .   -  ,   ,  ,   , .

, :

• ;
•  ,   ;
•     .

,   ?   .

 

,   .   - , - ,   .    ,   .    ,  ,  ,     . ―  .

,  Evrone,    ,    ,    , . , , , GitOps   .   .

 Evrone      . slack-. ,   .   ,    .    ,     .

 _{TeamLead Conf}

 — .     ,   .

      ?

 , .     ToDo- ― ,   :  ,   ,   wiki, code review   . ,       , .

-   ?

 .    ,  .    ,  .    :    .

  ,        ?     ,     , .   ,   . , .    ,          .

 ,   . , ? - ,    —   ,   . ,   Rust  Go . ,   . ,     10–15 %.   . ― , .   ,      .

, , , ,    .        .   , ― , .   .

   

, ,      ,   .    .   ,   ,   , «» .

,    ,   - ,       .       .

, ,    ,      .     , .   - .

,   .

  ,  . : «  ?». , , ― .

?   « ?»,   ―   «?». , -     . ,   .

?

.   ( : 1 9 8 4 4 5 1). ― ,  .   ,    (1984  451  ),   . (Chunking).

, ,   .  ,  , .   ,     «».

, . -   ,     ,  -   . ,   , . ,      . ― ― . , ,    . ,   IT- .

:  

• JavaScript. - ( )  ,    JS.
• Realpython.com.   .
• Learning how to learn  Coursera.     Chunking  Spaced Repetition  .

•   ( ) , .

 :

< >

g-mate, 30–50% , . — : , 3 .

@g_jobbot, .

</ >