How To Be A Great Programmer • Dave Farley • GOTO 2023

It's short. video Dave Farley is about being a great developer. Interestingly, Dave himself is a grated kalach, who in ancient times wrote the book Continuous Delivery. (I mean, told)“Modern Software Engineering: Doing What Works to Build Better Software Faster” is on my shelf. In this video, Dave highlights six things he thinks are important to cool engineers.

• Code as communication Dave says that code is a means for people to communicate with each other, not just to communicate with a computer. Code readability is important for saving time and money if we do not write a one-time script. So the total cost of ownership during the work with the code is less, because most of the time we read and finalize the code, and not once and for all carve it in stone:) Interestingly, Google has a separate process for maintaining readability in their huge codebase. told last postMeasuring Engineering Productivity" The guys at Google just had a question about how much this process pays off and whether it should be canceled due to the advent of linters and static analyzers. In the end, the guys realized that it was useful and decided to leave it.
• Be coutious of framework - here Dave talks about the benefits of frameworks, which are associated with risk. The trick is that frameworks determine the structure of your code. (The concept of inversion of control) This affects the development and maintenance of the project. Dave suggests using third-party code isolation behind his own abstraction. In the terminal stage, the risk of being hooked on frameworks looks like a developer on Spring Boot or Angular/React, which under their own framework ... and all:)
• Code is design Code and design are inseparable. The author says that often people by design understand the choice of specific technologies like K8s, which replaces the solution of the original problem. Another problem is the allocation of a separate post of architect, to which the issues of design and architecture go. By the way, that was the subject. Release of the "Code of Leadership" podcastLesha Tarasov and I, a Tinkoff-based social platform technician, discussed staff+ track for individual contributors and why an architect is the role of high-level engineers rather than a dedicated position. As a result, Dave ends with theses, good code is the choice of organizational principles to solve problems. Design is a choice we make every day when we write code.
• Quality over features Great programmers take pride in their work and strive to maintain and maintain their ability to make changes over time. This makes sense if you are not making one-time scripts. So the total cost of ownership during the work with the code is less, since most of the time we read and finalize the code. Code quality is easier to maintain if you have a customized CI/CD and work in a product-based rather than project-based approach.
• Software development is a social activity The author says that software development is a social activity and in order to be a cool engineer you need to be able to communicate well, be able to actively listen to others, and clearly convey your thoughts.
• Avoid code ownership Great developers are open to criticism and ready to learn new things. In a professional environment, it is important to share responsibility for code and avoid sole responsibility.

P.S. I used to. told about another Dave video.The Most Powerful Software Development Process Is The EasiestWhich may be interesting to see in the video.

#Management #Software #Engineering #SoftwareDevelopment #Processes #Devops #SRE #SelfDevelopment