Why Coding Skills Matter More Than Ever in the AI Era

The Importance of Coding Education in the Age of AI

The question surfaces repeatedly in boardrooms and classrooms alike: if artificial intelligence can now generate code from simple prompts, why should anyone spend time learning to code? The answer, according to Karlie Kloss and Osi Imeokparia of Kode With Klossy, reveals a fundamental misunderstanding of what coding education actually provides.

Their perspective, shared in a recent McKinsey interview, challenges the narrow view that coding education exists solely to produce software engineers. Instead, they argue that coding represents a foundational literacy for the modern economy, developing capabilities that extend far beyond writing instructions for computers.

The Real Value Proposition of Coding Education

Imeokparia articulates a crucial distinction that many organizations miss: "We are producing a generation of young people who are technologists and lifelong learners of technology, and that is the output of our programming, not just the creation of engineers." This reframing shifts coding from vocational training to fundamental education.

The distinction matters because it addresses the core challenge facing organizations today. As AI tools democratize the technical act of code generation, the differentiating skills become increasingly human: judgment, taste, risk assessment, and the ability to identify which problems deserve solving in the first place.

Consider the parallel to literacy. No one argues that spell-check software makes learning to write obsolete. The tool handles mechanics, but understanding language structure, constructing arguments, and communicating effectively remain human capabilities that require development. Coding education follows similar logic.

Kloss emphasizes this point through personal example. Despite having no need for coding skills in her modeling career, she chose to learn because "technology is transforming our lives and world now more than ever." Her subsequent ability to experiment with AI research tools during a delayed flight, building business models around new ideas, demonstrates exactly the kind of technological fluency that coding education provides.

Computational Thinking as Core Competency

The transferable skills that coding education develops deserve explicit recognition. As Imeokparia explains, "Learning to code is more than just writing code. You are learning computational thinking. You are learning how to take a big problem and decompose it. You are learning how to find patterns and create abstraction. You're learning how to define algorithms."

These capabilities apply across professional contexts. A marketer who understands algorithmic thinking can better design customer segmentation strategies. A doctor who grasps pattern recognition can more effectively diagnose complex conditions. A salesperson who comprehends system design can identify integration opportunities that create customer value.

Research from Carnegie Mellon's Jeannette Wing on computational thinking supports this argument. Her work demonstrates that the mental models developed through programming create frameworks for problem-solving that extend well beyond software development.

Yet organizations often fail to recognize these connections. They view coding as a specialized technical skill rather than a broadly applicable cognitive capability. This misunderstanding leads to underinvestment in technological literacy across their workforce, creating vulnerability as AI transforms business processes.

The Paradox of AI Democratization

Here's where the argument becomes particularly interesting: AI tools that make coding more accessible actually increase the importance of coding literacy rather than diminishing it. Imeokparia frames this paradox clearly: "If everybody is generating the same basic app, using the same AI tools, how do you have a breakthrough? How do you have innovation in a sea of lots of different generated apps?"

The answer lies in what she calls "spiky" capabilities, the distinctive skills that allow individuals to stand out when technical execution becomes commoditized. These include editorial judgment about what to build, taste in user experience, risk assessment in technical decisions, and strategic thinking about which problems merit solution.

But developing these capabilities requires understanding the medium you're working with. You cannot exercise sophisticated judgment about software if you don't understand how software works. You cannot identify innovative applications of technology if you lack mental models for what technology can do.

Kloss reinforces this point through her work at i-D magazine, where she asks, "How do we utilize technology to preserve and protect humanity, the creativity? How do we use technology to further unlock that?" These questions only become answerable when you understand both the capabilities and constraints of technological systems.

The AI Compass tool that Kode With Klossy is introducing into their programming exemplifies this approach. Rather than viewing AI as either threat or panacea, it helps students make judgment calls about when AI use serves their goals and when human-driven approaches work better. This kind of discernment requires foundational understanding that coding education provides.

The Persistent Diversity Challenge

The interview surfaces uncomfortable data about gender representation in technology. Only 22 to 25 percent of computer science majors in the United States are women, a figure that has remained stubbornly low despite years of attention to the issue. This matters not just for equity reasons but for business performance and innovation.

Kloss identifies the core problem: "In tech spaces, there isn't an accurate reflection of the diversity in our world, especially of women. That's a problem." When the people building technology don't reflect the diversity of technology users, the resulting products embed blind spots and biases that limit their effectiveness and reach.

Kode With Klossy's results demonstrate what's possible with intentional intervention. Among their community members of college age, approximately 70 percent pursue computer science majors or minors, compared to the 4 percent national average for women. This 17x difference suggests that the pipeline problem stems from access and environment rather than interest or capability.

