My learning journey is vast, immersive, and cyclical. If I don't finish something right away, or if I start something new, I almost always cycle back to the old ones. I feel I have learned a lot this way, for better or worse.
The only (self-)criticism I would offer regarding my course of learning is that I have really struggled to make time to sit down and #code at my actual keyboard
so tonight, for the record, I took a bit to copy these tweets over to LinkedIn.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Uninstalled and reinstalled @ProgrammingHero again, did the exam for #Cpp course, and it still crashed at the end.
:/
It could be my phone. I'll have to try installing it on another device. Still a bummer
Also resinstalled the very different app, @Prghub, which has much shorter courses and as a result felt deceptive about how much you were learning. I haven't uses it in over a year for sure. They have a bunch of new courses. I'll try some-I don't know if I'll keep at it w this app
#willwritesandcodes#100DaysofWriting#Day23-#Day27, need to keep track of how much I write and where. I kind of write a lot, but not always towards the goals I want to write toward. So I'm writing this tweet to stand in for missing those days' record while noting that I do write
@wildlearnerapp's #React course has taught me more so far than at least one other online course, if not two others.
My strategy is #repeatedexposure - the more I get aquainted with a lot of the concepts, the easier I find it to engage in coding itself, its concepts, syntax, & logic --- especially since I have such a hard time getting to sit down to actually code, given my job and family life.
"The falsity of the antecedent does not make that "equally irrelevant" as "if an avalanche happens happens the moon will explode," with or without determinism."
Several issues come in here:
truth, possibillity, causation, wh is probably why we run into difficulty.
Today I did several @enkidevs workouts on #CSS and #interviewprep, finally actually finished the #HowToProgram video on Python Modules, typing up a #python program from the video which I hope to record an audio code walkthrough for.
Hoping to get more done today still. Overall, I've been pretty productive, due in part to using the #forestapp for #focus.
I've heard a number of people talk about how important it is to get used to reading other people's code, actually understanding it, and talking about it, so if I start doing these walkthroughs it will be to practice those skills.
I find it is frustratingly easier to study than to actually sit down and code. Is this procrastination? Why is typing out lines on the computer harder than reading etc?
Probably fear of failure mixed with the sense of being so slow, already bypassed by others, that I feel walking in the right direction is almost - a waste of time?