{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"AI Thoughtmakers","title":"Human Engineering in an AI Native Future |","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/8c743b5d\"></iframe>","width":"100%","height":180,"duration":928,"description":"AI is writing code, fixing bugs, and deploying software. So what does the future of software engineering look like when AI can handle more of the work?\n\nIn this episode of AI Thoughtmakers, we sit down with Jaspreet, Tech Lead at GeekyAnts and a team of one shipping and owning everything on his project, for a conversation that every engineer needs to hear right now — about what it actually means to be indispensable in an AI-native world, and why the engineers who are thriving aren't the ones who are scared of AI, but the ones who've made it their multiplier.\n\nFrom why coding has always been just 20-30% of the job (AI just made it visible), to why you can outsource your thinking but never your understanding — this is the most grounded, practical take on the future of human engineering you'll find.\n\nKey topics covered:\n• Why there are two kinds of engineers today — those panicking and those shipping faster than ever\n• The headlines that are misleading engineers — and what Google's \"25% AI-written code\" actually means\n• What system-level thinking is — and why it's the only thing that will keep engineers relevant\n• What you should never delegate to AI — customer calls, understanding, and judgment\n• Why coding has always been 20-30% of the job — and AI just made that visible\n• Why universities should stop treating syntax as mastery — and focus on fundamentals instead\n• The one skill every engineer must master: debugging\n• Why communication matters more than coding in the AI era\n• How prompt engineering evolved into context engineering — and why that's actually bigger\n• How managers need to evolve — from counting tickets to measuring system stability and outcomes\n\nIf you're an engineer anxious about where things are going, a tech lead building AI-native teams, or a student trying to figure out what skills actually matter — this episode will give you more clarity than any headline.\nSubscribe for more conversations on AI, engineering, product development, and the future...","thumbnail_url":"https://img.transistorcdn.com/9ucptEYd5kVPtNA_zR1pGGq70YIZjxQEgWQXPqsHHDg/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yNGQz/ZmI1YWRiYWMxMTM3/YmQyNDA4YTQ2ZTY4/N2RjNi5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}