95 karma · joined March 15, 2021
Do try psychotherapy. At the very least, talking about things you're going through can bring you relief and possibly actionable insights.
I strongly recommend some kind of sport as a hobby. There's something powerful about routinely choosing to be uncomfortable (to a tolerable level) and seeing your body and mind transform as a result. Not to mention it becomes really (oddly?) fun at some point.
If your current situation sucks and you can step away (NOT end your life), do it. Whatever chance exists for things to get better, it's better than sticking with something you know is bad.
When I do expect DOMS to kick in, I drop weights to 50% my max sets (usually dropping weight vs reps). This makes me "somewhat sore" the following day but no more than that. I also put an emphasis on sleep, "clean" nutrition and supplement with electrolytes. Works really well for me.
As for low intensity cardio, I feel it's good for me, but I have to say it can be a struggle to keep it low. The feeling of "I want to push harder" can sometimes be overwhelming.
But guns sure help.
I'm just concerned with the possibility of us "winning over death" and how it would transform everything. It's not another cure for an illness or another 100 years to live. It's no one ever going away without someone else making them. For better or worse. That's not a part of life. That's an entirely different existence.
So yeah, how is a CDN centralizing your infra? You could just have your CNAMEs point to a different provider or directly to your gateways. Or you could even go down the multi CDN path, and have someone like ns1 automatically redirect your CNAMEs to an alternate CDN on a per-geo basis to overcome local failures.
It's just another SaaS component in your system. You could self host if you're willing to take on the ownership challenge, and at certain scale it would even be more cost effective.
Care to clarify so I could take the mandatory contrarian approach?
It might make sense to add an Ansible type of reaction as well, though I'm unsure of the scenario.
I think abstracting ipmitool is nice but it's just a building block. The real killer is when you put it all together - recognizing a system is down, and bringing it back up automatically despite having no working OS. It might require using ipmitool. But it might also require clearing state in a provisioning system via an HTTP call. Or sending some keystrokes.
It's about moving beyond manual recovery when no OS is present.
What we haven't figured out yet is who's the buyer.
And to top it off, it seems like it's all undocumented know-how. You have to be a practitioner to pick it up.
We find that the tools are focused on all sorts of inventory (DCIM) and provisioning. Processes are homegrown based on whatever ticketing system you have in place. That's what we're looking to change.
So far it feels like the colo side aren't hyped around introducing tools to automate things. It's like their jobs are at risk. And the customer side is bent on building their own tooling from scratch.
We have found some early adopters, but they're hard to come by. Even when we can quantity savings in money and time to market. Not to mention engineering frustration.
Would love to have a conversation around this!
We're wondering if automating this headache to some SaaS that offers BoM templating, compatibility validation, interchangeable parts and such, could be of interest to such an org. Essentially they'd be left with approvals and the rest would be stepping through an automated workflow. WDYT?
Not sure if it would hold?
Sure, building the forms and the workflow is an annoying experience. If Jira admin hasn't set up a good separation of templates, things get mixed up and cluttered (for project admin tasks). And it feels like you're working for the system instead of it working for you (again, when building your flows).
Still, once you get used to Jira's way of putting things together, building what you want becomes "not so bad". And you can have pretty much whatever process you want in place.
I think devs dislike it because it's riddled with layers upon layers of abstractions targeting enterprise deployments. Meaning if you want something quick and simple, it's probably the wrong tool.
But at the end of the day, it's about the process you build and making sure the tools serve it (mostly on the daily work level rather than admin). Jira let me refine the process and didn't get in the way of others on the team. Frankly, we liked it.
I can't stress this enough. Being part of a team you appreciate helps a lot. First and foremost, with burnout. Knowing you have teammates you can share daily stuff with, and lean on when you need to, is a lot. Feeling like they can do the same with you, makes it an even more powerful experience.
All in all, it sounds like, at this point, you should optimize for people and not tech excellence. The latter can follow when you have a supportive environment.
As others suggested, take some time off to put out the fire. Then move on to find a job in a team you think you might like.
btw, during the time off, things might get worse mentally before they get better. Simply because you won't be able to hide from your thoughts and feelings anymore. It could do you good to set simple, achievable daily goals that serve a small purpose and not aim for something big (like learning a new skill). Stuff like going to the beach every day, or meditating for 10 minutes (without the purpose of "learning meditation" or "doing it right").
Be kind to yourself, your life isn't a race to be won. Maybe more like a hike through the wilderness.
Anyone in particular you have in mind? Other than Michael Dell, I mean.