---
title: "Discussion on \"A note on the detriment of Jargon\" | Hashnode"
description: "Discussion on \"A note on the detriment of Jargon\". I work on decreasing patients' Time to Therapy in the HealthTech space. As such, I have to communicate with many external stakeholders about highly technical decisions. There are ridiculous amounts of jargon that have to be plowed through before any ..."
url: "https://hashnode.com/posts/a-note-on-the-detriment-of-jargon/64501794fd50ffe294dde5fd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A note on the detriment of Jargon](https://blog.austn.net/a-note-on-the-detriment-of-jargon?utm_source=hashnode&utm_medium=feed)

I work on decreasing patients' Time to Therapy in the HealthTech space. As such, I have to communicate with many external stakeholders about highly technical decisions. There are ridiculous amounts of jargon that have to be plowed through before any ...

May 1, 2023 · 2 min read · blog.austn.net  
Read the article

-   [#programming-blogs](https://hashnode.com/tag/programming-blogs)
-   [#communication](https://hashnode.com/tag/communication)
-   [#learning-journey](https://hashnode.com/tag/learning-journey)
-   [#learning](https://hashnode.com/tag/learning)
-   [#healthcare](https://hashnode.com/tag/healthcare)

## Written by

[Austin](https://hashnode.com/@austn)

@austn

  
[View profile](https://hashnode.com/@austn)

Software Engineer

Professional software engineer working at CoverMyMeds, an enterprise healthtech firm that ensures patients get access to the medication they need. Primarily focused on backend and systems design through Ruby and Elixir, but experienced with JavaScript and all things frontend Interested in learning and teaching the craft of software; technical or otherwise Join me as I innovate by iterating!

## Responses 1

Markdown supported · ⌘↵ to post

[yetanothertroll](https://hashnode.com/@yetanothertroll)

[May 29, 2023](https://hashnode.com/posts/a-note-on-the-detriment-of-jargon/64501794fd50ffe294dde5fd/comment/64741884a8d1afa35bae6b76)

You guys just need to hammer out a list of terms and their definitions that you all agree on. Nobody's getting anywhere fast if you have to spend ¾ of each meeting defining O notation, "web server," "object," "base class," "sorting," "database," yadda yadda yadda

[Austin](https://hashnode.com/@austn)

[May 29, 2023](https://hashnode.com/posts/a-note-on-the-detriment-of-jargon/64501794fd50ffe294dde5fd/comment/64741884a8d1afa35bae6b76#reply-6474ed38e39ae2b4d6e38284)

Yeah definitely agree that building that common language is important. Unfortunately in my experience lots of teams build no such thing, and instead stumble gracelessly through slogs of language

Instead of building a common index of important terms, providing lessons and lectures and communication surrounding our language, we simply hope for learning through osmosis. Lots of unnecessary manual work, repetition, and frustration in that process IMO

[yetanothertroll](https://hashnode.com/@yetanothertroll)

[May 30, 2023](https://hashnode.com/posts/a-note-on-the-detriment-of-jargon/64501794fd50ffe294dde5fd/comment/64741884a8d1afa35bae6b76#reply-647561da731d78b677df6af1)

[Austin](https://hashnode.com/@austn) Yup, someone's going to have to step up and nail down a list of terms and their definitions that everyone can refer to. I wonder who will end up getting voluntold to do it?
