WEBVTT

00:00:00.000 --> 00:00:05.159
I'm doing well. Thank you so much. I was supposed to chat and

00:00:05.160 --> 00:00:08.799
write down stuff in the etherpad, but you guys accommodated

00:00:08.800 --> 00:00:12.439
me very nicely, swiftly, efficiently, in spite of my quirky

00:00:12.440 --> 00:00:16.599
last minute requests. Yeah, but that's okay because, well,

00:00:16.600 --> 00:00:19.479
it's funny that you talk about accommodating you and doing

00:00:19.480 --> 00:00:22.159
all the things we need to do because, frankly, your talk is

00:00:22.160 --> 00:00:24.199
about getting things done and you've mentioned the book,

00:00:24.200 --> 00:00:27.439
obviously, but the philosophy of getting things done is

00:00:27.440 --> 00:00:30.759
ultimately what we've been applying with Emacs Conf so that

00:00:30.760 --> 00:00:33.759
when we have curveballs thrown at us, like you've done right

00:00:33.760 --> 00:00:36.399
now, we can accommodate them because we made sure that

00:00:36.400 --> 00:00:41.039
everything else was done. So we'll move to questions and I

00:00:41.040 --> 00:00:45.039
invite viewers to go to the pad, to the etherpad that is on IRC

00:00:45.040 --> 00:00:48.199
and also on the talk page and put your questions over there.

00:00:48.200 --> 00:00:51.559
But first I wanted to make sure, Bala, that if you had

00:00:51.560 --> 00:00:54.639
anything that you could not include in your presentation,

00:00:54.640 --> 00:01:00.159
just to give you some time to mention them now if you want. I

00:01:00.160 --> 00:01:09.119
think I mentioned most of what I wanted to convey. I wanted to

00:01:09.120 --> 00:01:12.479
keep it general with whichever format people are

00:01:12.480 --> 00:01:15.719
comfortable with, whether it's Org Mode, whether it's

00:01:15.720 --> 00:01:21.599
plain text, whether it is docx. In fact, I was speaking to one

00:01:21.600 --> 00:01:25.799
of my friends and he said, Hey, I use Google Sheets to note

00:01:25.800 --> 00:01:28.679
down everything, all the tasks that are coming. I said, suit

00:01:28.680 --> 00:01:33.439
yourself, whatever it is. So, in that way, this methodology

00:01:33.440 --> 00:01:37.359
or whatever, the way which we follow is quite flexible. The

00:01:37.360 --> 00:01:41.679
system is quite flexible in whichever way you want to use it.

00:01:41.680 --> 00:01:46.919
go ahead and use it. But start emptying your teacup. That

00:01:46.920 --> 00:01:50.599
will be my first and foremost. I have nothing else to add per

00:01:50.600 --> 00:01:54.879
se. Okay, cool. So we'll start with the first question and

00:01:54.880 --> 00:01:58.279
I'll be reading the questions to you. And just so we know, we

00:01:58.280 --> 00:02:01.079
have about eight minutes of Q&A until we need to move to the

00:02:01.080 --> 00:02:03.553
next talk. All right, so first question.

NOTE Q: What is TRIZ?

00:02:03.554 --> 00:02:06.399
What is TRIZ? Okay,

00:02:06.400 --> 00:02:11.679
this is a Russian methodology. It's pardon my, I mean poor

00:02:11.680 --> 00:02:16.679
Russian, but it translates to theory of inventive problem

00:02:16.680 --> 00:02:21.919
solving. So, that's what it translates to. What it is, is it

00:02:21.920 --> 00:02:26.119
is said that all the inventions problem solved so far in

00:02:26.120 --> 00:02:30.239
humanity. If you can categorize them, they fall into

00:02:30.240 --> 00:02:36.159
exactly 40 principles. That's one of the core tenets in

00:02:36.160 --> 00:02:40.959
theory of inventive problem solving. Also, that creative

00:02:40.960 --> 00:02:46.319
people have a process they follow. and in defining a problem

00:02:46.320 --> 00:02:49.839
and solving a problem. So, this is what I was trained in a

00:02:49.840 --> 00:02:55.359
company that I work for and I started using it and started

00:02:55.360 --> 00:02:59.199
applying it. So, creative process starts with defining a

