O.k., so after completing the design module, I rewarded myself with a movie! I watched Ex Machina at my local theater, it's a new movie that came out about artificial intelligence.
I made a few tiny modifications to the project files after uploading them to github, just to get some more practice pushing and pulling data (edited the readme file, for example). I'm glad I did, I want to practice using github more and more until it becomes natural. It's a tool that is very important for my development as a developer, so I have to make sure I'm proficient in its use.
I spent some time working with github today, getting familiar with it again.
The engineering module began with a basic overview of what the software engineering mini-course is about.
I read this article, which was an interesting read:
https://medium.com/@maebert/9-things-i-learned-as-a-software-engineer-c2c9f76c9266
Interestingly, the article was posted on Medium, that site that I did a design teardown of earlier. Medium works on a user-generated content model, and it's an interesting site from a business standpoint, in that it may be the future of one form of news. While companies like the New York Times may be able to weather the onslaught, the old news business, with large buildings in every city hosting journalists and editors, looks to be giving way to this new form of media. I just find the entire topic to be of note.
The chapter mentioned a tool called Pivotal Tracker in passing, which I have yet to use, but have now seen it mentioned twice during my coding education. According to the chapter, it helps us keep track of user stories, and is a way to stay organized and on task during a project.
I learned about TDD (test driven development) and pseudo-code. I'd heard of pseudo-code before, so I know what it is, but I've never actually used it in solving a coding problem. I really want to learn how to apply it, because I think it will help me break down problems, then take them on in a more efficient manner.
I learned that we should implement a philosophy of solving a problem first and THEN coding the solution. The lesson mentioned "SOLID" principles of design, but did not go into them. It also mentioned two Agile project management techniques, SCRUM and XP (eXtreme programming). Agile techniques embrace adaptability and rapid iteration instead of long formal planning and development processes, with the emphasis on shipping product.
Next was chapter 3, which was an overview of how the engineering course will work.
SUMMARY OF CODING SKILLS
I made a few tiny modifications to the project files after uploading them to github, just to get some more practice pushing and pulling data (edited the readme file, for example). I'm glad I did, I want to practice using github more and more until it becomes natural. It's a tool that is very important for my development as a developer, so I have to make sure I'm proficient in its use.
I spent some time working with github today, getting familiar with it again.
The engineering module began with a basic overview of what the software engineering mini-course is about.
I read this article, which was an interesting read:
https://medium.com/@maebert/9-things-i-learned-as-a-software-engineer-c2c9f76c9266
Interestingly, the article was posted on Medium, that site that I did a design teardown of earlier. Medium works on a user-generated content model, and it's an interesting site from a business standpoint, in that it may be the future of one form of news. While companies like the New York Times may be able to weather the onslaught, the old news business, with large buildings in every city hosting journalists and editors, looks to be giving way to this new form of media. I just find the entire topic to be of note.
The chapter mentioned a tool called Pivotal Tracker in passing, which I have yet to use, but have now seen it mentioned twice during my coding education. According to the chapter, it helps us keep track of user stories, and is a way to stay organized and on task during a project.
I learned about TDD (test driven development) and pseudo-code. I'd heard of pseudo-code before, so I know what it is, but I've never actually used it in solving a coding problem. I really want to learn how to apply it, because I think it will help me break down problems, then take them on in a more efficient manner.
I learned that we should implement a philosophy of solving a problem first and THEN coding the solution. The lesson mentioned "SOLID" principles of design, but did not go into them. It also mentioned two Agile project management techniques, SCRUM and XP (eXtreme programming). Agile techniques embrace adaptability and rapid iteration instead of long formal planning and development processes, with the emphasis on shipping product.
Next was chapter 3, which was an overview of how the engineering course will work.
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: 6
Total Hours Coding: 500
No comments:
Post a Comment