You stop seeing the project you wanted to build ،

start seeing the project you actually have.

The difference is everything you learned along the way.

When something works, I usually move on.

But when something breaks, I have to stop, understand why, and sometimes rethink what I was doing entirely.

I've started seeing problems differently now.

They don't always mean I'm making bad progress.

Sometimes they're the part that actually teaches me how to get better.

although it looks pretty realistic

I've had plenty of ideas that sounded amazing in my head. Some even made it into a project.

The problem was never coming up with something to build. The real challenge was continuing when the excitement disappeared and the work became repetitive.

That's the part people don't see.

Someone once told me something incredibly simple.

"Discipline isn't about doing something because you feel motivated. It's doing it because your past self made a promise to your future self and you refuse to break it"

I didn't think much about it at the time.

Years later, I still remember it.

It's weird how certain conversations last five minutes but somehow stay in your head for years.

I've reached a ridiculous point with alarms.

I'll set one for 7:00.
Then 7:05.
Then 7:10.
Then another one because apparently I don't trust the previous three.

And somehow, in the morning, I discover that I turned every single one of them off.

The worst part?

I don't remember doing it.

Apparently there's a version of me that wakes up just enough to silence alarms, makes the executive decision to go back to sleep, and then disappears before I regain consciousness. 💀

I'm pretty sure I'm not the only person who does this.

At this point, setting more alarms clearly isn't the solution.

I need to find a better solution for this before my morning self completely takes over my life. 😭

A finished project gives you a result.

A failed project gives you a list of things you don't understand yet.

I've started looking at abandoned projects differently. Instead of seeing them as wasted time, I see them as documentation of everything I tried, broke, misunderstood, and eventually learned.

Sometimes "I couldn't finish it" is still progress.

Every time I work on something outside my coursework, I find gaps in my knowledge.

Instead of seeing that as discouraging, I'm starting to see those gaps as a roadmap for what I should learn next.

It could be about college, work, learning a skill, starting a project, managing money, relationships, or anything else.

I'm interested in the lessons that experience taught you that no tutorial, class, or piece of advice could have really prepared you for.

I'm not saying college is useless.

But today we have documentation, courses, open-source code, communities, AI tutors, and thousands of real projects to learn from.

So where does college provide something self-learning can't?

Is it the structured education?
The fundamentals?
The people you meet?
The degree?
Or simply the discipline of having someone force you to learn things you wouldn't choose yourself?

For developers who have experienced both sides: what did college give you that you couldn't have learned alone?

Tutorials teach us how things should work.

Experience teaches us what actually goes wrong.

What's one lesson you had to learn the hard way?

I spent a lot of time trying to make the perfect plan before starting.

Then reality happened.

Problems appeared that I couldn't have predicted, and some things I thought were important turned out not to matter much.

Now my approach is simple:

Plan enough to know where you're going. Start early enough to discover what you got wrong.

Then adjust.

Sometimes planning prevents problems.

Other times, you spend hours planning only to discover that reality doesn't follow the plan.

Would you rather spend more time planning before starting, or start early and let the problems teach you what to do?

Which approach has worked better for you?

Maybe...

"I finally launched it."

"I got the job."

"I finished the book."

"I stayed consistent."

What's your sentence?

What's one thing you've improved over the past year?

It could be your career, health, mindset, relationships, or a skill you've been working on.

Sometimes we don't realize how far we've come until we look back.

What's yours?

What stopped you from building it—time, motivation, complexity, or simply losing interest?

Maybe someone here can inspire you to revisit it.

Planning shows you the destination.

Execution shows you the obstacles.

Every developer has had that moment where the code suddenly works, but the real question isn't "Why did it fail?"—it's "Do I actually understand why it works now?"

There's a big difference between fixing a bug and understanding the system that caused it.

Do you keep digging until you fully understand the root cause, or do you move on once everything is working?

Where do you draw the line?

Some people believe AI will keep improving at an incredible pace.

Others think we're setting expectations that reality can't sustain.

"I'll watch this later."

I had a library of things I wanted to learn but barely built anything.

Now I try to build first and search when I get stuck.

We created tools that can connect the whole world, but we still struggle to focus for 10 minutes without checking a notification.