3 ms·
As professional developers we are usually in a business context and our purpose is not to be artists, to create, we are there to provide the reliable building b
by SanderNL 3y ago
As professional developers we are usually in a business context and our purpose is not to be artists, to create, we are there to provide the reliable building blocks out of which actual creation can arise.
The focus here is “reliable”. Let the creative guys mess around, we should focus on keeping stuff clean. If we start becoming messy that’s no good, because it’s all downhill from there. How can you draw skulls, no matter how messy, if the drawing functions don’t work?
Using this article’s story, we are the ones creating the drawing functions, not the “skulls”. We make sure those guys that actually see the skulls can do whatever it is they do. We are bad at that, so when we are asked to be creative we arrive at what the author describes: few lines, something simple, something algorithmic.
That’s not because you are all about cleanliness.. you just lack creativity and vision and an artist’s drive to make it reality. And that’s OK.
- sisve 3y agoI think you are both right and wrong at the same time. Even in a business context its not sure you want reliable over feature. And I think a lot of developers are focusing way to much on good code. And with that they think a lot on how it can be extended in the future. But they fail to see that from a business perspective this code is properly not living for many years. I have seen so many projects with good code beeing shutdown. Its of course another side here, where you code is in production for 10 years+ with 100 developers making changes to the files... But a great developer / architect are able to really understand the business context they are working on and understand how that influence what you consider good code and good architecture