Hacker News new | past | comments | ask | show | jobs | submit login

A friend of mine said their engineering processes came from pooling their knowledge about what sucked at other places. So maybe focus more on what not to do?



My main one as a remote worker of a non-remote company: don't leave your remote workers out-of-the-loop of design or api changes. Documentation must exist, APIs must be documented before implementation. I spent 1 month implementing something that wasn't read. "just mock it" they said. Then the mockers all became totally obsolete.


Completely agree! Being remote in a non-remote company is one of the hardest things as those companies don't have procedures in place for keeping everyone in the loop.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: