Only because it got leaked early, denying them the opportunity to hype anything

I think it’s more like killing humans on bicycles.

Or because it’s basically a swampland and should be abandoned.

Project it onto the glass

Did you ask the hospital if they could reduce that or pay for some of it from grant money or something?

That was the funniest bit in the series for me

About what? Didn’t expect everything to be in Chinese?

Sounds like when the guy knocked on the door she could’ve just shouted “we don’t want any” and he would’ve left

You guys know this article is about Walgreens, right?

No she’s an 18 year old woman

Having eaten at McDonald’s in both USA and Europe, I can say the food quality is noticeably better in Europe.

Magic can accomplish all of this, so I choose that

What does Denmark have to do with this? There are closer countries than that.

A lot of great answers here, but there’s another possibility I haven’t seen mentioned yet. When you are gathering information like this it says to the engineer that you want to change things, and they don’t know if that change is going to make things easier or harder for them. Usually things only ever get harder as a project lives longer. So they’ll be less incentivised to help you unless you give them an idea of what you intend to do and specify what problems you intend to solve to make life easier for them personally.

Also, as an engineer, things like this I generally see as less important than making sure the product works and that development is processing on pace. Having to explain everything about my job to someone coming in with 0 prior knowledge is a huge waste of time.

One tip I saw mentioned works well in this situation: get them to start complaining about things they hate about the current processes. Everyone likes to complain because it is cathartic.

It will help if you can educate yourself before talking to them. Present the info you have and ask them to fill in the blanks or make corrections. Must engineers like to solve problems, so present this as one for them to solve like a puzzle. Engineers are generally not novelists. Don’t ask them to just start spitting out history of The Process to you.

The whole point in being a whistleblower is to release the documents. Why would you tell everyone what’s happening and not provide the evidence? After you release it, there’s less chance of being harmed, and your job is done besides showing up to court.

Nice try. Romanes eunt domus!

Not even an employee, just an interviewee.

Fuckin A

They have access to X’s proprietary code to affect what algorithms it uses?

I would allow it and approve the PR, then I would ask the team lead if he wants to schedule time to update the style guide to cover cases like this, and set up a linter which can ideally autofix any existing code that violates that rule. Not everyone will agree with the rules set by a linter, but they ensure style consistent, and, more importantly, save everyone time and drama related to inconsequential differences in opinion (at least inconsequential to the bottom line).