The article mentions that this will allow the company to recruit from areas where pay is much lower than the Bay Area, but I wonder if this will affect the pay of current workers.
Atlassian tells employees they can work from home forever
11–20 of 462 posts
Re: Atlassian tells employees they can work from home forever
#12I hope those now remote employees have access to some good issue tracking, repo hosting, and collaboration/documentation tools. Else they'll be forced to use something like Jira, Confluence, Bit Bucket, and such, which suck...
lmao, i don't mind jira, but bitbucket sucks all the balls
Re: Atlassian tells employees they can work from home forever
#13Re: Atlassian tells employees they can work from home forever
#14It's a no brainer. We will look back at offices like we look back on Victorian warehouses. Edit: People seem to be agreeing but I'm getting downvoted. WTF.
Yep, Victorian warehouses but with snacks, slides and peers.
Indeed, they are comfortable warehouses but warehouses nonetheless.
Re: Atlassian tells employees they can work from home forever
#15uber laidoff american staff and is hiring in India[1]. This is not an exception, just a sign of things to come.
If you do ordinary CRUD coding at work in USA, I would seriously start looking at how to pivot out of that job.
1. https://www.businessinsider.com/uber-india-south-asia-stipen...
Re: Atlassian tells employees they can work from home forever
#16I hope those now remote employees have access to some good issue tracking, repo hosting, and collaboration/documentation tools. Else they'll be forced to use something like Jira, Confluence, Bit Bucket, and such, which suck...
I am directly responsible for Jira and Confluence admin/infrastructure on an enterprise level and once you know how at least Jira works, its a fairly powerful tool for PM's. I haven't run into many issues except during a migration where we knew we were going to run into issues. Atlassian's documentation isn't that good however.
>once you know how at least Jira works, its a fairly powerful tool for PM's.
I'm not a PM and I don't really want to get to know the ins and outs of an issue tracker.
Re: Atlassian tells employees they can work from home forever
#17Earlier quoted context omitted.
I am directly responsible for Jira and Confluence admin/infrastructure on an enterprise level and once you know how at least Jira works, its a fairly powerful tool for PM's. I haven't run into many issues except during a migration where we knew we were going to run into issues. Atlassian's documentation isn't that good however.
> its a fairly powerful tool for PM's That's the fundamental problem. Jira is sold to PMs and managers, not to developers, and it shows. Jira isn't an issue tracking tool, it's a work-tracking and developer-tracking tool masquerading as an issue tracker. The people who spend the most time with it aren't the customer.
You can set it up to be an issue tracker or you can set it up to be work & developer tracking. It's really dependent on how your PM sets your projects up.
Re: Atlassian tells employees they can work from home forever
#18I hope those now remote employees have access to some good issue tracking, repo hosting, and collaboration/documentation tools. Else they'll be forced to use something like Jira, Confluence, Bit Bucket, and such, which suck...
Apparently I'm in a minority but I love Jira for remote work.
Re: Atlassian tells employees they can work from home forever
#19Earlier quoted context omitted.
I am directly responsible for Jira and Confluence admin/infrastructure on an enterprise level and once you know how at least Jira works, its a fairly powerful tool for PM's. I haven't run into many issues except during a migration where we knew we were going to run into issues. Atlassian's documentation isn't that good however.
> once you know how at least Jira works, its a fairly powerful tool for PM's. I'm not a PM and I don't really want to get to know the ins and outs of an issue tracker.
I'm not entirely sure why you'd comment this in the first place? If you're a developer you simply need to login and look at your project, not really know much else except how to click issue buttons. I'm talking from an administrator standpoint. Developers also aren't the center of the universe no matter how much we think we are.
Re: Atlassian tells employees they can work from home forever
#20Earlier quoted context omitted.
I am directly responsible for Jira and Confluence admin/infrastructure on an enterprise level and once you know how at least Jira works, its a fairly powerful tool for PM's. I haven't run into many issues except during a migration where we knew we were going to run into issues. Atlassian's documentation isn't that good however.
> its a fairly powerful tool for PM's That's the fundamental problem. Jira is sold to PMs and managers, not to developers, and it shows. Jira isn't an issue tracking tool, it's a work-tracking and developer-tracking tool masquerading as an issue tracker. The people who spend the most time with it aren't the customer.
Interesting how perspectives differ. Having used Jira for many years, I think it's straightforward for engineering work, but particularly hard for PMs and managers. Why? On the engineering side, it's pretty straightforward to integrate into a lifecycle. But for PMs and management it's a nightmare because they still haven't gotten their birds-eye-view roadmapping / bulk editing act together. The usual issue I have with Jira is that the engineering team gets it integrated into their workflows, things work ok, but it's a continual challenge getting global rollup views to the business at large. We keep ending up with Excel, Airtable, or what-have-you high level views that then point to particular Jira issues for details (yes, we've used Portfolio).
I think this actually might be a fundamental issue that is masquerading as design issues on Jira's side, because when you're doing roadmapping views you want to continually refactor them to reflect better metaphors and realities, whereas when you're doing issue tracking you want issues to stick around and be solid entities linked intimately into the history of the software application. So tools like Portfolio have to juggle both ends.