I had this as a case for the iPhone 4 (or 5S, can’t remember). Was amazing but very bulky.

I’ve been reading covers letters for most applicants we receive. Generally we get 25-40 applicants (IT management or specialists positions) and if the CV looks half decent I’ll always read the cover letter.

If you have ANY customers in the EU, then you are subject to GPDR.

Maybe just comply with GDPR?

Doesn’t every password manager support this too? I have my TOTP codes on my Apple Watch through 1Password.

Could you try another card ? or get a giftcard from 1password? Can you pay via their app using Apple/Google Pay?

I've used 1password for 10+ years without any billing issues at all.

This is build in to Gitea. I mirror multiple github repos to my private gitea instance.

This is kinda what Denmark has. Companies and government agencies can send digital letters to your government digital mailbox.

I got 0.087 with firefox but subsequent tries are all in the 0.3-0.8 range.

Same situation here. Super frustrated with these apps that moves old purchased apps to “classic” and forces people to buy a new app. $50 is ridiculous.

I understand what you are saying, but a request/demand like that would be a hard pass for me as a manager. I’ve worked at companies that require a high level of security clearance and we wouldn’t be able to show you anything before you are cleared. No NDA will fix that. What I’ve done before is to show cases or examples of fake code/work tasks that looks like production examples but are very different. This is for the candidate to get a feel of what they will work with.

I totally understand regarding the security clearance.

I updated my comment in terms of framing it as an ultimatum - that's not what I would say in the interview process.

Showing examples of fake code seems like a possibly great middle-ground here. As long as that code is an accurate reflection.

I have a hard time imagining that if their code base is awful, they'll present you with awful fake code that accurately represents that.

Thanks for the clarification. Ultimately I think a developer (and other employees) should be able to work with any task and (in this case) the status of the code shouldn’t determine if you want the job or not.

Personally I value other factors such as work/life-balance, coworkers, work-benefits and salary higher than the individual task I’m completing on a day to day basis.

Just because you "should be able to" doesn't mean you'll want to. If the job is going to be unpleasant because the code base is steaming dumpster pile of garbage, that would be nice to know. Maybe you'll appreciate that kind of challenge, maybe not.

These are good points... I certainly value these factors as well.

And agree with you, to a point, that an engineer "should" be able to work with any task or codebase. We aren't primary care doctors in a community clinic who are obligated to treat every person who comes through the door.

I know myself pretty well. I know the kinds of environments in which I am most productive. I know the kinds of environments that I find to be a tedious and mentally exhausting slog. I prefer to avoid those. Some codebases are just awful to touch. I think it's OK to have some boundaries around that.