Journal Timeline
240 Hours of Coding
Let me start with a question, how was my first day of OJT? Well, things didn 't go well to the way I was expecting to the way we were requested by the chief of Planning and Management Office (PMO) to show our current system to what we have accomplished so far. Somewhere along the way, there were a lot of errors which was not there the last time I checked it but I think it still turned out well and I think they will understand that we are still in the development period. Then, another problem arise, we don 't have any workplace for their office is small to accommodate us then I remembered something that Madam Lany once mentioned that she is willing to let us use one of the laboratories in our department for our workplace and that explains why we are in our department even we are under the Planning and Management Office.
By the time we had an access to use one of the laboratories, we started it with a quick meeting to our approach of either rebuild the whole system or continue the current system and we all agreed to rebuild the system from scratch based from the recommendation and suggestions from the PMO earlier when we presented the system. As we came up with ideas and suggestion for the system, we listed up the task and flow of our development and let them choose which task they want to work on. We decided our weekly output to keep track with the progress of our development and also, we scheduled a weekly appointment with Sir Erwin Torres to check on our development process.
The rebuild of the system started with a slow pace during those 2 days for we need to identify and redo the procedure of the process to build the basic foundation of the system and change some tables in the database. We made progress of our development during those days with finalizing the database design, front-end design, flow and needed inputs. We applied what we learned in System Analysis and Design to help us with the development. By the end of the week, we finished most of the important parts of the system and the needed inputs for the department level. We assigned tasks for every member of the team with the set output per week. Our collaborative works made it possible to finish things up in time for we are scheduled by next month to present the system to the college deans. Our development team is well balanced with regards to the respective skills like designed, analyst and programmers.
By the time we had an access to use one of the laboratories, we started it with a quick meeting to our approach of either rebuild the whole system or continue the current system and we all agreed to rebuild the system from scratch based from the recommendation and suggestions from the PMO earlier when we presented the system. As we came up with ideas and suggestion for the system, we listed up the task and flow of our development and let them choose which task they want to work on. We decided our weekly output to keep track with the progress of our development and also, we scheduled a weekly appointment with Sir Erwin Torres to check on our development process.
The rebuild of the system started with a slow pace during those 2 days for we need to identify and redo the procedure of the process to build the basic foundation of the system and change some tables in the database. We made progress of our development during those days with finalizing the database design, front-end design, flow and needed inputs. We applied what we learned in System Analysis and Design to help us with the development. By the end of the week, we finished most of the important parts of the system and the needed inputs for the department level. We assigned tasks for every member of the team with the set output per week. Our collaborative works made it possible to finish things up in time for we are scheduled by next month to present the system to the college deans. Our development team is well balanced with regards to the respective skills like designed, analyst and programmers.
As we start our 2nd week, things got complicated as we were doing the important part of the system such as manipulating data entry from different tables. One of the tasks is doing some changes based from the recommendations of Sir Erwin when we checked on us last week.
I enjoyed our workplace for we applied what we learned in data communications in using a server-client setup to centralized our codes in one place and test our system. I also enjoyed our working environment for we help each member with their coding and share our knowledge and experience in coding using AJAX, JQuery, Javascript, Object Oriented, CSS and other tricks. One of the challenging experiences in our workplace is that we have no internet so fixing errors will be a hurdle but it did not stop from moving forward for we have our members in our back to support and willing to help.
I enjoyed our workplace for we applied what we learned in data communications in using a server-client setup to centralized our codes in one place and test our system. I also enjoyed our working environment for we help each member with their coding and share our knowledge and experience in coding using AJAX, JQuery, Javascript, Object Oriented, CSS and other tricks. One of the challenging experiences in our workplace is that we have no internet so fixing errors will be a hurdle but it did not stop from moving forward for we have our members in our back to support and willing to help.
After our long weekend, we 're back again doing the usual tasks to finish in time but for me, I took advantage of that long weekend on downloading books for references in coding if I ever stumbled in errors which I never encountered just to be prepared. One of the highlights of this week is that our schedule of presenting the system to the college was moved up to next week and this was the stage where finishing things up in time is our priority.
When Sir Erwin visited our workplace, he told us that we will be coming along in the upcoming BU Leadership workshop that will be held in CamSur next week and by that time we will be presenting our system there. At the end of the week, not much difference were made for we solely focus on debugging and testing our data table of its accurate results.
This week is the best experience ever as we come along in the BU Leadership Workshop which was held in Calabangga, Camarines Sur were we are not part of the workshop but still we were invited there to present our system that we are developing. The venue was great because it has a pool, air conditioned room for the place to stay, free supply of foods and 4 meals a day.
We were scheduled to present our system on Thursday so the remaining time will be used in finishing the needed parts of the system to be present in the workshop. It 's like a hackathon with a 60 hours of code to finish the needed parts of the system. We were coding day and night like we 're not sleeping at all (we still sleep but shifting cycles with other members) and I remember a comment in one of our roommates, which is one of the staff of the PMO, he said that we needed to get some sleep at some point but we did sleep but in a less number of hours only. One of the weirdest experience was seen in our room because we were able to hear different kinds of snoring from our roommates, imagine it like there 's a heavy equipment crossing way ahead.
When we presented the system with the presence of our respected Deans and Directors of Bicol University, it was the best experience ever as I, being the team leader, was the representative to talk and discuss the system. That kind of opportunity was unprecedented for us for we were told that only the USC president and other university leaders has that opportunity to talk in front of that kind of audience. It was one step forward in the kind of experience of talk that I had. Our presentation was a success and other directors and deans commented in our system they were amazed of our process by the way and even our Vice President of Administration and Finance were impressed. During our presentation, the presence of our respected Bicol University was that there for he has to important meeting to attend to.
We were scheduled to present our system on Thursday so the remaining time will be used in finishing the needed parts of the system to be present in the workshop. It 's like a hackathon with a 60 hours of code to finish the needed parts of the system. We were coding day and night like we 're not sleeping at all (we still sleep but shifting cycles with other members) and I remember a comment in one of our roommates, which is one of the staff of the PMO, he said that we needed to get some sleep at some point but we did sleep but in a less number of hours only. One of the weirdest experience was seen in our room because we were able to hear different kinds of snoring from our roommates, imagine it like there 's a heavy equipment crossing way ahead.
When we presented the system with the presence of our respected Deans and Directors of Bicol University, it was the best experience ever as I, being the team leader, was the representative to talk and discuss the system. That kind of opportunity was unprecedented for us for we were told that only the USC president and other university leaders has that opportunity to talk in front of that kind of audience. It was one step forward in the kind of experience of talk that I had. Our presentation was a success and other directors and deans commented in our system they were amazed of our process by the way and even our Vice President of Administration and Finance were impressed. During our presentation, the presence of our respected Bicol University was that there for he has to important meeting to attend to.
After an awesome experience last week, we kind of missed the usual free meals and the pool but back to reality we again do our usual stuffs like coding, fixing bugs and writing codes. We were scheduled, the chosen ones, to attend an online meeting and Natural Language Processing workshop in the upcoming dates of May 17 and May 24 to 25.
As the week ends was as always like a life of a programmer where writing codes is what we do as our daily basis. It 's like a 240 hours of coding in our whole summer OJT. Our weekly goals was mostly finished but there are still bugs that needs to fix and if we had internet in our workplace our time spent in error handling will be reduced but still we took as a challenge.
As the week ends was as always like a life of a programmer where writing codes is what we do as our daily basis. It 's like a 240 hours of coding in our whole summer OJT. Our weekly goals was mostly finished but there are still bugs that needs to fix and if we had internet in our workplace our time spent in error handling will be reduced but still we took as a challenge.
Our usual week starts with coding and fixing errors and handling data. In the middle of the days of the week, which are Wednesday and Thursday, things got spiced up because we attended the workshop with ignited our love for our course and saw the potential and advantage of being a computer science student.
Final week with most of the important part of the system are finished and only few bugs are needed to be fixed and things are running well. The overall of the system is still a lot to work with so the end of our last day of our OJT we had a meeting and distributed workloads to do even at the end of our OJT.