About
The work comes first.
I’m Bhanu Prakash Korthiwada, a software practitioner in Hyderabad. I build and maintain software, and I examine the decisions that determine whether it becomes useful, operable, and understandable.
Why these articles exist
My work began close to code and gradually expanded into the choices around it: what should be built, how a system should be shaped, where complexity is justified, and how a team can own the result.
Writing is how I turn those choices into something another practitioner can inspect and use. The goal is not to present myself as careful or authoritative. It is to show enough of the situation, evidence, trade-offs, and limits that you can judge the conclusion for yourself.
What I try to publish
Each article should help with one real software decision. It should be grounded in work I have done or observed, an artifact I can examine, or primary research I can verify. When the evidence is incomplete, I will say so. When later work changes the conclusion, I will revise it.
The recurring questions concern technical judgment, product intent, complexity, ownership, team clarity, and the changing shape of software work. They are connected by consequences, not by a list of roles.
Follow the evidence
The articles contain the complete arguments. Code and public technical artifacts live on GitHub. If an article connects with something you are building—or you think I got something wrong—email me.