itschaffey

What do you think will happen with Angular after 2.0?

What would you say is the best way to describe React?

Node haha? Dang. As mentioned in an answer to another comment, perhaps framework was the wrong terminology to use, and something more all-encompassing to reflect what is wanted would've been better.

What do you think a developer using Javascript should use/know right now?

Noted – use of terminology could've been more accurate, but for the purpose of this article we tried to keep it quite simplified. Perhaps the wrong approach with regards to accuracy.

What were your thoughts on the broader points of the post?

Hi Jonaldomo - could you clarify what you mean?

I think both followup questions are valid. As others have mentioned in addition to yourself, there is wariness of companies' intentions, which ties into getting someone for less/value/than what they're worth.

On the flip side, case may be they genuinely can't afford to pay as much - but potential applicants may be swayed if they trust in them, and choose to forgo a higher salary or accept other compensation methods or benefits.

No need to apologise - it's a perfectly justified way of putting it. Could be considered a cynical view, but justified still.

Ah, oh dear haha.

That's fair logic - what if other forms of compensation were included in the listed range? (e.g. top end of band + equity)

To get in touch/an understanding of the company/team?

Ah sorry, I've muddled myself somewhat with 'bid to play.'

But what you've said here would be appropriate when it comes to the best in their fields. And not just with salary (other compensation, care packages, etc). But would 'competitive' be less appropriate than something like 'negotiatiable?'

Job titles have definitely become weirder/amgbiguous/watered down over time.

Instead of salary range, what would interest you? (firm, tech stack, vision?)