My preferable development environment would be an IDE I built myself, perfectly tailored to the peculiars of MY workflow. It would also need to feature easy ext

My preferable development environment would be an IDE I built myself, perfectly tailored to the peculiars of MY workflow. It would also need to feature easy extensibility to make it affordable to extend it, sometimes on a per-project basis. I'd eventually end up working on optimizing my productivity in a quite direct manner, by analysing what the bottlenecks (anything that hampers Flow) are in my different projects and devising solutions. When you work in Lisp by making DSL's and generally problem-specific extensions, I think the next logical step is to extend the IDE to support it directly (especially if you use the extension in many projects). If for example you make a CSS DSL, it would be great to have full property completion support, syntax highlighting and the other usual suspects. Two areas I expect to work on a lot is 1. making the operations of my IDE more "semantic" (as in, adapted to what I want to do. If it's easy to think about, it should be easy and quick to carry it out) and 2. Making a system of views that would let me bypass the traditional file-based view of a project. If you program in a mostly functional way, most of the time the load order and segregation into files is much less important than other possible views of the project.