# Best practices for documenting programming in a glide app

**URL:** <https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179>\
**Category:** Ask for Help\
**Created:** [February 21, 2021, 3:15pm UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179 "2021-02-21T15:15:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Burdine\_Jr](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/john_burdine_jr/32/9776_2.png) [@John\_Burdine\_Jr](https://community.glideapps.com/u/John_Burdine_Jr)\
**Post date:** [February 21, 2021, 3:15pm UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179/1 "2021-02-21T15:15:22Z")

</div>

I wondering what ya’ll have found to be the best way to add details to columns so future editors can read what the columns are doing? I’m already circling back to things on my app and struggling to remember which other tabs and columns are using the data from given column and why things are set up the way they are. I had a habit of adding notes to cells in Google Sheets but that doesn’t help me with relation, lookup, template columns and the like. I’m also seeing some columns that seem to be redundant or obsolete as we’ve evolved but I’m afraid things will break if I delete them.

---

<div class="post-metadata">

**Author:** ![Luther](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/luther/32/17929_2.png) [@Luther](https://community.glideapps.com/u/Luther)\
**Post date:** [February 21, 2021, 3:24pm UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179/2 "2021-02-21T15:24:37Z")

</div>

I once put a feature request similar to this…

I am not sure if it got any votes

> [@Notes/Comments in the glide editor](https://community.glideapps.com/t/notes-comments-in-the-glide-editor/21402):
>
> I am not sure if this was not proposed before or not. If it was then I apologize in advance… I would like to suggest if it is at all possible to add a space to add notes in the glide editor, especially when dealing with computed columns… For example for a template column, you have a label section, if we could get a “description section” underneath where you can write notes/comments why you made a certain calculation, that way when you go back to your data editor after months, then you know th…

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 21, 2021, 3:36pm UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179/3 "2021-02-21T15:36:24Z")

</div>

- I try to make my column names as descriptive as possible.
- I also use a consistent naming scheme, especially with calculated columns.  
So all my relations are named `rel-xxx`, all my lookups are named `lk-xxx`, all my math columns are named `mth-xxx`, etc.
- I also spend a fair bit of time re-arranging columns, so that they follow some sort of logical order from left to right.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [February 21, 2021, 3:38pm UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179/4 "2021-02-21T15:38:07Z")

</div>

What I’d like to see is just a way to click on a column and see all of the other related columns and components that are affected by that column. It seems like they already track that because your can rename a column and it’s handled in every other affected column and component.

---

<div class="post-metadata">

**Author:** ![Manu.n](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/manu.n/32/11679_2.png) [@Manu.n](https://community.glideapps.com/u/Manu.n)\
**Post date:** [February 22, 2021, 12:23am UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179/6 "2021-02-22T00:23:28Z")

</div>

- 1000 Votes

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [February 22, 2021, 12:44am UTC](https://community.glideapps.com/t/best-practices-for-documenting-programming-in-a-glide-app/23179/7 "2021-02-22T00:44:32Z")

</div>

Since I used Glide at first time I missed that feature, I know it as **X-Ref** and in many software it is a classic tool and almost a must.

Saludos