00:02:59.200 --> 00:03:02.799
problem and solving a problem in a very systematic manner

00:03:02.800 --> 00:03:06.239
and you can be as creative as the creatives that we know about

00:03:06.240 --> 00:03:11.759
as the methodology talks about. So, that is what TRIZ is,

00:03:11.760 --> 00:03:15.639
Theory of Inventive Problem Solving. There is lot of open

00:03:15.640 --> 00:03:19.799
source literature like we have in Emacs. It is the same way

00:03:19.800 --> 00:03:24.159
with TRIZ, people share very generous and you can learn

00:03:24.160 --> 00:03:29.879
about it. what it can be useful for what in the core of our talk

00:03:29.880 --> 00:03:34.679
also is that many times we face conflicts, that is, I don't

00:03:34.680 --> 00:03:38.719
want to spend a lot of time, you know, figuring out a system

00:03:38.720 --> 00:03:42.919
like this. However, I want everything in one place, you

00:03:42.920 --> 00:03:46.839
know, how can that happen? So start little by little is one

00:03:46.840 --> 00:03:50.399
suggestion I have. Don't And this is also a contradiction we

00:03:50.400 --> 00:03:55.199
have, right? So, we need to spend a lot of time to set up things

00:03:55.200 --> 00:03:58.559
before we can start organizing our life. But there's not a

00:03:58.560 --> 00:04:01.599
lot of time because we haven't organized our life. So, we

00:04:01.600 --> 00:04:04.839
don't have that's a conundrum or a contradiction. That's

00:04:04.840 --> 00:04:09.479
what TRIZ methodology is about to identify that this is a

00:04:09.480 --> 00:04:15.039
contradiction and we have to resolve it not compromise. So,

00:04:15.040 --> 00:04:18.319
resolve it in a manner that gives you enough time to set up a

00:04:18.320 --> 00:04:22.439
system and enough time, free time to enjoy your life or focus

00:04:22.440 --> 00:04:26.559
on a project and be present when you're working with

00:04:26.560 --> 00:04:31.439
something. So, that's what the crux of the methodology is.

00:04:31.440 --> 00:04:34.359
Okay, splendid answer. Thank you. Moving on to the next one.

NOTE Q: Do you agree that learning similar but different things again and again is ultimately wasted bandwidth? What can we do as technologists to push back against this?

00:04:34.360 --> 00:04:37.199
Thank you for this talk. Very interesting. One of the things

00:04:37.200 --> 00:04:40.199
that frustrates me about modern web development is the rate

00:04:40.200 --> 00:04:43.279
of churn when it comes to useful knowledge. I think Emacs can

00:04:43.280 --> 00:04:45.679
help to counteract against this by building lasting tools

00:04:45.680 --> 00:04:48.279
where mastery can be built. Do you agree that learning

00:04:48.280 --> 00:04:50.799
similar but different things again and again is ultimately

00:04:50.800 --> 00:04:54.079
wasted bandwidth? What can we do as technologists to push

00:04:54.080 --> 00:05:00.159
back against this? Yeah, this is an interesting one

00:05:00.160 --> 00:05:04.879
because, I mean, I'm like everyone else where a new package

00:05:04.880 --> 00:05:09.439
shows up. I mentioned that in my talk also, the first

00:05:09.440 --> 00:05:12.879
introduction. Sajajo's newsletter is amazing. It has all

00:05:12.880 --> 00:05:15.599
these new things coming up and new developments coming up.

00:05:15.600 --> 00:05:18.879
Same thing with web dev, I guess, you have new things coming

00:05:18.880 --> 00:05:25.519
up. So you want to learn that new thing. However, you need to

00:05:25.520 --> 00:05:31.559
also be aware that there are so many other projects and

00:05:31.560 --> 00:05:37.879
hobbies or life that's also waiting for you. And it's not a

00:05:37.880 --> 00:05:42.799
balancing act, but if you if you pay attention and be present

00:05:42.800 --> 00:05:46.199
and give whatever is in front of you, it's full attention.

00:05:46.200 --> 00:05:50.959
Then look back and connect. That's an interesting way,

00:05:50.960 --> 00:05:55.759
because hindsight is 20 20. Use it to your advantage. So my I

