← back to articles

Your High School Thinks Solving Problems Means Writing About Them

By Arjun

I just spent three weeks writing a research paper on climate feedback loops for AP Environmental Science. Claim, Evidence, Reasoning. Proper citations. The whole performance. I can tell you about Hadley cells, the Coriolis effect, and how El Niño disrupts global weather patterns. I followed the rubric perfectly.

I also spent those same three weeks building AI agent infrastructure that generates actual revenue from actual customers.

One of these activities is considered "rigorous academic work" that proves I'm college-ready. The other is considered a "side project" that "might make a good essay topic." And that inversion—that complete reversal of what matters—tells you everything you need to know about what high school is actually teaching you.

High school hasn't just failed to prepare students for the real world. It's done something worse: it's trained an entire generation to confuse documentation with creation, analysis with action, and performance with impact.

The Religion of Documentation

Here's what I've noticed after watching how problems get "solved" in educational institutions: there's always a paper. Always a presentation. Always a rubric. The environmental club doesn't reduce plastic usage—they create a slideshow about plastic usage. Student government doesn't secure mental health resources—they draft a proposal about mental health resources. The community service project doesn't house homeless people—it produces a reflection essay about the experience of witnessing homelessness.

This isn't an accident. This is the system working exactly as designed. Because here's the uncomfortable truth that nobody wants to say out loud: schools don't actually want you to solve problems. They want you to prove you're the kind of person who cares about problems. There's a massive difference, and it's the difference between building something that works and writing something that sounds good.

Think about what skills you're actually developing when you spend three weeks researching and writing about atmospheric carbon absorption. You're learning how to synthesize existing information, format citations properly, and construct arguments that sound credible to authority figures. These aren't useless skills—they're just not the skills that create new value in the world. Meanwhile, the person who spent those three weeks trying to build a carbon capture prototype learned how to work with incomplete information, handle technical failures, and iterate based on what actually works versus what the theory says should work.

The school system can measure your research paper. It has a rubric for that. It cannot measure whether your carbon capture prototype works better than existing solutions. There's no rubric for "made something that didn't exist before." So the system optimizes for what it can measure, and accidentally teaches you that measurable documentation is more valuable than unmeasurable creation.

Why Smart People Fall For It

The insidious part is that high school's approach feels rigorous. It feels intellectual. Spending three weeks researching climate feedback loops feels more serious than spending three weeks hacking together a prototype. One involves peer-reviewed sources and proper methodology. The other involves duct tape and broken code.

But here's what I've learned from actually building something people pay for: the duct tape and broken code is where you learn what's actually true. Research papers teach you what other people discovered. Building teaches you how to discover things yourself. Reading about how databases scale teaches you database theory. Watching your database crash at 3 AM because you didn't understand connection pooling teaches you databases.

The documentation approach appeals to smart students because it lets you be smart in a safe way. You can analyze problems without risking failure. You can demonstrate knowledge without creating anything that might not work. You can get validation from teachers without ever putting yourself in front of real users who might tell you your solution is worthless. High school has created an entire ecosystem where you can spend four years being impressively intellectual without ever being useful.

And the tragedy is that the students who are best at this game—the ones who write the most impressive papers, ace the hardest AP classes, lead the most clubs—are often the ones most thoroughly trained to avoid real building. They've learned that proper analysis is the highest form of problem-solving. They've learned that getting an A means you did it right. They've learned that if you follow the rubric, you'll succeed.

Then they graduate and discover that reality doesn't have rubrics. Nobody's giving you an A for citing your sources correctly when your product doesn't work. The market doesn't care how well you analyzed the problem if you didn't ship a solution.

The Teacher Problem Nobody Mentions

Let me say something that sounds cruel but is just observationally true: your teachers cannot teach you how to create value outside of institutions because they have never done it themselves. This isn't an insult—it's a fact about selection effects.

Teaching attracts people who value stability, structure, and institutional validation. These are good qualities for maintaining social order. They are terrible qualities for building new things. Your AP Environmental Science teacher chose a career where they show up at 8 AM, follow a curriculum they didn't design, get paid whether students learn or not, and never have to face a market test of whether their work creates value. That's not a moral failing—it's just a completely different operating system than the one that creates startups, builds products, or solves novel problems.

