Another advantage of the "it's on your phone" aspect is that it follows you when you switch cars. If I use my friend's car, I still have MY system. If I rent a car for a trip, I still have MY system.
I think this is cool proof of concept. But a warning: because it stores all the data on your PDS, and (at the moment) all PDS data is public, DO NOT USE IT to store any private information.
It is a huge drawback, but in the future it may become more interesting.
First of all, that’s great. That’s what I hope it would happen: non technical people using this tools, feeling the apart of “power” of coding, and feeling the desire to learn more.
About your question, it is hard to give one. I don’t think there is one big thing that makes everything click, and if there is one, it is probably different for different people. But I can give some advices.
1. You can ask the AI itself to explain how the code works. In my experience they are usually fine at that. You can probably tailor the explanation to your technical level, so that’s neat.
2. Stick to one language. I don’t know which language your AI is using for your tools (probably Python if they run on your machine or JavaScript if they work on a browser). Learning what you are using is the first step.
3. Once you know that, you can use the AI and some online guides to learn the very basics of the language. Maybe ask the AI for very simple toy tools (e.g., a web page where you write a phrase, click a button, and it will show that phrase with the words in reverse order) and try to understand what the code does. You may still ask the AI about the lines you don’t understand.
4. It is a potentially long journey. Go as far as you like. After these first steps, you will likely have more specific questions. That’s good. :)
I made something similar on my blog and had the same question. I decided to show in my blog only the comments that I liked. Therefore transforming the “like” action into an “I approve” action.
But I have few comments. Not sure if is a good solution for people with a lot of comments.
This works for me in general. If I am procrastinating, I ask a coding agent for a small task. If it works, I have something to improve upon. If it doesn’t work, my OCD forces me to “fix it.” :D
Not only that. My brain operate differently at different times. I may find that an approach that works for me now doesn't work in a year. It doesn't mean the approach is "wrong" or that I was wrong choosing it a year ago. Maybe it was the right approach for that time, and now I have different needs.
> And if you know enough to know to ignore ChatGPTs suggestions, you didn’t need it in the first place.
This will invalidate even ispell in vim. The entire point of proofreading is to catch things you didn’t notice. Nobody would say “you don’t need the red squiggles underlining strenght because you already know it is spelled strength.”
This looks fine, but then if I rename the note, the code changes, invalidating all the hand-written notes links. So it feels unpractical. I would still prefer to encode the creation timestamp and put it in the title/filename/property. At least this would be fixed.