Explaining Your Thoughts = Pitching an Idea

Lukas Jääger - 22.03.2026

411 words

One Instagram reel explained how you shouldn't look at problems as either easy or hard, but more like familiar or unfamiliar. I really like that idea and the aspect of perspective, which then led me to this thought.

Before that, though, I'd say this works best in programming, but can also be used in other fields or subjects as well — although in most cases it might just overcomplicate things.

When using AI for coding, sometimes the output can be very confusing or difficult to follow (at least for me, especially when the output is very large). If I ask a clarifying question about a function or a part of the code, the answer is usually something like: "this x function returns y, which is used to do z." Okay, well that's what the function does, but it can still remain confusing, which leads me to think about: "Is this the most effective way?", "What are the alternatives?", "Is this optional, or can it be integrated with some other function?" etc...

The solution to this is explaining the answer like a pitch.

Instead of just answering plainly what the function does, it could explain why this is the best way of doing it, what benefits it has, and what problem it solves. I think this is much more interactive and gives a much better understanding of the code.

When writing code yourself, you of course know better what each part does and what its purpose is, but when AIs create thousands of lines of code with many different helper functions, I think this is where it helps the most. It is a more niche way of viewing a solution, but in the real world I think it could be used in longer STEM problems as well. For example, a physics problem might use five different equations to get to the result. A student asks what the purpose of one of the equations is, and then the teacher, instead of just saying "this gives us the mass," explains why this mass is necessary in the first place, why other equations might not work, and how it ties together with the overall problem.

I don't know how good these examples were, but the point I'm trying to make is about perspective. Simple, plain answers might not give the results we want, and in these cases using 'pitching' as a way of explaining can be a lot more effective and insightful.

Other thoughts