One-Off se Worker tak: Manufacturing ki taraf Handoff
1 Signal · 4 Promotions · 1 Fork
Do mahine pehle, is track ke shuru mein, Ana ne apne Monday ke task ko dekha (hafte ke customer messages ko groups mein sort karna aur aik summary likhna) aur usay laga ke is ka aik Mode 2 future hai: aik aisa task jo woh har hafte, usi tareeqe se karti thi, aur jo clearly aik dafa build karne ke layeq tha. Lekin filhaal, yeh ab bhi aik Mode 1 job tha: woh isay har Monday, saat principles ka istemaal karte hue, hath se solve karti rehti thi. Yeh har dafa kaam karta tha. Aur yeh har Monday ki subah bhi khaa jata tha.
Us ke colleague Diego ke paas isi qism ka weekly task hai. Woh bhi isay har hafte hath se, achhi tarah, solve karta hai. Woh is mein mahir hai.
Aik saal baad, Ana is par taqreeban koi Monday subah nahin lagati. Woh cross kar gayi: us ne apne baar baar wale Mode 1 solution ko aik aise worker mein badal diya jo routine ko khud sambhal leta hai, aur woh sirf un exceptions ko check karne ke liye beech mein aati hai jinhein worker flag karta hai. Diego ne apne par taqreeban pachaas Mondays lagaye hain (lagbhag sau ghante) aur agle saal pachaas aur lagayega. Wohi task, wohi skill. Farq sirf itna hai ke Ana ne problem ko solve karna band kar diya aur solution ko manufacture karna shuru kar diya.
Yeh course wohi crossing hai. Yeh Mode 1 ka aakhri stop hai aur Mode 2 ka on-ramp.
Yeh kis ke liye hai
Koi bhi jis ke paas aik aisa task ho jise woh aik agent ke saath, usi tareeqe se, baar baar solve karta rehta hai, aur usay yeh mehsoos hone laga hai ke har dafa isay hath se karna jeene ka ghalat tareeqa hai. Yeh course aap ko dikhata hai ke isay solve karna kab band karna hai aur isay aik permanent worker mein kab badalna hai, aur jab aap aisa karte hain to actually kya badalta hai.
Yeh book poori dunya mein parhi jaati hai, un logon ke zariye jo kayi mukhtalif zabanon mein kaam aur parhai karte hain. Yahan ke examples saadi English aur roz-marra ke halaat use karte hain jin ka matlab aik hi rehta hai chahe aap kahin bhi rehte hon. Naye lafz (jaise spec, eval, aur runtime) pehli dafa aane par samjhaye jate hain.
Pehle Problem Solving with General Agents mukammal karein; yeh course farz karta hai ke aap saat principles ka istemaal karte hue aik hi session mein kisi problem ko achhi tarah solve kar sakte hain. Yeh bhi farz karta hai ke aap Is This an Agent Problem? kar chuke hain aur jaante hain ke Mode 1 (isay aik dafa solve karo) aur Mode 2 (aik permanent worker banao) ka kya matlab hai.
📚 Teaching Aid
Poori Presentation Dekhein — One-Off se Worker tak
Usool, aik line mein
Aap aik worker scratch se nahin banate. Aap aik aise solution ko promote karte hain jo aap pehle prove kar chuke hain.
Log "aik AI worker banao" sunte hain aur kuch bhi na hone se shuru karne ka tasavvur karte hain: aik blank screen, aik mushkil engineering project, hafton ka kaam. Yeh tasavvur ghalat hai, aur yeh logon ko us sab se qeemti cheez se door bhaga deta hai jo woh kar sakte the. Sach is ke ulta hai: jab tak aik task worker banne ke liye taiyar hota hai, aap zyada tar kaam pehle hi kar chuke hote hain. Har Monday jab Ana ne apna task hath se solve kiya, woh, bina jaane, theek theek yeh maaloom kar rahi thi ke worker ko kya karna hoga. Manufacturing invention nahin hai. Yeh aik aise solution ko le kar jise aap pehle hi hath se prove kar chuke hain, usay permanent banana hai.
Wohi reframe poora course hai. Neeche, aap woh aik signal dekhenge jo aap ko batata hai ke aik solution cross karne ke liye taiyar hai, aap ke Mode 1 kaam ke woh chaar hisse jo aik worker mein promote hote hain, aur raaste ka woh aik fork jahan aap chunte hain ke kis qism ka worker banana hai.
Mukhtasar version (chaar bullets)
- Sirf wahi cross karein jo aap pehle prove kar chuke hain. Aap aik worker sirf us solution se manufacture kar sakte hain jise aap ne hath se, cleanly, kayi dafa solve kiya ho. Yeh repetition automate karne se pehle zaaya kiya hua waqt nahin hai; yehi woh tareeqa hai jis se aap discover karte hain ke worker ko actually kya karna chahiye.
- Aap shuru se shuru nahin kar rahe. Chaar cheezein jo aap pehle hi Mode 1 mein hath se kar chuke hain (aap ka brief, aap ka check, woh steps jo aap ne drive kiye, aur khud session) un mein se har aik aik permanent form mein promote hoti hai. Yehi poora build hai.
- Isay permanent banana do tarah fork hota hai. Aap aik personal worker own kar sakte hain (halka, sirf aap ke liye) ya aik Digital FTE manufacture kar sakte hain (bhari, kisi organisation ke liye). Fork aik sawal se tay hota hai: worker kis ke liye hai?
- Payoff hai task versus asset. Hath se solve karna labour ko aik task ki tarah kharch karna hai: aap har dafa woh ghante lagate hain. Aik worker labour ko aik asset banata hai: aap aik dafa build karte hain, aur woh tab bhi kaam karta hai jab aap so rahe hote hain.
Part 1 — Signal: kya yeh waqai cross karne ke liye taiyar hai?
Yeh kis ghalti ko rokta hai: "Maine aik aise task ke liye aik permanent worker bana liya jise maine abhi theek se samjha bhi nahin tha, to maine aik hafta ghalat cheez banane mein laga diya, aur phir usay dobara banana pada."
Is This an Agent Problem? mein, Gate 2 ne aap ko signal ka pehla hissa pehle hi de diya tha: aik task tab Mode 2 hota hai jab teenon dials oopar hon: aap usay aksar karte hain, har dafa us ka shape aik jaisa hota hai, aur woh effort ke layeq hota hai. Trigger simple tha: jab teesri dafa aap wohi task usi tareeqe se karein, ruk kar check karein.
Lekin aik doosra hissa bhi hai jise Gate 2 check nahin kar sakta tha, aur yehi woh hai jise log skip karte hain: kya aap ne isay actually achhi tarah solve bhi kar liya hai?
Aap sirf aik proven solution se manufacture kar sakte hain. Agar aap aik aise method se worker banate hain jise aap abhi samajh hi rahe hain, to aap ghalat worker banate hain, aur aap ko pata sirf effort lagane ke baad chalta hai. To cross karne ke poore signal ke do hisse hain:
- Gate 2 kehta hai Mode 2 (aksar, aik jaisa, layeq), aur
- Aap ne is task ko Mode 1 mein itni dafa cleanly solve kiya hai ke method ne badalna band kar diya hai.
Yeh doosra hissa hi asli test hai. Apne aap se poochein: pichli teen dafa jab maine yeh kiya, kya maine usi tareeqe se kiya? Agar haan, to shape stable hai, aap ne worker dhoond liya. Agar aap ab bhi har hafte isay thora alag solve karte hain (alag steps, alag checks, naye faisle) to aap ne abhi stable shape nahin dhoondi. Isay Mode 1 mein solve karte rahein jab tak yeh settle na ho jaye. Yeh repetitions aap ka automate karne mein nakaam hona nahin hain. Yeh aap ka woh research karna hai jo worker ko batata hai ke kya karna hai.
Aik task ko hath se karte rehna inefficient lagta hai jab aap jaante hain ke yeh aik Mode 2 job hai. Aisa nahin hai. Har dafa jab aap isay solve karte hain, aap aik edge case, aik behtar step order, aik aham check discover karte hain. Hafte aik par bana hua worker yeh sab miss kar deta. Hafte paanch par bana hua worker paanch hafton ki mushkil se hasil ki gayi knowledge par bana hota hai. Tab cross karein jab learning dheemi ho jaye, us se pehle nahin.
Part 2 — Reframe: worker kaam ke andar chhupa hua hai
Yeh woh hissa hai jo poori cheez ka feel badal deta hai. Jab bhi aap ne Mode 1 mein task ko achhi tarah solve kiya, aap ne aik trail chhoda, aur wohi trail worker ka raw material hai.
Sochein ke aik achhe Mode 1 session ne actually kya produce kiya. Aap ne aik brief likha (kis se kaam karna hai, aap ko kya chahiye tha, "done" ka kya matlab tha). Aap ne output aik clear shape mein maanga. Aap ne yeh yaqeeni banane ke liye aik check chalaya ke woh sahi hai. Aap ne result aik file mein save kiya. In mein se kuch bhi throwaway nahin tha. To manufacturing do moves hain, scratch se build nahin: pehle un pieces ko harvest karein, phir har aik ko itna harden karein ke woh aap ke baghair chal sake. Is doosre move ke baare mein saaf nazar rakhein: hardening asli kaam hai, yani exits design karna, aik aisa eval banana jo khud ko grade kare, aur aik runtime khara karna sab genuine engineering hai, sirf yeh likh lena nahin jo aap pehle se karte hain. Reframe aap ko blank page se bachata hai; yeh build ko trivial nahin bana deta.
Yahin economics palat jaati hai, aur yeh poori book ka dil hai. Jab aap aik task hath se solve karte hain, aap ka labour aik task hai: aap waqt kharch karte hain, aap ko aik result milta hai, aur woh waqt chala jata hai. Jab aap us solution ko aik worker mein promote karte hain, wohi labour aik asset ban jata hai: aap usay build karne mein aik dafa waqt lagate hain, aur woh baar baar results deta rehta hai, jab ke aap koi aur kaam karte hain. Yehi Diego, jo saal ke sau ghante lagata hai, aur Ana, jis ne aik dafa kuch ghante lagaye, ke darmiyan poora farq hai.
Task ke taur par labour aap ko kharch karta rehta hai. Asset ke taur par labour aik dafa kharch hota hai, phir aap ko wapas deta hai. Lines logon ki tawaqqo se jaldi cross karti hain.
Part 3 — Chaar promotions
Crossing aik bara build nahin hai. Yeh chaar specific upgrades hain, aur in mein se har aik ke liye mushkil soch-bichaar aap pehle hi Mode 1 mein kar chuke hain. Har promotion us cheez ko leti hai jo aap ne hath se ki thi aur usay aisi cheez mein badal deti hai jo worker khud karta hai. Har aik aap ko us Mode 2 course tak bhi pahuncha deti hai jo isay poori tafseel se sikhata hai.
Aap chaar nai cheezein add nahin kar rahe. Aap chaar aisi cheezein upgrade kar rahe hain jo aap ke paas pehle se hain.
Promotion 1 — Aap ka brief aik spec ban jata hai
Mode 1 mein aap har dafa aik quick brief likhte the: kis se kaam, aakhir mein kya chahiye, done kab (Gate 3 ki teen lines). Woh aap ke zehan mein ya kisi scratch note mein rehta tha, aur aap usay on the fly adjust kar sakte the.
Aik worker aap ka zehan nahin parh sakta aur na yeh pooch sakta hai ke aap ka matlab kya tha, isliye us brief ko aik spec banna padta hai, yani specification ka short, aik likha hua document jise worker har aik run par parhta hai aur jo theek theek batata hai ke woh kya karta hai, kis cheez par, aur kis standard tak. Spec wohi teen lines hain jo aap pehle se likh chuke the, magar explicit, mukammal, aur permanent. Isay skip karein, aur worker gaps ko guesses se bhar deta hai, har run thora alag.
Yahan seekhein: Spec-Driven Development.
Promotion 2 — Aap ka check aik eval ban jata hai
Mode 1 mein aap output ko khud verify karte the (teesra principle): aap usay parhte the, numbers ko source ke against check karte the, aur usay isliye trust karte the kyun ke aap ne dekha tha.
Aik worker aap ke dekhe baghair chalta hai, aksar din mein kayi dafa. "Aap har dafa usay parhein" scale nahin karta, aur yeh woh lamha bhi nahin pakadta jab worker khamoshi se cheezein galat karne lagta hai. To aap ka check aik eval ban jata hai, yani evaluation ka short, example inputs ka aik saved set jo apne known-good answers ke saath paired hota hai. (Zyada fuzzy kaam ke liye, "known-good answer" aik label, aik rubric score, ya aik checklist ho sakta hai jise output poora kare, hamesha aik perfect block of text nahin.) Worker ke results in ke against khudkaar tareeqe se grade hote hain, to checking aap ke baghair hoti hai aur usi lamhe aap ko warn kar deti hai jab worker drift karne lagta hai. Aap ki aik dafa ki reading aik aisa test ban jaati hai jo hamesha chalta hai. Isay skip karein, aur drift khamosh rehti hai, aap usay aik naraz customer se sunte hain, kisi check se nahin.
Yahan seekhein: Eval-Driven Development.
Promotion 3 — Aap loop se nikalte hain, aur exits design karte hain
Mode 1 mein aap loop ke andar the (chhata aur saatwan principle): aap har step ko dekhte the, jab woh bhatakta usay redirect karte the, aage barhne se pehle approve karte the. Aap safety net the.
Aik worker steps khud chalata hai, koi dekh nahin raha hota. Yeh woh hissa hai jo log galat samajhte hain: routine aasaan hissa hai: aap ka Mode 1 method usay pehle hi handle kar leta hai. Mushkil hissa edges hain: ghair-maamooli input, woh case jise aap ke method ko kabhi deal nahin karna pada. Aap ko pehle se tay karna hoga ke jab worker kisi aisi cheez se takraye jise woh handle nahin kar sakta to woh kya karega. Taqreeban hamesha jawab yeh hota hai: ruk jao aur kisi insaan ko bulao. Un exits ko design karna (kab escalate karna, kis ke paas, kis maloomat ke saath) is promotion ka asli kaam hai, aur yehi woh kaam hai jo aik worker ko trust karne ke layeq mehfooz rakhta hai. Aur har task ke edges hote hain, woh bhi jo simple lagte hain: aik worker jo code likhta hai woh ruk kar aap se poochta hai jab us ki change tests tod deti hai; aik worker jo invoices pay karta hai woh kisi muqarrara amount se oopar ki har cheez ko pay karne ke bajaye flag kar deta hai; aik worker jo documents file karta hai woh us aik ko, jise woh confidently sort nahin kar sakta, guess karne ke bajaye alag rakh deta hai. Shape kabhi nahin badalta: routine handle karo, exception escalate karo. Isay skip karein, aur worker, der sawer, wohi aik case handle kar lega jise usay flag karna chahiye tha, confidently aur galat.
Yahan seekhein: Build AI Agents aur Building a Digital FTE.
Promotion 4 — Aap ka session aik runtime ban jata hai
Mode 1 mein kaam aik aise session mein rehta tha jo aap kholte the. Aap laptop band karte aur us ka wujood khatam ho jata. Agli dafa ke liye kuch bhi save karna (paanchwan principle) aap the, hath se, cheezein files mein daalte hue.
Aik worker ko us waqt bhi maujood rehna hota hai jab aap wahan nahin hote. Is ke liye aik runtime chahiye, yani woh software jo worker ko zinda aur khud-ba-khud chalta rakhta hai, aur usay rehne ke liye koi jagah taake woh reachable aur reliable ho. Us ki memory khud-ba-khud persist hoti hai, is liye nahin ke aap ne usay save karna yaad rakha. Isay skip karein, aur koi worker hai hi nahin, sirf aap, hath se aik session kholte hue, jo theek wahi jagah hai jahan se aap ne shuru kiya tha.
Yahan seekhein: Deploy the Agent Harness. (Agar worker sirf aap ke liye hai, to aik halka raasta bhi hai, neeche fork dekhein.)
Chaar promotions aik nazar mein:
| Mode 1 mein aap ke paas kya tha | Mode 2 mein woh kya banta hai | Isay kahan seekhein |
|---|---|---|
| Aap ka brief (kis se kaam / aakhir mein kya chahiye / done kab) | Aik spec jise worker har run par parhta hai | Spec-Driven Development |
| Aap ka apna eyeball check | Aik eval jo worker ko khudkaar tareeqe se grade karta hai | Eval-Driven Development |
| Aap ka dekhna aur redirect karna | Worker khud loop chalata hai aur edges par escalate karta hai | Build AI Agents · Building a Digital FTE |
| Aik session jo aap kholte aur band karte hain | Aik runtime jis par worker rehta hai | Deploy the Agent Harness |
Bas yehi poora crossing hai. Chaar upgrades, har aik aisi cheez jo aap hath se kar ke pehle hi samajh chuke the.
Chaar promotions woh hain jo cross karte waqt badalti hain. Aik aham cheez zyada nahin badalti: aap ke plugins, yani woh skills (packaged know-how jo aik agent dobara use karta hai) aur connectors (aap ki doosri apps aur data se links) jo aap Mode 1 mein solve karte waqt pehle hi use kar chuke the. Kyun ke yeh open, cross-runtime formats par bane hote hain, wohi skills aur connectors claude.ai, woh general agents jo aap ne drive kiye (Claude Code, OpenCode, Cowork, OpenWork), aur personal harnesses ke across saath chalte hain, aur aksar sirf halki adaptation ke saath, un workers mein bhi jo aap manufacture karte hain. Jab tak aik plugin un open formats par qaaim rehta hai, woh crossing ke paar zyada tar jaise-ka-taisa aa jata hai; yeh aik aur wajah hai ke worker banana zyada tar promotion hai, invention nahin. In se naye hain? Skills & Connectors dekhein.
Yeh kyun kaam karta hai (is ke peeche ki research) — optional
Do purane ideas batate hain ke "promote karo, scratch se mat banao" sahi order kyun hai.
Pehla Fred Brooks ka hai, jinhon ne 1960 ki dahai ke sab se bare software projects mein se aik ki qiyadat ki aur is ke baare mein The Mythical Man-Month (1975) mein likha. Un ka mash'hoor mashwara: plan to throw one away — waise bhi aap phenkenge hi. Pehli cheez jo aap banate hain woh aap ko sikhati hai ke aap ko kya banana chahiye tha; rakhne ke layeq version doosra hota hai, us seekh ke saath banaya gaya jo aap ne hasil ki. Aap ke baar baar ke Mode 1 solves bilkul wohi throwaways hain. Aap automate karne se pehle hafte zaaya nahin kar rahe; aap woh experiment chala rahe hain jo aap ko batata hai ke permanent worker kya hona chahiye. Worker ko hafte aik par banana us version ko banana hota jise aap ne hamesha phenkna hi tha.
Doosra Lisanne Bainbridge ke Ironies of Automation (1983) se hai, kaam ko automate karne par sab se zyada cite hone wale papers mein se aik. Un ki finding: jab aap kisi job ke routine hisson ko automate karte hain, to aap insaan ko hatate nahin, balke insaan ko theek un kam-yaab, mushkil cases ke liye zimmedar chhod dete hain jinhein automation handle nahin kar sakti, aur automation jitni reliable hoti hai, woh kam-yaab interventions utni hi zyada aham (aur mushkil) ban jaate hain. Yehi theek wajah hai ke Promotion 3 exits design karne ke baare mein hai, routine ke nahin. Routine automate karne ka aasaan hissa hai; value aur danger dono edges par rehte hain, isliye aap escalation ko jaan-boojh kar design karte hain, is umeed par nahin chhodte ke yeh kabhi pesh hi nahin aayega.
Sources: Brooks, F. P. (1975). The Mythical Man-Month. Addison-Wesley. Bainbridge, L. (1983). "Ironies of Automation," Automatica, 19(6), 775–779.
Part 4 — Fork: isay permanent banane ke do raaste
Jab aap cross karne ka faisla kar lete hain, "aik durable worker banao" do mukhtalif raaston mein fork ho jata hai. Yeh wohi chaar promotions use karte hain, lekin yeh mukhtalif logon ke liye bante hain, aur yeh farq matter karta hai.
Wohi proven solution, do destinations. Faisla-kun sawal yeh hai ke worker par bharosa kaun karta hai.
Own it — aik personal harness. Agar worker aap ke liye hai (aap ka inbox, aap ka code, aap ke kaam) to halka raasta aik personal harness hai (woh software jise aap khud chalate aur own karte hain jo aap ke liye aik worker ko zinda rakhta hai). Aap chaaron promotions karte hain, lekin halke andaaz mein: spec aap ke apne notes hain, eval aap ki apni chand misalein hain, escalation yeh hai ke worker aap ko message karta hai. Wahan tak pahunchne ke liye aap ko shayad kabhi poore Mode 2 track ki zaroorat na pade. Yeh wohi raasta hai jo Personal Agent Harnesses section sikhata hai, OpenClaw aur Hermes ka istemaal karte hue.
Manufacture it — aik Digital FTE. Agar worker kisi organisation ke liye hai (aisi cheez jis par doosre log bharosa karenge, jise reliably chalna chahiye, governed hona chahiye, aur scale karna chahiye, aur shayad bechi bhi jaye) to woh aik Digital FTE hai (aik "digital full-time employee"), aur aap chaaron promotions sakhti se karte hain: spec shared aur reviewed hota hai, eval aik aisa gate hai jis par poori team bharosa karti hai, escalation kisi named insaan ya team ke paas jaati hai, aur runtime asli production infrastructure hota hai. Yeh poora Mode 2 — Manufacturing track hai.
Faisla-kun sawal aik line ka hai: worker kis ke liye hai, aur is par bharosa kaun karta hai? Sirf aap ke liye → personal harness. Kisi organisation ke liye → Digital FTE. Wohi crossing, do gehrai ke rigour.
Aap kis se banate hain. Do raaste constant hain; tools variable hain, aur yeh aksar badalte hain. Yeh raha woh variable jaisa 2026 mein hai; aap raasta pehle hi chun chuke hain, isliye aap ko sirf woh column chahiye jo us se match karta hai:
| Raasta | Aap kis se banate hain (2026) | Isay kahan seekhein |
|---|---|---|
| Own it — aik personal harness | OpenClaw ya Hermes — open-source harnesses jinhein aap khud chalate aur own karte hain | Personal Agent Harnesses |
| Manufacture it — aik Digital FTE | OpenAI Agents SDK, ya aik managed Claude agent setup | Mode 2 track; Choosing Agentic Architectures aap ko chunne mein madad karta hai |
Woh general agent jise aap Mode 1 mein drive karte aaye hain (Claude Code, OpenCode, Cowork, ya OpenWork) yahan ghaib nahin ho jata; dono raaston par yeh wohi tool hai jise aap worker ko build aur install karne ke liye use karte hain. Bas yeh har dafa task karne wali cheez hona band kar deta hai, aur woh cheez ban jata hai jo task karne wali cheez banati hai.
Aik cheez jis ke liye budget rakhein. Aik durable worker API par chalta hai, jahan har model call metered hoti hai aur us ki qeemat lagti hai, aur yeh dono raaston par sach hai: aik personal harness (OpenClaw, Hermes) API par utna hi chalta hai jitna aik manufactured Digital FTE chalta hai. Yeh claude.ai, web app, ke andar AI use karne se mukhtalif hai, jahan kisi plugin ki calls aap ki subscription ya free tier se nikalti hain, koi alag per-call bill nahin hota. To crossing "sochne" ko aap ke plan mein bundled cheez se aik asli, per-call cost mein badal deta hai. Yeh aik aur wajah hai ke "worth it?" wala signal matter karta hai: aik worker ko na sirf aap ka build time wapas karna hota hai, balke woh model bill bhi jo woh har dafa kaam karte waqt charhayega. (Aik personal harness ke liye woh bill aap khud pay karte hain; aik Digital FTE ke liye aap ya organisation karti hai, aur agar aap worker bechte hain, to wohi per-call cost woh number hai jis ke gird aap pricing karte hain.)
Aik personal harness own karna Mode 1 aur Mode 2 ke darmiyan baitha koi naya mode nahin hai: yeh wohi "aik durable worker banao" wali activity hai, jo aik shakhs tak scale-down ki gayi hai. Mode yeh poochta hai ke aap aik dafa solve karte hain ya rehne ke liye build karte hain; ownership yeh poochta hai ke worker aap ka hai ya kisi organisation ka. Do alag sawal. Aap koi bhi mode aisi harness par chala sakte hain jo aap own karte hain.
Ana ka blueprint, bhara hua
Apna karne se pehle, yeh rahi Ana ka Monday task, crossed: wohi chaar promotions, bhare hue. "Done" aisa dikhta hai, aur ghaur karein ke har line bas woh cheez hai jo woh do mahine se hath se kar rahi thi.
- Brief → spec. Har Monday, Support folder mein naye messages parho. Har aik ko theek aik group mein daalo (complaint, question, order, ya other) aur aik one-page summary likho jis mein har group ka count aur teen sab se aam complaints hon. (Us ki Gate 3 ki teen lines, hamesha ke liye likhi hui.)
- Check → eval. Baarah purane messages jinhein woh pehle hi hath se sort kar chuki thi, har aik apne sahi group ke saath save kiya hua. Jab bhi woh worker ki instructions badalti hai, usay pehle un baarah ke against chalaya jata hai; agar woh aik se zyada ko ghalat sort karta hai, to woh usay asli mail ko chhoone se pehle theek kar leti hai.
- You → exits. Agar koi message aisi zaban mein ho jise worker handle nahin karta, ya kisi aisi refund ka taqaza kare jo us ki set ki hui limit se bara ho, to worker guess nahin karta, woh message ko flag karta hai aur Ana ko ping karta hai. Baqi sab kuch woh khud handle kar leta hai.
- Session → runtime. Worker har Monday subah aik chhoti always-on machine par chalta hai aur apni woh list khud rakhta hai jo woh pehle process kar chuka hota hai, to Ana kuch nahin kholti aur kuch yaad nahin rakhti.
In mein se kuch bhi crossing wale din invent nahin hua. Yeh do mahine ke Mondays hain, permanent banaye hue.
Aap ki baari
Aik aisa real task lein jise aap pehle se aik agent ke saath, usi tareeqe se, aik se zyada dafa solve karte hain. Usay crossing se guzaarein, neeche diye gaye teen steps bharte hue.
Apne task ke liye teenon steps bharein. Grader yeh check karta hai ke task waqai proven hai ya nahin, aap ke chaar promotions concrete hain ya nahin, aur, sab se aham, ke aap ka exit aik skip kiye gaye edge ke bajaye aik asli escalation case hai ya nahin.
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
Agar aap teenon steps bhar sakte hain, to aap "kisi din shayad aik agent banane ke baare mein soch" nahin rahe. Aap aik ka blueprint thaame hue hain. Mode 2 track bas chaar promotions hain, asal mein kiye hue.
Yeh aap ko kahan handoff karta hai
Yehi crossing hai. Mode 1 labour aik task ki tarah tha: aap har dafa ghante lagate the. Mode 2 labour aik asset ki tarah hai: aap aik dafa build karte hain, aur woh tab kaam karta hai jab aap so rahe hote hain. Yeh course wohi jagah hai jahan aik doosra ban jata hai.
Ab aap Mode 2 — Manufacturing track mein aik blueprint ke saath dakhil hote hain, blank page ke saath nahin. Wahan har course chaar promotions mein se aik ko asal mein banata hai:
- Python in the AI Era: woh language jis mein manufacturing bani hoti hai (aap direct karte hain; agent us ka zyada hissa likhta hai).
- Build AI Agents: woh worker jo loop chalata hai aur escalate karta hai.
- Eval-Driven Development: woh eval jo usay grade karta hai.
- Building a Digital FTE: chaaron promotions aik aise worker mein assemble kiye hue jis par koi organisation bharosa kar sake.
- Deploy the Agent Harness: woh runtime jis par yeh rehta hai.
Aik proven Mode 1 solution aur aik bhara hua blueprint le kar daakhil hon, to aap kuch bhi na hone se shuru nahin kar rahe. Aap aik aisi cheez ko promote kar rahe hain jo pehle se kaam karti hai.
References
Is course ke claims ke peeche ke ideas, har us shakhs ke liye jo originals chahta hai.
- Brooks, F. P. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley. "plan to throw one away" wali daleel, yani ke aap ke proven Mode 1 solves wohi prototype kyun hain jis se asli worker banta hai, isi naam ke chapter mein hai. (overview)
- Bainbridge, L. (1983). "Ironies of Automation." Automatica, 19(6), 775–779. doi:10.1016/0005-1098(83)90046-8. Routine ko automate karna insaan ko un kam-yaab, mushkil cases ka zimmedar kyun chhod deta hai; yehi wajah hai ke Promotion 3 exits design karne ke baare mein hai, routine ke nahin. (readable summary)
- Munroe, R. "Is It Worth the Time?" xkcd 1205. Task-versus-asset chart ke peeche ka break-even logic: aik task kitni baar repeat hota hai yeh tay karta hai ke worker banana worth it hai ya nahin.
Flashcards Study Aid
Knowledge Check
Abhi aap ne jin ideas se guzra, un par aik tez gated self-check.