2 ms·
It took me a long tome to mostly get over this, but a turning point was realizing how temporal code is. It’s written in a snapshot in time, to solve a problem
by Zetice 3y ago
It took me a long tome to mostly get over this, but a turning point was realizing how temporal code is. It’s written in a snapshot in time, to solve a problem that may evolve hour by hour, competing with dozens of other tasks also needing attention.
So what you produced in that maelstrom is really just a reflection of the moment, not of you.
This also helps me not judge other peoples' code. I only see the outcome (the code), not all of the inputs so it's hard to know if this is good work or not in a "is this person good at their job sense" (though obviously there is better and worse code).