Contradiction
Life is always full with contradictions. It depends on how you judge things, sometimes there is no excellent solution for a matter, but just the best fit one. I hate coming to this point, but that's life, up and down, left or right?
The story began with a silly mistake in the work, I found that we have some hardcorded links in the main page of the application. Everytime when we migrating the codes to another server (such as testing server, staging server, production server), instead of moving the files straight, we have to make amendment on few of the files manually in each server, which is absolutely unwise you see.
The 3.5 years of experience in IT software technical field told me that the best code in the world doesn't come with hardcoded values, not even once. From the past experience in the profession, yes I have to agree, both theorically and practically. But when it comes to making decision, I am not the one yet, the only thing I can do is just propose the solution which I believe can help in improving the quality of work.
In this case, my major concern was how much extra effort required to change the code in each server manually. Yes, you don't feel the pain when you are not the one who are going to do that. I wasn't the one who will need to do this but I proposed my solution still, apparently I was too busybody, agree? If yes, then you're SO WRONG! You see, my point was to reduce the effort of the team when doing codes migration. Also, manual works can cause more problems in my very humble opinion.
The proposed solution is that, storing all the links in a configuration file and the main file will always refer to this configuration file. From the view of files migration process, it makes our lives easier, the config file should be the same all the times, while the main file can be changed over and over and being migrated across all the servers without manual effort required (to change the URL link in the main file). The solution sounds cool isn't it? xD
On the other hand, the application will need to load two files, the main one and the configuration file. Performance wise, it is not a good idea. So, the contradicting point here is, if you want performance, let go the best practise, or vice versa. Having said that, I do not agree with this point. I mean, yes there are two files to be loaded in this case. But believe me, the config file will only consume small capacity, usually 1-2KB.
If I were given a chance to decide, I will go for best practise. I will ensure my application is a quality one, easy customisation yet requires minimum human effort, compare to just a little bit more bandwidth to run two files instead of one.
But still, the decision was to go for performance. Disappointed? Nah, not really. As long as I have done my part to propose the solution, I respect the decision. Well, theory is only applied during exam. In a commercial world, no one really give you a damn on quality codes. As long as it works with better performance, that's the best solution. I felt like I am just a fool that following the so-called best practise. *Sigh* Now I learnt.
If you are someone who are experienced in IT software technical field, which one will you go for? Share me your thought if you don't mind. But again, I expect no comment for this post, just like the rest of my posts.
The story began with a silly mistake in the work, I found that we have some hardcorded links in the main page of the application. Everytime when we migrating the codes to another server (such as testing server, staging server, production server), instead of moving the files straight, we have to make amendment on few of the files manually in each server, which is absolutely unwise you see.
The 3.5 years of experience in IT software technical field told me that the best code in the world doesn't come with hardcoded values, not even once. From the past experience in the profession, yes I have to agree, both theorically and practically. But when it comes to making decision, I am not the one yet, the only thing I can do is just propose the solution which I believe can help in improving the quality of work.
In this case, my major concern was how much extra effort required to change the code in each server manually. Yes, you don't feel the pain when you are not the one who are going to do that. I wasn't the one who will need to do this but I proposed my solution still, apparently I was too busybody, agree? If yes, then you're SO WRONG! You see, my point was to reduce the effort of the team when doing codes migration. Also, manual works can cause more problems in my very humble opinion.
The proposed solution is that, storing all the links in a configuration file and the main file will always refer to this configuration file. From the view of files migration process, it makes our lives easier, the config file should be the same all the times, while the main file can be changed over and over and being migrated across all the servers without manual effort required (to change the URL link in the main file). The solution sounds cool isn't it? xD
On the other hand, the application will need to load two files, the main one and the configuration file. Performance wise, it is not a good idea. So, the contradicting point here is, if you want performance, let go the best practise, or vice versa. Having said that, I do not agree with this point. I mean, yes there are two files to be loaded in this case. But believe me, the config file will only consume small capacity, usually 1-2KB.
If I were given a chance to decide, I will go for best practise. I will ensure my application is a quality one, easy customisation yet requires minimum human effort, compare to just a little bit more bandwidth to run two files instead of one.
But still, the decision was to go for performance. Disappointed? Nah, not really. As long as I have done my part to propose the solution, I respect the decision. Well, theory is only applied during exam. In a commercial world, no one really give you a damn on quality codes. As long as it works with better performance, that's the best solution. I felt like I am just a fool that following the so-called best practise. *Sigh* Now I learnt.
If you are someone who are experienced in IT software technical field, which one will you go for? Share me your thought if you don't mind. But again, I expect no comment for this post, just like the rest of my posts.
Labels: Career, Technology
This entry was posted
on Monday, April 13, 2009 at 2:33 PM.
You can skip to the end and leave a response.
0 Comments:
Post a Comment