> To summarize, the main problem for me is to feel like a text processing machine, receiving mails, Jira tickets and chat messages as input and writing code as output, without the human interactions needed to make it more meaningful. I do not like becoming a kind of a remote developer black box. This sounds fantastic, where can I get such a gig? There's really nothing better than being given a more-or-less defined ta…
The Stress of Remote Working
41–47 of 47 posts
Re: The Stress of Remote Working
#42IMO, still much better than the stress of driving in rush hour traffic 2x a day to go to an office where everyone is looking over your shoulder all the time and won't hesitate to interrupt you, or the guy right next to you, or anyone in the room, for a quick, disruptive chat that everyone can hear.
Re: The Stress of Remote Working
#43I've worked remotely for a company in another state for the past 5 years, I can relate to many of these issues. On socialization, I can understand the feeling there, but for me the solution was to find social circles beyond work. For me I have my church community and also meetup groups with other developers in a similar field. If you don't have those already you will definitely be feeling the loneliness. Other things…
This should be the norm not the exception.
The impression that I get is that this idea of socialising at work is stronger in the US.
Re: The Stress of Remote Working
#44I am 100% fully, completely remote. I love it so much. I don't mind the office but the distractions are brutal and I never get momentum going. Plus the commute. Oh god, the commute. No, I think working remote is much less stressful than the office. If someone calls me and I don't want to talk to them, I don't answer the call. Responding to every ping and call as if your job is on the line is going to stress you out n…
Re: The Stress of Remote Working
#45IMO, still much better than the stress of driving in rush hour traffic 2x a day to go to an office where everyone is looking over your shoulder all the time and won't hesitate to interrupt you, or the guy right next to you, or anyone in the room, for a quick, disruptive chat that everyone can hear.
Re: The Stress of Remote Working
#46Earlier quoted context omitted.
It seems to me that one reason you are able to sit down and just get shit done on Friday is because you've been in the office Monday - Thursday to get context, discuss implementation strategies, understand the business goals, and ask/answer any questions. Then by the time Friday comes around you're ready to sit down and bang out code. But whether you're in the office or not while writing that code is completely ortho…
Ah, gotta have the requirements to get things done - right, I’m with you on that one. Where would all software dev be if we didn’t have requirements? ideally printed out and distributed in neatly packed binders. Seriously, do you really think that something that cannot be worked out over slack/confluence/phone call can be worked out in person sitting in the busy office with all kinds of distractions and stress caused…
You do realise you do actualy need some form of requirements, otherwise what are you doing, just writing code with no goal?
Granted it doesn't need to be a big up front document, but some of those slack/confluence/in person meetings will ultimately be around "so, guys/gals for this next proposed , feature, story (requirement), w/e, this is how I'm achieving it". Oh, and as for non functionals..
Having spent years working remotely with office focused teams, the nuances of these discussions are the ones that get missed by the remote attendee unless everything is set up correctly.
Re: The Stress of Remote Working
#47Earlier quoted context omitted.
You have never written a spec have you? Not only is the 5% important, as every "only 5% left" tends to be, you are completely ignoring possible developer questions.
I've read my take of shit ones. Most of the time, the writer hasn't bothered to think about it past the initial idea and needs the developer to help them understand what they want. That's not the developer's job.