Revision is important! (I think)
Hello to each and every reader, and hello to future me!
I remember studying the tiniest amount of other programming languages, and then burning out really fast and forgetting all of the material, so now I'm making an effort to revise what I'm learning, which is great timing because the next step on the android course thingy is practicing with compose!
But in regards to actual progress, I didn't manage to do much today.
I got a bit stuck doing the practices, but before I look at the solution code, I'll give it another shot tomorrow once I'm well rested.
I'm starting to think that if I keep making such small steps forward, there's no chance I'll have anything functional in a month or so. But, I keep reminding myself that I signed up for the app development contest as an excuse to learn something I otherwise wouldn't. So, if I don't meet the deadline, I'll just ignore it and continue learning at my own pace.
That's all for now, cya tomorrow! :D
Here is a trick! Code should be self documenting. So make it! :D 20% of my C++ language is in my notes. The rest is here:
They are created on Godbolt.org and can be oppened and read in on it too, or any other IDE:
Written by me, for me. And when it runs it tells me what is happening and why!
And everytime I need a concept I go back and figure it out from these. Sometimes my notes are not good enough and I still cannot remember or use the knowledge. Then I improve my notes! So they get smoother over time! :D That way I can retain infinite knowledge! :D
Thank you so much for sharing this!
It makes a lot of sense to use code to document what the code actually does, it's genius! (and I feel a bit silly for not doing this already lol)
I'll start implementing this type of note-taking asap.
Thank you again!
Woooooo! Moose did a success!
Would you advice to do this for personal projects or can I do this for the company projects?
Yes! But! It is important to think about what you want the code to say, and who you want to say it to. That is also why doing it for yourself, even for language stuff is a good idea. Because communicating with yourself is a version of it that is easier that communicating with a developer that you will never meet who sees your code after 15 years. So start with the easy version where you can notice both how you write the things down, and how you understand them when you come back to them later. And then start doing it in projects in general. Once you start writing with code instead of writing code you get this... dizzy feeling as you realize that programming languages are just details for the spell that links you with a machine so you may whisper a soul into its metal frame. Its a neat way to think about code is my point :p
