Anti-patterns sune "mafita" masu maimaita waɗa kula suke kamar sannu amma suna lalata ƙira. Mafi yawan a OOP shine God Object, zurfin iko na iko, da Anemic Domain Model.
Aikin da ke sani da kuma yin abubuwa da yawa - tarwatsa Single Responsibility.
{
{} {} {}
{} {} {}
}
Entity → LivingThing → Animal → Mammal → Carnivore → Feline → Cat → HouseCat
Kuwaji kowane matakin ɗin zuwa iyaye duka; canja kusa da saman yana tabowa a ko'ina (fragile base class). Gyara: bugawa da abubtuwa; gwada "has-a" iyawa fiye da zurfin "is-a" sarari.
Abubuwa waɗa ke zama akwatin getters/setters kawai da duka aiki yana zama a waje - OOP kawai cikin suna.
// ANEMIC: data with no behavior; rules live in a separate "service"
class Order { List<Item> items; double total; /* only getters/setters */ }
class OrderService { double calcTotal(Order o) { ... } } // logic exiled
// RICH: behavior lives with the data it operates on
class Order {
private List<Item> items;
double total() { return items.stream().mapToDouble(Item::price).sum(); }
}
→ Yo-yo problem (jumping up/down a deep hierarchy to follow logic)
→ Circular deps (A needs B needs A)
→ Feature envy (a method that mostly uses another class's data)
Anti-patterns shine yadda kyakkyawar niyya ke lalata: God Object yawanci ya fara azaman ɗan karamin taimako, anemic model azaman "kawai DTOs", sai a ossify.
Ba da sunaye yana ba da kawaa gida-gida jiya-jiyoyi ga ƙungiyoyi a bita ta zana zuwa, kuma kowane anti-pattern yana nuni kai-kai iyaye (SRP, abubtuwa, encapsulation) da ya warware shi.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa