Hacker News new | past | comments | ask | show | jobs | submit login

> Really? A workplace with no proper desk, chair, lighting, multi screen setup, isolation from domestic distractions, crappy phone lines due to bad internet, the hurdle of contacting someone who used to sit next to you, and the impossibility of scribbling something on a whiteboard etc?

1. The desk, chair, lighting and multi-screen setup I have at home is vastly superior to any I had in any company I worked for in the past, including FAANG.

2. Know what is worse than domestic distractions? Office distractions. People around you constantly talking in those noisy, nightmarish open offices. At home I can tell my wife I need to focus, shut the door to the home office room, and be productive. During the 15 years I worked from the office I had to wear fucking headphones with loud music to drown out the incessant office noise.

3. Not sure what you are going on about bad internet. Where the fuck do you live that internet connection is unreliable these days?

4. The beauty of asynchronous communication these days. I don't even like slack very much, but it is so much better than in-person communication, that even in the odd occasion when I am at the office I prefer to use it rather than speaking in person.

5. Ah, whiteboards. Funny you mention that, there are numerous excellent collaborative tools for that sort of thing nowadays. They end up being clearer since my writing and drawing skills are shit, and they are also asynchronous, which makes it so much nicer.




I have to agree with you. It took me until I'd got quite far through their comment to realise they were talking negatively about WFH and not being in-office.


The office, is probably 20% of your home. That's a substantial amount of money depending where you live.


Money I saved anyway, moving out of expensive, crowded cities.


Ah yes, async.. in theory it's good. It lets you context-switch. Unlike a computer, context switching for humans isn't nanoseconds.

And because the other person is also replying async, you have to wait. So you get the same fan-out problem as microservices.


I used to think so. Except it works great.

In a regular scenario I have multiple things ongoing that I have to wait beyond communication. I need to wait for code reviews. I have to wait until some changes are deployed until I can perform something. Truth is that a whole damn lot of what I do is async anyway. Instead of moaning about it, I decided to embrace it.

Maybe I am lucky that I work in a remote friendly environment, where people also work asynchronously.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: