It's been nearly a month since I last posted anything. One of the DISadvantages of going so long without working on things is that I lose my place and spend time trying to figure out where I was when I left off.
But now that I think of it (10 minutes later?), I think I need to work on homework 2. So am done with
WRITING my template (really just a copy of Bill's). Next step is to check html and post to the server.
Tim spent copying the 3 html/php docs: around 2.5 hours.
Thursday, December 15, 2011
Monday, November 21, 2011
My SQL lesson is done!
Finished reading it in about 3 hours. So 3 hours/lesson is benchmark that can be improved. Want to cover assignments thru this lesson now. Maybe will be able to plan how much time till finished with f this class soon!
Monday, November 14, 2011
Finished Unix, File Permissions, Command Line lesson
This material seemed boring, at times, and that probably slowed me down. But it is probably important. It may have taken me longer than 4 hours to read this lesson and really if I want to finish all I want to finish, I should probably try to be faster in future studies. The good news is that I enjoyed and believe I understand the programming used in this lesson. That will hopefully make things faster and more fun!
Tuesday, November 8, 2011
Getting Back. Again.
Reviewed my earlier php notes on google docs. This took about an hour and best of all most of it made sense to me. So am I back where I left off? Probably not quite, but doing the HW will be the test.
Friday, July 22, 2011
Getting Back on Track
Reviewed class lessons today, primarily to figure out where I left off. Seem to have completed lesson 8 on arrays, so will start with lesson 9. When understanding returned to me, so did my interest in the material, as well as a feeling of engagement.
Wednesday, May 11, 2011
Falling Behind
It is taking around 8min/page to read the micro book. At this rate it will probably take around 150/8 = 20 hours (or about 5h/day) to finish this thing!
Also did a lesson in php, which if I remember correctly was 2 hours.
What I need to do from this point:
Get caught up in micro. This will take most of my weekday time, and a large portion of my weekend time.
Once I am caught up, I should be spending about 2 hours/day, six days a week on that class.
Revised estimate for JS: 400*3/60/4 => 1.5 hours/day (incl. .5 for coding).
Revised estimate for php: 1h/day for readings + lets say .5/day for coding = 1.5 hours/day.
...all that makes about 5 hours a day. I SHOULD try to squeeze in the IT103 stuff on the weekends (and phys), as it might be possible to complete it this quarter.
if I can do it. But JAVA I think is out until this summer.
Also did a lesson in php, which if I remember correctly was 2 hours.
What I need to do from this point:
Get caught up in micro. This will take most of my weekday time, and a large portion of my weekend time.
Once I am caught up, I should be spending about 2 hours/day, six days a week on that class.
Revised estimate for JS: 400*3/60/4 => 1.5 hours/day (incl. .5 for coding).
Revised estimate for php: 1h/day for readings + lets say .5/day for coding = 1.5 hours/day.
...all that makes about 5 hours a day. I SHOULD try to squeeze in the IT103 stuff on the weekends (and phys), as it might be possible to complete it this quarter.
if I can do it. But JAVA I think is out until this summer.
Thursday, April 28, 2011
Time Keeping
Read the PHP lesson on error handling today. It took about 2 hours. If there are 3 Lessons per week and it always takes 2 hours, then that is at least an hour per day for this aspect (alone).
Read chapter in the Javascript book. About 2 hours to cover 30 pages. Material should all be familiar, so isn't there some way to speed this up? At this rate it would take 500/30, or about 16 hours to read the whole book. So for this aspect alone it would be about 16/6 = 3 hours per week for this aspect alone.
Still have not started JAVA, nor the networking stuff, nor physics.
And then there's micro. Read about 10 pages in about 90 minutes. Estimating based on the reading we've done so far, I should be spending about 7 hours per week reading the book.
So, hours per day: 1+.5+1 = 2.5 hours per day to stay caught up with this stuff. This should be doable, so where did the time go?
Read chapter in the Javascript book. About 2 hours to cover 30 pages. Material should all be familiar, so isn't there some way to speed this up? At this rate it would take 500/30, or about 16 hours to read the whole book. So for this aspect alone it would be about 16/6 = 3 hours per week for this aspect alone.
Still have not started JAVA, nor the networking stuff, nor physics.
And then there's micro. Read about 10 pages in about 90 minutes. Estimating based on the reading we've done so far, I should be spending about 7 hours per week reading the book.
So, hours per day: 1+.5+1 = 2.5 hours per day to stay caught up with this stuff. This should be doable, so where did the time go?
Sunday, April 24, 2011
Lost track
The goal of this blog was to document how long it takes me to perform tasks. The reason for this was both to give me a basis for estimating the time required to perform future tasks, and also to encourage efficiency by making me conscious of how long I've been at a task. It also provides a benchmark for future reference.
Anyway, forgot to keep track, so will need to do so in the future!
Anyway, forgot to keep track, so will need to do so in the future!
Thursday, April 14, 2011
Getting Started
During my second sesssion of today, I set up my 000webhost account then created and uploaded a very simple html page that meets the basic requirements of assignment 1.
Total time spent on this task was about 50 minutes.
No project plan or file description document yet, because there are no files or project, other than my "under construction" page.
Total time spent on this task was about 50 minutes.
No project plan or file description document yet, because there are no files or project, other than my "under construction" page.
NerdWing's Assignment 1
Tasks:
Read all the modules thru #5. Time spent was about 1 hour per module.
Read all the modules thru #5. Time spent was about 1 hour per module.
Subscribe to:
Posts (Atom)