I turn unclear needs into buildable parts
I would rather ask one more question early than keep building on an assumption that gets expensive later.
My name is Alexander Ahman and I build digital systems from Västervik. My strength is understanding what needs to work, making the technical direction clear, and getting a runnable version into shape.
I would rather ask one more question early than keep building on an assumption that gets expensive later.
I like understanding the full chain: what the user does, which rules apply, how data is stored, and how the system is operated.
It should be small enough to finish, but serious enough to show whether the direction holds.
Names, structure, error handling, and small technical decisions matter when the next person needs to understand the system.
Start with the projects. They show how I think about booking logic, data flows, and public web experiences.