This blog is for Thursday/Friday(until 12:30) of ITW.
I spent Thursday (still awake from Wednesday), continuing working on getting the functionality of the Application working. I messed with the GPS more and got it to start tracking continuously as the user went about their walk. I integrated the camera and displaying thumbnails to the user and worked on the ‘End of the walk’ activity.
Earlier in the day I tried to work on campus but once again encountered errors on importing on my laptop and the uni computers didn’t support some of what I needed to continue working on the APP (The uni computers do not allow you to update Android Studio, gradle or the Android SDK!).
A lot of the day was a blurr..
For Friday (after finally getting -some- sleep). I continued finishing up the app, working on the server upload and trying to clean up the code.
Unfortunately, it wasn’t totally finished, and so our uploading to the server of both data and files is not quite there or compatible with the website, although close enough to be able to do it with some more time.
I did do a large portion of JavaDoc, however, due to the time constraints, the version that got uploaded for submission and review was one with a lack of commenting. I feel disappointed that we couldn’t get the cleaned up and commented version of the application in, and know that we have lost marks for maintaining the product there.
I keep wondering if there is a way to change this, but I know it’s too late now. Likewise for errors in the application that I wish to change, such as returning the user back to the start screen on the upload of an app, stopping the user from adding Walks/Walklocations without data in some sections, etc Nothing can be done now though sadly.
Hours for Thursday: 14 (ish.. could be more)
Hours for Friday: 4
Reflections on ITW:
I feel I did the most I could with the time provided.
Without staying up for more than the approximately 40 hours I did do and ploughing on with work whenever and wherever I could, there was not much else I could do.
My development was severely impacted at the start of the week by errors in GitHub’s own application, Eclipse and Android Studio. Either R errors caused by XML files that had no issues, the JVM being corrupted, gradle going crazy or by GitHub’s application wanting to wipe our entire repo before uploading (later fixed by changing working directories each time it wanted to do this). This set me back a lot.
I was slightly disappointed by the progress we had (or hadn’t) made before the week began. With respect and apologies to Jack, I must say that I feel I would have been better placed to be ‘lead programmer’ and to have worked on it more in my own time, such as over Xmas. I do blame myself for this too. By having him as lead, I put faith that it would be under control and didn’t do more when there were signs of issues.
I think I did that partially because I didn’t want to come off as a jerk and tell someone that I might be better than them, especially when said person has claimed to have previous experience working with Android. The result was that I was apathetic until the start of this week when I saw the state of the application (which has since been modified to the point of being completely different).
The actual Android programming wasn’t too tough. The Model side of the application is no different than how I’m used to, and in order to do everything else there are a number of well-documented and helpful websites online to learn from. This was especially true when it came down to the GPS tracking and server uploads.
Before this week, I couldn’t say I knew how to program in Android. While I’m still not that much better, I’ve now worked with it enough to be comfortable writing more apps in it in the future, which I suppose is the purpose of this really. To learn something new.
While I won’t be volunteering myself for more 40 hour no-sleep coding runs, I’ve definitely learned a thing or two:
- I can do some Android
- I can work under pressure
- When something needs doing, I get it done
- I’m now more comfortable with version control
- Don’t put too much faith in others- Raise issues and take control, even if you want to believe things will pull through
- How to write interesting git commit messages
- Functioning as a team (or dis-functioning, sometimes!) to get a work load done for a project time.
I’m sure I’ll be writing all of this again and more when it comes to my final report!
For now, I’m off to rest a little. I think tonight with be an early night. =)