TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Low Context – Software's Silent Killer

16 pointsby staccatomeasurealmost 3 years ago

4 comments

nescioquidalmost 3 years ago
This article clearly borrows from the concept of context in communication, but seems to invert the meanings (and doesn&#x27;t use the word &quot;communication&quot; at all in the article).<p>Low or high context indicates how much context is required for the interlocutor to <i>understand</i> an utterance. Low context would be something like a text book (it has all the answers and does not require the reader to fill in the blanks); high context would be &quot;They don&#x27;t know what to do with it&quot; (you can only understand that utterance if you already know &quot;them&quot;, &quot;it&quot;, and why &quot;it&quot; requires something be done with it).<p>The article refers, however to &quot;high-context&quot; or &quot;low-context&quot; <i>individuals</i>. I would expect a &quot;high-context&quot; individual to require someone else to fill in all the blanks (just the opposite of a text book). However, the article means that a &quot;high-context&quot; person is knowledgeable about the work context, not that you have to show them where the power outlet is and why you need to plug in the computer.<p>If we simply replace &quot;high-context&quot; with &quot;knowledgeable&quot;, then all the article is trying to say is &quot;Make sure to have your knowledgeable teammates dispersed and training others&quot;. Not a blinding insight? But then, you wouldn&#x27;t have much of a blog post because you wouldn&#x27;t have to build up a silly explanation of what a &quot;high context&quot; individual is in the first place.
darkteflonalmost 3 years ago
Context is something I’ve found constantly challenging in a number of roles over the years. It often seems under-valued.<p>While the ideal might be a well-structured team wiki where decisions and their context are recorded in full, in practice those tend to end up de-prioritised and poorly-maintained. They just don’t reflect the way people actually work.<p>With the growth of remote work, the mass adoption of the context-free Slack model of team chat feels like one of our biggest problems. The threading model of apps like Quill (now gone), Zulip and Twist (and even email) feel like a better solution because they explicitly place context next to decision. They’re not perfect, but they’re much more likely to stay relevant than a wiki.
itsdrewmilleralmost 3 years ago
This is one of the better posts on a blog that is consistently great - I recommend reading the whole thing.
kjellsbellsalmost 3 years ago
Feels like the tldr of this is &quot;keep your old people around, cos they know stuff.&quot;