Their community also reflects meaningful diversity along other dimensions, with 80 percent identifying as people of color, 40 percent qualifying for free and reduced lunch programs, and at least 25 languages spoken across member homes. These demographics prove that interest in technology exists broadly when barriers to entry are removed.

Yet Imeokparia correctly identifies that individual skill-building alone cannot solve the diversity challenge. She emphasizes the need for "both an individual change-making and a systemic change-making lens," pointing to the "broken rung" phenomenon where women fail to receive promotion to first-level management roles at the same rate as male peers.

This systemic perspective challenges organizations to examine not just their hiring practices but their retention, promotion, and culture. As Imeokparia notes, "You also need to examine the conditions for success that exist or don't exist specifically within corporate spaces."

Reimagining Career Development

The conversation surfaces a crucial insight about how career paths actually develop in modern economy. The traditional model, linear progression from formal education through predetermined career tracks, no longer reflects reality for most workers.

As the interview notes, approximately 50 percent of lifetime earnings come from experience capital rather than formal schooling. This split suggests that organizations overweight credentials and underweight demonstrated capability when making talent decisions.

Kloss embodies this alternative pathway. Despite lacking formal computer science credentials, her curiosity-driven learning has enabled her to participate meaningfully in technology spaces, launch a successful nonprofit, and acquire a media company. Her example demonstrates what becomes possible when organizations recognize capability over credentials.

This approach has particular relevance as AI reshapes work. The half-life of specific technical skills continues shrinking, making adaptability and learning orientation more valuable than static knowledge. Individuals who have developed the habit of experiential learning, particularly through hands-on technical projects, are better positioned to navigate ongoing transitions.

Yet many organizations maintain rigid educational requirements that screen out precisely the kind of continuous learners who thrive in changing environments. Imeokparia's emphasis on project-based learning speaks to this issue: "You cannot only talk about it in the abstract. Project-based learning allows you to get your hands dirty."

This learning philosophy contrasts with credentialism that values certificates over demonstrated ability. Organizations that continue prioritizing degrees over portfolios of actual work will find themselves unable to compete for talent that has developed relevant capabilities through non-traditional paths.

The Leadership Dimension

Perhaps the most challenging aspect of the discussion involves leadership behavior during technological transition. Imeokparia offers pointed advice to McKinsey and other organizations: "As a leader, when you ask your team to do something, it's always best not to ask them to do things you aren't doing."

This observation cuts to a core challenge in AI adoption. Many executives mandate AI use across their organizations while maintaining personal distance from the technology. They require their teams to transform workflows without modeling that transformation themselves.

The result creates cynicism and resistance. Employees correctly perceive that leadership lacks understanding of the challenges involved in integrating new tools into existing processes. They observe leaders making strategic decisions about technology they don't personally use.

Imeokparia advocates instead for "personal AI mastery as a leader," visible demonstration of the transformation leaders expect from their teams. This approach requires humility, the willingness to be a beginner again and learn alongside junior colleagues who may have greater facility with new tools.

Kloss reinforces this point with different language: "Embrace this moment. There can be a lot of fear in companies. The opportunity is yours to take your work to a whole other level." Her framing rejects the defensive posture that characterizes many organizational responses to AI, replacing it with opportunistic experimentation.

Both perspectives point toward a leadership stance that combines optimism about possibility with realism about challenge. As Kloss notes, "I try to be an optimist but also a realist about it. AI is happening. How do we ensure that equity is guiding its development?"

The Community Imperative

A consistent theme throughout the interview involves the importance of community in developing technical capabilities. Imeokparia, reflecting on her experience as often the only Black woman in educational and professional settings, emphasizes that "everything is better with friends."

This insight has implications beyond individual experience. Organizations that fail to create communities of practice around technical learning limit the effectiveness of their upskilling efforts. Isolated individuals struggle to maintain motivation and persist through inevitable difficulties.

Kode With Klossy's model addresses this through near-peer mentorship, with alumni returning as instructor assistants. This approach creates multiple benefits: current students see accessible role models, alumni deepen their own understanding through teaching, and the organization builds a self-reinforcing community that extends beyond formal programming.

The 11,000-person community spanning 105 countries that Kode With Klossy has built demonstrates the power of this approach. Members find not just skill development but belonging, the sense that their interest in technology connects them to something larger than themselves.

Organizations can learn from this model by creating internal communities around technical learning. Employee resource groups focused on AI adoption, coding clubs that meet regularly to work on projects, and mentorship programs pairing technical and non-technical staff all represent practical applications of the community principle.

Yet many companies treat skill development as individual responsibility, providing access to online courses but little social infrastructure to support learning. This approach misses the reality that sustained behavior change requires social reinforcement, particularly when developing challenging capabilities outside one's comfort zone.

Forward-Looking Implications

