Why I Started Building in Public

For years, I worked as an engineer building internal tools, dashboards and web applications. I enjoyed the work, but something always felt incomplete. Almost everything I built stayed invisible. Private repos, private systems, private improvements. When a project ended, all of it simply disappeared.

I’ve also spent years building large-scale enterprise systems in the .NET ecosystem. That background shaped how I think about architecture, reliability and real engineering. But over time, I realized something: the speed, flexibility and reach of the modern JavaScript ecosystem opens doors that traditional backend stacks don’t.

React, Next.js and Node.js allow me to build complete products end-to-end. One person. One laptop. Global reach. This transition isn’t about abandoning .NET. It’s about expanding my toolkit and building products that can reach anyone, anywhere, instantly.

I was learning and improving, yet there was no visible trail of my work or my progress. I wanted to change that. I wanted my work to live somewhere outside closed environments. I wanted to show what I can build.

In 2025, I decided to take a different path. I decided to build modern products in public. Not because it is a trend, and not because I want attention. I am doing it because sharing the journey helps you learn faster, build better and stay accountable.

Building in public gives you things that are almost impossible to gain when you build alone. You receive early feedback. You stay consistent. You create new opportunities. You connect with other developers. And you document your progress in a way that benefits both you and others.

I am not trying to teach anything here. I am simply sharing what I build, what I learn and how I think along the way.

---

What I Am Building

I am focusing on useful and simple web products.
Clean interfaces.
Developer tools that improve workflow.
Automation systems.
Dashboards.
Small experiments and product ideas.

My main stack is straightforward. React, Next.js, Node.js and PostgreSQL.
Just solid tools for building real products.

---

What You Will See Here

I will share progress updates, product ideas and the challenges I face while building.
Sometimes small demos, sometimes lessons learned.
Sometimes mistakes and how I fix them.
Sometimes the thought process behind a feature or a new idea.

If you enjoy real progress, practical building and learning through action, you will probably feel at home here.

---

Why Do It Publicly

Building privately keeps you comfortable.
Building publicly pushes you to grow.

When others can see what you are working on, you naturally gain momentum. You think more clearly. You make decisions faster. You become more consistent. Most importantly, people understand your skills through real work, not through descriptions or titles.

I no longer want to be the invisible engineer whose best work lives only in internal systems. I want to create things that stay. Things that can be improved. Things that others can benefit from or learn from.

This is my way of stepping out of that invisible space.

---

Let’s See Where This Goes

I am not aiming for perfection. I am aiming for progress.

Maybe I will fail. Maybe I will build something useful. Maybe I will launch several products. Maybe this journey will lead to something unexpected.

No matter what happens, I will learn and share everything I can.

I am active here and on X.

https://x.com/alicanbuild
https://github.com/alicanbuild

Let’s build something meaningful, step by step.

I share daily progress on X and ship all projects on GitHub.