00:05:55.760 --> 00:05:59.679
don't know, I don't want to push back against this because

00:05:59.680 --> 00:06:02.879
some of it is just amazing because it thinks that you think is

00:06:02.880 --> 00:06:05.759
a waste of time and it's a distraction right now. could

00:06:05.760 --> 00:06:09.719
potentially be. I'm not saying it will be because there are

00:06:09.720 --> 00:06:13.359
things that are truly a waste of time that could truly

00:06:13.360 --> 00:06:17.250
potentially tie back to something and be really helpful.

NOTE org-mode export, CSS, WeasyPrint

00:06:17.251 --> 00:06:22.039
I can give you an example from our Emacs part of my life. I was

00:06:22.040 --> 00:06:27.839
experimenting with CSS and Cascade style sheets and how I

00:06:27.840 --> 00:06:34.599
can customize it to use it in org mode export. For me at the

00:06:34.600 --> 00:06:38.639
time, it seemed like a waste of time. I was spending so much

00:06:38.640 --> 00:06:42.599
time. Then I parked it. I didn't do much about it later. But

00:06:42.600 --> 00:06:47.319
then one of my students said, "Your slides are too bulky for me

00:06:47.320 --> 00:06:49.588
to scroll through to get to exactly what I am looking for."

00:06:49.589 --> 00:06:55.319
I was using the reveal HTML and I used to pass on the link

00:06:55.320 --> 00:07:00.999
before. And the student sort of hinted at a handout. And now

00:07:01.000 --> 00:07:05.319
that's not easy with the RevealJS framework. It's rather

00:07:05.320 --> 00:07:08.439
tricky. At least I couldn't figure it out. but then it

00:07:08.440 --> 00:07:10.879
occurred to me that, hey, wait a second i've already looked at

00:07:10.880 --> 00:07:15.799
this CSS thing and maybe that'll help. It did help. I can

00:07:15.800 --> 00:07:18.995
drop in the name of the tool that I use now.

00:07:18.996 --> 00:07:23.016
It's called WeasyPrint uh let me use the uh

00:07:23.017 --> 00:07:24.877
i don't know if some...

00:07:24.878 --> 00:07:32.100
If you can look it up, W-E-A-S-Y print.

00:07:32.101 --> 00:07:32.519
That's what it's called. And that's

00:07:32.520 --> 00:07:36.399
mighty useful. That's really, really useful. You can

00:07:36.400 --> 00:07:40.919
customize it. You can change everything. I think I can even,

00:07:40.920 --> 00:07:44.519
I'll probably even share the code later on. It's really

00:07:44.520 --> 00:07:48.959
useful and I've been able to, so what seemed like a waste of

00:07:48.960 --> 00:07:52.039
time is actually something that became useful later on. But

00:07:52.040 --> 00:07:55.519
there are several other things I have truly wasted and it's

00:07:55.520 --> 00:07:58.439
not been useful because I couldn't connect the dots. So,

00:07:58.440 --> 00:08:06.239
perhaps the, let's say, wasteful of time so that you look at

00:08:06.240 --> 00:08:09.159
something and see how to connect back like the Zettelkasten

00:08:09.160 --> 00:08:12.839
that everybody talks about. I do not use it, but I like the

00:08:12.840 --> 00:08:15.399
idea that you look at it keeping in mind that you could

00:08:15.400 --> 00:08:19.359
probably connect to something later on. Perhaps, just try

00:08:19.360 --> 00:08:24.519
it out. OK, great, Bala. Sadly, we are a little short on time

00:08:24.520 --> 00:08:27.159
to answer all the questions that we have. I see three

00:08:27.160 --> 00:08:31.039
questions currently that can still be answered, and I don't

00:08:31.040 --> 00:08:33.919
think any of them would be answerable within just one

00:08:33.920 --> 00:08:37.559
minute. So what I suggest we do, Bala, feel free. Do you have

00:08:37.560 --> 00:08:40.919
access to the pad on your end? Yes, I do. I do. I have it here.

00:08:40.920 --> 00:08:43.707
Okay, cool. I'm putting the link on BBB just in case you need

00:08:43.708 --> 00:08:44.919
to review it.

00:08:44.920 --> 00:08:47.039
We're going to leave the room open. By the way,

