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
{{ message }}
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
Internal tools are helpful for both the Rome core team and for other contributors. They let people gain an understanding of our various data structures; they facilitate debugging and bug reporting; they help with comparing to other tools. They're also great because they're (relatively) easy to make without too much knowledge of the codebase.
That said, we shouldn't devote too much time to internal tooling, as we do need to ship the actual product, and internal tooling can be a great way of procrastinating that actual work.
My hope is that by documenting potential internal tooling tasks, contributors can potentially take them over.
Description
Internal tools are helpful for both the Rome core team and for other contributors. They let people gain an understanding of our various data structures; they facilitate debugging and bug reporting; they help with comparing to other tools. They're also great because they're (relatively) easy to make without too much knowledge of the codebase.
That said, we shouldn't devote too much time to internal tooling, as we do need to ship the actual product, and internal tooling can be a great way of procrastinating that actual work.
My hope is that by documenting potential internal tooling tasks, contributors can potentially take them over.
run
function #2619The text was updated successfully, but these errors were encountered: