I’m an engineering student.
I build apps.
I run something called PixelSphere — an ecosystem of products connected by a single idea.
But the reality of managing all of this at the same time?
It’s messy. Unstructured. And honestly, exhausting in ways I didn’t expect.
The Two Worlds I’m Living In
On one side, there’s college.
Lectures, assignments, internal submissions, exams — a system that is already demanding on its own. It expects consistency, focus, and time.
On the other side, there’s everything I’m building.
PixelSphere isn’t just one project. It’s a collection of apps — each with its own purpose, users, and problems to solve. Apps like Echo Music, Net Bar, and others I’ve worked on are not just ideas anymore. They exist. People use them. They need to be maintained.
And that changes everything.
Because now it’s not about “building when I feel like it.”
It’s about responsibility.
PixelSphere: More Than Just Apps
When I started PixelSphere, the idea was clear — don’t build random apps. Build something connected. Something consistent. Something that people can trust over time.
That idea still stands.
But what I didn’t fully understand back then was what it actually takes to sustain something like this.
Each app brings its own set of challenges:
Bugs that show up unexpectedly
Features that feel incomplete
Performance issues that need attention
Updates that users expect
And when you have multiple apps under one ecosystem, these challenges don’t come one at a time.
They come together.
The Problem Isn’t Work — It’s Structure
If I had to explain the real issue, it’s not that there’s too much to do.
It’s that nothing feels organized.
Some tasks are written down.
Some are in my head.
Some are half-started and forgotten.
I start my day with a plan, but it rarely stays that way.
A small bug turns into hours of debugging.
A quick update turns into rethinking an entire feature.
One idea leads to three more.
And suddenly, the day is gone.
Not wasted — but not structured either.
Constant Context Switching
This is where things start getting mentally exhausting.
A typical cycle looks like this:
I sit down to study →
I remember an issue in one of my apps →
I open my laptop “just for a few minutes” →
I get pulled into debugging →
Time passes →
Now I’m stressed about not studying
Then the reverse happens.
I try to focus on academics →
But my mind keeps going back to PixelSphere →
“What if something breaks?”
“Did I forget to fix that issue?”
So even when I’m working, I’m not fully present.
I’m always split between two priorities.
Nothing Ever Feels Complete
In college, there’s a clear definition of “done.”
You finish an assignment. You submit it. It’s over.
But with apps, there is no “done.”
Echo Music can always be improved.
Net Bar can always be optimized.
PixelSphere itself can always be expanded.
There’s always:
Another feature to add
Another bug to fix
Another improvement to make
So even after hours of work, it never feels finished.
And that creates a constant sense of incompletion.
The Pressure of Building Something Real
The moment people start using what you build, everything changes.
Now:
Bugs matter more
Delays feel heavier
Decisions feel more permanent
PixelSphere is no longer just a personal project.
It represents my work, my thinking, and my standards.
That creates pressure — not from others, but from myself.
I want it to be good.
I want it to grow.
I want it to actually mean something.
But maintaining that while managing studies?
That’s where things start clashing.
The Trade-off That Never Goes Away
There’s no perfect balance here.
If I spend time building:
My academics take a hit.
If I focus on studies:
My apps slow down.
And no matter what I choose, something feels neglected.
That’s the frustrating part.
Not because I don’t want to do both.
But because doing both properly feels almost impossible with the time and energy I have.
Mental Fatigue Is the Real Problem
This isn’t just about being busy.
It’s about constantly switching between:
Problem-solving (coding)
Learning (studies)
Planning (PixelSphere vision)
Debugging (unexpected issues)
That kind of switching drains you.
Even when I’m not actively working, my mind is still occupied.
Thinking about:
Features
Bugs
Missed tasks
Things I should be doing
It never fully stops.
Everything Feels Slightly Disorganized
If I’m being completely honest, the most accurate way to describe things right now is:
Nothing is fully in place.
Work is happening.
Progress is happening.
But structure is missing.
Days feel reactive instead of planned.
Tasks feel scattered instead of organized.
Focus keeps breaking.
And that creates a constant low-level annoyance.
But There’s Still a Reason I’m Doing This
Despite everything — the chaos, the lack of structure, the constant pressure — I’m still building.
Because PixelSphere matters to me.
Not just as a project, but as something I want to grow into something meaningful.
Even if right now it feels messy.
Even if I don’t have everything figured out.
Final Thought
This phase isn’t clean.
It’s not optimized.
It’s not balanced.
It’s not fully under control.
It’s just real.
Trying to manage studies while building something bigger than yourself doesn’t come with a perfect system.
It comes with confusion, trade-offs, and a lot of unfinished things.
And maybe that’s okay.
Because right now, the goal isn’t perfection.
It’s just to keep going — even when everything feels a bit messed up.