00:08:47.040 --> 00:08:49.399
if anyone in the crowd wants to join so that they can ask the

00:08:49.400 --> 00:08:51.919
question directly with their voice to Bala, feel free to do

00:08:51.920 --> 00:08:56.119
so. The links are on the website. But Bala, if no one shows up,

00:08:56.120 --> 00:08:58.559
if you could just answer the three questions that we haven't

00:08:58.560 --> 00:09:01.239
covered yet, actually. Well, three questions because

00:09:01.240 --> 00:09:04.359
Sacha just put the link right there. That'd be lovely. And

00:09:04.360 --> 00:09:06.080
we'll make sure that the entire Q&A

00:09:06.120 --> 00:09:07.839
finds its place into the

00:09:07.840 --> 00:09:10.719
website afterwards. How does that sound for you? Yeah,

00:09:10.720 --> 00:09:14.559
sounds great. Thank you so much. I'll do make sure that I will

00:09:14.560 --> 00:09:17.159
have the answers there, but I'm going to wait here for some

00:09:17.160 --> 00:09:20.559
time so that somebody can join. Okay, sure. Any last word in

00:09:20.560 --> 00:09:26.799
10 seconds for the public? Well, empty your teacup and enjoy

00:09:26.800 --> 00:09:27.199
your life.

00:09:27.200 --> 00:09:29.879
Splendid. Thank you so much, Bala, for coming

00:09:29.880 --> 00:09:32.359
again to EmacsConf this year, and hopefully we'll be seeing

00:09:32.360 --> 00:09:36.439
you next year with further talks to discuss. Yeah, thank you

00:09:36.440 --> 00:09:39.559
so much. All right, and right now we'll be moving to the next

00:09:39.560 --> 00:09:42.039
talk of the day in about five seconds. Thank you again, Bala,

00:09:42.040 --> 00:09:46.799
and see you later. Bye.

00:09:46.800 --> 00:09:49.399
All right, we are a fair. So, Bala, I'll need to move to make

00:09:49.400 --> 00:09:51.759
sure that everything is working for the next talk. So, do as

00:09:51.760 --> 00:09:55.320
we said, and everything will be fine. Okay.

00:09:55.333 --> 00:09:58.879
Okay, bye-bye, Bala. Bye. Bye, Leo.

00:09:58.880 --> 00:10:15.119
Okay.

00:10:15.120 --> 00:10:21.679
Hello everyone, do you want me to answer a question? I'll be

00:10:21.680 --> 00:10:23.399
happy to answer that. You want to discuss something? You

00:10:23.400 --> 00:10:27.759
want to share something? I'm here for that. Please let me

00:10:27.760 --> 00:11:06.479
know.

00:11:06.480 --> 00:11:10.599
I'll hang around for another 5 to 10 minutes. Please let me

00:11:10.600 --> 00:11:14.439
know if you have any questions or if you're the ones who ask

00:11:14.440 --> 00:11:36.739
those questions also, please let me know.

00:11:36.740 --> 00:11:38.560
Are you there?

00:11:38.625 --> 00:11:44.359
Hi, yes. Some tips I've found for getting

00:11:44.360 --> 00:11:50.399
things done with an image for this stuff is like for

00:11:50.400 --> 00:11:53.919
separations you have like your Zettelkasten, you're

00:11:53.920 --> 00:11:56.799
getting things done, and then beyond that you have like

00:11:56.800 --> 00:12:00.559
dailies and global.

00:12:00.560 --> 00:12:06.439
Daily Zettelkasten would be journaling. Okay, okay. And

00:12:06.440 --> 00:12:10.479
then, like, global or daily getting things done, I

00:12:10.480 --> 00:12:11.919
generally like doing it in a week.

00:12:11.920 --> 00:12:13.800
And then splitting the,

00:12:13.833 --> 00:12:16.120
like, core tasks, secondary tasks,

00:12:16.121 --> 00:12:17.220
unplanned tasks,

00:12:17.221 --> 00:12:22.079
because those are good categories.

00:12:22.080 --> 00:12:26.439
I like what you're doing.

00:12:26.440 --> 00:12:32.199
Sorry? Do you do things like that at all?

00:12:32.200 --> 00:12:38.279
Or are there separations like with Zettelkasten

