Your Technical Documentation Should Be a Graph: Here’s Why
By Bryce Merkl Sasaki | April 25, 2016
TL;DR: This blog post is mainly about how technical documentation should ideally be structured: as a graph (not to be confused with a chart). As a software developer and author I have had the chance (and also the obligation) to… Read more →
Keywords: github • graph • graphconnect • Knowledge Graph • natural language processing • nlp • software developer • stack overflow • Structr • technical documentation
Subscribe
Slack
Contact Us
From the CEO
Have a Graph Question?
Reach out and connect with the Neo4j staff.
StackoverflowSlack
Contact Us
Share your Graph Story?
Email us: content@neotechnology.com
Popular Graph Topics
- cypher (331)
- graphconnect (204)
- nosql (135)
- graph visualization (96)
- relational database (95)
- emil eifrem (86)
- sql (76)
- data model (70)
- Connected Data (65)
- graph technology (63)