But what shall I call them?

I have been here over five weeks now! I will be going home in just three and a half weeks. I'm feeling very ready to go home. I would love to be doing the same work, but just returning to my apartment at the end of the day though. I moved over the weekend and it threw me off a bit, even though it's better since I have less of a commute.

This week we are working on our personal projects. I went through decision paralysis over the weekend about what to work on and eventually decided to go with an idea I had wireframed before beginning the program. It was originally called "The Digital Therapist" but I have since changed it to "Your Therapy Homework." I will probably change it again. The idea is that people can fill out therapeutic worksheets online, and save them. The long-term goal would be for therapists to be able to create their own worksheets. It's not super fancy but actually wound up being more complicated than I would have thought. Mostly the database was challenging because I wanted everything to be very easy to edit, and I wanted users to be able to save the worksheets they've done.

I spent yesterday on a "mock up" where I did all the HTML and CSS, and some Javascript. Now I am moving into a Model-View-Controller (MVC) framework in CodeIgniter, and feeling very indecisive about naming my controllers. I realized I am giving myself a hard time for not being sure what to do, but I think the reason is that it's actually somewhat important and I want to make a good decision. I also have a tendency to perfect more than is healthy. I want this to end up being AMAZING when it is only my first project. I also enjoy thinking about organizational decisions. For example, if I name one controller "users" and one "worksheets" which controller leads to the worksheets that users save? My remote TA suggested "tags", "tasks", and "users", but I don't really know how to implement that.

I've been listening to Sandi Metz talk. I don't understand all of it yet, but it's a reminder that many of the things I'm thinking about are what "real" programmers (as in, not me yet) think about all the time. I get scared to break my lovely well-crafted programs, but I must in order to help them grow. We had a google Rails developer (from Wildfire) speak to us about Agile development, which is all about letting go of perfectionism. Time to try to implement this!