wewbull

If you really want to give it one last chance before leaving my advice would be to have a 1-on-1 talk with her.

Start out by saying that:

• You understand that she works in a different way to you.
• You feel more secure when your private and work lives are separate.
• You feel you are able to do your best work when you can focus on the task without distraction.

"Feel" is an important word here. You're not trying to be confrontational. You're trying to express your position so she can understand you and how you work better. You're trying to show her the right way to manage you, rather than pointing out the wrong way.

Then ask a couple of questions:

• Does she want you to communicate more because she's worried that you're not communicating issues that she needs to be aware of in her role? If so, that's a valid concern. Maybe organise a fixed time each week to discuss such issues so you can plan for it and come prepared.

• Does she think she can accommodate how you like to work?

I expect she values "openness" but that doesn't need to be sharing your whole life with the people you work with. So meet her half-way, be open about what you're working on and the problems you're facing. She may be able to help you by resolving your dependencies on others, or getting you what you need.

It's an issue for society.

...and the reason those Nissan batteries are failing is because they famously weren't (aren't) temperature controlled. Most batteries are looking like they'll have longer lives.

Anti-cheat "compatibility" means allowing software kernel level access and after Crowd strike I think that tide will be turning even on Windows.

Anti-cheat will change. Not Linux IMHO.

Getting interview practise is no bad thing. Being interviewed is a skill you learn to be sure.

I think a lot of people miss that interviews in the technical world are often not smartly dressed exams. Some are, but those are probably jobs where they won't mentor you and invest in you. They expect you to come fully developed.

Good interviewers are trying to imagine you as an every-day team member. Will you...

• ...work well with others?
• ...be engaged with the problem space?
• ...ask for clarifications or just make assumptions to avoid appearing "dumb"?
• ...let a lack of knowledge on something become a road block?

Knowledge is easy to give you. These things are much harder to teach.

Also, knowledge based questions might be designed to find your limit. So if you don't know something, that doesn't mean it's pointless from that point on. The interviewer may just have pushed you to your limit, and only they know if that was good enough. Keep going, stay engaged.

I don't know if any of that helps you design your bot, but maybe it gives you some ideas about being an interviewer.

...and let me guess. Critizing Israel's actions is tacit support of Hezbollah?

Worse than that. Fraud. He's scammed people out of millions.

...because removing somebody's kernel maintainer priv and the industrialised genocide of people is remotely comparable.

That sounds like policy written by somebody who has no idea what the reality of software development is.

1 year to rewrite critical software in a new language?

It's space cuties! Arrrggghhh!

I don't know, but given that forces involved are on the molecular level, I suspect those are driven by the kinetic energy of particles in a fluid (i.e. heat) and that there's a very slight cooling going on.