What I'd Do Differently If I Started KiloNorth Again

KiloNorth is live. I tested it on multiple devices and it is working fine. I also shipped a small enhancement after launch — added logging to track what is happening inside the app. That update made me think. If I started this project again, logging is the first thing I would set up. Not the last.

Try it: kilonorth.netlify.app

Read the previous Post: Building KiloNorth - A Product Manager’s Hacks for Shipping Code with AI Interns

What Happened

When I was building, my focus was on getting things to work. Features, UI, testing, and shipping. Logging felt like something I could add later once the app was running.

After launch I had no way to see what was actually happening. The app was running. People were opening it. But I did not know where things were working well or where they were quietly breaking.

Adding logging after launch took more time than it would have taken from the beginning. The code was already written in a way that did not account for it.

Why I Think It Matters

Logging is not just a technical thing to check off. It is how you understand what your app is actually doing.

Without it you are making decisions based on what you think is happening. With it you can see what is real — what people are using, what is failing, where they are stopping.

That Is Really It

No big lesson here. Just one small thing I would do earlier next time.

Build in visibility from the start. It is cheaper than adding it after.

Even with four users, I would rather have that information from day one than go back and add it later.