Live data from Hacker News

Best practices for remote software engineering

cacm.acm.org

191–200 of 205 posts

Re: Best practices for remote software engineering

#191

Earlier quoted context omitted.

So, first, let me say that, yes, that sounds like a bad workplace. Second, just to point out (I'm sure you realize, but just in the spirit of the parent comment), no agile workplace cares about the load of tasks dev has. Are they busy doing valuable work? If not, is there valuable work they could be doing? That's it. If yes to the first, no problem. If no to the first, and yes to the second, no problem, "hey, I've go…

I agree that a True Agile workplace would not care about making sure that everyone looks busy. So far 2 for 3 of the scrums I've been involved with have degenerated into micromanagement and pointed questions if there wasn't constant process, even if that came at the cost of overall velocity. Maybe just bad luck and bad workplaces, but I am increasing skeptical that there are any true 'Agile' workplaces.

I don't think there's a clear definition of what a 'true agile workplace' is.

That said, agile is, if anything, a culture. It's why it started with a manifesto, and it's why retrospectives are the only meeting that is spelled out in it; the retros aren't to try and determine what parts of a particular process you're not adhering to, but what isn't working (process or otherwise), so that you can change it (i.e., "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly").

There are plenty of workplaces that have that culture, even if the processes are all over the place. Of the last four workplaces that called themselves agile that I've worked in, three of them had that culture, and I and my teams got amazing work done in them (in fact, my reason for leaving at least one of them was -directly- due to the hiring of a micromanager and the ousting of someone who protected the teams from upper management). The fourth was an old school enterprise company you've almost assuredly heard of, with high employee retention, a culture of top down management and decision by committee, and, surprise surprise, their injection of agile processes did nothing to make them actually deliver software any faster, nor did it lead to any better results.

Re: Best practices for remote software engineering

#192

I was just having a discussion about this with my manager during 1:1. I'm curious how any fellow devs with ADHD have managed the transition to remote work over the last year? I love the freedom and ability to focus that working from home provides, but I often find myself taking advantage of that freedom and focusing instead on podcasts or reddit for 3 days to avoid 3 hours of writing unit tests.

ADHDer here. WFH was a nightmare the first six months, but the past few months have been working out great. My findings from this past year: * Finding the right medication, in the right dose. Biggest QoL improvement. YMMV * Whenever I get lost in the sauce and start spinning my wheels, I schedule a call with a colleague and ask them to help sort my priorities out. This also helps me with accountability, in a softer w…

What features make Muse the one for you, as opposed to alternatives? Just curious.

Definitely agree with working using the best equipment money can buy, if you spend so much time with it.

Re: Best practices for remote software engineering

#193

Earlier quoted context omitted.

I stopped being able to get work done at all. It gradually tipped me into a low-self-esteem death spiral. I tried lots of different approaches to fix it: more accountability with my manager, new medication, more regular exercise, therapy, a bit of disability leave, even moved to a bigger apartment where I could have my own office. Nothing got me past the block. I quit my job, spent six weeks studying and interviewing…

How long were you able to push your start date from when you accepted the offer? Weeks? Months?

Months. Certain very large companies hire engineers into a general pool rather than to a specific team, so once you've passed the interviews they don't mind too much if you put off actually starting work.

Re: Best practices for remote software engineering

#194
post #140

Earlier quoted context omitted.

It's ok, although I have a tendency to wear myself out mentally when I take stimulant meds. Certain kinds of programming have a very high activation energy. In each programming session, it can take a lot of time (sometimes hours) before I've gathered enough context to start making progress on a problem. Once I start making progress my motivation is usually self-sustaining. Sometimes I can't focus long enough to get t…

I've been a programmer for 20 years and you just described my daily struggle with my job so precisely. Is this kind of experience happening to neuro-typical people or is this a very ADHD thing? I ask because I have often wondered if I am undiagnosed as something or other and this post hit me hard.

I've seen coworkers that I'd describe as neuro-typical work in a similar way sometimes. But the tendency to alternate between periods of difficulty focusing and periods of hyperfocus is a recognized trait of ADHD. If you're interested in learning more I'd recommend Hallowell's book, the one I read was "Delivered from Distraction" but he might have a newer one. Just read the first couple chapters and if it resonates a lot then it might be worth getting tested.

Re: Best practices for remote software engineering

#195

Earlier quoted context omitted.

I'm in the same boat right now. Since my company insists on using an "air-gapped" development network (it basically means no internet connection, but that didn't stop the Chinese from copying our code and designs but I digress) we have to go through two different VPNs, which means remote desktop lag. Usually I don't mind for a few days, but after more than one year I just can't stand it, especially when we're we're f…

