It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Anchoring is abusable only if the other party is coming to the discussion without a number in mind already. That's why planning poker works: everyone's starting from the same position, has heard the same things about what they're "bidding" on, and is only bringing their own inclinations and ideas about a still-fairly-abstract quantity to the table. If someone were to bid first, their assessment would naturally affect subsequent bids.
That doesn't describe salary negotiation in the slightest. The hiring manager knows what their budget looks like; they have a number already and their hope is that you'll come in well under it. Anchoring effects are irrelevant. Make them tip their hand.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Anchoring is abusable only if the other party is coming to the discussion without a number in mind already. That's why planning poker works: everyone's starting from the same position, has heard the same things about what they're "bidding" on, and is only bringing their own inclinations and ideas about a still-fairly-abstract quantity to the table. If someone were to bid first, their assessment would naturally affect subsequent bids.
That doesn't describe salary negotiation in the slightest. The hiring manager knows what their budget looks like; they have a number already and their hope is that you'll come in well under it. Anchoring effects are irrelevant. Make them tip their hand.