Atlassian tells employees they can work from home forever
cnbc.com
cnbc.com
I have a lot of calls that are mostly people in eastern time and central European time. It mostly works pretty well. We schedule calls typically between about 8:30 and 11 ET. Sometimes those of us in ET have a bit earlier calls than we prefer and the Europeans have calls a bit later than they'd prefer but it works pretty well. And we just don't expect Europeans to get back to us on the same day if we send them an email in the afternoon and they don't expect us to respond to emails in their morning.
Of course, if you're contracting the client may well want a more synchronized schedule.
I know someone who did this. If you're a morning person already, the 5am wake-up isn't terrible, and finishing work at 2pm means you get prime surfing time every day. Not a bad way to go.
I do this, but from New Zealand: 5am (in winter) is 10am in SF, so I wake up at 4:50am. I'm usually online by about 5:15am. I manage a software team, who are distributed across North and South America.
It works fine. There's more than enough overlap between all our timezones (some of my South America team have adjusted towards SF time, too, though I haven't asked them to). Many of my colleagues don't even know what time it is for me, which is kind of the idea - it makes it easier if I just stick to west coast office hours, then no-one else has to think about it.
The early starts do drag as winter goes on, but I have the first daylight savings coming up in about 6 weeks - that'll mean 6am starts - then another DST shift will make it 7am (but I'll probably do 6:30am).
I am a morning person, and though I wouldn't usually wake up at 5am by choice, I wake up and become fully alert quickly enough that it's fine.
Having a big contiguous block of time in the afternoon / evening is amazing. Even in the middle of winter I finish work at 1pm and I have ~4 hours of daylight left to do whatever. In summer I'll finish around 2pm and have 7 hours of daylight. It's like having a full day to do stuff, every day - provided I have the energy.
Could you explain what you mean by this argument?
Companies that hire young driven workers and have a good environment can get a similar amount of overtime and the work all the time attitude.
Thanks a lot for your perspective!
Looked around.
No chairs. This was in vast contrast to my employer at the time where lunch was a practical siesta.
Ok.. "so you take this back to desk?" I asked someone.
Yes.
QED that.
For context this was early 2000s.
Join a company in London. They have no seats. I'm not talking about free food or a company restaurant. Just having a place to sit with a table.
The place I just left had a wonderful rooftop terrace, overlooking central Helsinki, complete with an amazing sauna, a foam-pit, and gaming spaces too. That's a bit of an outlier, but there are a lot of amazing spaces across the whole of Europe.
Let's not imagine that widening a hiring pool is going to change top-down company cultures.
Why compete with FAANG trying to pay new grads $300k when you can pay an experienced developer from Europe $100k? I honestly never understood it.
I make right about $100k, which is pretty competitive for the area from what I can tell. It's possible I'm just getting completely fleeced, but I think that's unlikely.
But then again, I guess you can just play the "No true Scotsman" game and argue that I don't count as a truly great developer.
I moved from SmallTown southern United States four hours away to Metro City southern US for increased opportunities almost 25 years ago.
Gotta be happy where you are. Otherwise I guess you could go join the rat race and make the big bucks.
Beginning of 2020, I was 45 years old making A little more than the average senior SaaS CRUD developer made locally because of $bad_career_decisions. It was about $50K -$80K less than a CS grad would make a couple of years out of school working for a FAANG or even a second tier software company on the west coast.
Then Covid hit and the company I worked for had an across the board 10% pay cut.
Just dumb luck and being at the right place at the right time - I happened to have a combination of skills that let me slide into a remote position as a cloud consultant for BigTech.
Now I’m 46 working (virtuallly) along side 26 year olds making more than I do. Win??
I'm 31 making 3-4x what my father ever did.
And I get to sit in an office instead of busting my ass doing repetitive labor on an assembly line day in day out.
It's all about perspective I guess.
But, my mom retired from teaching after 30 years at 55 and my Dad retired from his factory job at 57. When they were 62, they were both getting pensions and social security checks. They’ve been married for 50+ years and retired for 20+ years.
I won’t be retiring before 67...
Again perspective...
My dad was a member of the steelworker's union for 25 years and then they closed down the plant he worked at and moved the production line to Mexico. He got to train his replacements. Then he delivered propane for a couple years, and ended up getting a job at Cargill on a line that made eggs for McDonald's breakfast burritos and Jimmy Dean breakfast sandwiches.
He worked there for 5 or 6 years, finally scored a nice job as the custodian at the rec center in town and planned to ride that out until retirement.
Shortly after his 57th birthday he started acting funny and was diagnosed with Glioblastoma [1], probably better known as "that cancer John McCain had". Died a year and a half later.
I don't think either or us is really adding much to the original conversation, but I am enjoying swapping stories nonetheless. Hopefully some of the bystanders are as well...
That being said, I was speaking to my CTO about hiring and I asked him, why doesn’t he hire in the Nebraska office, it would be a lot cheaper. His reply was “not really”. I know in my metro area, salaries for your standard experienced software as a service CRUD developers (no insult intended - as a developer that’s what I am), were making between $125K-$155K pre-Covid. I can only assume they were making about the same in Kearney and Omaha Nebraska.
Whether you agree with it or not (and I don’t), companies looking for great developers usually want them to be able to pass an algorithm style interview. Can you do it?
Personally, I consider myself to be a pretty good enterprise developer/architect but I wouldn’t get past the first round of an algorithm heavy technical interview without lots of practice.
Considering I tutored people in college that went on to work at the FAANGS of the world, I would guess so.
But also I guess it doesn't terribly matter. I got off that treadmill a long time ago.
Of course, top talent does exist in Europe but there's way less than the US.
I specifically mean EU countries by the way, Switzerland and London are the only exceptions -- and even then the US is better.
You don't. You spend those "millions" of dollars on ridiculously expensive medical care, on ridiculously expensive education, on car ownership, on... And in return you get worse infrastructure, worse medical care, worse ecology etc.
As for medical care, all half decent tech employers provide comprehensive healthcare coverage.
I don't know what you've been reading, but unless healthcare costs $200,000 a year (it doesn't cost 1/10th of that), you're better off in the US.
As for "worse infrastructure", you'll have to be specific. There's crumbling infrastructure all over the US and Europe.
Worse medical care is also a stretch. In fact, in some areas (heart attacks and strokes, for example) the US is a world leader. [1]
I'll remind you that new grads in the US are often paid substantially more than senior level developers in the EU.
[1] https://www.cnbc.com/2018/03/22/the-real-reason-medical-care...
Yeah, ain't that right. I've been programming for 20 years, worked as a lead developer/architect and have usually been among the most highly compensated technical people in companies I've worked for. And yet I have never seen anything close to the kind of money fresh grads get at FAANG.
On the other hand, if I landed a job paying 300k-400k USD a year, I'd probably just retire after 4-5 years.
Most are basically forced to. We're not US citizens, we don't have a right to work in the US.
Even with great communication and good management, having little overlap during the day for realtime conversations made it hard for me to feel like we were a well-oiled machine, especially with so much of the product changing on a daily basis. It’s very much a complex decision to make, in my opinion.
I’m sure there are people who’d work 13-22 but I’d bet a substantial sum employee churn would be consistently higher.
Wife used to work for a company with an office in Yorkshire where working hours finished at 2pm (7-2 no lunch). Horses for courses.
HN does seem to bias towards morning based extrovert urbanites in its group think. It’s nowhere near as universal as you might think.
The biggest time gap team I've worked on was east coast US and China.
Great. 12 hour gap.
US team changed to being in the office, or at least online, at 6am. China team started at 11am in China. Roughly a 3 hour handover time.
It worked.
But for some was a toil. When interviewing and taking pains to point this out, the usual response being "Ok, no problem" but then a few months later seeing someone looking visibility drained wasn't good. Helped them find an alternative role. And some loved it, especially the reduced traffic and sense of community.
During this handover period everyone had a webcam on their OC, a fair amount of travel between sites which all participants were excited for on and three US-China marriages happened over the years.
Great for some. Terrible for others.
It did mean that my mornings were totally free and I could get a lot done - so it swings both ways, but outsource everything to Europe isn't the panacea some people assume it to be.
I am pretty sure even FAANG dont pay $300K for fresh grad.
Also $200K is on a higher end and depends on other offers, etc. Average is around $180K.
It’s a flywheel. Investors give preferential to local teams, which leads to teams having to hire local, which reinforces the prices. The big tech that can’t really move or adapt to a more remote workforce pushes the salaries up, local cost of living rises, and the cycle continues. The cost to move from that culture is extremely high, so the salary differences end up being “justifiable”
- 5 weeks paid vacation per year(6-7 if we skip regional holidays)
- 13th month salary (that is independent from other bonuses)
- Paid overtime the minute it goes above the agreed upon working hours. 1.5x pay for night or weekend work.
- Maximum hours per week the must not be exceeded.
- Protection from the employer wanting to constantly monitor me, do drug, medical, lie detector test and such nonsense.
- Co-Paid pension, health. disability, unemployment etc. insurances
- Minimum contract termination notice periods and unjust termination protection
- Paid sick and paternal leave
- That other employees, who might not happen to have a as sought after job and thus negotiation power as me get largely the same basic benefits as me nonetheless.
I'd never work for an US company for a 100k given all the stuff I'd have to compensate.
You didn't make it clear in your post, though I think that must be the angle you're coming from.
Likewise, mandatory pension contributions (employee and employer) in most of Western Europe exceed 20% of income (upwards of 30% in some cases), as contrasted to 12% in the U.S.: https://www.oecd-ilibrary.org/docserver/pension_glance-2017-... Who in the U.S. contributes 10-20% to their IRA or 401(k) on top of FICA payments? It's not even legal to make such large contributions pre-tax. (Some of us are privileged enough to make up the difference with higher salaries; a smaller fraction of a higher salary let's us contribute more to retirement.) Note that employer contributions aren't generally reflected in salary figures, and in some European countries employer contributions exceed 20%.
Five weeks vacation is a legal minimum. Most companies I worked for here in Denmark will give you six. It’s technically not five weeks, but 25 days.
Also many bills are due on the first of January for the whole next year e.g. insurance. So it was kinda like a holiday and large bill windfall, but it wasn't additional to salary.
That was just one company, maybe other countries or employers are different.
- 14 payments (extras in June and December)
- 12+1 in December
- 12 + 2 x 0.5 (one extra in June and the other In December)
I believe dates were pick to match Xmas and Summer Holidays, two big spending anomalies
Anyhow you always negotiate yearly gross.
No, it's not. It might be in some European countries, though.
Also, not all of those apply to Norway at least and some are provided by the government.
It is not like the possibility to work remotely for US companies that in absolute numbers pay more than the local ones is completely novel. But at least in my circles pretty much no one is interested in doing so.
Me making 150, 200 or 300k actually has fairly limited impact on my life. Everyone else getting the same benefits or not has, in a way not easily compensated by salary.
the point is you get all these benefits and on top of this you get several times higher salary (I'm from Europe myself originally for what it worth).
I have absolutely no doubt that if you want to maximize personal compensation and benefits, the US is the place to be. Nothing else comes close
But originally this threat was about "Why compete with FAANG trying to pay new grads $300k when you can pay an experienced developer from Europe $100k? I honestly never understood it."
I doubt that a statistically significant amount of new grads get 300k in compensation plus those kind of benefits. I haven't spent a whole time researching but I couldn't find anything backing this up. E.g. it seems that you need to stay at Google 5 years to get 25 days vacation and entery level total compensation at FAANG being more in the 150k - 200k range.
On the other hand as an experienced developer making more than a 100k in just salary plus at least these benefits is not that hard in Europe if you are willing to move or find a remote job.
From all I heard or read, outside FAANG, the financial industry, and certain hotspot, the compensation and benefits within the US go down quite considerably and the difference to Europe is still big, but less exorbitant.
So sure, if you come in with full FAANG (many / all? of which have had engineering teams in Europe for a long time) style compensation packages plus benefits you will be able to attract many Europeans, especially if they don't have to move. But then we are quickly back to square one: Why compete with FAANG?
And again, I'd argue a big part of the reason why US companies can offer these much higher compensation package to positions like software engineers is because they save it on lower end jobs and there are fewer regulations for the common good in place that would cost them money. For some, this makes US companies a non-starter independent from the individual offer.
Practically, the American companies usually employ Europeans through their European subsidiaries/branches (which to local government look exactly like local companies).
Because $300K vs $100K makes very little difference to them when they're printing money. One idea from a top dev can make the whole thing pay itself and then some, for years.
ISPs and wireless carriers are the most profitable companies in the USA all with 60% gross profit margin if you look and any of the financials.
When my friend was younger he worked for a cable company, where he did installs. He said the capital costs were usually covered in the first month of service, and everything was gravy after that.
So. What if in another country instead of extracting the profit, they put 5% of it back into the infrastructure. I suspect you would have what a lot of europeans have - fast internet. And what if you didn't take as much profit? You would have the other thing europeans have, cheap internet.
I mean, I like capitalism. It works! But I think there are some things that are out of whack.
That it also comes with a substantial pay rise, zero travel and the opportunity to work on stuff I actually find interesting is just a gigantic cherry on the cake.
It was by far the largest factor in getting me to go look elsewhere though not the only one.
I was frank (though polite) with my boss (since I'm a lead and I have zero intention of ever returning) about it - they are going to haemorrhage their senior developers and I know stuff he doesn't yet about others leaving.
In this context it means slowly bleed out developers from the teams until all the vital parts have left and you have a husk left.
It's also commonly used when referring to money when an unexpected event has led to losing a lot of money unexpectedly.
When our team first arrived in the office, a colleague walked over to them and said something along the lines of `let's get some sunlight in here' before opening them to reveal the deception.
Boss simply couldn't understand that someone would choose to sit in a quiet, miles away from anyone else on site, air conditioned office even without windows.
Honestly, never bothered me, lots of plants and replacing the strip lights with 5000K bright LED's for the overheads and some LED lamps dotted around it was only the same as working at night at home.
Hands down the best physical work environment I've had outside of work from home.
I joked at the time I'd program in a cave if it had good internet and was quiet.
Having said all that, I really hate Jira and Confluence and would not like being a developer working on them. The front end is such a mess, I hate to think what the back end looks like.
“Turn the HN angry mob mode off - it’s not helpful. We’re all in this together.”
When asked by non technical people “Should I install this app? Is my data / privacy safe? Is it true it doesn’t track my location?” - say “Yes” and help them understand” https://news.ycombinator.com/item?id=22986426
And here’s an article:
“Australian tech darling Atlassian is among the five private companies that helped the federal government build its COVID-19 contact tracing app.”
https://www.innovationaus.com/atlassian-and-the-covidsafe-te...
The fact that they didn’t wait for Apple and Google’s contract tracking API and instead went for an app that needs the phone turned on and in the foreground for it to work properly is the reason why nobody is using it :headdesk:
I'd sooner work the curb while living in a coal bunker
That's the best way of putting that I've ever heard. Stealing it.
Every engineering org has things like this – features that they know the customer rightfully wants and should have, and seem to the customer to be simple, but in reality bring your eng org to its knees.
I've certainly pulled my hair out a million times with Jira, but TBH I'm extremely impressed with their redesign. They've really scaled back the complexity IMO while still giving my team the customizability we need (we started on Trello and quickly hit roadblocks).
I was responsible for bring Jira into my team at 'megabank' not long after it launched around 2003/4, because the alternatives were horrific to set up and use. That was pretty much it.
You want to split stories and leave sub-tasks behind? Sorry, that's not Agile, so we're not going to make it easy.
You want to Subtask estimates to accrue to the Story estimate? Sorry, that's not Agile, so we're not going to make it easy.
You want to customize the sprint report based on custom labels? Nope, probably not Agile.
You want to plan the capacity of your team to see how much work you should take into an iteration taking into account vacations and partial availability? Sorry, that's not Agile, so we're not going to make it easy.
And on and on, with very basic needs...
I’m shocked how naive people seem to be in these threads about remote work. There is tons of remote work. There already has been for decades. It’s called outsourcing. The reason you can’t find remote jobs in high wage countries is because no one would be crazy enough to pay those wages for remote workers when they can find the same level of talent for less than half the price.
So that person, even if they are highly skilled, will instead have to work at a low skill job for low wages . Not because they have lower skills, but because their government is looking out for the wealthy asset class as opposed to the working class and those other countries(like India) do not legally allow US citizens to live and work in their lower cost of living country.
I know of many companies with outsourced talent, that have a local office in the US where clerical workers and the janitors of the building make higher wages than the overseas outsourced engineers. And those clerical workers and janitors do not make enough income in the US to have decent housing or health care. They are forced, by the laws of the lower cost of living countries, to stay in the US and live poorly.
Hot desking is your CEO standing up and saying "I got nothing" when asked how to increase profitability.
a cute one liner, Regularly scheduled video chat meetings are anti pattern for remote work.
That's my feeling at the moment. trying to schedule people around the world to do video chats is a lost cause. Its also trying to cram the office experience into remote work. Video chats are a waste, no one is engaged, probably because most meetings are useless. Like stand ups, who's listening? We were only engaged becasue its socially awkward to not be in person. Now, I can turn my camera and mic off and stretch until I hear my name or just do my work. There's my stream of thought and slight rant.
The fewer people out and about, the less opportunities for the virus to spread.
Yes, it's messed up, but it's better than the alternative: Everyone going about their lives like normal and spreading it even more.
I honestly don't see any better alternative.
And since most of those jobs aren't usually salaried, I think they'd all welcome being able to go to work and continue to earn.
Let's hope everyone can choose the job they want and have the benefits that come with it.
I know plenty of blue collar workers that would never want to work behind a desk, and also know plenty who started earning a lot of money at 18.
I find your "blue collar victims" mentality very strange.
I'm pretty sure this is what is regarded as "progress" these days... :)
Given that some people are not working from home, surely it's strictly better for them if the spread of the virus is reduced?
That would be messed up, but what is actually being said is “Given that you need to go out into the danger, its good for you that I don't go out and needlessly increase that danger.”
In fact, I've heard the exact argument made from the side of workers that have to go out into the danger—whether to deal with it directly because thet are in healthcare, or because they work in retail in essential sectors, or whatever—that out of respect for their safety, people who don't need to be out magnifying the danger shouldn't be.
Perhaps even some kind of comfortable spacesuit you can just live in all day will help the blue collar workers.
I'm only half joking. I would like to think there will be a strong push for a much more hygienic society in the future. A corona vaccine will never completely solve the problem, and who wants to even get a traditional flu. I suspect these social distancing measures are just how we live now.
I'm sure right now, lots of people who dreamed of wfh and couldn't have tried it and learned that it might not be the right arrangement for them.
Also, I find it hard to accept that people who pick certain jobs out of preference (not made to chose out of circumstances) like "blue collar jobs" would expect working from home. What does it mean for a steel worker to be working from home? A warehouse worker? A painter? A housekeeper? A cook?
I do agree with the rest of the sentiment you shared though... The sense that some people who are enjoying the current state of affairs want others to return to normalcy while they are living the exception.
This isn't a decision that could be rolled back easily or without significant capex. Companies that are doing this must be thinking it's a long term thing.
Or they were thinking along these lines anyway and this was the push to get them over the line. Or they're putting real estate expansion plans on indefinite hold in the case of "you don't need to come back in the office but you can."
Similarly, I suspect that the people moving out of NYC aren't those with a mindset of "I could never live anyplace else on account of the opera." In many cases, they're probably people who were toying with idea already and this accelerated the process.
Also you might think "my company doesn't cut salaries", or "I just won't say I've moved". That might work if you stay at the same company for the rest of your life, but if you move jobs there's no way you'd get the same deal.
Often times, there's plenty of places that are _totally_ within commuting distance, but really aren't. Do you think Facebook would lower someone's wages for living in Davis rather than Palo Alto or San Jose?
Yes of course. You only think that would be surprising because until now companies can tailor salaries to the office location, based on the reasonable assumption that most people will live nearby, and the annoyance of commuting long distances will roughly cancel out the lower cost of living.
As soon as the annoyance of commuting is removed they will definitely take into account your cost of living.
I work in hardware development, and moved an entire lab to my house. I could think about what it's costing me to maintain this space and pay taxes on it, or think about the fact that I still have a job. And it would be hard to imagine this work being done in a lower cost region.
We had 4 people working from home until the school year ended. But the kids are old enough to be reasonably self sufficient during the day. It's actually been pretty easy.
Younger colleagues who are living in starter homes, or apartments, and have small kids, are having to figure out more compromises. Places with extremely expensive real estate also have higher salaries, at least for tech workers, so those folks may still be ahead of us Midwesterners.
Even before the COVID, there was a trend towards people buying a bit of extra space to set aside just in case their careers turned towards consulting or other similar work.
It's anybody's guess what the future holds.
On the other hand, if you're in a studio city apartment, don't want to leave the city, and can normally walk to work, renting a co-working space or a larger apartment obviously isn't a great financial deal relative to going into an office. That said, I doubt many companies will eliminate their offices for people who want to go in. But it may be a while. And I know people moving out of the city--at least some permanently.
It's not going so far as to pay us enough to offset the rent of a dedicated home office room, but they're still quite nice perks. The Australian government is helping out quite a bit too - there are many additional benefits this tax season for those who are working from home.
That's time I can't get back or do anything with - compared to the remote position I just accepted (on higher pay ironically) I'll take the nominal increase in costs of working from home over that, intention was to buy a house next year and convert the garage into one half motorcycle workshop, one half office so I'll just accelerate those plans potentially.
Edit: this comment was a bit sarcastic, just in case somebody didn't get that.
Btw, currently my job is a 25 minutes subway ride away, so... So and so. Not a lot, to be honest, I don't have to drive and the monthly public transport subscription is fairly cheap (~39€/month).
My office is 12 minutes "run-commuting", there are a couple of good restaurants there, if I make a mess on my desk in the office, my desk at home is still clean, I got four whiteboards, I am not bothered by the neighbor's Amazon package, nor coworkers as they are all working from home.
Now granted, if I had to come 2x1 hour by car, I wouldn't do it, but a 30 min walk in the morning is actually pretty nice
I really miss real whiteboards.
The only thing worse that being on a software team that has no whiteboards, is being the only remote person on a team that has whiteboards in the office.
I’m also not convinced that there is a tool that when mastered can provide the same fluidity, but I can claim that, and to the contrary I’d love a recommendation.
It’s definitely not the same as drawing on a whiteboard, but I’ve found it useful for explaining abstractions.
(That said, if whiteboards are important to a team, I would imagine there's software for sharing tablet drawing. I've heard there is. I just haven't investigated.)
You can get an entry-level Wacom for < $100, and it scratches the whiteboarding itch for me in a lot of situations.
It's been _rough_. I knew going in that I hadn't joined a new company in 5 years, so it'd be difficult. But this has been a whole different level.
Nearly 6 months in now and I still don't feel like I've meshed with the majority of my team, only one or two people who are just extra friendly, and forget knowing anybody outside of my team at all.
I rarely get pings from anyone asking how things are going; I usually wind up needing to do that myself.
I've never been a very extroverted person, but I'd definitely prefer working from an office (in obviously better circumstances) during this period of on-boarding and readjustment. I feel so isolated right now, which is completely opposite of how I think I would have been if I were still at my last role but during this environment.
I think in 6, 12 or 24 months possibly longer for some. Many will regret when they look back they didn't realise what was really going on with the company. They just heard from their contacts and also heard what people wanted them to. They got stuck in a silio.
The new section of the office where a team was parachuted in which somehow has an impact.
How do people expect to form casual but often extremely useful contacts with the people who really know what's going on in other teams, department, divisions or other locations?
You won't hear the gossip from your workmate who works early or late, the postroom, the security guard or receptionist about that out of hours meeting the management team had or whatever.
How will you really know of you haven't been offered a poisoned promotion?
To a degree your rely on being told the full picture by those with the overview. Which is likely to be the management. Which no doubt may happen in many places the majority of times until the one time it really affected you or your team.
For example a group of us headed in to the Riverside sub office on the outskirts of London by the Thames yesterday. For aircon offices and a r oriverside pint at lunchtime as the UK had its hottest August day in 17 years.
Straight away those who caught on a group of us had met up in the office started to wonder why? With a number of messages and calls wondering what we were up to.
While we bonded and had a change of scenery. Some of those at home, for no reason got paranoid.
The reality is that there is a real advantage in working in person. Whether it’s increased trust, communication, or lower friction. We could see it pre-COVID in a he fact that there are barely any successful remote offices (let alone individuals).
This means that employees would see advantages to coming to work, and those that don’t would fare worse in promo and productivity on average, bringing the equilibrium state back to the office.
And that presents a long term problem.
There is no inherent advantage to "working in person." Lower trust or communication or higher friction are not inherent to working remotely, they are the product of poor and overconfident management (at least in tech, given our forum here) and can be seen in any number of environments. You can replace "working in person" with various other specious truisms like "having an organized workspace" or "having weekly status meetings" or "using agile methodologies" and the two sentences above will be likewise banal and true only in specific instances.
Most technology work can be done remotely, and I'd argue should be done both remotely and asynchronously (many companies recently forced to do the remote piece are still are holding dearly to 9-5 and constant meetings), unless there are specific use cases that require more in person synchronous efforts (and to be sure this is the case in some cases, especially when specific hardware must be used for instance). The perception that there is something "better" about 9-5 in-office work is more a product of tradition and resistant over-management than inherent advantages to either setup.
I really miss whiteboard sessions and and being able to chat without lag.
I wish there was a way I could make a bet that 100% remote will NOT become the norm. Given how contrarian this opinion seems to be, surely there must be some way to profit if I am right?
I think it's pretty obvious that 100% will not become the norm. But maybe 50% for some types of jobs? And some number of smaller companies will go 100%? Those seem plausible.
Similar to the studies with brainstorming where people doing it in a group come up with fewer and less diverse ideas than people brainstorming individually and collating the results.
it depends what their goals are. having worked in-office and remote for the same company, it's way easier to get shit done in the office. at least if you're reasonably extroverted/persuasive/bold. there are so many times I was able to walk up to someone's desk and spend ten minutes to save multiple weeks of protocol and runaround. partly because it's easier to apply pressure, but also partly because communicating face-to-face is so much higher bandwidth. but if you're remote you're easier to ignore, and a lot of office workers are very good at ignoring people who want to create more work for them
but the flip side is it's way easier for remote workers to fade into the background and hardly do anything. a skilled developer can emulate a mediocre developer while working a fraction of the hours. a skilled manipulator can "work" a fraction of the hours managing expectations and barely produce much of anything. plenty of people will figure out how to automate their jobs and just never tell anyone
there's this idea that remote will benefit introvert/aspie types because it's so word-focused. you have few face-to-face conversations but you write tons and tons. but really, apsie types will produce reams of literal-minded descriptive and often very helpful documentation and discussion, while people-people types will manipulate their image to appear very legibly valuable and come out ahead more often than not
my honest opinion for awhile is that remote is going to a massive efficieny drain on big tech companies and startups doing stuff that's easy to phone in like webdev/saas/whatever, such that if you founded a small committed colo team you could probably outcompete them in whatever domain you want even without any special edge
Let's ignore how you interrupting someone cost them potentially hours of productivity.
I agree face-to-face is higher bandwidth for easy/simple topics. "Bob, what's the mainframe password" is easier shouted than written, and the reply likewise (assuming Bob knows it by heart).
It gets tricky when the topic is complicated or when Bob is distracted and confused. You might get a half-assed dismissive and incomplete answer (which you may or may not notice), or it might take Bob much longer to figure the answer out than if you had messaged it to him.
The quality of your communication depends on many factors, and your perception may not necessarily match reality.
there were more than a few times when the schedule slipped by months because someone outside the project delayed something by weeks. those kinds of issues I never had when I was in the office because I could get what we needed through force of personality. but outside, you have to go through process, and process is inefficient
seasoned remote workers might counter the org was dysfunctional (a charge I will not deny, hence why I left) but they don't have solutions other than more process. because remote depersonalizes work interactions, they have to layer on policies and documents. it's fundamentally a bureaucratizing force
I'm curious as to what you base this statement on. Game theory is modeling of strategic interaction between two or more players in a situation containing set rules and outcomes. Did you create the actual model? Is there an insight you mind sharing?
Piecemeal is more difficult but it's basically what my company was pre-COVID and presumably will be again (with probably a lot more remote) posy-COVID. It does mean the people who are co-located need to have the discipline to treat decision-making, etc. as if everyone is remote.
It probably helps that we're a somewhat larger company so most things are piecemeal anyway--people working together are in multiple offices even if they're not working at home.
I mean, even Philly (where I live) has seen somewhat of a resurgence (especially relative to the MSA at large), despite a lot of jobs being outside the city.
I think we'll see the hypergrowth of the tech hubs drop off. I think cities more broadly might slow growth as millennials age into parenthood and that might be accelerated by recent events making cities more broadly seem less welcoming.
But I'm not sure that jobs will be the main driver here.
That's the thing though. For the next $few years, they offer nothing but a higher chance of infection. All enjoyable things are closed
Streets are bustling and patios are pretty full again.
I think this whole thing is overblown and we will return to normal sooner than people think.
Presumably big companies moving jobs away from cities will have some impact.
I'm aware I reduced the two sides in summarizing them above haha.
That's the problem, no?
For me not fan of city dwelling and even more now with cities having the highest cases of Covid, at times there are not so peaceful protests and it's more expensive to live in close proximity to others.
Will probably see a substantial rebalancing between metros though, with people fleeing super expensive ones to cheaper ones.
I might be interested to moving to a nicer city probably stay slightly away from the expensive side but moving completely away from City is difficult for a lot of families who have enjoyed that life and its perks.
If you can sleep or working during your two hour automated commute, it would be a game changer.
No matter how much easier doing unnecessary work is, it still doesn't make sense.
Sitting in an enclosed space for 3 hours is still sitting in an enclosed space for 3 hours.
This bubble of tech workers aside, most people don't want to sit at home all day. I like going somewhere to work where I can socialize a little or a lot on a given day, depending on my mood. Communicate with people in person when I don't want to deal with the online trade-offs. Go to lunch with people. Leave my work at work rather than have it invade my personal space.
I don't think covid has turned me into a minority on that. I'm dealing with this subsistence level of contact because I have to, but when this is over the companies that can offer me a comfortable work space will have a recruiting advantage over the ones that can't. I'll still favor being in my city.
People who move to cities just for work and who are on the edge may elect to move out.
But I was born in a city, grew up in the suburbs, lived in small university towns and now I'm in a big city again. I think I'll always want to live in a city -- or at the very least in any outlying cosmopolitan areas with easy access to the city core. COL be damned -- I'll make it happen, even if I have to live in a smaller space.
Else they'll be forced to use something like Jira, Confluence, Bit Bucket, and such, which suck...
Atlassian's documentation isn't that good however.
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.
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.
When you're working with Python, Jira will render __init__.py as an italicized version of _init_.py even when you put it in monospace with the {{braces}}. If you're talking more abstractly about algorithms, O(n) turns into the letter O followed by the thumbs down emoji.
It's a good thing no one uses Jira for software projects because that'd be really awkward!!!
A non sane place would have 20 obscure mandatory fields per ticket, require the ticket to go through 10 different states that makes no sense, and last but not least, every click would take a full minute to load the page.
I'm not a PM and I don't really want to get to know the ins and outs of an issue tracker.
Also, looking at my project is a pain since my tickets are outside the sprint and I either need to go into the backlog and scroll a bunch, or use a custom search.
Collaborating over JIRA on a video conference is PAINFUL AF. A lot of time is spent just waiting for the UI to respond. It is completely unacceptable.
The current implementation of jira and confluence I’m using is worse than having _no_ ticket tracking and documentation system.
Because if it didn’t exist there would be the impetus to implement something. But we just kinda barely limp by with what we have.
It’s so barely functional that people actively avoid using it.
I’m fully aware that the company is to blame and not necessarily atlassian though, as we have a number of plugins and random custom fields.
One of the most dangerous things about jira is that it tries to be everything to everyone and people get carried away in the customisation believing they need it. It slows everything to a crawl and leaves you inundated with mandatory fields and a nightmare of matching stories with sprints and estimations in order to bring a bloody task in.
Life was better with rt and mediawiki.
Also the mandatory fields are definitely a per-organization thing. At my org we have I think 3 mandatory fields, which are the project the ticket goes under, the title, and the description. In many cases, "migrating" from JIRA to JIRA but 90% of the features are disabled would probably be an improvement.
... I suppose that might be the main difference between people who hate JIRA and people who find it a little bit clunky but generally acceptable: people who mostly have the baseline stuff happen automatically are fine with it, and people who spend a lot of time interacting with the web frontend in repetitive ways hate it.
I ended up forcing my slack bot to issue POSTs to Jiras API out of frustration.
The two workhorses of my integration are two methods named jira_get and jira_post.
function jira_get {
ENDPOINT="$1"
PAYLOAD="$2"
URL="https://your-org.atlassian.net/rest/api/2/$ENDPOINT"
QUERY_STRING="$(jq --null-input --raw-output --argjson x "$PAYLOAD" '$x|[to_entries[]|((.key|@uri)+"="+(.value|@uri))]|join("&")')"
curl \
--silent \
--request "GET" \
--header "Content-Type: application/json" \
--user "$JIRA_USER:$JIRA_TOKEN" \
"$URL?$QUERY_STRING";
}
function jira_post {
ENDPOINT="$1"
PAYLOAD="$2"
URL="https://your-org.atlassian.net/rest/api/2/$ENDPOINT"
QUERY_STRING="$(jq --null-input --raw-output --argjson x "$PAYLOAD" '$x|[to_entries[]|((.key|@uri)+"="+(.value|@uri))]|join("&")')"
curl \
--silent \
--request "POST" \
--user "$JIRA_USER:$JIRA_TOKEN" \
--header "Content-Type: application/json" \
"$URL" \
--data "$PAYLOAD";
}
Then if you want to get the available transitions, and required fields for those transitions, you can do ISSUE=PRJ-1234
ISSUE_JSON="$(jira_get "issue/$ISSUE/transitions" '{"expand":"transitions.fields"}'
TRANSITION_NAMES="$(echo "$ISSUE_JSON" | jq '.transitions[].name')"
and then given the transition in question, you can look at the fields required for the transition, and figure out where you get the data that goes in those fields normally. Any time the data that goes in those fields is obtained through a rote process, you automate that process, and then prompt for any fields you can't get in an automated fashion (e.g. "signed off by" you can fetch the reviewer names from the github api for the associated pull request).But yeah, a slack bot that issues requests to the JIRA api is a perfectly workable solution, and I think you'd be surprised at how much of a quality of life improvement you'll get by continuing to add capabilities to it that reflect your specific workflow.
The problem is that this anecdote is not even remotely surprising. I've used JIRA and/or Confluence at three employers and all three had wildly different, and awful, configurations. I have never worked with any technical folks who loved either, although I think on the whole Confluence is slightly better than JIRA.
I thought the same thing for a long time - that Atlassian makes decent products that are often implemented poorly - but the problem is, at what point does it become Atlassian's fault for making products that seem so easy to implement so badly that developers will go out of their way to track work in Excel instead of JIRA?
A couple of mandatory fields (department, team, application), that were manageable and that's about it.
They even the JIRA during my tenure there. Made user sessions last for a while instead of being disconnected every 15 minutes.
Feel free to email me if you think your company may be open to using outside help to clean things up.
Incidentally that conversation started with the suggestion to bring Jira into our already bloated set of services.
I'd rather learn a completely new system every 90 days than use JIRA.
On a typical day moving tickets around , reviewing everyone's items and confluence with its WYSIWHG editor only approach is 20% of my day gone.
Just making the UI non blocking for every single action would double my productivity. Their mobile apps are definitely better than web, so it is not like they cannot build decent interface and application, The web app just smells of legacy and debt to me.
Even if its because of customizability they provide, it is really on them, to approve all sorts of plugins and for all straitjacketing they and/or AGILE ( as typically implemented) does to your development in the name of structure, restricting some of this customizability would not have hurt product more.
Ultimately like any other SaaS business they serve the buyer and not the user. They are interested in what sells more, more often than not it does not intersect with what the users need. Customization sells, saying NO doesn't in enterprise.
I guess we should be thankful they are not IBM or Oracle and build your kitchen sink and neighbours too
I am tempted at least once every few months to just build a better interface and frontend which isnt' crap. Management is not going change from JIRA. Developers / users would happily pay out of pocket for a saner interface which helps simply manage their items without fuss, most people don't really care about the backend and the fancy reports, burndown charts for the most part, those who do can use the official app .
I'd rather use a tool that is flexible by default than use a rigid tool that you need to change every six months.
Then they decided that they wanted to look serious, and reduced the meme size to 32px. That’s when the product fell out of fashion, because it was just like Slack with fewer features.
Thousands of years of linguistic progress out the window...
One day I need to have a beer with these people who say Jira is fast. I've seen everything from "unremarkable" to "If we don't reboot the servers on Monday then nobody can work after 10 am on Friday". But never, ever, fast.
I've used it for 6 months - it's garbage. At least, absolutely ZERO times better than Jira as an overall productivity tool.
I can't tell you how many times issues have never loaded (see: blank screen), painstakingly prioritised lists of HUNDREDS of issues that have had their ordering completely scrambled, to name two off the top of my head.
If you hate Jira, think about whether it's the thing you hate that you're used to. Because you're absolutely going to be trading for a NEW thing that you hate, and have to learn to use from scratch.
If anything wfh means spending more time in your home neighbourhood, so you’re going to need more amenities closer by - which are generally found in cities.
That's deep decrease (~33%), I fully expect the effects to show up starting Q4.
Landlords are stubborn beings always thinking they can rent easily and for more. Gotta take a beating with the property being empty for weeks/months before they adjust to reality. (Lettings agents don't care about waiting and pushing tenants out, they make fees either way).
Expect multiple hits downward over the coming year(s) as layoff benefits come to an end, personal savings dry up, evictions are reinstated, properties are foreclosed, etc...
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...
no, not all parts of the country will be so hardcore about remote work into the future. For example, I see Utah (which leans heavy into enterprise SaaS and already booming in tech) to continue as normal except with masks or a little more space between desks.
If some businesses do better in person, then they will make it happen somehow.
2. extremely portable work goes abroad
Why would someone go through the hassle of hiring and bringing a H1B at higher salary in USA when they can hire the same person in India at much lower cost.
Why do so many companies hire at a higher salary in the Bay Area when they can hire the same person anywhere else in the US at much lower cost?
1. Reduce foreign workers in the US
2. Allow WFH from anywhere* thereby reducing total cost of workforce domestically
*remember things are never done to be awesome for the employee, just the companies bottom line, if both happen then that is fine too.
Government job, so they wouldn’t outsource me, but you could easily give someone else a login and that is all it would take to replace me.
Would be scrambling were I in the private sector in this type of job.
If a company has had somebody stagnant for years (many years), they're not going to be replaced for cheaper. The crash might cancel the last couple years of inflation at most.
Also, the employee is much more experienced now (could go from junior to senior over 5 years). Will the replacement be equally experienced or starting from scratch again? A fresh experienced hire is certainly more expensive than what the employee was originally earning.
What I'm asking is: Do you think another type of developer (e.g. Systems programming) will not need to pivot?
1. Hey, let’s hire cheap Indian workers!
2. WTF, we didn’t expect all these time zone and quality control issues!
3. Let’s onshore again!
Believe me they’ve been trying to do the Indian outsourcing thing for a looooooong time. It doesn’t work as well as imagined. The Indian developers who are as good as their western counterparts don’t stay in India.
If high COL located companies starting going fully remote, it's a huge opportunity for workers in medium or low COL. For workers still determined to live in a high COL, it will absolutely put downward pressure on their salary. Their labor market is being exposed to a lot of competition that wasn't there before.
I think if this trend of going fully remote holds up, it becomes much harder to justify living in an expensive city, especially as workers age.
There's still distinct benefits to big cities. You can order stuff online fast, even groceries. You get good Internet connectivity, which is a thing that you need for remote work. Lots of services around.
Define “big city.” I live in a medium-sized city in a low cost of living area and my house has AT&T Fiber, Google Fiber, and cable available to it. I dare say that’s better than most people in the Bay Area have access to. And yes, Amazon delivers here too.
I'm sure that the reduction of CoL opens up plenty of financial room for a car, but it's a whole extra set of things to have to worry about that I personally would rather not.
Further corollary: more workers will be concentrated around 2nd-tier hubs where their wages will be lower than 1st-tier, but higher that median wages. 2nd-tier median wages will then drive up housing prices which will rinse & repeat COL increase trends seen in the Bay Area.
Hopefully these other hubs will have better development zoning & housing policies than San Francisco / Bay Area.
Edit: People seem to be agreeing but I'm getting downvoted. WTF.
I agree, but mostly because high speed internet connections aren't that widespread yet.
Now, the plan is :bring everyone back to the office, despite clear better kpi and more output etc.
Old managers just cant let go.
If I send you an email with some pithy questions that you need to answer for me to complete my task, you should respond to them. If you don't respond to them, even with a "I can't help you", then you aren't hiring people who are good at communicatimg.
If the answer is "I'm busy right now and I am not responsible enough to remember all of the people I need to follow up with to at least give them a pointer of who could actually help", then your company is dysfunctional.