Wait, is there an ethical reason you think the project should be completed? Like, it's really going to help starving orphans or something? Because otherwise you should quit yesterday, like the others say. You don't owe them nuthin'.

> Wait, is there an ethical reason you think the project should be completed?

I had a higher salary than demanded because they needed me to complete the task. Sure I could quit, it's just I'd feel bad about myself.

>ike, it's really going to help starving orphans or something? Because otherwise you should quit yesterday, like the others say. You don't owe them nuthin'.

Can't deny the logic of that.

Re: Best practices for remote software engineering

#196
post #100

Earlier quoted context omitted.

I stopped being able to get work done at all. It gradually tipped me into a low-self-esteem death spiral. I tried lots of different approaches to fix it: more accountability with my manager, new medication, more regular exercise, therapy, a bit of disability leave, even moved to a bigger apartment where I could have my own office. Nothing got me past the block. I quit my job, spent six weeks studying and interviewing…

If you don't mind me asking, how did you find programming on meds? I can't do it.

I found meds to have enhancing effects on my code. Everything I have earned is because of it.

My best guess is you are still in the phase of titration and finding the correct type of medication that works for you.

Having an empathetic doctor who is willing to work with you can make that road smoother. She printed out papers from pubmed to help me better understand what I'll be taking and what to expect. It felt very nice to actually be taken seriously.

I do notice that the other experiences may not truly reflect the efficacy of medication. The actual symptoms are still not well defined, not all doctors are equal, being misdiagnosed, etc.

Hard truth? It's still guess and check. There are so many comorbid conditons associated with ADHD - most of the time it is just the symptom of an underlying cause. ADHD meds only work on people with ADHD :)

Re: Best practices for remote software engineering

#197

Pomodoro Technique seems to work brilliantly. There are many desktop apps like "Be Focused", you can actually do a lot more in a short amount of time using it and don't really have to work that much all day.

I tried the pomodoro technique yesterday. I had one successful pomodoro on the morning when it was quiet, and then when I went to take five minutes to clear a few things away before starting the next pomodoro, those five minutes some how became the rest of the day and I never got a chance to start my second pomodoro

Re: Best practices for remote software engineering

#198

Earlier quoted context omitted.

I stopped being able to get work done at all. It gradually tipped me into a low-self-esteem death spiral. I tried lots of different approaches to fix it: more accountability with my manager, new medication, more regular exercise, therapy, a bit of disability leave, even moved to a bigger apartment where I could have my own office. Nothing got me past the block. I quit my job, spent six weeks studying and interviewing…

I'm in the same boat right now. Since my company insists on using an "air-gapped" development network (it basically means no internet connection, but that didn't stop the Chinese from copying our code and designs but I digress) we have to go through two different VPNs, which means remote desktop lag. Usually I don't mind for a few days, but after more than one year I just can't stand it, especially when we're we're f…

Everyone is saying you should quit, which might be a reasonable suggestion, but it sounds like your issue is with working remotely. It sounds like you are able to be very productive and get satisfaction from your work when you can come into the office. If you don't want to quit, you could alternatively demand that they let you work from the office or relax development security. If they realize that saying "no" means jeopardizing the project, you might have some leverage.

Re: Best practices for remote software engineering

#199

Earlier quoted context omitted.

I stopped being able to get work done at all. It gradually tipped me into a low-self-esteem death spiral. I tried lots of different approaches to fix it: more accountability with my manager, new medication, more regular exercise, therapy, a bit of disability leave, even moved to a bigger apartment where I could have my own office. Nothing got me past the block. I quit my job, spent six weeks studying and interviewing…

Strange tip, I use to do part time local delivery. It made my brain cool off (safe regular activity, simple money, low skills). In between deliveries I often wrote small bits or small feature branches. I found it a good balance. It also made me think differently because I'd favor changes that were high ROI. No large design, no syntactic change. Only solid and valuable additions. Something I never really felt before.

Interesting. I have thought about working at a grocery store or something just to feel useful and connected, but my immigration status doesn't allow it. And honestly even though it would probably be good for me, it's hard to consider working for 1/10th of my usual wage.

Re: Best practices for remote software engineering

#200

I was just having a discussion about this with my manager during 1:1. I'm curious how any fellow devs with ADHD have managed the transition to remote work over the last year? I love the freedom and ability to focus that working from home provides, but I often find myself taking advantage of that freedom and focusing instead on podcasts or reddit for 3 days to avoid 3 hours of writing unit tests.

Regular 20-30 minute walks interspersed throughout my day have helped, usually every 2-3 hours It's probably more breaks than I would otherwise need but getting outside had helped me be mindful and exercise inhibition; a bit of a reset, so to speak. If not, I find myself getting stressed out at home more than I otherwise would as well
Post reply on HN