Hello Habr! A developer is often hired to solve business problems like a professional. But sometimes developers do not listen to the opinion of developers on issues in which they are more competent than business representatives. The fact that this can be done and why it should be the developer, I'd like to talk.
Happiness and job satisfaction
— . , . — . , , .
(software development) , . , , , , , , — . .
?
, , . — , , « ?» ( . ). ( , hard skills ). — , « ?». Agile (https://agilemanifesto.org/).
, *argumentum ad auctoritatem ( ).* , — , .
, — . , , , , , — errare humanum est. , , .
?
best practices , , . — . , — , , . — , .
, , , . :
, . , , . . — , , .
: , . . — , . , , , , , , .
?
, , . , , , , . , , . — — , , TDD ( ) code review, . — — , best practices, , .
, , . , , . , , . , , — , , .
— . , . , , best practices — . , , , , .
, , . , — , , , , .
, . , , .
This article is a deeply subjective opinion on how a developer can get more pleasure from his work by showing professionalism and communicating subjective ideas to the business that the developer, as a professional, considers correct. The article is largely inspired by the ideas of Agile, the book "Clean Architecture" by Robert Martin, as well as my own experience, experiences and the experience of friends and colleagues.