677 karma · joined September 26, 2014
Although, the nice thing about conspiracy theories is you can always just layer on another explanation. Obviously the Deep State didn't trust Trump with this dangerous knowledge, so they kept him in the dark. Some things not even the President is cleared to know. Duh.
0: https://www.npr.org/2022/11/18/1137474748/trump-tweeted-an-i...
To be honest we never "solved" it. Eventually the younger reached kindergarten age and my wife returned to full time work. I wish I had better advice. The suggestion to have a dedicated office space with a door is a good one, but if your partner does not respect boundaries that won't be enough. If finances allow, you could look at leasing a part time desk in a coworking space or even a dedicated office. I know it feels silly to pay for office space when you can do the job from home, but if it's damaging your relationship, it may be worthwhile. Some employers might even offer a stipend for remote workers to help offset costs. The fact that you refer to your partner as a nagging micromanager tells me something has to change.
I hope this post doesn't make me sound like a dick. I have immense respect for my wife for choosing to pause her career to care for our children. Raising kids is HARD, harder than the work I get paid for to be honest. We're partners in life and parenthood. But my role in the partnership at that time was to hold down a job and that's a lot harder to do when you're being interrupted 10 times a day. Hope you are able to work something out.
You'll notice he doesn't say "I regret my actions and the harm I caused". Just a vague allusion to "such discussions". As if the people discussing him falsifying research are somehow the problem. When someone goes down for a scandal, they rarely express true remorse or take responsibility. It's always "I'm sorry... that I got caught".
His response speaks to his character, but I'm not sure it says what you think it does.
Doesn't really bother me, although it does make evaluating what you might actually DO in a particular role challenging. In this "SRE" position am I writing Kubernetes operators in Go, or am I a Jenkins pipeline janitor, or am I working the graveyard shift in a data center swapping dead hard drives? WHO KNOWS!
I've seen some replies that this is basic stuff everyone should know, but the fact is, people don't. Even Senior or Principal engineers (depending on the company). You can get very far in software engineering without understanding anything outside the bubble of your domain. Hell this is basically why the field of SRE exists, because a lot of developers do not know how to write reliable software that works in the real world, not just in a perfect test environment. If you've somehow worked your entire career surrounded by engineers who have even an entry level understanding of how networks function, you're the outlier. More often I've found people invent their own bizarre mental model of what's happening that only has the vaguest grounding in reality.
And honestly that's ok much of the time. Everyone can't be an expert in everything. Just have some grace about it. Don't pull a Dunning-Kruger and assume because you are a fabulous Java developer you are automatically an expert in every technical field. Most of us aren't.
Thanks for Redis and all your other contributions.
I mostly work in the cloud now but when I last had to manage a bunch of physical machines we had a physically separate network accessed via its own VPN to get onto the BMCs. Because yeah, the security situation was a joke.
Fast forward several hours of heavy drinking and we were getting hungry. He makes a hot dog and confidently dumps like a tablespoon of hot sauce on it. Takes a bite, sprints to the bathroom, and spends the next half hour with his head jammed under the sink faucet moaning in misery.
Sounds like your booze-and-hot sauce experiment went a bit better :)
But VB did so much of the work for you. And it was BASIC, which I already knew well. So it was exactly what I needed to understand the fundamentals without having to boil the whole ocean at once just to get a window with a button on my screen.
Agree it wasn't really suitable for large scale projects (although it got used for them anyway heh). Somehow VB apps always looked and felt "wrong", like they were a cheap knockoff. But for learning, and writing quick non-commercial apps, it was just right.
All that said, I feel no nostalgia or desire to go back.
I'm also not going to tell them what to do with their own body. But "run it by your doctor first" seems like a reasonable thing to suggest, even if they ultimately decide to do it anyway.