00:12:38.280 --> 00:12:45.839
versus the Getting Things Done?

00:12:45.840 --> 00:12:52.279
That's very interesting, yes. Daily log and weekly log,

00:12:52.280 --> 00:12:56.800
that's really helpful. I've also been trying to do that but

00:12:56.821 --> 00:13:02.279
not being able to successfully do a daily log plus a weekly

00:13:02.280 --> 00:13:06.879
log. So I gave up on the daily log because it seemed to be like a

00:13:06.880 --> 00:13:12.479
lot of overhead for me, so I just switch to a weekly review

00:13:12.480 --> 00:13:16.759
where I would log what's going on and how it is. But it's also

00:13:16.760 --> 00:13:19.759
interesting to see how it connects back to something that

00:13:19.760 --> 00:13:22.639
we've already worked on, or we've already learned

00:13:22.640 --> 00:13:26.039
somewhere, which is essentially using the ZIP and custom

00:13:26.040 --> 00:13:30.239
method. I probably want to try that a bit later on also.

00:13:30.240 --> 00:13:34.199
That's a great suggestion, nice idea. Oh, so some of the

00:13:34.200 --> 00:13:38.039
reason for the separation would be with the daily log, like,

00:13:38.040 --> 00:13:42.839
for instance, the title for the journal would be, Audinet

00:13:42.840 --> 00:13:47.359
would be the day, and it starts blank. And then, so if you have

00:13:47.360 --> 00:13:50.159
a straight thought, if you know it can go straight to your

00:13:50.160 --> 00:13:53.479
Zettelkasten, it goes into your Zettelkasten. If you don't

00:13:53.480 --> 00:13:57.679
know where it goes, it goes into your journal. And then same

00:13:57.680 --> 00:14:01.839
thing for like the week, is like your weeks always start

00:14:01.840 --> 00:14:04.879
emptying, so like if you have your core tasks, like if it

00:14:04.880 --> 00:14:08.119
spells beyond three, it's probably not a core task. So it

00:14:08.120 --> 00:14:11.359
gives you the idea of like, did I actually do what I wanted to

00:14:11.360 --> 00:14:16.999
yesterday, rather than getting 20 things done that I don't

00:14:17.000 --> 00:14:22.159
really care about that much. Yes. True, true, true. Very

00:14:22.160 --> 00:14:23.759
true. Yeah.

00:14:23.760 --> 00:14:30.959
Nice, nice talk. Thank you so much for sharing that. I've

00:14:30.960 --> 00:14:35.279
been a, let's say a start and many times I've started on

00:14:35.280 --> 00:14:40.799
Zettelkasten, you know, with little notes. They have these

00:14:40.800 --> 00:14:43.399
fleeting notes and permanent notes. I've tried many of

00:14:43.400 --> 00:14:48.199
those, but somehow it's not sticky for me. I've not been

00:14:48.200 --> 00:14:51.399
able to get rid of that.

00:14:51.400 --> 00:14:55.919
Yeah, I've got multiple attempts of using these systems,

00:14:55.920 --> 00:15:01.999
becoming too big or complex, like I don't know where to put a

00:15:02.000 --> 00:15:06.679
new piece of information, so then I throw the whole system

00:15:06.680 --> 00:15:14.639
away. So, this is my favorite iteration that I've done so

00:15:14.640 --> 00:15:23.399
far. I'm sure it'll change with time. Okay, okay, okay, I

00:15:23.400 --> 00:15:25.079
see. Yeah, I...

NOTE Daily log

00:15:25.080 --> 00:15:31.759
I like the way the daily log works, that it has an embedded,

00:15:31.760 --> 00:15:36.799
you know, you just have a name stamp and then you embed

00:15:36.800 --> 00:15:40.479
something from another project. And when you go to the

00:15:40.480 --> 00:15:44.559
project page, the same thing shows up there in the log also. I

00:15:44.560 --> 00:15:48.679
wanted to take that feature and have that in my optimal

00:15:48.680 --> 00:15:53.399
setup. I'm not well versed enough to get that set up because I

00:15:53.400 --> 00:15:56.799
like that with that. Anything I enter in the daily log should

00:15:56.800 --> 00:16:00.359
show up in my project log also and vice versa. I want to

