I'm definitely guilty of 4, though I try to make comments about it And here's an extra one two: Using and IDE integrated Task List (ie VS) : overuse of TODOs - damn things pile up quickly. Ignoring compiler warnings. They're sometimes useful, and ignoring the buildup of minor things can make you miss big things like architecture mismatches

While inelegant, sounds like a workable solution. I'll make sure to post the idea for mixed permissions to the feature requests when I get the chance. Thanks for the answers!

Excellent! That brings up another question, though, regarding Privatization - is there any way to mix and match privitization of apps and projects? Say I create a library I'd like to keep private, but release an API, would there be a way to publicly display the API Wiki (and thus the project itself so people can access said Wiki), but keep the Repo itself and an internal Wiki private?

Is there a specific Terms of Service with regards to Workspaces, specifically paid-for Private Workspaces? I've been trying to find such, and have seen mentioned that private projects are very private, but the existing ToS wouldn't seem to accommodate that. Regarding thus, would it also render a private Workspace public if the creator's Pro subscription expired or was canceled? Or would they just be unable to add apps to the project until renewing?