The topic of development methodologies and processes is usually not of much interest to developers. It's absolutely normal to hear: “ There must be a manager who does this. “It seems to me that most developers simply don't see enough value in understanding company processes. However, in my experience, this is an extremely important component that allows programmers to become stronger from a technical point of view, as well as move up the career ladder. I will try to show this connection.
, , - , , , , . Hard Skills.
Soft skills, , , , , . Hard Skills , - Soft Skills.
, , , "" , . . Agile. , , “ ” .
, , Hard Skills , , .
, , , , : UX, UI, , , , .
, , . , , , , . , , .
: . , , , , .
: . , ! , . … .
, .
- , . , , , , — .
, , ( ) . .
, - , , . , , , .
. , , . , , , , .
, . , , .
180 , , , . , , .
, . .
- , Theory of constraints, .
: ( ) , !
6 . , - - YouTube. , , , Slack. , , , .
- , , , , , . , Waterfall, . :
, .
.
. , , , .
, , . : .
, , .
, : (up-front design) — , .
, , . , , .
, , , 2 :
1. ,
2. ,
. Up-Front design, , .
. , , . :
, - , , . 2 ?
, ?
, , ?
, , , .
, .
: ? .
- , “ ” (Soft — ) , .
, “ ” , , . , . , .
“ ” , :
When requirements change, the difficulty in making such a change should be proportional to the scope of the change, not to the shape of the change. The difference between scope and shape often drives the growth in software development costs. It is the reason that the first year of development is much cheaper than the second, and the second year is much less expensive than the third.
The goal of software architecture is to minimize the human resources required to build and maintain the required system.
, : , , . . , ?
, . , . , , , , . :
, .
(, ! ?).
— .
— .
, “”, , . , . :
, , , , “” . , . , . , .
, . , . , , .
- . , , , . , .
, , , . . . , , , . ( ), , , . Agile Architecture Lean Architecture. : .
. , . , . , , .
, , . , , . Soft skills , . . , : , , .
, .
. , , . . .
, Android, , . . , PayPal, Palm OS. .
, . , , , , . . ?
?
, , , . , , . , . , . :
. , , “ ?”, “ ?”, “ ?” ..
, , , . .
, , , - . ., . , 2- , , .
, , 2 . — , . — .. - , , , , ..
, - , .
. , . - . , , , . , . , - , . .
The developer must be interested in and involved in the processes and methodologies. Only in this way will he be able to take into account all the unspoken or hidden requirements and solve the assigned tasks. If you don't notice them, you can very soon find yourself stuck on supporting outdated decisions made many years ago, without the possibility of changing anything for the better.