AI ba ya cire software lifecycle — yana matsa kowane mataki kuma yana canza aikinka daga rubuta code zuwa ƙayyadewa, review, da tabbatarwa. Ka riƙe matakai iri ɗaya (spec → design → implement → review → test → ship) amma ka sa human gates a fili.
ka ɗauki AI a matsayin junior pair mai sauri, mai kwaɗayi — yana yin draft cikin sauri amma yana buƙatar jagora da dubawa. Ma'aunin aiki ya zama a kowane mataki, ba "buga duka da kanka ba".
Spec ──▶ Design ──▶ Implement ──▶ Review ──▶ Test ──▶ Ship
AI AI AI HUMAN AI HUMAN
draft options code+tests gate gen+run gate
Babban canji: bottleneck yana motsawa daga rubutawa zuwa review da tabbatarwa — don haka ka saka jari a specs, tests, da review, ba raw typing speed ba.
Mai hirar yana duba ko kana riƙe engineering discipline ko kawai "bari AI ya rubuta shi". Amsa mai rauni: "AI yana rubuta code don haka muna ship da sauri." Amsa mai ƙarfi: lifecycle iri ɗaya, AI yana hanzarta kowane phase, mutane suna da alhakin gates (spec, review, ship), kuma tabbatarwa ita ce sabuwar bottleneck.
Tsallake spec yana samar da confident nonsense; tsallake review yana gina quality/security debt; auna sakamako (software mai aiki, ƙarancin incidents), ba lines of code ba.
Ɗakin karatu na tambayoyin hira na IT tare da amsoshi cikakke — daga Junior zuwa Senior.
Ba da Gudummawa