David Oakes Learning Journal

Another bi-weekly post. Or at least, it is by official declaration. The final eighth week of each class in the program is only half length. Which is somewhat confusing to say at least. By my count, this is covering the 21st and 22nd weeks, which is making me think I've missed a post or two somewhere in the program. In any case, despite how well things have gone for me thus far in the program, I find myself having lengthy moments of what I can only describe as "overextension of perception of the surrounding world." At one point I would've been able to write them off as mere anomalies. Unusual spates of activity from my, frankly, overactive imagination. Little nightmares, more often impossible, of futures bearing fruitlessness or failure. I know that this sort of thing isn't healthy. That expecting the worst means expecting to not be disappointed. But that's why I find it often helps. After a certain point, one learns that its way more fun to be surprised than i...

 So, here we are with another bi-weekly post. I did have that quick message with the instructor about maybe branching out in regards to topics here on the learning journal. And, to be frank, I'm still not sure what I was expecting out of it, if anything. According to the instructor, it was designed around the learning science. He did recommend that I at least try to maintain weekly posts, even if it did amount to short recollections of the mundanity of the learning process.  Still, the seeming mundanity of the course as it is, isn't all bad. I'm finding even mildly novel experiences to be rather exciting. It might not seem like much but this weeks Python code work had a novelty in one of the test files. I'm so used to seeing near instantaneous responses out of these, the fact it took nearly a minute and a half to complete had me thinking I'd somehow managed to deadlock it. Another novelty, The answer being simple and straightforward. I'm so used to answers needi...

 In all honesty, I would've posted something last week, but I just didn't very much to post about. The most interesting thing that's happened, school-wise, is the fact I had my first proctored exam on the 31st. Don't get me wrong, I'm confident in how it turned out, and it was a pleasing twist on the usual online/Canvas test taking. The issues is that that's really the only thing that I have to write about that's related to school. This is why I don't see myself as a blogging sort of person, I always run out of things to say. Yes, there are other things going on in life and the world but I'm not sure if any of it fits the limitations here. These supposed-to-be-weekly writings are meant to be a learning journal throughout the program I'm in, and some of what I have to talk about is much more likely to come across as me ranting about something unrelated to my learning experiences. So, as much as I wish I could pen more about how things are going he...

 I know. I know. I missed last week's post. But that just shows how much a break (as needed as it was) can mess with one's rhythm. Entering the new year we began our Intro to Database Systems course. I wasn't expecting to meet back up with the Python programming language again. Or the fact that setting everything up would be so quick and straightforward for such an intricate and widely used set of programs.  I consider this a good thing, as a groupmate of mine had started an internship and Docker Desktop was one of the programs they were being tasked with using. It was through them that I learned how widely the tool was used, so it should come as no surprise that I feel the need to keep a notebook of various functions, tools and tricks to use with Docker and other programs like it for use later. Come to think of it, I've been having that same feeling, albeit retroactively, about the software engineering course I finished before the new year. I certainly hope I can go ba...

The semester now comes to a quiet close. Sorry I couldn't post last week. Christmas is rolling up, and the second and final project must be finished by Friday morning. I simply haven't been able to find the time. Regardless, my time in the Software Engineering course is also coming to a close. Tomorrow begins the last official week until the winter break, in time for Christmas. My question: Where the heck did it all go?! I feel like I've only gotten started.  Regardless, This last prompt has asked me how I would've approached the first homework assignment differently, knowing that which I do now. All truths told, I don't think my approach would've changed particularly much. The Hangman assignment was a simple game of hangman played within the console. Much of it is built around the StringBuilder and a collection of integers. I personally, do not see how a Data Access Object or Repository would improve it, beyond adding a few extra bells and whistles. Pulling the...

My time managment skills(more like the lack there of) are really starting to show here. Cut it real close with the Gymlog program we had as homework. Got it in the end, but am I worn out from all the frantic bug checking. Once again the prompt this week is to reflect on last weeks homework. In this case it was  a Markov text generator. And at the hour I'm penning this I once again won't be able to answer every question. I know, I really need to get this work scheduling thing down! In any case, much of my strategy for Markov was the same as the LDPM from the week before. Go over the documentation, set up the method frameworks and comment-notes, then write out the code. And spend at least an hour fuming over that one bug that's shown up unannounced and is wrecking everything. Considering how well the approach is performing thus far, save that last bit, I might end up keeping it. And that statement goes for how I handle Java style, too. If it isn't broken, why risk breakin...

 Now this was a busy week. Not coursework, but a lot of holiday prep. Thanksgiving is literally day after tomorrow and here I am trying to get coding work done. This week's work saw us delve into the workings of Android studio in greater formality. As much as I wish I could go into greater detail, the writing prompt for this journal that Dr. C had provided wanted me to go over my solution to the major project the class had finished last week. The project was called Legally Distinct Pocket Monster, or LDPM for short.   Granted the prompt also directly stated that I was to work with at least one other student, but I couldn't get that to happen. Equal parts the bedlam of upcoming holidays and my own shortfalls in time-management. I'll get the latter sorted out at some point. Hopefully. Maybe. Probably.  In any case, I won't be able to answer every question on the prompt. Obviously not the ones that mention the approaches of my fellow student, at least. Solving the assig...