3 ms·
super cool! have long been interested in tooling for making code archaeology easier! any plans for building extensions for various issue/work tracking systems
by a-dub 4y ago
super cool! have long been interested in tooling for making code archaeology easier!
any plans for building extensions for various issue/work tracking systems, wikis, email archives, etc? i've longed for comprehensive views across tickets, pull requests, bug reports and wikis for all relevant knowledge for a given effort in past.
- sebmellen 4y agoIt looks like integration with ticketing systems is on the roadmap https://github.com/orgs/watermelontools/projects/1 https://github.com/orgs/watermelontools/projects/1.
- baristaGeek 4y agoYes! We're exploring Jira, and Notion integrations mostly. We're discarding Slack for the moment because of the technical feasibility, but would be something we look further down the road. What's your opinion about the create docs direction we're exploring to complement your Indiana Jones coding? (Love your "code archeology" term).
- a-dub 4y agothat is less interesting to me personally as that's often handled locally. (most sites with many projects will have some sort of locally customized project boilerplate or template to start with). i'm more interested in tooling that gives as much context as possible for why something is the way it is. code ages like a novel would as passed through the telephone game. the more context that is readily available for each generation of changes, the more consistent the design remains in the long run. also, it's incredibly handy when in emergency breakfix situations.
- baristaGeek 4y agoTy very much! We'll keep this in mind.