This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
blog:fall2015:pgrant3:journal [2015/09/15 00:17] – [September 7, 2015 UNIX] pgrant3 | blog:fall2015:pgrant3:journal [2015/12/08 03:56] (current) – [November 16, 2015 C Prog] pgrant3 | ||
---|---|---|---|
Line 8: | Line 8: | ||
This week I have learned how to create files and directories, | This week I have learned how to create files and directories, | ||
+ | |||
+ | ====September 17, 2015 UNIX==== | ||
+ | |||
+ | I can now look up manual pages for commands rather than just using the limited help feature. | ||
+ | |||
+ | ====September 23, 2015 UNIX==== | ||
+ | |||
+ | After practicing more with wildcards, I am comfortable utilizing them in order to list files based on certain parameters. | ||
+ | |||
+ | ====September 24, 2015 UNIX==== | ||
+ | |||
+ | After saving three of the configuration files to my home directory, and logging into the lab46 pod in class today, I saw how much I altered. | ||
+ | |||
+ | ====September 28, 2015 UNIX==== | ||
+ | |||
+ | With regards to the answers that were asked for on pbx0, after copying file.txt from the public directory, and using the file command on it, file.txt was an ASCII file, which is what I would have guessed from viewing it as well. However, I now understand that unlike in windows systems, he .txt file name extension has no bearing on the filetype of the document. | ||
+ | |||
+ | I found pbx0 to be challenging and fun. Now knowing that we will not have procedural instructions to complete a task, solving a problem seems more rewarding. | ||
+ | |||
+ | ====October 5, 2015 UNIX==== | ||
+ | |||
+ | After getting through pbx0, and experiencing the accomplishment that I felt for solving it, I thought that pbx1 was going to be almost the same thing. | ||
+ | |||
+ | Something that I found was interesting on the endeavor of pbx1 so far was having to modify file permissions when we called on uudecode, in order to be able to see the file that it created, upon decryption. | ||
+ | |||
+ | We also covered vim a lot more this week as well, as well as beginning shell scripting. | ||
+ | |||
+ | We began covering shell scripting last week, in one class I believe. | ||
+ | |||
+ | ====October 19, 2015 UNIX==== | ||
+ | |||
+ | I have continued my exploration of vim through my iMac at home. I was not aware that it came stock on mac machines, which is nice. After attempting to code and script on my mac via vim, I learned that you can get extensions for vim that allow it to become and IDE. I very briefly looked into this, but it looks like it would be extremely useful to my needs. | ||
+ | |||
+ | The new project we are working on has us creating a web based text adventure style game, with different pages that link to one another. | ||
+ | |||
+ | With regards to shell scripting, I have let it take a back seat to working with proficiency in vim as well as the current project. | ||
+ | |||
+ | ====October 26, 2015 UNIX==== | ||
+ | |||
+ | My web based text adventure is going well, I have the ground work laid out on paper, and know exactly how I am going to finish it. Prior to this project I was not interested in learning front end web development, | ||
+ | |||
+ | We looked at shell scripting more in class, and I have been playing with it out of class. | ||
+ | |||
+ | ====November 2, 2015 UNIX==== | ||
+ | |||
+ | After completing the wpa0 project, I have learned a lot about changing web pages based on directories that the source code is located in. That was my biggest issue when working on this project. | ||
+ | |||
+ | The next project that we are doing seems difficult in the way that the puzzle box projects were. We are given a file and we have to use the tools at our disposal to resolve the problem. | ||
+ | |||
+ | ====November 9, 2015 UNIX==== | ||
+ | |||
+ | I successfully completed udr0. As I said in my previous entry, I had spent quite a bit of time poking at it, just looking for a place to start. | ||
+ | |||
+ | The next project we have due this Wednesday has us writing a script, which I desperately need more practice with. I haven' | ||
+ | |||
+ | I ended up downloading a Unix based OS on my home computer called Fedora. | ||
+ | |||
+ | ====November 16, 2015 UNIX==== | ||
+ | |||
+ | I have started working the logic on for the project that was extended a week, due this Wednesday, rather than last Wednesday, out on paper. | ||
+ | |||
+ | As far as working on my own, I couldn' | ||
+ | |||
+ | ====December 7, 2015 UNIX==== | ||
+ | |||
+ | After finishing sfp0, I can comfortably say that I am almost a little bit comfortable with scripting. | ||
+ | |||
+ | After looking at the end of course experience, I am glad that I took the last assignment as serious as I did. It looks like that is a significant portion of our final project set. I will probably go through all the previous projects as well in order to refresh myself. | ||
====September 7, 2015 C Prog==== | ====September 7, 2015 C Prog==== | ||
Prior to this course I had no knowledge of memory management when I would write a program. | Prior to this course I had no knowledge of memory management when I would write a program. | ||
+ | |||
+ | ====September 14, 2015 C Prog==== | ||
+ | |||
+ | Throughout this week, I had to take a close look at pointers and really focus on what they are doing to finally understand what they do. I can confidently say that I understand them enough now to actually say I understand them. That a pointer points to a physical memory address in the machine, rather than a set value that we give it, and every time we run that program, the address of the pointer will change. | ||
+ | |||
+ | ====September 17, 2015 C Prog==== | ||
+ | |||
+ | I understand loops more than I had ever thought I would or, ignorantly, thought I would need to. Approaching problems before, when I needed a loop, I would always default to a while loop. I understand when to use for loops, such as when you know how many iterations of the loop you would like to run. Also, I encountered a situation when I was doing the DOW0 project where I was attempting to use a while loop, but the condition I was evaluating had a variable that I had not initialized prior. | ||
+ | |||
+ | ====September 21, 2015 C Prog==== | ||
+ | |||
+ | We started going over how to find digits in a number, mainly using the % operator to find the remainder, and putting that into a loop with a counter variable. | ||
+ | |||
+ | ====September 28, 2015 C Prog==== | ||
+ | |||
+ | In the past week, I haven' | ||
+ | |||
+ | After reviewing the pattern that is used in order to multiply a one, two, or three digit number by eleven, as mbe0 asks us to do, one can definitely see a pattern develop. | ||
+ | |||
+ | The only part of the project that I seem to be having trouble with is determining if the input is one digit, two digits, or three digits. | ||
+ | |||
+ | At the end of the day, I am getting a lot more comfortable with the mindset of looking at a problem, and breaking it down into smaller pieces, and working through one thing at a time. Before, I would just rush and half way understand something, before trying to implement it further, into something I barely understood. | ||
+ | |||
+ | ====October 5, 2015 C Prog==== | ||
+ | |||
+ | This past week we have looked at functions again, and in greater detail. | ||
+ | |||
+ | Aside from that, I have been working on completing the current project due, mbe1. This time we could use arrays and loops in order to satisfy the algorithm. | ||
+ | |||
+ | After coming in close to finishing the project, I have found that if you want to complete many tasks, of the same nature, using a loop is definitely more viable. | ||
+ | |||
+ | Something that I have been thinking about as well, when looking for side projects outside of class to do, is looking online. | ||
+ | |||
+ | I have made it a goal of mine to attempt to solve at least one problem on that website, that is of easy grade, each week along with the current projects that we are doing. | ||
+ | |||
+ | ====October 19, 2015 C Prog==== | ||
+ | |||
+ | After many hours of attempts, I finally got mbe1 to a point in which I was totally happy submitting it. I got all of the kinks out over the course of picking at it for three days. At a first glance I was sure that it would be more simple than mbe0 due to the fact that we could now use loops. | ||
+ | |||
+ | On this week off I decided that I needed a break, so I did something that was a little different. | ||
+ | |||
+ | ====October 26, 2015 C Prog==== | ||
+ | |||
+ | This week we are supposed to start covering C++, and I am excited for that. I have completed cos0 and ended up turning it in pretty early. | ||
+ | |||
+ | The next project however, seems like it really stepped up difficulty wise, to me at least, compared to our other projects thus far. We have to create our own functions to solve a problem. | ||
+ | |||
+ | ====November 2, 2015 C Prog==== | ||
+ | |||
+ | We delved into C++ in further detail this week, and looked at classes with respect to parent and child classes. | ||
+ | |||
+ | As far as projects go, I am not worried about the current one due on wednesday, with the encoding and decoding, and I have written a similar program before during the problem solving final exam. And a Caesar Cypher, which is what we are utilizing, in my opinion is not that difficult to implement. | ||
+ | |||
+ | ====November 9, 2015 C Prog==== | ||
+ | |||
+ | I definitely should not have underestimated this project that is due in two days. Firstly, I completely overlooked the fact that we are required to use fgetc() to grab characters from stdin or from a file, instead of fscanf() which is what we have used all semester up until this point. | ||
+ | |||
+ | On my own time, I am taking another look at the Cave Story game that I was attempting to recreate in C and C++. After going over syntax changes, that aren't really that different from what we have been doing in C, I feel a lot more comfortable tackling this task. I understand now more than ever how important baby steps are when you're trying to create something that is large. | ||
+ | |||
+ | ====November 16, 2015 C Prog==== | ||
+ | |||
+ | I ended up finishing the sam0 project on time. When it came down to it, I was not sure that I would be able to do it. At first I was looking to attempt to implement functions and solve it that route, but I ended up breaking it in to too many functions to do. That project taught me that sometimes, especially for some things that can be solved in only a couple logical steps, don't need four functions to operate. | ||
+ | |||
+ | For the project that is due this week, as usual I feel like it should be working, but it seems not to be. I think that I need to learn the functions that I am attempting to use. Once I get clarification on them, I am certain that the logic and code, for the most part, will be correct as is. It has been interesting learning how to look at programs with regards to handling bytes that make it up, rather than the ASCII content that makes it up. This introduced me to several new ways of thinking in regards to solving problems when dealing with files. | ||
+ | |||
+ | ====December 7, 2015 C Prog==== | ||
+ | |||
+ | I have done a lot with respect to programming in C and C++ over the past two weeks, especially over the break week. I find the projects that we have for this class almost easily do-able, and I am really happy with where I stand, at least as far as C goes. Over the break I resumed recreating the game CaveStory in C++. This time though, I actually understood, for the most part what was going on. At this point I am just going through a guided tutorial of sorts, as I do not know the least in structuring a major project, especially a game that renders images the screen. | ||
+ | |||
+ | As far as the end of course experience goes, I am more than confident that I can complete the projects without too much hassle. |