News for hackers. Stuff that matters.
Re:Atlassian's new terms forbid benchmarking by beepbeepbeep1 on Sunday September 30, 2018 @06:24AM (#18105535)
[redacted by author request]
Re:Atlassian's new terms forbid benchmarking by Waterluvian on Sunday September 30, 2018 @08:31AM (#18105893)
I'm skeptical that there isn't another side of this story or at least less absolute terms used.

For example, maybe there's a push against everyone using all their own favourites everywhere. I can see a strong argument for, "please stop writing in Foo. We use Java, Go, Python, and C++. Pick the right one of those for the job at hand. We all benefit from using a common set of tools."

I'm not denying what you're saying. Just feeling a healthy skepticism that they "ban" languagues without a good faith objective.

Re:Atlassian's new terms forbid benchmarking by jsjohnst on Sunday September 30, 2018 @08:13AM (#18105847)
I’d probably stop talking on this thread if I were you. If your management chain sees this, you’ll have at minimum a conversation about using judgement when speaking in a public forum, at worst, your comments might be used as justification for disciplinary action.
Re:Atlassian's new terms forbid benchmarking by winslett on Sunday September 30, 2018 @08:36AM (#18105908)
His management has already nudged him to find a new job.
Re:Atlassian's new terms forbid benchmarking by beepbeepbeep1 on Sunday September 30, 2018 @09:30AM (#18106097)
Last comment

This was a bit back but not to far back.

Took a significant pay rise. elsewhere and got to work with some other ex atlassian colleagues.

Re:Atlassian's new terms forbid benchmarking by jsjohnst on Sunday September 30, 2018 @08:58PM (#18109307)
Disparaging your former employer might also be against your employment agreement and doesn’t make you look good either. Just giving a friendly heads up!