A civil engineering student's journey into software, AI-assisted development, and why I believe trust matters more than features.
There was one evening that made me stop and think.
I wasn't doing anything complicated. I just wanted to finish a few small tasks before going to bed.
Compress an image.
Generate a QR code.
Create a strong password.
Convert a PDF.
None of those tasks should have taken more than a few minutes.
Instead, I found myself opening one website after another. Some were full of advertisements. Others wanted me to create an account for something that should have taken less than a minute. A few asked me to upload files without clearly explaining what would happen to them afterward.
Some websites were excellent.
Some weren't.
But after jumping between multiple tabs just to finish a handful of simple tasks, I caught myself asking a question that had never crossed my mind before.
Why does something so simple still feel so complicated?
That question stayed with me long after I closed my browser.
From Civil Engineering to Building Software
I'm not a software engineer.
I'm a civil engineering student.
If someone had told me a year ago that I'd spend my evenings thinking about browser tools, user experience, and software design, I probably wouldn't have believed them.
Like many people, I simply used whichever website appeared first in a search result.
Sometimes I had a great experience.
Sometimes I didn't.
Over time I realized something surprising.
It wasn't the lack of online tools that frustrated me.
There are already thousands of them.
What frustrated me was never having one place that consistently respected my time, my privacy, and my attention.
Eventually, I stopped searching for the perfect utility website.
Instead, I started asking:
What would my ideal utility website look like if I built it myself?
That simple question eventually became UtilityKit.
UtilityKit Isn't Trying to Reinvent Online Tools
Image compressors already exist.
QR generators already exist.
Password generators already exist.
File converters already exist.
I'm not pretending to invent something new.
Instead, I'm trying to improve something much smaller.
The overall experience.
The small moments where a website either earns your trust—or slowly loses it.
The moments where you hesitate before uploading a file.
The moments where you wonder whether creating another account is really necessary.
The moments where you just want to finish a task and move on with your day.
Those moments matter more than people think.
Learning Without a Programming Background
One thing I've learned is that software isn't just about writing code.
It's about making decisions.
Should this tool require an account?
Does it actually need one?
Can this task happen directly in the browser instead of sending files to a server?
Does adding another feature genuinely improve the experience, or does it simply make the product more complicated?
Every product is a collection of small decisions.
Over time, those decisions become your reputation.
That realization changed how I think about software.
Where AI Fits Into This Journey
I don't come from a traditional software background.
I'm learning by building.
AI has become my development partner.
It helps me explore ideas, generate code, solve problems, and learn faster than I could alone.
But one lesson became obvious very quickly.
AI can generate code.
It cannot decide what deserves to exist.
It cannot define values.
It cannot understand users unless someone first understands their problems.
The more I build, the more I realize that good software starts long before writing code.
It starts with asking better questions.
The Principles I Want UtilityKit to Follow
Before adding dozens of new tools, I wrote down a few principles I don't want to compromise on.
Respect people's time.
Simple tasks should stay simple.
Respect people's privacy whenever practical.
People shouldn't have to wonder where their files or information go.
Avoid unnecessary friction.
If something doesn't genuinely require an account, don't ask for one.
Be honest.
Don't promise features that don't exist.
Don't exaggerate what the product can do.
Earn trust gradually.
Trust isn't built through slogans.
It's built through hundreds of small decisions users rarely notice—but always feel.
For me, these principles matter more than having the biggest collection of online tools.
The Current Reality
The website that's online today is an early public demo.
It isn't perfect.
Some tools will be redesigned.
Some will disappear completely.
A much more advanced version is already under development.
I considered waiting until everything felt perfect before sharing it.
Then I realized something.
Software rarely becomes better in isolation.
It becomes better when real people use it, question it, and point out things you've stopped noticing yourself.
That's why I decided to publish the demo.
If You're Curious
If you'd rather judge the product than the story, here's the current public demo:
🔗 https://utilitykits.netlify.app/
Everything currently works completely in the browser wherever practical, and I'm continuing to improve the experience based on real feedback.
It's intentionally simple.
I'm far more interested in honest feedback than compliments because the next version is already being rebuilt from the ground up.
I'd Love Your Perspective
I'm not looking for people to tell me everything looks great.
I'm looking for people who are willing to point out what doesn't.
If you have a few minutes to explore it, I'd genuinely appreciate your thoughts on questions like these:
Was the purpose of the website immediately clear, or did anything feel confusing?
Was there anything that made you hesitate or reduced your trust in the website?
Which tool did you try, and how was your experience?
If you could improve just one thing before the next version, what would it be?
Would you bookmark or return to this website? Why or why not?
You're also welcome to share your broader thoughts:
What makes you trust an online utility website?
What's one thing that immediately makes you leave one?
If you could redesign one everyday online tool from scratch, what would you change?
I'm not looking for compliments.
I'm looking for honest criticism.
I'd rather hear what's confusing or disappointing today than spend months building the wrong thing.
Whether UtilityKits remains a small personal project or grows into something much bigger, I hope it always stays true to the reason it started.
Not to create another collection of online tools.
But to make everyday digital tasks a little simpler, a little more respectful, and a little more trustworthy.
Because I believe good software isn't remembered because it has more features.
It's remembered because, over time, people stop thinking about the website itself and simply trust it to get the job done.
Thanks for reading. If you leave feedback—positive or critical—I promise I'll read every comment. Those conversations will directly influence the next version of UtilityKits.
Top comments (0)