ENB: the biggest picture

[Edward K. Ream]

In this Engineering Notebook post I would like to remind everyone, including myself, of what is ultimately most important about Leo.

We Leo devs typically all spend about 99% of our time working on UX issues and fixing bugs. There is nothing wrong with this. Hangnails are super annoying.

However, it's the other 1% of time that really makes a difference in the long run. Not only is this sliver of time most important, it's also more fun and easier than endless coding details.

Leo's preface contains a list of Leo's unique features. As I write this I see that I should mention Leo newish clone-find commands ;-) There probably should also be a link to "The Leonine way to refactor code", buried in the appendices.

Anyway, Leo's unique features are worth expanding if we possibly can.

Summary

The most important additions to Leo have never been about the UX. Instead, they have been surprisingly simple ideas. The motto is, "it doesn't have to be difficult!"

Imo, the leoInteg project (Leo in vs code) is extremely important, for two reasons:

1. leoInteg advertises Leo to a wider audience.

2. leoInteg lets vs code handle all the editor-related chores that we spend most of our time on.

In my next post, I'll discuss how my brother Speed uses Leo outlines (.leo files) as SQL DB's. It's brilliantly simple. I would like to see some more of these kinds of ideas for Leo.

Edward

[Rob]

I can't wait to see that post from Speed!

Rob...

On Friday, September 18, 2020 at 2:48:54 PM UTC-4 Edward K. Ream wrote:

In this Engineering Notebook post I would like to remind everyone, including myself, of what is ultimately most important about Leo.

[Edward K. Ream]

On Fri, Sep 18, 2020 at 2:10 PM Rob <lar...@gmail.com> wrote:

I can't wait to see that post from Speed!

I've sent the first draft to Speed for his comments and corrections. I hope to post it tomorrow.

Edward

[k-hen]

That's fantastic news, really looking forward to it :-)