I started the day with chapter 3, which was an overview of how the engineering course will work. According to that chapter, the course should only take about a week to complete, depending on how much time we put into it. That's excellent, because that means I can get to module 4 pretty quickly, finish that, and then take the test.
The next Viking Code School cohort begins classes at the end of June, so I aim to be offered an opportunity to join that cohort. All the work I am putting in will advance my coding education regardless, so it's a win-win either way.
The Pivotal Tracker web app that was mentioned earlier was mentioned again. It looks like we will be managing stories with it. Nice.
I'm now on Chapter 4, "A Very Brief History of Software Engineering." I read the Wikipedia entry, "Moore's Law," and also, a short work, "A Brief History of Software Engineering," by Niklaus Wirth. At the end of that chapter, I watched a 36 minute video by Paolo Perrota, giving a short history of software engineering.
The next chapter was Chapter 5, "Basic Principles of Software Engineering." We went over the systematic process for creatively solving problems, which looks like this:
1. Understand the problem (understand).
2. Plan a solution (plan).
3. Carry out that plan (execute).
4. Examine your results for accuracy (test).
The key takeaway from the above is that most of the significant effort goes into the first two parts of the process. Solve your problems fully BEFORE diving into the implementation of the solution. If you fail to do so, you will waste a lot of time. Basically, the themes are:
Think first.
Break the problems into pieces.
Keep it simple.
At the end of the chapter, I read an article called "Principles of Software Engineering, Part 1," by Nathan Marz.
The next chapter was Chapter 6, "Approaching Complex Problems." It dealt with examples of breaking down projects into modules and then ranking the modules by importance before working on the project. Next was Chapter 7, "Engineering Product vs Process." After that, I went through Chapter 8, "What is Agile Development?" The chapter mentioned that eXtreme Programming (XP) and SCRUM are ways in which Agile is implemented in the real world. After that, I started on Chapter 9, Agile Development with XP and SCRUM.
SUMMARY OF CODING SKILLS
The next Viking Code School cohort begins classes at the end of June, so I aim to be offered an opportunity to join that cohort. All the work I am putting in will advance my coding education regardless, so it's a win-win either way.
The Pivotal Tracker web app that was mentioned earlier was mentioned again. It looks like we will be managing stories with it. Nice.
I'm now on Chapter 4, "A Very Brief History of Software Engineering." I read the Wikipedia entry, "Moore's Law," and also, a short work, "A Brief History of Software Engineering," by Niklaus Wirth. At the end of that chapter, I watched a 36 minute video by Paolo Perrota, giving a short history of software engineering.
The next chapter was Chapter 5, "Basic Principles of Software Engineering." We went over the systematic process for creatively solving problems, which looks like this:
1. Understand the problem (understand).
2. Plan a solution (plan).
3. Carry out that plan (execute).
4. Examine your results for accuracy (test).
The key takeaway from the above is that most of the significant effort goes into the first two parts of the process. Solve your problems fully BEFORE diving into the implementation of the solution. If you fail to do so, you will waste a lot of time. Basically, the themes are:
Think first.
Break the problems into pieces.
Keep it simple.
At the end of the chapter, I read an article called "Principles of Software Engineering, Part 1," by Nathan Marz.
The next chapter was Chapter 6, "Approaching Complex Problems." It dealt with examples of breaking down projects into modules and then ranking the modules by importance before working on the project. Next was Chapter 7, "Engineering Product vs Process." After that, I went through Chapter 8, "What is Agile Development?" The chapter mentioned that eXtreme Programming (XP) and SCRUM are ways in which Agile is implemented in the real world. After that, I started on Chapter 9, Agile Development with XP and SCRUM.
SUMMARY OF CODING SKILLS
Total Treehouse Points: 5,385
Treehouse Points by Subject Matter (Miscellaneous not included):
HTML: 663
CSS: 1,599
Design: 1,193
Development Tools: 747
Javascript: 1,120
Treehouse Ranking (%): "You have more total points than 94% of all students."
Treehouse Badge(s) Earned Today:
Treehouse Courses Completed:
How to Make a Website
HTML
CSS Foundations
CSS Layout Techniques
Aesthetic Foundations
Design Foundations
Adobe Photoshop Foundations
Adobe Illustrator Foundations (66% complete, switched focus from web design to web dev)
Git Basics
Introduction to Programming
Javascript Basics
Codecademy (& other) Courses Completed:
HTML and CSS (Codecademy)
Design Foundations
Adobe Photoshop Foundations
Adobe Illustrator Foundations (66% complete, switched focus from web design to web dev)
Git Basics
Introduction to Programming
Javascript Basics
Codecademy (& other) Courses Completed:
HTML and CSS (Codecademy)
Books Read or in Progress:
Completed: "Head First HTML and CSS," by E. Robson & E. Freeman
In Progress: "Eloquent JavaScript," by Marijn Haverbeke (On pg 27)
In Progress: "Head First Javascript," by Eric Freeman and Elisabeth Robson (On pg 56)
In Progress: "A Smarter Way to Learn Javascript," by Mark Myers (on pg 72)
My Progress on The Odin Project:
1. Introduction to Web Development 100% Complete
2. Web Development 101 29% Complete
3. Ruby Programming 0% Complete
4. Ruby on Rails 0% Complete
5. HTML5 and CSS3 0% Complete
6. Javascript and JQuery 0% Complete
7. Getting Hired as a Web Developer 0% Complete
Hours Spent Coding Today: 8
Total Hours Coding: 508
No comments:
Post a Comment