> the hospital. Once it is complete, what do you suggest in
> terms if implementation?
>
> 1) Impose the standards only on newly created apps
> 2) Go back and implement the standards on apps that were
> built in the past (pre-standards)
>
> As far as the feasibility of #2, it's slim to none
> considering I am the only coder (though we will be hiring an
> additional one next month).
>
> Also, when standards are updated and/or changed, do you go
> back and update the previous work, or just apply it to new stuff?
>
> Just wanted to get your thoughts on how you have implemented
> your standards, etc.
If #2 is unfeasible, you shouldn't consider it!
In general, I suspect that people usually just apply standards to new
applications for just that reason. To the extent that you're maintaining
existing applications, you may conform to those new standards when you
change things, if you can do that without having to rewrite additional code
beyond the scope of your changes.
If you find that you're having performance problems in existing
applications, that may also be an impetus for rearchitecting them and
conforming to those new standards as well.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
