271–280 of 399 posts
Senior software engineers: sure. Engineer II or below, terrible. Literally zero productivity, or even negative productivity.
Are you saying remote work only works for Seniors, or remote work is over for Seniors?
Earlier quoted context omitted.
> However, if your work is about innovation and collaboration, Please, I've worked on plenty of successful new projects with a distributed team. This in-person bias is largely for people who don't know how to communicate effectively.
Please, I've worked on plenty of successful new projects with a fully onsite team. This remote bias is largely for people who don't know how to behave effectively around other people.
Being co-located in the same building has a few advantages especially from a company culture and relationship prospective. But finding great talented people around the HQ becomes a big constrain and it is expensive.
If you run the company "remote-first" so everyone remotely has the same experience, you may argue that the pros are largely outweigh the the cons.
Hybrid is more difficult to make it work but not impossible. The challenge is to keep everything "remote-first" so the remote people are not left behind in any manner.
Starting a company/team "remote-first" since the beginning is easier because workflow can be built remote-first. Transitions to remote-first present more challenges.
Earlier quoted context omitted.
I’m not sure I agree. Our industry isn’t full of people that have more integrity than the general population, and “your problem for hiring the wrong people” is short sighted, or even victim blaming. I’ll share this recent HN post: https://news.ycombinator.com/item?id=35767280 Remote work only makes sense when everyone has integrity, but that seems less and less likely in my experience, sadly.
I see nothing particularly bad about the post you shared (it's just a personal account of someone that doesn't really care about their job), and the only thing that it tied to remote work is the mention of "multiple full time jobs". But then I have to ask - if his employers are happy enough with his work to keep him around, what is the problem there? Keep in mind, I am also the sort of guy that doesn't rage against e…
In SW environments, having the time to do more work is supposed to mean actually completing more projects. They hire you to "perform duties for x hours a day", not "complete x tasks/x story points per sprint", so if everyone on a team is taking a similar approach, your velocity might be half or less what it could be if everyone ended up on-site.
OpenAI is at 3180 18th St, San Francisco, CA 94110, US. That's a crappy location in the Mission in SF.
Luckily we don't have to rely on gurus or influencers to decide this. Companies will succeed or they won't and my bet is that plenty will succeed with significant remote headcount and Altman will be shown to be wrong.
What we need is stronger labour laws, so power-trippers such as Sam Altman can't dictate other people's lives.
Earlier quoted context omitted.
Only part of my learning was from direct question answering. Seeing how senior people worked also helped a lot. E.g. over hearing a design discussion or seeing how they debugged outages was very helpful to me. Those things are very hard to recreate remotely.
Those things are easier to recreate remotely. You can see their actual screen instead of watching on a projector or over their shoulder. Pair programming is even easy to do remotely, there are IDEs that support it. Hop in any kind of voice call and they can talk you through what they’re doing as they’re doing it.
Earlier quoted context omitted.
Those things are easier to recreate remotely. You can see their actual screen instead of watching on a projector or over their shoulder. Pair programming is even easy to do remotely, there are IDEs that support it. Hop in any kind of voice call and they can talk you through what they’re doing as they’re doing it.
It's not about the activity, it's about the serendipity. There is no serendipity when you are working remotely.
Earlier quoted context omitted.
What I meant is that I learned a lot watching senior members of the team interact. I was like a fly on the wall during their discussions just because I happened to be sitting near their desks when the discussion started. Or when there was an outage, I could overhear how they were debugging the issue. Also, I've run a remote work company over the pandemic. Maybe you don't feel working remotely is different, but many,…
Clearly we differ on how we feel about approaching people. I’d rather get a simple message. When people have to write things they tend to think more about what they want to say. And what you’re describing about the fly on the wall is still simply they aren’t communicating well if they aren’t including coworkers that may only be included for the benefit of learning how to handle situations. One way to handle that is t…
This is the bad part -- the best stuff to learn from has been filtered out. Text is written with a specific audience in mind, and that audience generally isn't students. You can write a second document sure, but that requires dedicated tome to writing a second document, and even then, the author may not know which details are most important for the student to know