The two-year horizon that Imeokparia emphasizes for organizational change reflects appropriate urgency. She focuses specifically on working with corporate partners to address structural barriers to women's retention and advancement, particularly the broken rung phenomenon.

This pragmatic focus on concrete, measurable change contrasts with the vague commitments to diversity that characterize many organizational statements. By targeting specific policies, programs, and practices that create inequity, Kode With Klossy aims to demonstrate that systemic change is achievable within realistic timeframes.

The organization's expansion to support community members beyond their teenage years, particularly the 70 percent now 18 and older, recognizes that skill development and career support must continue past initial introduction. This lifecycle approach has implications for corporate learning and development functions.

Rather than treating technical literacy as something individuals either possess or lack, organizations need to create ongoing learning pathways that support continuous development. The person who learned to code five years ago requires different support than the person learning today, but both need structured opportunities to advance their capabilities.

Kloss's emphasis on policymaker understanding also merits attention. As she notes, "We need policymakers who understand the significance of this moment and of this technology as well." The regulatory frameworks and public investments that shape technological development depend on informed decision-making by people who understand both capabilities and constraints.

This suggests that coding literacy has civic dimensions beyond economic benefit. An electorate that understands how algorithmic systems work is better equipped to make informed decisions about their regulation. Citizens who grasp the possibilities and limitations of AI can engage more productively in debates about its governance.

Practical Recommendations

For organizations seeking to build technological literacy across their workforce, several principles emerge from this discussion:

1. Frame coding education as foundational literacy rather than vocational training. The goal is developing computational thinking and technological fluency that applies across roles, not creating a workforce of software engineers.
2. Emphasize project-based learning over abstract instruction. Imeokparia's point about getting your hands dirty reflects the reality that coding requires practice with real problems, not just conceptual understanding.
3. Create community infrastructure around technical learning. Isolated individuals struggle to maintain motivation. Groups working together on projects, sharing struggles and successes, persist through difficulties that would stop solo learners.
4. Address systemic barriers alongside individual capability building. Technical skills alone cannot overcome workplace cultures that disadvantage certain groups. Retention and advancement require examining policies and practices that create inequity.
5. Model the behavior you expect. Leaders who mandate AI adoption while maintaining personal distance from the technology undermine their own initiatives. Personal mastery by leadership creates credibility and surfaces practical challenges.
6. Recognize experience capital as equivalent to formal credentials. Individuals who have developed capabilities through non-traditional paths often bring valuable perspectives. Rigid educational requirements screen out precisely the continuous learners who thrive in changing environments.
7. Personalize learning journeys to real problems individuals face. Imeokparia's example of using AI to organize school emails illustrates how learning sticks when it solves actual challenges rather than abstract exercises.
8. Develop judgment frameworks for technology use. The AI Compass approach, helping students decide when AI serves their goals and when human approaches work better, represents the kind of critical thinking that coding education should develop.

Conclusion

The question of whether learning to code matters in the AI era rests on a fundamental misunderstanding. Coding education never existed primarily to teach syntax or memorize functions. It develops ways of thinking about problems that apply far beyond software development.

As AI tools handle more of the mechanical work of code generation, the human capabilities that coding education develops become more valuable, not less. Computational thinking, pattern recognition, system design, and problem decomposition represent cognitive tools that apply across professional contexts.

The diversity imperative adds urgency to this issue. Technology built by homogeneous groups inevitably reflects the blind spots and biases of its creators. Broadening participation in technological development requires both individual skill-building and systemic change to workplace practices.

Leaders face a choice in this moment. They can view AI as threatening existing approaches and respond defensively, or they can see opportunity to develop new capabilities across their organizations. The difference lies partly in their own willingness to engage directly with new tools rather than delegating technical learning to others.

Kloss and Imeokparia's work with Kode With Klossy demonstrates what becomes possible when organizations commit seriously to broadening access to technical education. Their results, particularly the 70 percent of community members pursuing computer science degrees compared to 4 percent nationally, prove that pipeline problems stem from barriers rather than interest.

The coding literacy they advocate extends beyond professional benefit to civic participation. Citizens who understand how technological systems work are better equipped to make informed decisions about their governance. In this sense, coding education represents not just economic development but democratic infrastructure.

Organizations that recognize this broader value proposition will invest in technological literacy across their workforce, not just within technical functions. They will create the community infrastructure and systemic support that enables diverse individuals to develop and apply these capabilities. And they will measure success not just by the number of engineers produced but by the breadth of technological fluency across their entire organization.

The future belongs not to those who can write the most elegant code, but to those who can think computationally about complex problems, exercise sound judgment about which technological solutions serve human needs, and create conditions for diverse perspectives to shape technological development. Coding education, properly understood, develops exactly these capabilities.