What is being a good developer?
The driving experience on the roads of Kiev gave me a couple of interesting thoughts. We all know that on the roads "a bunch of idiots." Exactly the same is the case in development - wherever you look, it’s scary to look at the code. Why it happens?
After all, each of us considers himself a cool driver! We know how to drive fast, squeeze in between cars, skip somewhere, and so on. In general, quickly get to the place we need. And many consider themselves a cool developer too. Just give us a more difficult task - we create a solution for it very quickly, perhaps even building design patterns. So what's the deal then?
')
The thing is that to be a cool driver is not the ability to quickly get to your destination. This is, first of all, the avoidance of emergency situations during their movement. Because emergency situations increase the risk of losing a lot of time and money, both ours and others. Nobody needs movement with such risks (many simply don’t think about them).
Cool driver? Do you want to drive fast and re-align? Show turns at the same time, do not cut at the speed of another driver. Not enough time or reaction to it? Then you're not a damn cool and eat like everyone else! A really cool driver doesn’t drive, but he knows a lot of travel options, when it is necessary to change lanes beforehand, what speed to develop to get into the “green zone”, competently assesses the risks of getting stuck in traffic and makes adequate decisions ...
Exactly the same rules apply to developers. Cool "pedal" code that seems to work, but then it can neither be understood nor supported? You're not a damn cool developer! Write code that machines can understand almost everything. Writing code that other people understand and does not spend a lot of time on its support and development - this is a sign of professionalism.
Quickly getting a low-quality working code means putting the risks aside for later, at the most unforeseen moment. A cool developer understands this. And a cool developer can write completely covered with tests, well-structured, clear and working code faster than others. This is his “classiness”!
For drivers, there are at least some penalties (we will not start talking about their actions in Ukraine) for false “professionalism”. They are not in development, and this makes our projects of joyful and “blooming” “foul-smelling” and dull. And the “professionals” blow their cheeks and tell how quickly they can write code of any complexity ...
After all, each of us considers himself a cool driver! We know how to drive fast, squeeze in between cars, skip somewhere, and so on. In general, quickly get to the place we need. And many consider themselves a cool developer too. Just give us a more difficult task - we create a solution for it very quickly, perhaps even building design patterns. So what's the deal then?
')
The thing is that to be a cool driver is not the ability to quickly get to your destination. This is, first of all, the avoidance of emergency situations during their movement. Because emergency situations increase the risk of losing a lot of time and money, both ours and others. Nobody needs movement with such risks (many simply don’t think about them).
Cool driver? Do you want to drive fast and re-align? Show turns at the same time, do not cut at the speed of another driver. Not enough time or reaction to it? Then you're not a damn cool and eat like everyone else! A really cool driver doesn’t drive, but he knows a lot of travel options, when it is necessary to change lanes beforehand, what speed to develop to get into the “green zone”, competently assesses the risks of getting stuck in traffic and makes adequate decisions ...
Exactly the same rules apply to developers. Cool "pedal" code that seems to work, but then it can neither be understood nor supported? You're not a damn cool developer! Write code that machines can understand almost everything. Writing code that other people understand and does not spend a lot of time on its support and development - this is a sign of professionalism.
Quickly getting a low-quality working code means putting the risks aside for later, at the most unforeseen moment. A cool developer understands this. And a cool developer can write completely covered with tests, well-structured, clear and working code faster than others. This is his “classiness”!
For drivers, there are at least some penalties (we will not start talking about their actions in Ukraine) for false “professionalism”. They are not in development, and this makes our projects of joyful and “blooming” “foul-smelling” and dull. And the “professionals” blow their cheeks and tell how quickly they can write code of any complexity ...
Source: https://habr.com/ru/post/174957/
All Articles