jaaron

2 maanden geledendiscuss

For similar reasons, I strongly prefer org-mode to markdown. I find that with org-mode and extensions (such as in-line elisp) I have a _significantly_ more powerful system. For example, specs can have tasks and roadmaps inline which reduces risk of drift. The biggest downside is, unfortunately, not enough folks are emacs proficient.

I hadn't considered HTML and I'm definitely going to try this.

jaaron

9 maanden geledendiscuss

I was thinking the same thing: why is everyone reinventing emacs?

gnu and emacs already have a long history of cli and text friendly solutions that LLM dev agents can easily use and are trained on.

Or for structured data, just use a database. Dev agents can work with SQL just fine.

jaaron

10 maanden geledendiscuss

Agreed that picking the right size of work is critical.

I didn't know about Kiro specs. I've been playing around with my own org-mode based approach with mixed success in keeping dev agent work tracked:

https://github.com/farra/dev-agent-work

Submissions

The Second Coming of the Command Line

comments