I started the day on Chapter 9, Agile Development with XP and SCRUM.
I won't get too much work in today because I'm attending the "Longhorn Startup Demo Day with Michael Dell." It's an event here at UT where UT students present their startup ideas to investors, and as such, I thought it would be a great idea for me to attend, since I am working on immersing myself in that world. :)
I learned about pari programming, which is when two developers work on the same work station (or through some system that accomplishes the same), which ensures high quality code, since there's a constant code review going on.
Here is SCRUM, at a glance:
I like SCRUM, it will be very helpful to me when managing a project launch. Every day, it asks project participants:
1. What did you do yesterday?
2. What will you do today?
3. What is blocking you (are there any obstacles you want help with)?
I saw this excellent video, it gives a broad overview of Scrum:
The next chapter was Chapter 10, "Working with Agile Stories." In reference to user stories, they should be brief, in the language and perspective of the user, and contain the following:
1. Who the user is (specifically)
2. What the user's goal is for that story
3. Why that goal is important to the user
A story should fit in a single note card or sticky note. They have a brief title and are written in the following format:
As a [specific type of user], I want to [accomplish some specific goal] so I can [achieve some benefit]. Here's an example:
"As a [reader of this post], I want to [subscribe to your newsletter] so I can [follow your blog]."
This forces the project to remain rooted in creating value for the end user. On the back of the notecard or sticky post, we should list the acceptance criteria for that story. This will include core paths and edge cases (I don't know what those are yet). The story above might include the following acceptance criteria:
1. The visitor can enter a valid email to the subscribe form
2. The visitor cannot submit the form without entering a valid email
3. After submission, the visitor should see a "thank you" message on the top of the screen
These are the basis for the things we would need to write tests for during the development process. Once a client agrees that all criteria are met, the story is accepted and we can move on to the next one.
SUMMARY OF CODING SKILLS
I won't get too much work in today because I'm attending the "Longhorn Startup Demo Day with Michael Dell." It's an event here at UT where UT students present their startup ideas to investors, and as such, I thought it would be a great idea for me to attend, since I am working on immersing myself in that world. :)
I learned about pari programming, which is when two developers work on the same work station (or through some system that accomplishes the same), which ensures high quality code, since there's a constant code review going on.
Here is SCRUM, at a glance:
I like SCRUM, it will be very helpful to me when managing a project launch. Every day, it asks project participants:
1. What did you do yesterday?
2. What will you do today?
3. What is blocking you (are there any obstacles you want help with)?
I saw this excellent video, it gives a broad overview of Scrum:
The next chapter was Chapter 10, "Working with Agile Stories." In reference to user stories, they should be brief, in the language and perspective of the user, and contain the following:
1. Who the user is (specifically)
2. What the user's goal is for that story
3. Why that goal is important to the user
A story should fit in a single note card or sticky note. They have a brief title and are written in the following format:
As a [specific type of user], I want to [accomplish some specific goal] so I can [achieve some benefit]. Here's an example:
"As a [reader of this post], I want to [subscribe to your newsletter] so I can [follow your blog]."
This forces the project to remain rooted in creating value for the end user. On the back of the notecard or sticky post, we should list the acceptance criteria for that story. This will include core paths and edge cases (I don't know what those are yet). The story above might include the following acceptance criteria:
1. The visitor can enter a valid email to the subscribe form
2. The visitor cannot submit the form without entering a valid email
3. After submission, the visitor should see a "thank you" message on the top of the screen
These are the basis for the things we would need to write tests for during the development process. Once a client agrees that all criteria are met, the story is accepted and we can move on to the next one.
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: 2
Total Hours Coding: 510
No comments:
Post a Comment