thek3nger
Joined 15 years ago
Joined 15 years ago
It is a huge drawback, but in the future it may become more interesting.
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. :)
But I have few comments. Not sure if is a good solution for people with a lot of comments.
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.”
[actions.sidebar]
buffer = "replace-pane"In some sense, premium Spotify users pay also for the free users and, therefore, the average is lower (yes, there is ads income but I bet is negligible).