EverydayCS
Real problems. CS solutions. Documented.
Why This Website Exists
I got tired of building projects just because they looked good on a resume.
Another to do app. Another clone. Another project built from a tutorial.
So I decided to change the way I build.
Now, I try to notice problems in my own life first. Small frustrations. Repetitive tasks. Things that feel unnecessarily difficult. Then I ask myself a simple question:
"Can I solve this with Computer Science?"
Sometimes the answer becomes a tiny Windows utility. Sometimes it turns into a full stack application with a backend, cloud infrastructure, and weeks of debugging.
That is how projects like CapsLight and Reelit started.
This website is my public archive of that process.
Not just the final product, but the actual journey behind it: what I noticed, what I tried, what failed, how I designed the solution, what I learned, and what I would improve next.
I am still learning. Some solutions will be imperfect. Some ideas may fail completely.
But every project here starts with one rule:
What I'm Trying to Become
I don't want to be someone who only knows frameworks, syntax, or how to follow tutorials.
I want to become an engineer who can look at a messy real world problem, break it into smaller pieces, make technical decisions, and build something genuinely useful.