I've always been bothered with the saying "code as if the next person maintaining your code is a violent psychopath who knows where you live".
Why are we instilling fear and promoting toxic behavior and workplace violence?
You should code so that you can take that beach vacation without having to be on call.
Code so that you have free time to be with your family.
Code (and document things) so that you can leave the project for something even bigger.
@mariatta my mantra has long been "code for myself to read in ten or twenty years time" - i.e. long after I've forgotten almost everything about how and why I wrote it.
Admittedly it took me ten years to see why that was wise, and then twenty to be really clear about it, but hey that's time for you.
@jhwgh1968@mariatta which, to return to the sentiment of the original post, involves coding with a sense of kindness and generosity.
At least that's the kind of state of mind I like to have while coding.
I like to think this goes well with the idea that the code will be posted as Open Source - even when, or maybe especially because I don't know who, or if anyone will ever read it.
@mariatta I had an early colleague who would always decry a common euphemism about documenting things: "In case you get hit by a bus." He would say, why is the sentiment always so negative? We should be saying, "In case you win the lottery."
So much of corpo tech speak is needlessly toxic and violent. I always hate all the military terms in tech. Sounds both violent and like people are overcompensating.
@mariatta
i need notes not to forget groceries i don't buy regularly...
so i do comment what i code basically for myself because i know when i leave the room and come back i will wonder what the heck i have thought about doing stuff this way...
Edit: the thing with the violent psychopath, i'm not sure about yet...some day the intrusive thoughts may win
Add comment