Working in a shared, long-lived codebase is very different from hacking bash scripts for yourself. Because many others will see your code many times, you spend far more time on docs, clarity, and organization. I'm realizing the same mindset applies to cloud-first orgs.
-
Show this thread
-
When your job is to collaborate with others via a shared database (Docs, Notion, ...), you need to invest WAY MORE on clarity, organization, cleanups. "This doc doesn't link to it's related data" should "smell" awful in the same way as a variable named "x".
1 reply 1 retweet 8 likesShow this thread -
It should also smell bad to keep org data locally (text files, paper notes), make overly long docs, track unrelated concepts in the same node, track data in the wrong format (a text file that should be a spreadsheet). How much of 21c org success is just following this mindset?
1 reply 0 retweets 3 likesShow this thread -
Comment here with your favorite tools & practices for cloud-first orgs, or even better some "doc smells". Inspired by the sometimes painful slog of creating
@PronomosVC as a cloud-first org with a "nebulous team" (new concept I'm working on).1 reply 0 retweets 1 likeShow this thread
Some smells: Asserting an example exists without linking to an example. Contra one of your assertions: over-brevity. CTRL+F goes a long way. Distinctions between documents can be artificial. It's context-dependent. Letting comments on a doc linger (incorporate or resolve!).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.