4 ms·
TLDR; Yes, it is exhausting, but I have found ways to mitigate it. I don't develop stuff that runs billions of queries. More like thousands. It is, however, i
by ChrisMarshallNY 5y ago
TLDR; Yes, it is exhausting, but I have found ways to mitigate it.
I don't develop stuff that runs billions of queries. More like thousands.
It is, however, important infrastructure, on which thousands of people around the world, rely, and, in some cases, it's not hyperbole to say that lives depend on its integrity and uptime.
One fairly unique feature of my work, is that it's almost all "hand-crafted." I generally avoid relying on dependencies out of my direct control. I tend to be the dependency, on which other people rely. This has earned me quite a few sneers.
I have issues...
These days, I like to confine myself to frontend work, and avoid working on my server code, as monkeying with it is always stressful.
My general posture is to do the highest Quality work possible; way beyond "good enough," so that I don't have to go back and clean up my mess. That seems to have worked fairly well for me, in at least the last fifteen years, or so. Also, I document the living bejeezus[0] out of my work, so, when I inevitably have to go back and tweak or fix, in six months, I can find my way around.
[0] https://littlegreenviper.com/miscellany/leaving-a-legacy/ https://littlegreenviper.com/miscellany/leaving-a-legacy/
- zaphirplane 5y agoFront end and no dependencies, tell us more
- ChrisMarshallNY 5y agoFeel free to see for yourself. I have quite a few OS projects out there. My GH ID is the same as my HN one. My frontend work is native Swift work, using the built-in Apple frameworks (I ship classic AppKit/UIKit/WatchKit, using storyboards and MVC, but I will be moving onto the newer stuff, as it matures). My backend work has chiefly been PHP. It works quite well, but is not where I like to spend most of my time.