Code: what is it, how it's evolved, and why it matters for all businesses
What Is Code? — You are an educated, successful person capable of abstract thought. A VP doing an SVP's job. Your office, appointed with decent furniture and a healthy amount of natural light filtered through vertical blinds …
Context & Ripple Effects
Bloomberg's 'What Is Code?' was written for exactly the reader it describes — a VP doing an SVP's job in a company where software decisions were already being made by people who couldn't make them. At the time, coding literacy for executives meant reading explainers; the adjacent coverage showed tech companies turning coding ability itself into a recruiting filter through competitions.
The decade that followed answered the piece's implicit question by removing the need to answer it: low-code database services like Airtable let non-programmers build real systems, then Codegen raised $16M to automate codebase-wide migrations and Codeium raised $65M at a $500M valuation to write code alongside engineers — culminating in a journalist shipping production code at Notion as a vibe coding engineer.
First-order effects
- Businesses whose managers read the piece get a shared vocabulary for software decisions they were already making badly — the explainer's premise is that code has become a general management competency, not an engineering specialty.
- Tech recruiters formalize what the piece implies: coding competitions become standard hiring venues, making demonstrated code ability a screening signal rather than a résumé claim.
Second-order effects
- Vendors respond to the non-programmer audience the piece addressed: Airtable-style low-code tools absorb the demand from people who took the lesson literally, while Codegen and Codeium raise venture money to serve the next tier — automating the refactoring and migration work that used to require the engineers being explained to.
- As more non-specialists write code, the questions surface earlier: the programmer community's debate over unethical coding requests becomes a governance problem for every business now writing software without engineers.
Third-order effects
- If the pattern holds, the line between 'person who understands code' and 'person who ships code' collapses — the VP doing an SVP's job becomes someone who can produce working software directly, restructuring how companies staff and organize technical work.
- Software literacy stops being a hiring filter and becomes infrastructure: the durable question shifts from 'what is code?' to who controls the AI tools that generate it.
The trend: Coding is moving from a specialist profession explained to outsiders toward an AI-mediated capability any manager can exercise.