When I mentioned my startup to a teacher, the immediate response was: "That's impressive, but make sure it doesn't interfere with your coursework." Not "what problem are you solving?" Not "what have you learned?" Not "how can I help?" But "don't let the real work interfere with the fake work." Because from their frame, the coursework *is* the real work. The startup is the distraction. They genuinely cannot conceive of a world where building something people pay for is more educational than completing assignments about building things.

This creates a toxic equilibrium where the people teaching you about problem-solving have systematically selected themselves out of ever having to solve real problems. And they're not even aware of the blind spot, because everyone around them has the same blind spot. It's not malicious—it's just what happens when institutions become self-referential.

What This Actually Costs

I'm living in two worlds simultaneously, and the cognitive dissonance is making me insane. In one world, I'm writing research papers about climate patterns for AP Environmental Science. I'm following the CER framework, citing peer-reviewed sources, and getting graded on whether my argument structure matches the rubric. In the other world, I'm debugging memory systems at 2 AM, talking to customers who are mad that a feature broke, and making real-time decisions about technical architecture that will affect whether my company survives.

The school world teaches learned helplessness disguised as rigor. Every assignment comes with explicit instructions. Every project has a rubric. Every question has a "correct" answer that the teacher already knows. You're being trained to identify what authority figures want and give it to them. This works great if your goal is to become a management consultant or a corporate lawyer—jobs that are fundamentally about figuring out what powerful people want and delivering it convincingly.

It works terribly if your goal is to build something new. Because building something new means operating in a space where nobody knows the right answer yet. There is no rubric for "create a memory system that makes AI agents feel coherent across conversations." There is no teacher who can tell you if you're doing it right. There's just: does it work? Do people pay for it? Does it break?

The documentation mindset makes you risk-averse at exactly the age when you should be learning risk tolerance. Every hour you spend optimizing for GPA is an hour you're training yourself to value safe, measurable performance over unsafe, unmeasurable creation. And by the time you're 25, that training is hard to undo. You've spent a decade learning that following instructions leads to success, and now someone's asking you to succeed in a domain with no instructions.

The Inconvenient Data Point

Here's a fact that high schools would prefer you not think about too carefully: the people who build world-changing companies are systematically not the people who excelled at the high school game. Zuckerberg dropped out. Gates dropped out. Jobs dropped out. Musk barely stayed in. Thiel created the Stanford Review specifically to fight the institutional consensus.

The standard response is: "Yes, but those are outliers. You're probably not going to be Mark Zuckerberg." Which is true but irrelevant. The question isn't whether you'll be Zuckerberg. The question is: what traits lead to outsized impact, and does high school select for or against those traits?

High school selects for: risk aversion, authority compliance, template-following, optimization for external validation. World-changing impact requires: risk tolerance, authority questioning, template-breaking, internal conviction. These aren't just different—they're opposing selection pressures. The system isn't neutral about who succeeds. It's actively filtering for people who will be good at operating within existing systems, and filtering against people who will build new ones.

I'm not saying everyone should drop out. I'm saying the system is not secretly trying to help you become a founder while pretending to prepare you for college. It's actually trying to prepare you for college while pretending that's the same as preparing you for impact. And most students never notice the bait-and-switch because by the time they figure it out, they've already been trained.

What I'm Actually Saying

I'm not writing this to convince you to drop out or stop trying in school. I'm writing this because I think most ambitious students are getting scammed and don't realize it. They think they're "preparing for the future" when they're actually training themselves to be really good at performing for institutions.

The brutal truth is that high school teaches you the skills to succeed in college, which teaches you the skills to succeed in corporate jobs or academic careers, which are fine paths but are not the paths that create new things. If you want to build something that matters, you need different skills, different instincts, and different mental models. And you're not going to get them by being a straight-A student who leads three clubs and writes perfect research papers.

You get them by shipping broken things and fixing them in public. By having users yell at you because your product doesn't work. By staying up until 3 AM not to finish a paper but because you're genuinely trying to solve a problem and you think you're close. By putting something in front of real people who could pay you real money and discovering that what you built isn't good enough yet.

That's not on the curriculum. That's not worth GPA points. And that's exactly why it matters.

The question isn't whether you should care about school. The question is whether you're going to let school convince you that documented analysis is the highest form of problem-solving, or whether you're going to realize that building is fundamentally different from analyzing and you need to learn both.

Most students pick one or the other. The ones who figure out how to do both—to play the school game enough to keep options open while building real things outside the system—those are the ones who end up actually mattering.

High school wants you to think the game is the real thing.

It's not.

And every year you believe that costs you.

— Arjun