Mavjud vaziyatning sabablari tushunilmaguncha islohotlar o'tkazilmasligi kerak.
Ushbu tamoyil texnik qarzni bartaraf etishda dasturiy ta'minot muhandisligida dolzarbdir. Dasturning har bir satri dastlab kimdir tomonidan negadir yozilgan. Chesterton's Fence, birinchi qarashda ortiqcha yoki noto'g'ri ko'rinsa ham, kodni o'zgartirish yoki olib tashlashdan oldin uning konteksti va ma'nosini to'liq tushunishga harakat qilish kerakligini taklif qiladi.
Bu tamoyilning nomi G.K.Chestertonning hikoyasidan kelib chiqqan. . Bir kishi yo'lning o'rtasidan o'tib ketayotgan panjaraga duch keldi. Bu befoyda panjara to‘siq bo‘layotganidan hokimga shikoyat qiladi va uni olib tashlashni so‘raydi. Hokim birinchi navbatda nega panjara borligini so'raydi. Erkak bilmayman desa, shahar hokimi: "Agar uning maqsadini bilmasangiz, men uni olib tashlashingizga albatta ruxsat bermayman. Boring va undan foydalanishni bilib oling, keyin yo'q qilishingizga ruxsat beraman", deydi. u."
Chesterton's Fence on Wikipedia
Reforms should not be made until the reasoning behind the existing state of affairs is understood.
This principle is relevant in software engineering when removing technical debt. Each line of a program was originally written by someone for some reason. Chesterton's Fence suggests that one should try to understand the context and meaning of the code fully, before changing or removing it, even if at first glance it seems redundant or incorrect.
The name of this principle comes from a story by G.K. Chesterton. A man comes across a fence crossing the middle of the road. He complains to the mayor that this useless fence is getting in the way, and asks to remove it. The mayor asks why the fence is there in the first place. When the man says he doesn't know, the mayor says, "If you don't know its purpose, I certainly won't let you remove it. Go and find out the use of it, and then I may let you destroy it."
O'zbekcha
English