|
|
|
|
|
by bigiain
1656 days ago
|
|
You don't intentionally choose weak engineers, but a strong engineer working on the wrong thing because they can't communicate effectively is less useful than a slightly less strong engineer who's always doing the thing that's actually needed. This hold true as pretty much every level. A junior engineer who will never say "No, I don't understand, can you explain that to me again please?" and spends days/weeks writing code that doesn't meet a requirement is less productive than someone who'll talk to you to understand properly before starting to code. A senior engineer or technical cofounder who can't communicate well with customers will be much less effective in solving real customer problems or finding product/market fit. Being a great engineer isn't just about writing good code, its about writing the right code - and to know what that is you need good communication skills. |
|
Asking for help is more about humility and willingness to look dumb, than about being gregarious or chatty or socially open.