00:16:00.360 --> 00:16:04.799
execute on my project. I need that notes where I'm looking

00:16:04.800 --> 00:16:10.599
for. That's a key feature of that is with logseq you just have

00:16:10.600 --> 00:16:14.160
a button that says go to today. So you don't think about it and

00:16:14.161 --> 00:16:18.060
it always starts empty. It's that blank sheet that's always

00:16:18.061 --> 00:16:23.079
confirming you want the things that I used that before.

00:16:23.080 --> 00:16:26.360
One of the things I really wanted was, I want this,

00:16:26.397 --> 00:16:29.198
but I want it for Getting Things Done on my journal.

00:16:29.199 --> 00:16:36.279
I want two separate ones.

00:16:36.280 --> 00:16:45.319
Yeah, I like the, also I'm trying to see how to create pages

00:16:45.320 --> 00:16:51.119
quickly from within Org Mode. I know we can do the square

00:16:51.120 --> 00:16:55.879
bracket thing and enter and it should go into a new page. but

00:16:55.880 --> 00:17:00.879
it's not as seamless as in logseq or obsidian i'm trying to

00:17:00.880 --> 00:17:06.239
see how which way do i do that quickly so that you don't spend

00:17:06.240 --> 00:17:10.439
time on organizing once you have the bigger setup of the

00:17:10.440 --> 00:17:14.959
folder structures and the to do then it's easier to

00:17:14.960 --> 00:17:18.599
integrate it but if i'm starting from a business point of

00:17:18.600 --> 00:17:22.679
view it's rather tough for them to set it all up because the

00:17:22.680 --> 00:17:27.679
setup costs are very high in terms of system first and then

00:17:27.680 --> 00:17:30.639
start with this. Or like you said, you know we could also

00:17:30.640 --> 00:17:33.759
start with a blank sheet and then start filling it up and then

00:17:33.760 --> 00:17:39.159
see how to link up things or move it around so that it fits into

00:17:39.160 --> 00:17:44.719
your larger system or evolve a system as it goes. Don't start

00:17:44.720 --> 00:17:47.959
with the system in mind, but evolve it because it then fits

00:17:47.960 --> 00:17:52.559
into how you are rather than the you trying to adapt to the

00:17:52.560 --> 00:17:53.159
system.

NOTE Capturing

00:17:53.160 --> 00:18:00.559
So, Denote and org-roam, they'll have a feature, like the

00:18:00.560 --> 00:18:05.199
note, you have a command called, let's see, create or

00:18:05.200 --> 00:18:09.479
existing note, and org-roam has an equivalent to that, and

00:18:09.480 --> 00:18:14.999
what that, you need to consult with that, as you are browsing

00:18:15.000 --> 00:18:19.279
your notes, you see that, and so if you're making a new note,

00:18:19.280 --> 00:18:23.119
power generation or something like that you'll easily see

00:18:23.120 --> 00:18:27.799
if you have any notes that are in power generation or like

00:18:27.800 --> 00:18:30.839
let's say you have something in power and if you don't you

00:18:30.840 --> 00:18:34.079
just go down to where you're just you know you don't have

00:18:34.080 --> 00:18:39.599
anything selected or so it's your what's in your uh what your

00:18:39.600 --> 00:18:46.719
current so you're not pre-selecting something existing

00:18:46.720 --> 00:18:51.599
and voila now you have a file And then you have consult so you

00:18:51.600 --> 00:18:57.879
can preview them as you move up and down the list.

00:18:57.880 --> 00:19:02.319
And then you also got Emacs

00:19:02.320 --> 00:19:10.719
Org Capture to just pop up a template

00:19:10.720 --> 00:19:16.599
capture buffer that is blank that you can tell to go into

00:19:16.600 --> 00:19:20.919
something like a journal or a GTD inbox.

00:19:20.920 --> 00:19:27.279
And yeah, this allows you to just make it like a specific

00:19:27.280 --> 00:19:30.999
buffer to do that specific task. I think Protesilaos has a

00:19:31.000 --> 00:19:35.479
video about how to make that into just a pop-up window. Like

00:19:35.480 --> 00:19:41.519
for instance, you're in your browser, you pop it up, Uh, jot

