Hacker News new | ask | show | jobs
by chrisweekly 2437 days ago
Mostly good advice. Along similar lines (w/ more detail of course), see DHH's book "REMOTE" which includes advice on how to sell the idea to mgmt. As a first step I'd recommend starting even smaller though, vs framing it as a new and demonstrably better way for projectS to be done in general (ie, a big change). See if you can find a way to demonstrate the benefits on a personal/individual level, without making a big deal of it. If you can start the bigger conversation (involving teams / processes / policies) already armed with evidence of success at your current workplace, you'll gain credibility and engender confidence / assuage fears of those in management who need convincing.

For my part, I've been self-employed (full-time consulting), 98% remote, for about 3 years. Before that, in almost 20 years of traditional software-related jobs, about half my working days were remote. I was fortunate in being able to insist on a high degree of autonomy wrt how/where/when I got my work done, for most of my positions. Not always possible, but you'll never get the freedom if you don't look for the oppty and make the case for it.