Unconference Session: Bridging language from and to tech

[Maria to add notes]

Defining our title:

  • Standards for tech language
  • Translate between different domains (agriculture, tech people, policy makers, etc)
  • Miscommunication between developers and users. It’s a different language and a farmer won’t become fluent. Standarizing it to understand one another’s goals. Definition of different concepts that mean different things in the tech world. “Ontology” “claims” “token” . Everyone has their own agenda and their own language. We need to speak in their own domain.

WHY IS THIS IMPORTANT:

  • If GOAT grows, this is really important. Especially if you want people to feel included in this space. AND ESPECIALLY if you want farmers to help inform the work.
  • Language can create a very alienating environment. When you talk to a farmer, you have to simplify terms and know what they understand in order to build trust. The interpretation process happens at multiple levels.
  • Shared language creates belonging.
  • Helping advisors to translate things more easily, and will help her with her job, especially with farmworkers.
  • Waste of words, time, and energy if the person doesn’t understand.
  • It makes it easier for developer to know they need an interpreter.

Tech language share - how

  • Ideas: write on a sticky note a word that you’ve heard that made you feel disconnected ( related to technology) MRVs?
  • Lessons learned from the technology landscape on language not translating.
    Helpful to know what language everyone speaks:
  • Name badge with what language domain you speak
  • Visuals for words will be really helpful.
  • Have a little (i) on definitions so that people can expand, e.g. “conversion rate” and can help a farmer tremendously with a business savings.
  • GOAT creates a glossary on their website for these terms.
  • Can we do a gesture that we quickly do to say I don’t follow the term you just used. Put your pinky-finger up.

1 Like

How can language be more consistent in the ag tech landscape?

  • Standards for agtech language

  • Translate our terms among stakeholders like developers, farmers, policymakers

  • Open ag tech language is not simple or easy to understand

  • Technical terms, jargon. How do we make it more simple and understandable?

  • identify people from different field thru color stickers in name tags

  • A signal we can make when we need a vocabulary clarification e.g raising our pinky

  • Example ontology: relationships between concepts, a data dictionary

  • Schema has a very specific meaning in software development
    - Shared language creates belonging

  • Making language accessible to explain to different audiences and other languages

  • Explaining terms that may be jargon to someone outside of the field

  • Include pictures and graphics

  • Goat should have a glossary

Dunno if this came up during the session, but Domain-Driven Design (DDD) seems like it could offer valuable insights, particularly its concept of a ubiquitous language. It may be close to what was meant by “shared language,” but quite rigorous in the way it was originally described in Eric Evans’ canonical book on the subject. Just one of many tools in the box, not a cure-all, but it’s one I often find helpful.

1 Like