101–110 of 252 posts
That's why programmers should work remotely. It's the best thing I've ever done for my career. Moved back from Management to IC because it was remote and it's been amazing.
That's why programmers should work remotely. It's the best thing I've ever done for my career. Moved back from Management to IC because it was remote and it's been amazing.
Remote work is great for so many reasons. Off the top of my head: For the company: * less office space expense * bigger talent pool * low cost benefit * increased documentation * encourages the trend towards outcome based management (as opposed to butts in seats) For the programmer: * more control over their work environment * more control over their time * no "commuting" subsidy for their employers * arbitrage paysc…
I would expect that a larger talent pool maybe the case for smaller cities
On the general question of open vs. private offices, my views have tempered over time. The first time I worked in an open office, I hated it. But I've come to realize that a lot depends on the layout of the office and that there are better and worse ways to configure one. The first case -- the one I hated -- had a) long rows of desks, b) bright overhead fluorescent lights, c) a lot of noise due to being in a large ro…
I work in a team. The team of 5-10 people sit in the same office. That way we can talk to each other when needed. Some say that's disturbance, I call it collaborating. I'm not a code monkey. I don't sit alone in an office all day hammering out code. If that was what expected of me, I would change job. So, not exactly open floor plan, but not separate offices either. I think that's perfect.
My programming career involved an office at every position (Blue Cross Blue Shield, Cisco, HP, XTime, VMWare, and a handful of private equity groups). As I was transitioning into another field, the "open office" craze was taking over. I could be wrong, but I have a strong feeling I would not have enjoyed it. Nothing like being an hour into analyzing a core dump to be jerked back to reality by someone interrupting you…
Earlier quoted context omitted.
The problem with remote work is that you need very competent managers who understand the work deeply and can keep things together. From my experience there are not too many managers who can lead a remote team competently.
Sorry, I don't understand why competent management is required for remote work but not for non-remote work. Is there some advantage for onsite work in terms of management? In my experience, incompetent management won't do a good job of leading a team in any circumstances (remote or non remote).
I think you also need to hire differently for remote. People need to be self-motivated and self-sufficient.
2 years back We used to get a cabin office @Qualcomm for all Engineers same as VPs. Now Staff Engineers and above still get cabin office and others have moved to cubicles. We have a lab where most of us sit in the afternoon to collaborate. I must say this is the only place where I saw in my career where a fresh grad got cabin offices. It feels great to code in isolation uninterrupted. It also feels great to collabora…
To clarify, I'm not familiar with your usage of the word "cabin" in this context.
Stack Overflow does. I'm an engineer there and we still think providing private offices to our engineering team is important for their productivity. This includes engineers, SREs, designers, data scientists, PMs, and others. However, most of our engineering team is remote and if they're not in one of our locations, we give them pretty much what they'd like to build their own home office or go to a coworking space. Fo…
I'm still occasionally sad that I bombed an interview at SO a while back. I had prepped for more of a front-end/full stack JS role, and got asked a series of low-level data structure questions. I thought I did alright given the circumstances (I did work out the correct answer to each one), but the interviewer wasn't impressed. I asked for a do-over and they said no. Oh well...