With AI fundamentally reshaping the developer’s role, consider this: nearly two-thirds of professionals using ChatGPT rely on it for programming tasks, making code generation the most common use of the AI. In other words, over 60% of GPT’s usage is now for writing code. This staggering uptake is more than a quirky statistic – it signals a new era in software development. CEOs, tech leaders, and VCs should take note: coding as we know it is being disrupted, and a new kind of developer is emerging in its wake.
AI tools take lead in code generation
Not long ago, writing software meant painstakingly typing out every function and debugging line by line. Today, AI-powered coding assistants are doing a big chunk of that heavy lifting.
Platforms like OpenAI’s GPT-4 and GitHub Copilot can generate code, suggest improvements, and even fix bugs. The adoption numbers are telling. A recent GitHub survey found that over 97% of developers across several countries have used AI coding tools at work, underscoring the point that such assistants are “among the more popular use cases for generative AI today”. GitHub’s Copilot alone reached 1.3 million users by early 2024 (with 77,000 organisations onboard).
This unprecedented integration of AI into coding has boosted productivity and reduced the grunt work for human programmers. Routine code is now drafted in seconds, and entire boilerplate modules are spun up on demand. Developers aren’t spending days writing boilerplate CRUD functions or wrestling with syntax for a new library – they’re asking AI to do it and then refining the results. When 66% of ChatGPT’s professional users turn to it for coding help, it’s clear that AI isn’t just an experimental helper; it’s becoming the default first pass at writing code. This trend promises faster development cycles and leaner teams, but it also raises an urgent question: what is the human coder’s role when the machine can write the code?
From coder to creative supervisor
Far from rendering human programmers obsolete, the rise of AI coding tools is transforming the role of the developer into something new.
In forward-looking software teams, coders are evolving from hands-on keystroke generators into strategic, creative supervisors of AI-driven coding. As one observer put it, “the role of the coder transforms from ‘writer of code’ to ‘manager of AI that writes code.’ We become more like curators, guiding the direction, checking the output, and dealing with all the corner cases an AI might not anticipate.” In essence, the developer is shifting from builder to editor.
This shift is already influencing how tech organisations structure teams. Some CIOs predict leaner development teams comprised of a few senior engineers who oversee AI-generated work, with far fewer junior coders in the mix.
One tech leader likened the change to publishing: “Coders no longer have to be writers — they’re editors,” meaning the best developers will focus on understanding the story and context behind the code – the business logic, the customer needs – and ensure the AI’s output aligns with it. Instead of crafting every line, these engineers review, correct, and augment AI-created code. They translate product requirements into prompts, then refine what the AI produces. Crucially, they bring the judgment, domain insight, and creative problem-solving that no auto-complete can yet replicate.
The implications for the software industry are profound. Junior coding roles and rote programming tasks may diminish, while demand grows for developers who are critical thinkers with cross-functional skills. The “AI supervisor” coder must understand business objectives, communicate with stakeholders, and make high-level design decisions. In short, coding knowledge remains necessary, but it’s no longer sufficient on its own – strategic thinking and context have become just as important as syntax.
Rise of the ‘hustler coder’
Enter the ‘hustler coder’, a new breed of software professional perfectly suited for this AI-assisted landscape. The hustler coder is part developer, part strategist, part product thinker – a tech generalist who thrives by harnessing AI tools to their fullest. Rather than obsessing over low-level algorithms or getting lost in code for code’s sake, this person focuses on outcomes. They know how to guide AI to produce useful code, rapidly prototype solutions, and pivot between technical tasks and broader business conversations.
A hustler coder is characterised not by 10x coding speed in isolation, but by the ability to leverage resources and “hack” the process to get 10x results. They might prompt GPT-4 to generate a dozen different approaches to a problem, then pick the best one. They might stitch together APIs, AI-generated scripts, and off-the-shelf services to quickly solve a customer pain point – all while their more traditional peers are still debating which framework to use.
In meetings, the hustler coder can articulate the technical possibilities to non-engineers and then return to the keyboard to orchestrate those ideas into reality.
Importantly, the hustler coder isn’t defined by any single programming language or credential. Their superpower is adaptability and vision. In an AI-saturated development process, they act as the human glue – understanding the business context deeply and making sure the technology (much of it AI-generated) actually serves the intended purpose. This is in line with emerging industry expectations: the remaining developers in AI-heavy teams must be “critical thinkers who understand the business needs and can work in cross-functional teams,” not just coders operating in silos. The hustler coder exemplifies this blend of technical acumen, creativity, and business savvy.
Soft skills – the new tech superpower
Paradoxically, as code itself becomes easier to generate, the so-called “soft skills” are becoming the hard currency of tech. Communication, context comprehension, empathy, creativity – these are now must-haves for top-tier developers. In fact, some of the best preparation for an AI-driven coding career might not come from computer science alone, but from the humanities and social sciences.
It’s telling that one tech leader described the current moment as the “revenge of the humanities.” In the age of large language models, “not only is an English major valuable, but philosophical and psychological skills are also useful,” notes Steven Johnson, a director at Google’s AI lab.
Why would an anthropology or history degree matter in software development? Because building good software in the AI era is no longer a purely technical exercise – it’s about understanding human needs, crafting narratives for AI to follow, and anticipating user behaviors.
AI “prompt engineering” is as much about language and nuance as it is about logic. Skills honed in humanities disciplines – writing clearly, analysing context, understanding culture, reasoning through ethics and ambiguities – directly improve one’s ability to guide AI systems.
The term “prompt engineering” may sound technical, but it “involves skills from humanities like writing, rhetoric, and psychology,” and relies on abilities such as critical thinking and logical reasoning that humanities graduates excel at.
In practical terms, a developer who can artfully describe a problem to an AI, break down a complex concept, or empathise with a user’s experience, will get far better results from tools like GPT. They’ll spot when the AI’s solution, though syntactically correct, misses the mark for the end-user. They’ll inject the needed context or creative twist to solve a problem in a novel way.
These are the qualities of the new ‘hustler coder’ – not just a code monkey, but a translator between human intention and machine execution. And indeed, leaders in tech are starting to prize these interdisciplinary talents.
Some AI startups actively seek hires with liberal arts backgrounds because they bring a “creative and human-centric approach” to applying AI in real-world scenarios.
Anthropology – an unlikely advantage in the AI age
Speaking from experience, an education in anthropology turned out to be a secret weapon in my tech career. As a Goldsmiths, University of London anthropology graduate stepping into the software industry, I initially felt like an outsider among the coders. Yet, as AI tools grew in prominence, my background became a surprising advantage. Anthropology taught me how to study people and systems holistically – to observe patterns, understand cultural context, and ask the right questions.
These skills have proven invaluable when working with AI-driven development. For instance, crafting an effective prompt for GPT is eerily similar to formulating a good research question in anthropology: you need clarity, context, and an understanding of the “culture” of the AI (its training data and likely biases).
Rather than being bogged down by not having a traditional engineering degree, I found that the humanities gave me a toolkit for learning and problem-solving. In the words of one AI-focused anthropologist, “the humanities don’t teach you the technical details—rather, they give you a toolbox. Your skillset offers an aggressive competency to research anything and everything and distill that dizzying volume of information into a thoughtful final product.”
This resonates deeply with my journey. Each new technical challenge – whether it’s a new programming framework or an AI model’s quirk – became just another domain to research and understand. I would systematically gather information (much like conducting ethnographic research), synthesise insights, and then apply them to guide the AI or design a solution.
My anthropology lens also kept me focused on the human side of software. I’m always asking: Who is this for? What context will they use it in? What unintended effects could this feature have?
These questions often lead to improvements that pure coding prowess might miss. In an era where AI can churn out code on demand, it’s these human-centric considerations that distinguish truly great software. It turns out that studying human culture and behavior is excellent training for wrangling AI – because at the end of the day, technology serves humans, not the other way around.
The ability to bridge human needs and technical execution is precisely the edge that an anthropologist (or psychologist, or historian, or philosopher) can bring to a development team.
As one Cornell-educated historian-turned-AI developer put it, STEM (Science, Technology, Engineering and Mathematics) is fundamentally human, and “you definitely don’t need a CS degree” to contribute meaningfully in tech. I’ve lived that reality.
Rethinking tech talent – look beyond STEM
The rise of AI in coding is a call to action for leaders making hiring and investment decisions. It’s time to broaden the definition of “tech talent.” When software can partially write itself, the best hires aren’t those who can crank out the most lines of code – they’re the ones who can see the big picture and steer the machines in the right direction. This means that a candidate with an anthropology or English degree who taught themselves Python and prompt engineering might outperform a traditional coder when working alongside AI. Their diverse background gives them unique insights and adaptability.
Forward-thinking venture capitalists are already hunting for founding teams that mix engineering expertise with domain knowledge and creative thinking. Similarly, savvy CTOs are starting to pair coders with “AI whisperers” (some of whom hail from non-traditional backgrounds) to turbocharge their development efforts.
Leaders should actively look beyond the usual STEM pedigree when building teams. In fact, some companies have found that employees with liberal arts backgrounds excel in AI roles precisely because they bring a human-centric perspective to technology. They ask empathetic questions, consider ethical dilemmas, and ensure that products resonate with users – all crucial in guiding AI.
The future “coder” might be a history buff who can contextualise a problem historically before solving it, or a psychologist who intuitively grasps user behavior and can translate that into better user interface logic generated by an AI. By embracing these unconventional techies, organisations can cultivate teams of “hustler coders” who balance technical and soft skills, driving innovation in ways a one-dimensional team could never achieve.
For C-suite executives and investors, the takeaway is strategic: adapt your talent strategy to this new reality. When evaluating proposals or product roadmaps, ask not just “Can they code it?” but “Do they understand the context and can they direct the AI to build the right thing?”
The companies that blend AI capabilities with creative, context-aware human guidance will outpace those that stick to the old playbook. In practical terms, that might mean investing in training your existing developers in communication and prompt-design skills, or it might mean hiring that philosophy major who taught herself data science. The competitive edge in the AI-assisted coding era will go to those who assemble teams with complementary strengths – hard tech skills and the “soft” skills that turn technology into business value.
In conclusion, the coding workforce is evolving. AI tools like GPT are writing more than half the code in some organisations, and today’s developers are learning to lead these tools rather than compete with them. The ‘hustler coder’ epitomises this evolution: technically fluent but defined by adaptability, creativity, and strategic thinking. And as counterintuitive as it may sound, some of the most valuable skills for this new coder class come from outside traditional computer science. Anthropology, psychology, history, English – these disciplines teach the art of understanding humans, a skill now vital in guiding AI.
Tech leaders who recognise this shift will reshape their teams for the future, blending coders and non-coders into hybrid creative units. They’ll cultivate developers who can talk architecture with an AI one minute and business strategy with a CEO the next. They’ll fund founders who wield GPT as a force multiplier, regardless of whether they have Ivy League CS degrees.
The message is clear: the future of coding isn’t “no humans required” – it’s humans at their best, amplified by AI. And the best humans for the job might just be the ones with the broadest perspectives.
Embracing the era of AI-assisted development means embracing a new kind of tech talent – one that hustles, coordinates, empathises, and guides AI to drive extraordinary results.
Sources: The statistics on ChatGPT usage for coding and content creation are from a 2023 survey of US professionals : electronicspecifier.com
Insights on how AI is reshaping developer roles come from CIO interviews with tech leaders
cio.com
medium.com
Perspectives on the value of humanities in AI are drawn from industry voices and experts, including Google’s AI research leadership on the “revenge of the humanities” businessinsider.com
and commentary on prompt engineering’s interdisciplinary nature linkedin.com
A first-hand account of an anthropologist thriving in tech illustrates how human context skills translate into AI-era successalumni.cornell.edu
CEOs and investors are encouraged by examples of startups seeking liberal-arts-trained talent for their creative, human-centric approach to AI businessinsider.com
All these trends point to a common conclusion: the future belongs to those who can marry technology with humanity.
