Learning Node.JS and Bullet Journaling

For a while I have wanted to learn Angular, Laravel and other frameworks but I felt overwhelmed so I decided to learn JavaScript but then I found that I had gaps in my knowledge too, so I went over to Node.js. Now I feel that I am starting to understand more. I understand the context better. I understand the underlying code better. I have spent enough time studying around the subject that I have gained the contextual understanding not to be completely lost.

With HTML and other technologies you can build and fail, and build again and fail, and eventually you will get what you want. With Javasscript, and to some degree with CSS too, you need to understand what you’re doing to see a result. You need to find code, tinker with it, and get it to do what you want. It takes trial and error, and hours of experimenting in some cases.

That’s why you watch courses. With courses you have it explained to you. You then try to copy the code without inserting errors, and then you debug until you have found all the typos. Plenty of people will say that you’re not meant to just copy code. My aim, in having examples explained to me, is to gain a contextual understanding of how to do things, and how they work. The aim is to become self-sufficient enough to write my own functions and applications.

Bullet Journaling

I have known about Bullet Journalling for years but I have had no or little interest in it because it seemed like an archaic way of keeping track of tasks, projects and more. Yesterday my curiousity was woken again so I have decided to play with the concept. I am using an old notebook that I have had for years. I have until January to see if I like the idea or not. I want to see whether it has a positive effect on how I get on with projects.

I will write more, when I have more experience.