Week 4:

 

Part One: Set Your Educational Goals

My educational goals are broken down into smaller size goals because it could become overwhelming thinking of all the classes that need to complete. I break down my educational goals down to an assignment level and within that assignment level I break it down into sections. I decided to make a checklist of what assignments are due that week, as I complete each one, I check each off. I can visualize my progress using the checklist. I keep track of how many weeks, using a weekly module checklist, before the next class starts. I keep my Individual Learning Plan next to my desk to help me stay focused on my goal of finishing this degree. Like the assignment and module checklist I would like to check off the classes. Each check mark off one of my checklists gets me one small step closer to the goal of receiving my degree. It keeps me motivated and organized. I also reflect on the beginning its amazing how much we can grow in a short amount of time. When I started this journey, the pursuit of a computer science degree, I had a lot of doubts about whether I would be able to accomplish it. I had friends and family also doubtful in goal. Those same friends and family now see that I am determined to reach my goal. I burned my bridges back to safety there is no other way but to move forward, reach the finish line.

Part Two: Set Your Career Goals

My career goal is to eventually be a Lockheed Martin or another defense industry contractor software engineer employee. I understand sometimes these companies look for a few years’ experience, if that were the case I would be content with working for any software developing company that offers me an entry position. I would learn as much as a can there. I would commit at least 2-3 to that company before I apply to Lockheed Martin. Ultimately, I would like to work for the defense industry working on defense technology, such as drones or military aircraft systems. I would also like to move up to a supervisor level position or senior position, I like the idea of leading a large project.  

 

Part Three: Take a wild guess of your percentile of the ETS Computer Science test

 I reviewed the ETS page, the test description, and I even did the five 1st problems on the sample test. I missed one question out of 5, based on that I feel I will do well on the ETS exam. I am predicting that I will score higher than 75th percentile, I am predicting I will land somewhere in between the 75th to 85th percentile. I study and practice enough to learn the material well. Though I do forget some things because it’s a lot of details to remember but I retain the majority, that’s why I believe I will score in that range.

Part Four: Keep Up With Your Learning Journal


This week I got to learn more about the ETS test, and I downloaded the practice test. I will look at the problems and practice them. We got to guess two truths and one lie of my teammates. I had fun with the team activity, while I got to learn more about my teammates. We practice more debating skills, using ethical frameworks and valuating a claim. The article, The 7 Career Goals You Need to Succeed, was very informative. I will implement writing my goals down, to see if it makes a difference. We also learn about the types of claims in an argument. A claim is a statement that takes a side, and it can be argued. There are 5 different types of claims, fact, value, policy, definition, and cause. A claim of fact takes the position that something is true or not true. A claim of value takes a side on something such as tastes, approvals, or morals, proving the action is their right or wrong. A claim of policy will argue that a law or policy needs to be changed or added to address an issue. A claim of definition assumes that there is an agreement on a term. A claim of cause inference that something causes another event. We also learn about biases in arguments. The main ones are wishful thinking, that is because a person wants something to happen there for it will happen. Aversive thinking, is avoiding something that is negative and causes anxiety by saying there is another reason for it or it’s not true.

 

 

Comments

  1. Hi Adan,
    Comparing our blogs from last week’s journal assignment, I realized one of the methods is similar to how I based my goal on completing assignments. I liked your approach to breaking educational goals into smaller, manageable tasks. It will make it easier to track your progress. Using checklists to track your goals as assignments is a perfect tool, and it aligns with your goal of earning a degree in computer science. To achieve your career goal of becoming a software engineer at Lockheed Martin or another defense industry contractor, starting with an entry-level position with a different company is a strategic approach for the long-term goal. Seek group studies and additional resources related to software engineering. It will be vital to achieving your goal. Your dedication to beginning this journey and overcoming those doubts is essential for success. Keep up the hard work, and you will reach your goal.

    ReplyDelete
  2. Hi Adan,

    I love how organized and determined you are! Your checklist method is genius and super motivating. It's great to see how far you've come and how you're proving the doubters wrong. Keep adjusting your plans as needed and don't forget to pause sometimes to celebrate your progress.

    ReplyDelete
  3. Hi Adan,
    There is a lot to learn from your post. I love the way you take one step at a time and make checklists to ensure everything is done. Big goals can be overwhelming so it is nice to take baby steps towards your goals. I am sure having the support of your friends and family help build your determination even more. I also appreciate your detailed plan to balance your studies with practical work experience, which is crucial in our field. Your emphasis on continuous learning resonates with my own goal of staying updated with the latest technological trends. I would definitely suggest to join an internship to help gain some experience in your career goals.

    ReplyDelete

Post a Comment

Popular posts from this blog

CST438 Software Engineering: Week 8 (Final week)

CST438 Software Engineering: Week 1

CST370 Week 5