I don't think it's necessarily so black and white. Both parties fell for something, if that's still there, maybe it can be found again. Maybe.

If not, sure I agree with you. I don't think it's advisable to stay in an absolutely unhappy AND unfixable relationship. But I do think it's worth trying to fight for it.

I'm in a 15 year long relationship, and it's not been smooth sailing. Some experiences require knowing each other very deeply.

This is a very powerful experience IMO.

I've co-interviewed about ~15 people or so with the hiring manager and a guy from HR.

We're looking for people that

1. match the requirements at least somewhat. 2. we can get excited about software and technology. 3. can communicate clearly about software.

A good candidate has preferences in technologies and software. Bad candidates don't give a shit or can't mention languages or frameworks when asked.

We ask questions about soft skills too: Have you ever been in a conflict at work, if so how did you approach it. If not, have you had to act "professionally" in other situations?

Good candidates can always tell a story about some conflict where they talked it out with a colleague or a boss, or give some other lame story where they "learned something". Bad candidates can't say shit. The answers to such questions can reveal some true assholes that can easily be filtered.

Finally we ask why you want this job. Why this company? Good candidates have some bullshit story or can tell something they actually find fascinating about our products. Bad candidates tell you that they don't actually care much where they work, it's just for the money etc. Even whey you give them hints and clues etc., the bad candidates are usually just an obvious bad fit for the role.

Shitty applications get filtered in bunches. Good candidates write applications that read as if written for the job posting. Bad applications read as if written by ChatGPT or plain ol' copy/pasta.

my 2 cents

this is very solid advice - I completely agree with you

> This is also one of the reasons why printf won't work. You cannot pass a type like std::string to a variable args function.

Can't you just call .c_str() on the std::string first to get to the null-terminated char array? https://cplusplus.com/reference/string/string/c_str/

this project is AWESOME! cool idea man

I usually run a pre-processing step to identify all needed symbols and then create them dynamically. I find sympy works fine for such on-the-fly workflow. My experience is with predictive statistics and financial models.