The Structural Engineer > Archive > Volume 68 (1990) > Issues > Issue 11 > Definition of a Good Code
Name of File 5321-68-11.pdf cached at 15/12/2017 06:39:16 - with 2 pages. pdfPath: E:\k9.istructe.org\CMS\webtest\files\0f\0fc97dcf-c65c-4908-b3f2-6d500bc849ea.pdf. thumbPath: E:\k9.istructe.org\CMS\webtest\files\pdfthumbs\0fc97dcf-c65c-4908-b3f2-6d500bc849ea_1.png. objDoc: 1 - True. objPreview.Log: . strFileName: 0fc97dcf-c65c-4908-b3f2-6d500bc849ea_1.png

Members/subscribers must be logged in to view this article

Definition of a Good Code

There has been much said and written recently about the vexed question of Codes of Practice. Such is the intensity of emotion aroused that we have seen the setting up of the rival ‘permissible stress’ Code group who have written their own Code in place of the (apparently) much unloved ‘limit state’ Code. The fact that this is a concrete Code is of no particular significance, since similar reactions have been experienced with respect to all the new ‘limit state’ Codes which have been published so far (in the UK at 1east)- similar, that is, in terms of the level of anger at their increased complexity and the replacement of comprehended engineering parameters by non-dimensionalised mathematical criteria. J.E. Dibley