Using Voice to Code Faster than Keyboard

Re:Using Voice to Code Faster than Keyboard by wwweston on Tuesday August 13, 2013 @09:44PM (#6209513)

Yep. The difference in one role (management) the conditions you're describing read as signals of activity. In the other role (development) it reads as noise interfering with the activity you're working on.

A "successful" company probably already has a culture that's going to be hard to change, but where management is trainable, you can sometimes improve things by giving them something else like else to focus on, like commit logs, test suites, or ticket updates.

[ Parent | on HN ]

Re:Using Voice to Code Faster than Keyboard by sybhn on Wednesday August 14, 2013 @01:28AM (#6210043)

Glad you bring that up. I'm a manager. I do mostly the things you mentioned to give my team some breathing room, and have to WFH when i want anything serious done. As you can imagine if the ambience is bad for me, it is horrible for my team. I try to help with some WFH days here and there. But it is a culture thing. It's in the freaking DNS of the place. Only so much i can change.

[ Parent | on HN ]