We Don’t Simply Get Remote Jobs, We Join Remote Teams

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by chrishynes on Friday September 16, 2016 @10:06AM (#12514067)

You can't go based on something purely objective like lines of code, but a good code review will tell you if someone is working or slacking.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by tbrownaw on Friday September 16, 2016 @10:34AM (#12514270)

And when I spend the day planning ahead, or helping other team members research things, or bug hunting, or...?

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by chrishynes on Friday September 16, 2016 @01:17PM (#12515574)

Those things should also produce artifacts that can be reviewed by someone knowledgeable in tech.

Besides, it's not a day by day review, it should be week or month. If you haven't produced any artifacts in a week or a month then...

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by marcosdumay on Friday September 16, 2016 @11:13AM (#12514544)

Well, you really shouldn't measure any kind of human productivity on a daily scale.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by ozim on Friday September 16, 2016 @12:07PM (#12514986)

Yeah, I spent last week clarifying stuff with business analyst and QA person. Cleaning up delivery with small changes. When my team mate wrote quite a lot of code that need bunch of fixes. How to measure productivity.

[ Parent | on HN ]