What 18,000 Lines Taught Me About Surviving

I walked into my internship the way I walk into most things. Quietly, uncertain and already doubting whether I was supposed to be there.

Two semesters of showing up but not quite arriving. Still attending, still submitting, still doing what needed to be done. But, something in me had slowed down. An extended timeline. A CGPA that didn't look like the people I was being compared to. And now suddenly, a government office, seniors who had been doing this for years, and a brief that said: build an inventory system.

Simple enough on paper. Terrifying in practice.

The First Thing I Did Wasn't Code

It was watch.

I sat with that for a while. The watching. Not because I didn't know where to start, but because I'd learned something about myself by then: I understand people before I understand systems. And a system that doesn't understand people is just a complicated way to fail them.

So I watched my seniors. How they moved through the office. Where they slowed down. What made them sigh. What they had to do three times when once should have been enough. That's where the system came from. Not from a textbook. Not from a lecturer. From watching people work and asking myself — what if this didn't have to be so hard for them?

The Tools You Actually Have

I chose native PHP. Not because it was the right choice on paper, because it was what I knew. I'd heard of Laravel briefly from a senior, filed it away as something I'd figure out eventually. But eventually wasn't now. So I used what I had, and learned what I needed as I needed it. JavaScript came during the build, not before it. The port forwarding, the security layers, the file management. None of that was in any class I attended. I just kept hitting walls and figuring out what was on the other side.

“The best code doesn't just work — it understands.”

The Part Nobody Asked For

Somewhere in the build, I added WCAG compliance elements. Nobody asked for it. It wasn't in the brief. My supervisor didn't mention it. It wasn't a graded requirement.

I did it because I'm disabled. And because I know what it feels like to use something that wasn't built with you in mind.

Every designer, every programmer... they should be thinking about this. Not as an extra feature. Not as a checkbox. As the baseline. Because adaptive doesn't mean special accommodation. It means the system actually works for the people using it, all of them, not just the ones who look like the person who built it.

I also built a Telegram bot. Automated notifications, monthly restock reminders sent directly to the right people. That wasn't in the brief either. It came from the same place everything else did, watching someone do something three times when once should have been enough, and thinking: what if the system just told them?

What Surviving Looks Like

My supervisor congratulated me. Not because it was built with the most modern stack. Not because it was Laravel or Next.js or anything that would impress someone at a tech conference. Just PHP, CSS, and JavaScript — the basics, scaled up further than most people think the basics can go.

That meant more than any grade.

Because I know what it cost. The semesters that didn't go the way I planned. The mornings I showed up when showing up was the hardest thing. The quiet decision, made alone, to just keep building — even without a guarantee that I'd finish, or that it would matter, or that anyone would notice.