mshark
Joined 13 years ago
Karma
5
Submissions
6
Member since
Aug 22
Recent submissions
Comment · 7 months ago
Hadn’t seen Traycer, that looks really polished. An important difference is that eforge is open source (Apache 2.0). I purposefully left out planning features from eforge because I don’t want the same tool that builds my code to force me into a planning methodology. Our role as developers has shifted heavily into planning (offloading implementation), and I’m still getting comfortable with that and want to be free to explore the planning space. Maybe I’ll change my mind after my planning opinions evolve.
Comment · 7 months ago
Had the same realization which inspired eforge (shameless plug) https://github.com/eforge-build/eforge - planning stays in the developer’s control with all engineering (agent orchestration) handed off to eforge. This has been working well for a solo or siloed developer (me) that is free to plan independently. Allows the developer to confidently stay in the planning plane while eforge handles the rest using a methodology that in my experience works well. Of course, garbage in garbage out - thorough human planning (AI assisted, not autonomous) is key.
Comment · 12 years ago
Just this week I started learning org-mode by reading one of Charle Cave's postings on how uses org-mode to implement the Getting Things Done methodology http://members.optusnet.com.au/~charles57/GTD/gtd_workflow.h.... For me this has been a great tutorial.
Comment · 12 years ago
You should have a section in your README discussing differences from D3. I've used D3 a little and understand some of the pain points. Looking at your library I'm asking myself "why would I abandon D3 for this?".