Sleep and tackle the problem tomorrow with fresh eyes.
A colleague's eyes are always fresher than your own.
Too many times has a colleague been able to immediately pin down a problem I'd been pouring HOURS into.
(More junior) teammates often wonder why I'm so verbose with my status-reporting. I can't count the number of times where I've sent out a "I've been banging my head on , here's everything I've done - did I miss something trivial" only to have a reply, a few minutes/hours later, saying something as simple as "line 24 of your problem-description".
Doing this one right now. Completely borked the local database for one my apps today. Shut down my machine and went home. Going to play some video games and deal with it in the morning
That's why I love doing infrastructure automation: something's gone completely sideways with a system or an entire architecture? Punch a button to deploy a new, functional copy in a few (or few tens of) minutes.
I would love to but we're in feature factory mode so not a ton of time for that level of automation 🙁
Yeah. Automating deployments is definitely a time-suck, but it's a time-suck that, once done, quickly pays for itself by freeing you up to do other thing more quickly and easily. Unfortunately, many organizations that love to say "we want to do devops" or "we want to do infrastructure automation" don't seem to understand that you have to allocate considerable time to getting there. That it's an investment to reach the point where you replace broken systems – or even just do regular patching – with "lemme launch a new copy". Then again, there's a lot of shops that think that re-hosting into a CSP and/or switching to containers magically impart capabilities they never designed into their solutions.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.