3 ms·
What's missing on the "core competency" is communication. Honestly, communication and ability to turn a communicated idea into code is more important than probl
by barrkel 9y ago
What's missing on the "core competency" is communication. Honestly, communication and ability to turn a communicated idea into code is more important than problem solving ability. If someone is solving the wrong problems, they're not creating value. Whereas if someone is stuck on a problem, we can fix that by talking about it - as long as the discussed solution can be turned into code.
- crescentfresh 9y agoCommunication is such a nuanced thing. In our core senior group there is one guy who refuses to let us talk about anything remotely resembling an implementation-related detail if we're early in the high-level design stage, and it honestly shuts conversation down. I get his point, however at the same time a group of good engineers should be able to briefly and abstractly discuss the potential downfalls of a design decision while considering an implementation detail (say, using columnar storage to address some high-level requirement). Then, there's folks who communicate "well" in standups, meetings, design discussions, are cogenial, etc. At the same time they might be drowning in some technical debt they've taken on and no one understands it until they're 2 weeks overdue on a deliverable.