| 1. Nope, but the dev team is located on the other side of the country from the rest of the company (and I'm in between). 2. This company started as just a client and then they made me an offer that was too good to refuse. >The reason why I ask is because Principal-esque positions often come with perks not available to prole Developers. I definitely have a lot of perks. But I had even more freedom when I was a contractor, and I made plenty of money. If someone is a decent developer with good communication and business skills, a similar path is very achievable. >Not to sound snide, but the practical difference is - you're not the CEO. When I said practical I specifically meant other than the fact that he's the CEO. My point is that a well run company won't fall apart if the CEO is unavailable for a few hours per day, and a well run team won't fall apart b/c one developer (or their boss) is similarly unavailable. >It would not surprise me that some of these habits, fe. mentoring devs, meeting with leadership, etc, are best cultivated in a physical space before being done online. That's just me though. That's entirely possible. But my guess is that if there is an effect it's small compared to all the other variables. >Nothing to do with shitty bosses, but not everyone is exactly born with the qualities to check up on people regularly, ready to go out of the gate. Especially in a professional environment. I agree with you there, but I also think those people probably shouldn't be managers until they have developed those qualities, and I don't think this is a remote problem. Years ago I didn't have those qualities. I was a retail supervisor and I used to sit in the front office and mostly ignore the cashiers until there was a problem despite the fact that I was only 20 feet away from them. Remote work does require different skills, and managing a remote team probably takes more skill in general, but honestly I wouldn't want to work in house for a manager that didn't have those skills anyway. |