Live Application Form: Fill & Download for Free

Lack of Trust.I was working as Senior Software Engineer. I was working in a project where I was directly dealing with client. One day, Client asked me to do a change in live application at 8 PM IST. As I was already running out of time and it was live application so I had to monitor it after making some changes which was time consuming, I denied. So he forced me not to monitor anything and just do the changes and go offline. He said that if anything goes wrong, he will take care of it. (NOTE : Client was a technical person and he used to do code). I did whatever he had asked and also got it reviewed from a senior. After that I made those changes on production server, informed client to monitor system and left for home.Now here comes the next day. I logged in and can see messages of him saying that who did these changes which made system shut for hours. I was shocked by reading all his messages. I was about to check in system and then my boss entered into cabin and called my whole team for meeting in the same cabin.Without asking me for any explaination, he started scolding me in front of my whole team and other collegues. He had more trust on his client than his employees. This happened on Friday.I gave resignation on Monday without any second thought. I didn’t want to work with person who doesn’t have trust on me.Lesson learnt : Higher management force you to do mistakes and they say that they will take care of your mistakes. But when mistake happens in actual they are the first person to blame you.

It's the same. It's not necessarily the application that is coded, but more the programmers and company standards that dictate the style of code.Games engines end up with the same sorts of legacy problems that you see in any long lived application.

To be frank, you almost answered the question yourself in the description! Not all applications have the same requirements or desired behaviors, so choosing which one is worse is a matter of defining the desired properties of your application.Like you said, unpredictable and lengthy pauses are probably bad for applications that need to be responsive to the user. But for batch jobs with no UI, no one probably cares or notices if there is a pause in the processing.For long-lived applications that need to repeatedly allocate large chunks of memory off the heap, memory fragmentation could result in a crash if the allocator can’t find continuous pages of memory. But for short-lived applications, the chances of fragmentation causing a problem could be extremely low to none.Which is worse? Well, that depends on the application. Long-lived batch applications that allocate large chunks of memory and have no need for UI are going to be hurt more by fragmentation rather than GC. Short-lived applications requiring a snappy UI that do larger volumes of smaller allocations are going to be hurt more by GC than any fragmentation.Fortunately, many garbage collectors can be tuned to suit the behaviors of the app, so if you’re not sure about the behavior of your app, you can try to tweak those settings to get the performance you need.