smokeonline

3 ms·

1. 1.▲
   by smokeonline 1y ago

   My current plan is to generate this kind of graph from documentation pages, similar to what I did with Wikipedia. The dynamic I thought was loading new pages as I open nodes (the same way you can visit the whole Wikipedia by clicking links,
2. 2.▲
   Show HN: Looset Graph – OSS concept map tool (ClojureScript, Wikipedia demo)(jponline.github.io)

   2 points by smokeonline 1y ago|2 comments
3. 3.▲
   by smokeonline 5y ago

   It's a very good example of a front-end REPL. I used to think hot reloading was good, but to keep the state between reloads is a whole new level.
4. 4.▲
   An Architecture for Community Contribution, Speed and Modularity(jponline.github.io)

   2 points by smokeonline 6y ago|0 comments
5. 5.▲
   Looset – A source code explorer for big or unknown projects(forms.gle)

   7 points by smokeonline 6y ago|0 comments
6. 6.▲
   by smokeonline 8y ago

   This idea passes through BDD, Ubiquitous language, code as documentation and single source of truth. Do you think is possible and desirable to have code so idiomatic that a domain specialist would be able to understand a functionality by lo
7. 7.▲
   Non programmers reading code (code as documentation)(github.com)

   2 points by smokeonline 8y ago|1 comments
8. 8.▲
   by smokeonline 8y ago

   This is a nice idea, I've been looking for things like this to read. But my interest is more about generic systems, not that much about end-user software. You are talking about "trade-offs" and I had a similar idea about &quo