4
When Great Projects Die Underground
“AI won’t replace you, but someone using AI will.”
We hear this statement a lot, especially in tech. But lately, I’ve been looking at it from a slightly different perspective.
The conversation around AI often focuses on whether developers will be replaced, but there is another issue we don’t talk about enough: visibility.
There are people building useful products, solving real problems and experimenting with technology every day. Yet, somehow, many of these projects never get the attention they deserve.
I’ve seen situations where students build solutions to problems around them, only for very few people to know that those solutions even exist. Some are free, some are paid, and some are simply projects created to practice and apply what they’ve learned.
Meanwhile, another person who knows nothing about coding come along with a similar idea, package it differently, market it better, build trust around it, and suddenly reach a much larger audience.
And that got me thinking.
Is building actually enough?
For many Computer Science students, building projects is part of the learning process. We learn a programming language, identify something we want to solve, build a project around it, run into problems, debug, research, and sometimes use AI to help us understand or improve what we’ve built.
AI doesn’t necessarily remove the learning process. In many cases, it becomes another tool within it.
But building something and getting people to use it are two completely different challenges.
You can have a technically good product and still have almost no users.
You can build something free and useful and still have people paying for another product that solves a similar problem.
You can spend weeks learning, designing, coding and debugging, only for your project to remain known by the small circle of people who were around when you built it.
And honestly, that part hurts.
Maybe the problem isn't always the quality of what we build.
Maybe we also need to learn how to communicate what we build.
How do we make people aware of it?
How do we build trust around it?
How do we explain its value to someone who isn't a developer?
How do we turn a project from “something I built” into “something people actually want to use”?
These are questions I’m still thinking about.
Because perhaps the next challenge for many developers isn't just learning how to build.
It is learning how to make what they build visible.
Add a comment
0/2000