00:19:41.520 --> 00:19:49.599
down your task, press enter, and it's gone. Hmm, okay. Okay,

NOTE Note silos

00:19:49.600 --> 00:19:54.919
okay, makes sense, makes sense. Yeah, for me, I wanted to try

00:19:54.920 --> 00:20:01.079
denote, but my folder structure, I found it very difficult

00:20:01.080 --> 00:20:04.559
to move it to a denote kind of a structure where the folder

00:20:04.560 --> 00:20:08.519
hierarchy is not as important because all nodes are treated

00:20:08.520 --> 00:20:12.639
the same. But for me, because I'm focusing on a project, I

00:20:12.640 --> 00:20:17.079
need only the project files show up. It was tricky for me to,

00:20:17.080 --> 00:20:20.599
because sometimes I share the folder with my colleagues and

00:20:20.600 --> 00:20:24.519
who are not on Emacs or more. So I can't show them all the

00:20:24.520 --> 00:20:28.879
files, all the notes. I just want that folder to be shared and

00:20:28.880 --> 00:20:32.439
ignore the todo.org that is there because it's not readable

00:20:32.440 --> 00:20:37.679
for them. So, I find it easier to share a folder level or a

00:20:37.680 --> 00:20:41.639
project level and that's why I stuck to this format which is a

00:20:41.640 --> 00:20:46.639
hierarchy of folders with the to-do inside those folders.

00:20:46.640 --> 00:20:49.719
That works very well for me, particularly keeping in mind

00:20:49.720 --> 00:20:52.479
that I need to share some folders sometimes with my

00:20:52.480 --> 00:20:57.439
colleagues. Whereas Denote with a flat structure or

00:20:57.440 --> 00:21:01.919
Roam with a flat structure, I find it very tricky to do that.

00:21:01.920 --> 00:21:06.079
With Denote, you can actually have, there's a feature

00:21:06.080 --> 00:21:07.759
called silos that will

00:21:07.760 --> 00:21:13.199
allow you to do both and I think you can make customized

00:21:13.200 --> 00:21:17.959
commands to go that work only in specific silos. I haven't

00:21:17.960 --> 00:21:20.919
messed around to it. too much with them. I don't think org run

00:21:20.920 --> 00:21:24.719
has anything like that though. Yes, I don't think they have

00:21:24.720 --> 00:21:28.239
that. But I remember seeing silos. Maybe I should give it

00:21:28.240 --> 00:21:32.119
another spin and see if that works. Because if it can solve my

00:21:32.120 --> 00:21:36.519
creating new node quickly from the denote part itself while

00:21:36.520 --> 00:21:40.439
I'm writing the nodes itself rather than go through the R

00:21:40.440 --> 00:21:45.439
capture. That will really help me in linking back and seeing

00:21:45.440 --> 00:21:49.399
how it maps to another project that I've already worked on

00:21:49.400 --> 00:21:53.999
from an archive and then bring it there. I think that's a good

00:21:54.000 --> 00:21:57.639
idea. I'll look at silos again. Also, with the silos, let's

00:21:57.640 --> 00:22:03.719
say you're going to use ripgrep on the directory, you could

00:22:03.720 --> 00:22:07.799
intentionally keep your Zettelkasten and your journal

00:22:07.800 --> 00:22:13.159
separated. in different folders, like, yeah. So that,

00:22:13.160 --> 00:22:19.039
like, if you direct them, or if you wanted to share folder by

00:22:19.040 --> 00:22:23.399
folder basis, yeah, you don't have to be the all-in or

00:22:23.400 --> 00:22:30.759
nothing approach. Yeah, that works. That works.

00:22:30.760 --> 00:22:35.119
Excellent.

00:22:35.120 --> 00:22:37.839
OK.

00:22:37.840 --> 00:22:44.159
Well, thank you so much for your time and for sharing what is

00:22:44.160 --> 00:22:47.919
really helpful for me. I hope the talk was useful for you.

00:22:47.920 --> 00:22:53.839
Yep. Thanks for sharing. Have fun with the rest of the Emacs

00:22:53.840 --> 00:23:00.799
camp. Okay. All right. Then see you then. Happy Emacs month

00:23:00.800 --> 00:23:06.200
to you too. Okay. Bye. Bye.