> The deeper issue is tacit knowledge. Most of what a skilled engineer knows is not something they can articulate on demand.
Why is it that everyone says that soft skills can be more important than hard skills, that engineers talk to people they don’t sit in rooms turning requirements into code, but then, it seems like one of the criticisms about the interview process is “well, engineers can come up with good solutions when alone in a room”
That’s not the job. Articulating technical details when in conversation with your colleagues is.
Articulation is not the issue; the reasoning and consideration process is.
If you step back a bit from the words on that page and squint, what you might see is something like "Most of what a skilled engineer does is recognize, sense problems, and feel things that may not be obvious."
The discovery of the right path forward for the goals of the organization comes after that and takes time and planning.
Why is it that everyone says that soft skills can be more important than hard skills, that engineers talk to people they don’t sit in rooms turning requirements into code, but then, it seems like one of the criticisms about the interview process is “well, engineers can come up with good solutions when alone in a room”
That’s not the job. Articulating technical details when in conversation with your colleagues is.