Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The point isn't that they commit some useful code. It could be something as simple as just fixing a typo. But force them to go through the motions, so they can see the inefficiency in the processes.


And then what? Are they supposed to design a better development process and build tools to improve efficiency? Again seems like both a supreme waste of time and also as an engineer something I really would not want. Or are they supposed to tell the dev experience team to do something. If so why not just have the dev experience team or leader go through the motions instead?


Then they would become the inefficiency in the process




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

Search: