What is Going On With Paul
Paul is very busy. Very busy indeed. He is upgrading right now. Upgrading to the new PHP 5.2 which has a bunch of benefits that I will not bother explaining. Maybe the server will get all crazy tonight.
Yesterday, my boss and I, were waiting at the ATM when a guy went by with jugs marked radioactive, hm. I wanted to get a pic but by the tie my phone loaded the camera app it would have been over. I really need to buy a camera with the money from this side project I did for my boss. I am so sick of not being able to point and shoot even if the camera has the advantage. Once I have that and my new fancy heater you will see more of me on my journal.
On the work front I am busier than ever but I still like the job a lot. A project I projected would take 2-3 months ended up being delayed by other people for months until this month and now it is due on Nov 28th. I have no idea if this is realistic or not. I have made a lot of progress but today the database adminstrator locked out my password by accident when refreshing the test database with data from the production database this morning. Then when that was worked out my user did not have permission granted to view my custom tables, then the tables had triggers which went haywire after the upgrade from the production database.
I really believe that in this case having to work with a database administrator has only made the process a hundred times slower. Every time I want to make a change I have to run it by administrator and then they make the change to the tables that I need for the application, argh.
Sidenote: I have a hard time giving up any control over the development process.
Luckily, most of the database building is over. Now it is really time to work on the data. Basically, the system is made to allow for online evaluation of thousands of employees which is a complicated multi-tiered process. A person's supervisor initiates the review of an employee. This would be easy if the system that records who is who's supervisor was accurate but hundred of people have supervisors other than who is their actual supervisor which makes things more complicated. There are also a multitude of unions which negotiate the questions that are used to evaluate the employees. This means that normalizing the questions on the forms is generally impossible because the questions themselves have been negotiated by the unions.
To make matters more complicated many of the questions are questions to. e.g. the question and the answer are both blank and are dependant on the individual user position and are filled out by the supervisor at the time of review.
Once the supervisor is done reviewing the employee, the review is passed onto the reviewer, which is generally the supervisor of the supervisor but is also often not the case. They can add comments, then the employee gets to respond. Then the head of HR and then finally it is over.
I actually have it pretty under control. The only problem is the shear volume of the questions would are still being inputted.
P.S. It feels so freaking good to not be in school anymore!
Yesterday, my boss and I, were waiting at the ATM when a guy went by with jugs marked radioactive, hm. I wanted to get a pic but by the tie my phone loaded the camera app it would have been over. I really need to buy a camera with the money from this side project I did for my boss. I am so sick of not being able to point and shoot even if the camera has the advantage. Once I have that and my new fancy heater you will see more of me on my journal.
On the work front I am busier than ever but I still like the job a lot. A project I projected would take 2-3 months ended up being delayed by other people for months until this month and now it is due on Nov 28th. I have no idea if this is realistic or not. I have made a lot of progress but today the database adminstrator locked out my password by accident when refreshing the test database with data from the production database this morning. Then when that was worked out my user did not have permission granted to view my custom tables, then the tables had triggers which went haywire after the upgrade from the production database.
I really believe that in this case having to work with a database administrator has only made the process a hundred times slower. Every time I want to make a change I have to run it by administrator and then they make the change to the tables that I need for the application, argh.
Sidenote: I have a hard time giving up any control over the development process.
Luckily, most of the database building is over. Now it is really time to work on the data. Basically, the system is made to allow for online evaluation of thousands of employees which is a complicated multi-tiered process. A person's supervisor initiates the review of an employee. This would be easy if the system that records who is who's supervisor was accurate but hundred of people have supervisors other than who is their actual supervisor which makes things more complicated. There are also a multitude of unions which negotiate the questions that are used to evaluate the employees. This means that normalizing the questions on the forms is generally impossible because the questions themselves have been negotiated by the unions.
To make matters more complicated many of the questions are questions to. e.g. the question and the answer are both blank and are dependant on the individual user position and are filled out by the supervisor at the time of review.
Once the supervisor is done reviewing the employee, the review is passed onto the reviewer, which is generally the supervisor of the supervisor but is also often not the case. They can add comments, then the employee gets to respond. Then the head of HR and then finally it is over.
I actually have it pretty under control. The only problem is the shear volume of the questions would are still being inputted.
P.S. It feels so freaking good to not be in school anymore!