3 ms·
> 1) Shut up and listen I like that but many people get irritated and feel you're not proactive enough if you just occasionally ask questions.
by cJ0th 12y ago
> 1) Shut up and listen
I like that but many people get irritated and feel you're not proactive enough if you just occasionally ask questions.
- akoncius 12y agostill it's better to listen and try to understand everything instead of suggesting stupid solutions without deep understanding of problem. I've seen many cases when new dev joins company and instantly suggests some solutions to some problems without any knowledge of domain. Unless you are expert at that domain, you should do that "shut up and listen" in the beginning. OR raise respectful questions to get that knowledge of domain/programming skills.