On Thu, 24 Feb 2005 13:54:51 +1100, Andrew Scott <[EMAIL PROTECTED]> wrote: > Grant, > > I am not being critical of helpful posts, but when you are told you should
Yes you are. You're threads question was answered (well i might add) and that last tip from us was for free. You whiny sook. > do it this way because of best practices then that is assuming that I had > control of the code to start with. Secondly your comments about replacing > the code from document.all is another way of saying to me that you are not > aware of the situation at hand, I am trying to give you a clue that not all > situations require the best practice scenario. And in this case I could > change the code to use what you suggest, but then I would have to sit there > and test every module within the framework and who will pay for that, will > you pay for that! Yeah as opposed to testing the changes you make anyway? either way a test run has to be initialized.. who knows what ripple effects your code change could have - and the picture you have painted thus far sounds like must be a super duper ball of JS Code used through-out and being so large it needs 3 machines to render its reams of code.... So either way its got to go through QA - you being a top gun support engineer and all will have come to that conclusion. > When I am being paid to maintain and support, I am not going to go out of my > way to make changes to a live system and introduce problems that I am not > being paid for, and that is what is at stake and why I make my comments, > anyone who has been around development long enough will know this. maintain = change, so lets play devils advocate here and assume your client in question has NOT tried to run the script(s) in another browser. They ask you to make a change or a small nestled addition - you do so - they love your work and send you on your way. They then come back tomorrow and load the app in a non-IE-browser and note that the scripts are broken. Now it could go either way but what if they now turn around and blame you for it? Thankfully you were given a friendly reminder on this bloody great forum called CFAUSSIE that document.all isn't browser friendly thus the reason why - all because up until that point you *MAY* not of known about it. You're thanks in this query isn't needed, glad to help :D Again hypothetical scenario but you see the underlying principal in that just because you support software doesn't give yourself or your company a get out of jail free card. As a consumer thats not gifted with your technology powers can simply look to you with a pissed off expression / wanting a fix and probably harbouring doubts that previous developer was to be blamed....it has happened before...and will again no doubt (if not you others). Its why support contracts cost loads for legacy software as while its money in the bank to support it - it comes with pitfalls and traps... but that's my assumptions anyway. > Not whether I should be using best practice or not, and not if I want to use > best practice in the future or not. > > Like the earlier posts on upgrading of CF5.0 to CF MX.. If I could I would, > I can't so I won't and in an ideal world be could all be coding in the same > manner and using the same technologies right from the moment of its release. > We don't and I for one am sick of people like yourself that might wish to > push to newbie's that this is a best practice. > > As I said there is information out there on best practices, and I wasn't > asking for the best practice to make this browser non specific, I asked why > it wasn't working the way it should. To which you got your reply and a freebie hint to boot. Don't like it, leave / unsubscribe if its becoming to daunting for you to take in. > The point is unless the poster asks for best practices, no one should come > back and say that this is not the way you should be doing it, because that > would be assuming that that person had control of it too start with. Says who? If i ask a question and someone notes that my code seems "out-of-tune" with the best practices I for one would love you all to let me know (in the event i do know, i'll simply stay quiet or go "yerp, aware of that but hey, legacy and all..." which is all you needed to do if you felt we were belittling you or challenging your technical skills (which we weren't). > Grant all you are going to keep doing, is to push how much you don't know > about software development when it comes to maintaining code, your attitude > to me is well I would have done it this way and you'll go and do it that > way, think about the cost of that before you open your mouth, and you might > see that people don't have choices. Assumptions being the mother of all... I think grant is the level headed one in this topic. > > And one last thing, newbie's are always asking the questions that they need > to ask. So if they are unsure then they will ask for best practices or how > should I etc. Newbies sometimes don't know what else to ask for, thus if people take time out to notify them of "extra' information pertaining to the topic at hand, that will in turn reduce them from making the mistake or provoke extra learning/questions. My son is at an age now were he throws things on the ground instead of putting them away - now i can simply discipline him, show him were to put that said object correctly and send him on his way - or i can show him what he did wrong and explain to him why the object goes in the outlined spot. So then when he comes to a similar scenario his decision power is that much greater then it previously was as he has key information to compare against. > I pity your employer, because I know that you'll be costing him a lot of > money to develop things that he never wanted done!! For a "Consultant" you sure have nice people skills. -- Regards, Scott Barnes http://www.mossyblog.com --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
