Mindset Over Method: Programming & Work-Ethics Mindset in the Age of AI Agents

In this Knowledge Ketchup Session, Ganesh Kunwar explored the mindset developers need in an AI-driven workplace, moving beyond simply knowing programming methods and focusing on problem-solving, ownership, accountability, and work ethics.

This session looks at what happens when AI can write code faster than us, and why responsibility and the way we approach our work matter more than ever.

Transcript

1. Mindset Over Method Programming & Work-Ethics Mindset in the Age of AI Agents For Developers · QA · Designers · Product Owner · Team
2. The Shift AI agents now write, refactor, and even test code alongside us. Speed of Generation Your Accountability ↑ = Code generation goes up. Accountability doesn't move an inch. 3
3. OWNERSHIP Own the Output Outcome, Not Just the Input 01 Whether you typed it or an agent drafted it, your name is on the pull request. •“The AI wrote it” is not a defense in an incident review. •Accountability follows the person who merged it — not the tool that generated it. DEV QA DESIGN You approved the diff — you own every line, agent-written or not. “It passed generated tests” isn't a pass. Verify against real cases. A shipped flow reflects your call, even if a tool proposed it first. 4
4. 02 CRAFTSMANSHIP Eat Your Own Dog Food Especially the food an AI agent cooked. Generated code earns more scrutiny, not less. • Run it, click it, break it before a real user does. • Fluent output can still be wrong — use it the way your customer will. DEV QA DESIGN Run your own build locally before handing it to QA. Use the product daily, not just the test cases for this sprint. Live with your own flow on a real device before sign-off. 5
5. OWNERSHIP Take Responsibility for Your Own Task Work 03 “I wrote the code” or “I tested it” isn't the finish line. • “I made sure it works in production” is. • Ownership ends at outcome, not at handoff. DEV QA DESIGN “Merged” isn't done. Watch it in staging and prod. A missed bug in your area is your finding, whoever wrote the code. Follow through to the built screen, not just the handoff file. 6
6. 04 QUALITY Review Like You're the Last Line of Defense Because, increasingly, you are. • Agents don't know your users, your edge cases, or your business context. • That judgment call is still, and only, yours to make. DEV QA DESIGN Read every generated diff like a stranger wrote it — because one did. Design test cases for what the agent wouldn't think to break. Check generated UI against real content, not lorem ipsum. 7
7. 05 CRAFTSMANSHIP Understand Before You Accept If you can't explain why the code works, you don't own it, you're forwarding it. • Copy-pasting a solution you don't understand is technical debt with a delay timer. • Ask the agent “why” as often as you'd ask a teammate. DEV QA DESIGN Be able to explain your architecture without the chat log open. Understand the intended behavior, not just the observed one. Know the reasoning behind a suggested layout before you use it. 8
8. 06 GROWTH Sharpen the Saw Sharpen your judgment, not just your syntax. • Typing skill matters less every year; taste, architecture sense, and debugging intuition matter more. • Block real time for learning, it's not a nice-to-have, it's maintenance. DEV QA DESIGN Study the code an agent writes — don't just accept it. Grow your risk sense; tooling can't replace it. Keep building taste — it's what tools can't generate for you. 9
9. 07 GROWTH Build a Career, Not a Job Anyone can ask an agent for code. Your value is knowing what to ask, when to say no, and when it's confidently wrong. • Ask “what am I learning here?”, not only “did I close the ticket?” • Skills compound; tickets don't. DEV QA DESIGN Aim to out-think the tool, not just out-type it. Become the person whose judgment catches what scripts miss. Build a point of view tools can amplify but not replace. 10
10. 08 CRAFTSMANSHIP Leave It Better Than You Found It The Boy Scout Rule - and leave it understood. • Document the why, not just the what, especially when it only lives in a chat log with an agent. • Future-you can't grep a conversation nobody saved. DEV QA DESIGN Comment the reasoning, not just the mechanics. Log why a case matters, so it survives the next refactor. Annotate intent in the file, not only in a chat thread. 11
11. Eight Habits, One Thread Ownership doesn't get outsourced to the tool. Own the Outcome, Not Just the Input Eat Your Own Dog Food Take Responsibility for Your Own Work Review Like You're the Last Line of Defense Understand Before You Accept Sharpen the Saw Build a Career, Not a Job Leave It Better Than You Found It 12
12. Open Question “When do you trust the agent - and when do you override it?” Bring one real example from your own work this week. Thank you