Long.valueOf(prospect.getId());
It now changes to this
New Long(prospect.getId());
In the end, lots of code have to be changed. Ironic eh.. Well, at least the only thing I don’t have to do is repair these codes.
Long.valueOf(prospect.getId());
New Long(prospect.getId());
Do you all know what's behind Hibernate? You guys won't know as you have to learn more and more and I have been working since the day we use punch cards for computation.
Dear Rukky,
I have noticed that you have been coming in after lunch for the past few days. Can you let us know your time replacement schedule?
Dear Consultant,
It's funny that you have to checked on my schedule and my replacement time. Yes, it's good for the company and yes, I do stay back on days when you leave early. If you don't want to believe me, just stay back along with me, heck I can even go until 12am as I am used to staying back previously in my old companies, even overnighting.
Now if I were to do that, how will the company compensate me then? Since time is such crucial matter to you. Will the extra hours I have been working then replaced the time of work that I supposed to get? Isn't it funny then?
So in the future, I guessed I will come at 8am and leave at 5pm or better still arrive at 7am then leave at 4pm. Isn't that how you wanted to look at right? I don't care about the missing hours, I can replace them anytime.
I wonder if the next time I leave early at 5pm as I have finished my 8 hours in the office, will there be any reason to say anything? Then I can just bloody write in and post this post instead. Good riddance.
KPI(Key Performance Index) for every issues forward to support email is 4 Hours (Max) to resolve. An example would be ab email was sent at 8.30am, an expected initial feedback should be within 2 hours (before 10.30am) about the details of the problem. Then the problem should be solved before lunch in the region of 4 hours. If support team unable to meet the KPI set, the team would be penalised under their company.
Some of the errors you made are elementary in nature, indicating there is still weakness in your mastery of the foundation of object oriented programming. I hope you can spend more time to brush up you skills.
A programmer that simply do what is being told can only stay at the junior position. You have to learn to identify loop holes and ambiguities in the user requirements and work with the project manager to rectify them.
I don't mind your work a bit slow