This week I listened to a live talk, “Fixing Performance Problems Using Someone Else’s Toolbox” by a Java expert. The title of this video was originally what caught my eye. As soon as I was about 2 minutes into the video, I was a little apprehensive about finishing it. He basically was just describing what to do when the tools you depend on to test performance are no longer available. There are tools like JConsole, Visual VM, and Java Mission Control that people usually depend on for fixing performance problems. The Java expert talking (not sure why he didn’t say his name?!) told a story about his personal experience with a customer. The customer went to him and said that the whole system is slow, and it’s taking forever just to login. When the expert went to use his tools that he relies on to fix performance issues; he realized they weren’t working. He then started to panic a little bit, but he knew that with the knowledge he had, he could figure this out a different way. He went on to describe a series of problems that kept getting in the way of his alternative solutions. There were things like the firewall blocking RMX, JMX not being turned on, and the system not having a X server at all. Although I am not at all familiar with fixing performance issues, the way he went about everything and his thought process was the reason why I chose to write about this talk this week.
As a future software engineer I need to have the mindset that there is more then one way to fix everything. When your favorite tool breaks, you need to be able to work around that issue even if it’s not the most efficient and convenient way to do it. This video opened my eyes to the fact that all of these tools that we are so dependent on, are not by any means the only way to get things done. We are all so used to doing things the easiest way by using tools to make things a lot quicker..but in reality we don’t NEED them. An example in just everyday life that I can use to compare this to is, say for example your washer and dryer breaks and you don’t have the money to replace it. Initially you are going to freak out and think, “Great now I can’t wash my clothes, what am I going to do?” The reality of it is that you are going to have to find another option, like going to the laundry mat. I know that may sound terrible and extremely inconvenient to have to drive somewhere just to wash your clothes, but it is possible and it’s not the end of the world. Engineers need to be able to think logically and think about all of the possible solutions to a problem. Your original solution may work, but what if a major component of that solution breaks? As a computer scientist, you need to be able to apply the knowledge that you have when a tool you depend on breaks; both in the computer science world and in everyday life.
From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.
