Hey there 👋 I'm back with another little rant!
The other day I was thinking about what makes good code good. Or better said, the variables that ma...
For further actions, you may consider blocking this person and/or reporting abuse
Great post! The "iteration" and "observation" point really stuck out to me mostly because I think code is means to an end - to serve our end users and the business. It's important to not get bogged down towards making it perfect from the get go, or to stick to your metaphor, in trying to create a masterpiece with every program or code fragment you write
Thanks!
Yup, you should do it the best you can at a given moment, and continuously analyze and improve it. Masterpieces take time and effort
I feel triggered because that a variant of this is in my bio :)
But that's precisely what the quote says!
Only that it says it ironically to poke fun of the "planning is overrated" people.
Hahahahah I know it's a joke, just modified it a bit to better fit the post... Hope it did not trigger you too much xD
Regarding your (good !) point on consistency, in my case I would put it under "refactoring", because I'm just unable to start with something consistent and coherent first.
So
Not a bad point at all. I separated them because I feel we must think of consistency on it's own and refactoring encapsulated a lot more than just this. But I agree, first make it work, then make it good. But, if you can make it decent from early on, it will be easier to do so.
Good post. My snarky one liner is as follows:
I do care about my code like an artist cares about their painting, but that doesn't mean anyone else cares about it.
Good way of looking at it!
But artists are paid after the thing is done, we're paid to solve problems with help of computers... How to find a balance?
I'd say it's mostly the same, only the medium changes. I would even say that it's more important for us to take care of our code bases as we will be working on them for a long time.
Eu vejo o Código como um livro que escrevo. Cada detalhe do mundo que escolhi influenciar ou resolver um problema deve ser simplificado claramente em código.