Why Remote Engineering Is So Difficult

Re:Why Remote Engineering Is So Difficult by klochner on Wednesday December 31, 2014 @02:22AM (#8818526)

My experience is that engineers often:

    * hate meetings
    * prefer slack/hipchat/etc even if seated adjacently (myself included)
    * work asynchronously

So the main friction is in the interface between engineering and other disciplines. Remote works well so long as non-technical leadership has a local lead they can interface with.

[ Parent | on HN ]

Re:Why Remote Engineering Is So Difficult by illumen on Wednesday December 31, 2014 @04:49AM (#8818756)

The communication skills of other non-engineering team members can often suck in the digital domain. Empathy by text message can be hard to have. A combination of on-site and remote often works best. Learning the language of other domains can take a long time. The role of people who interface and translate between domains is important.

[ Parent | on HN ]

Re:Why Remote Engineering Is So Difficult by Vladipoteur on Wednesday December 31, 2014 @05:14AM (#8818808)

I totally agree with this statement.

> My job is in sales and I am teaming up with "sales" engineers. The bottom line is that they have the technical knowledge and I just have to manage/prioritise the relation with the Customer.

>>> I am doing the meetings instead of them >>> They don't like to be disturbed while producing, or move from their chair >>> hipchat is the best option for me >>> they are dedicated on different tasks/projects

So, when they are working remotely is fine for me as long as us don't loose the intimacy [common language]

[ Parent | on HN ]