You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it redundant to ask developers and designers to consider eventual publication/public working in all of their project design? To plan for their work to be open even while they're still working on a closed prototype?
For example, at the COVID app development webinar, we heard that apps were developed in private (due to the highly political/sensitive nature and media scrutiny), and then had to be fully reviewed for discouraging or embarassing code documentation or commit messages before publication.
The text was updated successfully, but these errors were encountered:
Even if it would be redundant, I think it still might be a good idea. Working radically in the open is still quite unusual, so extra reminders might be necessary for people not defaulting to a closed process/tool.
Is it redundant to ask developers and designers to consider eventual publication/public working in all of their project design? To plan for their work to be open even while they're still working on a closed prototype?
For example, at the COVID app development webinar, we heard that apps were developed in private (due to the highly political/sensitive nature and media scrutiny), and then had to be fully reviewed for discouraging or embarassing code documentation or commit messages before publication.
The text was updated successfully, but these errors were encountered: