I am always happy to see how people build their apps as I always come away with one idea to improve how I work myself. Sometimes these are things that are well known but sort of need to be discovered (such as naming columns with topic/ thing, topic/ another thing - to have collapsable columns).
I just saw how @rayo is using useful emojis and naming convention for his tables, as an example.
So, what other things have people come up with these days! Thanks 
I will take a note of some of my tricks:
when I am working on things like set columns, I often have to pick up values from all kinds of columns. Many of these are things like Question ID 1, QID 2, etc. So I use the type ahead to find the column - and I look for distinct text patterns I can copy. In this case, I would then type ‘id 1’, then ‘id 2’… and this would rapidly find the column (out of the 500+ columns in some tables)
column naming - I use the / to separate columns into groupings. I have some that are consistent across tables, such as manage/ to cover all the usc columns I use for admin, and either edit/ or user edit/ for things the user puts in.
more column naming - periodically I go through my columns and tidy up, merging some columns together in these grouping, renaming to make the groupings more clear, etc.
in data, I often us ‘duplicate column’ rather than add column. This keeps the name of the previous column to the left, and then I edit that. This helps given my above approach for naming - the names can get quite long, and often I have repetitive things (but using q1, q2, etc)
I NEVER use the default edit or form functions. Most of my use cases have a need to allow a user to type things… but they might change their mind and so I need a way of rolling back to their previous version. So I have the data columns for the final values, and then a manage/ or edit/ set using user-specific values. My actions then use set columns to move values back and forth.
from the above approach, I have learned it best to have consistent naming between my usc and normal values, to make it easier to find! For instance, I just changed one table away from :is content/ publish status and for some reason manage/ live status!
consistent column naming for computed columns - I do not like names that hide what is happening behind the scenes so my naming would be something like Content/ ite-status. My usual ones are ite (if-then-else), tp- (template), array (things with arrays), rup (rollup), sv (single value), rel- (relationships), etc
more to come! hope this helps folk