>I’m not very good at estimating timelines, so I gave a (very) rough estimate of 2 to 4 months. A reply affirming that that sounded reasonable, with an estimation of 300 to 400 hours of work, with a price tag of $10,000 was what I got back (assuming the project didn’t run seriously overtime).

The author of the article gave an estimate of hundreds of hours across 2 to 4 months and Analogue's valuation of that time was $10k - for an expert in the domain working in software. That number is an insult. Even doubled it's quite bad.

> Isn't it her job to ask for the appropriate amount of money, and reject an offer which isn't enough?

That's exactly what she did. She didn't lead by demanding a specific number, but in some cases, that's actually pretty good advice, it can be good to let companies make the first offer on salary.

Otherwise, she engaged with the company, told them upfront that $10,000 wasn't enough without leading them along too much; they came back with $20,000, which sounds like it still wasn't a great offer for her, but she engaged a bit longer to see what the context was and whether or not it would work.

When the company came back with NDA demands and demands around her own Open Source projects that she wasn't comfortable with, she decided that the job wasn't for her, and (imo, very respectfully) turned down the offer: https://endrift.com/resources/post-assets/analogue-13.png

Writing a blog post about this process is allowed, I don't see anything entitled or disrespectful about that. NDAs and non-competes would make me very nervous if I was contracting with someone, particularly if I'm a domain expert with a popular Open Source project in the field that they're hiring me to work on.

The other side of this comment thread is that she very factually described a negotiation process she had with a company, described why it went wrong and why it didn't work for her (she feels her time is worth more and wasn't being valued enough, among other issues), and described graciously breaking off the job offer on what seems like good terms to me -- and people are angry about that outcome?

> This reads like a case of 'all about me'-ism.

No, it reads like someone negotiating a salary and terms and having a clear view of what they think they're worth and when terms seem bad to them, which is a normal thing that people who look for jobs should be comfortable with. Ultimately, when you're negotiating a contract it does no one any favors for you to do anything else other than advocate for yourself during that negotiation process. Looking at company culture (trademarking fgpa, claims about emulation, etc), looking at side-project terms (delaying releases of an Open Source project), and looking at salary are all part of that -- and being honest about how you read those signals is something that good companies want. It doesn't help anyone to mask these objections.

I get a little frustrated when I see people describe normal negotiation as entitled. This article is how job searches and hiring processes are supposed to work.