Hi again,
The 12th week of school is over!!! Extreme, though short lived joy must be expressed for the end of that week. I had two projects due and an exam this past week, and then an exam tomorrow that I should still be studying for right now. All of these deadlines made for a crazy busy week, not to mention the perhaps overly lax approach my group and I took on this second iteration of (SB)IDB.
I’ll be able to take a breath after tomorrow, only to begin working on the last part of this project right afterward. One good thing about this last project is that it’s deadline is two weeks before the end of classes. So, it will not coincide with deadlines for other classes, or any other tests really, which for me is quite nice.
I don’t really have much to talk about this week because much of the work that was done this week was so close in context to what happened last week, but we do have a requirement to meet so, the blog must go on.
One thing you may note if you read any of the other students’ blogs from this semester is that the deadline for this project was extended by a day, due to a misunderstanding/oversight on the spec. The spec for this project was therefore updated with a clear representation of what was due at a late hour, and most of us realized at that point that we had quite a bit of work ahead of us. This last adjustment was about the API. The last iteration of the project required that we have documentation for an API using apiary.io. One cool thing about Apiary is that it allows you to set up the API and run your tests against a mock server. One thing that is not cool about this, is that it is not a full implementation of the API for your app. So, you have this API documented, but have to then implement it using another method, and need to run your tests against the real API, which could lead to some inconsistencies that you later find need adjusted. In the end it worked out, but I give much credit for the API to one guy in our group, and would like to say thanks for that, Yoan! Sitting in the lab with him and writing tests against the API was really helpful in gaining a greater understanding of what was actually going on.
My last thought for this week, “Hope the grades go well this time.”
Until next week,
Sophie
The 12th week of school is over!!! Extreme, though short lived joy must be expressed for the end of that week. I had two projects due and an exam this past week, and then an exam tomorrow that I should still be studying for right now. All of these deadlines made for a crazy busy week, not to mention the perhaps overly lax approach my group and I took on this second iteration of (SB)IDB.
I’ll be able to take a breath after tomorrow, only to begin working on the last part of this project right afterward. One good thing about this last project is that it’s deadline is two weeks before the end of classes. So, it will not coincide with deadlines for other classes, or any other tests really, which for me is quite nice.
I don’t really have much to talk about this week because much of the work that was done this week was so close in context to what happened last week, but we do have a requirement to meet so, the blog must go on.
One thing you may note if you read any of the other students’ blogs from this semester is that the deadline for this project was extended by a day, due to a misunderstanding/oversight on the spec. The spec for this project was therefore updated with a clear representation of what was due at a late hour, and most of us realized at that point that we had quite a bit of work ahead of us. This last adjustment was about the API. The last iteration of the project required that we have documentation for an API using apiary.io. One cool thing about Apiary is that it allows you to set up the API and run your tests against a mock server. One thing that is not cool about this, is that it is not a full implementation of the API for your app. So, you have this API documented, but have to then implement it using another method, and need to run your tests against the real API, which could lead to some inconsistencies that you later find need adjusted. In the end it worked out, but I give much credit for the API to one guy in our group, and would like to say thanks for that, Yoan! Sitting in the lab with him and writing tests against the API was really helpful in gaining a greater understanding of what was actually going on.
My last thought for this week, “Hope the grades go well this time.”
Until next week,
Sophie
No comments:
Post a Comment