June 27, 2006 at 9:26 am
Hi
Some of the developers in our environment are inserting records manually through EM, since they dont have any other form of data except the hard copy they are doing so, is this the right way? does it effect the performance in any ways whilie using the tool instead of t-sql commands.
June 27, 2006 at 9:39 am
I don't think this is going to cause you any problems from a performance standpoint; EM should just be executing an INSERT statement behind-the-scenes. Try running profiler and capturing what EM does when you insert data.
The part that concerns me is that the developers are using EM, which is a database administration/management tool, instead of QA, which is a data manipulation / analysis tool. I am a big proponent of setting good habits, because once a developer (or anyone for that matter) gets his mind set on how he does something, it sticks. I would challenge them to use QA to query and manipulate data because it will teach them much about how your data is stored and about how to use TSQL. If they are developing for this application, knowing the data structures will make them better programmers. Also, even if they are not ever going to program stored procedures/triggers/functions, they will learn a valuable skillset----database programming!!
June 27, 2006 at 1:00 pm
Could not agree more.It does not take a lot to insert data into a table does it ?
June 28, 2006 at 7:53 am
I haven't heard anyone saying this kind of stuff for a while now - make 'em do it the hard way - it's more educational. The last time was a Unix-fundamentalist complaining that what was unforgiveable about Windows was that you could use it without learning anything about how computers worked.
I mean, whatever next? You'll be able to buy loaves of bread ready-sliced if this trend of 'convenience of use' continues.
And always remember - if they can learn to do 'INSERT' - they can learn to do 'DELETE' and 'UPDATE' in QA too, and sometimes developers seem to prefer learning the hard way.
June 28, 2006 at 9:46 am
Convenience is for users and testers. Developers who do not know how the data is structured write poor code. By definition, a convenience is something that saves time and effort. Cutting time and effort from coding results in low quality code which results in a low quality application.
Don't baby your developers. They should be constantly striving to better their skillset and cutting corners is warm milk. If you are not spending a good deal of your time learning new things, get a new job! There are two directions in life, forward and backward. If your not moving forward, guess what....you're losing ground to those who are.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply