Nahom Dereje

I’m basically someone who likes to build things and understand them properly, not just make them "work." I enjoy digging into how systems are put together, how different parts talk to each other, and where something might break under real use. I’m more interested in solid, practical solutions than fancy tricks or trends.

I like working across different parts of an application. Backend logic, APIs, databases, auth, and even some frontend work all make sense to me as one connected system. If something feels confusing or overcomplicated, I usually take that as a sign it needs cleanup. I care a lot about readable code, simple structure, and clear behavior, especially when the project grows.

Most of what I know comes from building real projects and fixing real problems. Tutorials help, but the real learning happens when something breaks and I have to track it down. Debugging doesn’t annoy me much; it’s more like a puzzle. Following bugs from symptoms to root causes has made me more patient and careful when writing code.

I also pay attention to things that are easy to ignore early on, like security, validation, and reliability. Auth flows, permissions, and data handling matter, because small mistakes there can cause big issues later. I’d rather write code that’s a bit more explicit and boring than something clever that’s hard to trust.

When it comes to working with others, I try to write code that someone else can pick up without getting frustrated. I think about naming, structure, and consistency a lot, because future-me is also “someone else.” I like collaborating when expectations and boundaries are clear.

Overall, my style is simple: build, test, break, fix, and improve. I’m not trying to be perfect, just better than the last version, and I enjoy the process of slowly turning messy ideas into clean, working software