1/29/09

• Reviewed programming references once again
• Need feed file before I can finish my project

1/28/09

• Reviewed some more programming references

1/27/09

• Looked at a couple programming references online

1/26/09

• Had a meeting with my manager and programmer I'm working under
• Need to have test feed file given before I can finish the code and move to testing

Reflections on week 1/20/09 - 1/22/09:

1/22/09

• Downloaded and installed subclipse to allow access to SVN repositories
  1. Had to do manual install, allowing eclipse to update through the web wouldn't work
• Researched some information about SVN repositories
• Applied for access for the local SVN repository

1/21/09

• Tracked down problem with access card
• Reviewed some programming references

1/20/09

• Logged in to the testing servers and looked at the script that will run the application
• Did some basic testing against the changes I made

Reflections on week 1/12/09-1/15/09: This week I was given a clearer idea as to what I'll be doing(not sure if I can post the details here though…). Anyways, I basically need to write a method that queries a database and several different tables to get information pertaining to a certain ID. My experience with databases is limited to one short class session about JDBC, but it seems pretty easy. It took me a while to track down how the fields in the database corresponded to the fields in the feed file example I was given. It didn't take me long after that to write some PreparedStatements to get the data needed. However, I ended up going back and changing the code after talking to Jared(the programmer I'm under) and doing some research online. Its much better design wise and performance wise to write stored procedures on the database and call those from the program. It took me a while to figure out how to do that, including that I needed a different set of login to have access to add procedures to the development database and then that I had to set access to allow it to properly be called from the program(or else it silently does nothing).

I learned a lot about SQL this week basically. I didn't find it difficult, but it took time to get through a lot of stuff. There are several simple rules that allow you to write much faster SQL code that I learned which is pretty useful. One is the stored procedures example I went over earlier. The other is to to combine the queries into one using JOINs to limit network traffic. Also to specify the fields chosen instead of using the * operator unless you really want all the fields. There are a few more but I think I've given the general idea…

1/15/09

• Minor edits to existing code
• Drafted a document designating all changes done so far

1/14/09

• Figured out how to upload SQL scripts to the database and call them
• Wrote SQL stored procs to replace JDBC prepared statements to improve performance

01/13/09

• Worked on my project some more
• Edited my SQL statements
• Realized I need permission on the database

01/12/09

• Discussed more in depth what I would be doing
• Created a method that queries database input using JDBC and populates an array the same way data from a feed file would be parsed

Reflections for week of 1/05/09 - 1/08/09: Had a lot to do this week. Probably the biggest challenge was getting everything set up in the environment. Since I'm dealing with bank software, I have to be careful about everything. I also have to watch were I go on the web, and I can't check any of my school or personal e-mail or stuff like that while I'm there. I spent a lot of time on help desk trying to get all my passwords set up(one for e-mail/sametime/computer/etc.). In the end I had to have someone remotely access my computer just to get my e-mail set up. Even after all this I still have to wait a while for admin rights on the computer. I've worked around this by simply downloading everything to my temp folder and running programs that don't require registry edits to run. Its not ideal, but it works. :)

It was also a big change to get used to the business environment. Cubicles don't seem as bad as I've heard people make them out to be, but then again I haven't been there long. Everything is a lot more formal than school, but I guess that is just how it has to be at a bank. I'm still a little fuzzy on the details as to what I'll actually be programming but I think I've got the basic idea down and can start working on it. Also, everyone seems nice and I always get a quick response when I ask questions.

01/08/09

• Was given a better idea of what I needed to do for my project
• Read up on SQL(never did databases before)
• Reviewed SQL scripts that were relevant to my project

01/07/09

• Downloaded and installed programs I would need(Eclipse, Squirrel SQL, etc.)

01/06/09

• Was introduced to TECs(the project I would be working on)
• Set up my computer so I could work

01/05/09

• Started internship at JPMorgan
• Went through orientation
• Was introduced to team members
• Looked over some code