Salesforce development
Started close to business process, where data quality, permissions, handoffs, and workflow details are not abstract concerns.
About
I'm Himanshu. My work and writing sit around AI, machine learning, software systems, and the practical questions that shape how technical ideas become usable in real settings.
I came to AI and ML through software work, not around it. That matters because intelligent systems sit inside products, workflows, planning habits, interfaces, and teams that already have ways of making decisions. The useful questions are often about how the system is framed, where the data comes from, how behavior is evaluated, who needs to trust it, and what has to change for the work to become part of a real operating rhythm.
Journey
The route was not a straight line into modeling. It moved through several layers of how software, systems, and decisions actually work.
Salesforce development
Started close to business process, where data quality, permissions, handoffs, and workflow details are not abstract concerns.
Full-stack development
Building across front end, back end, data, and integrations made the full product surface visible.
Application architecture
Architecture work made maintainability, reliability, modularity, and handoff part of the default frame.
AI, ML, and analytics
AI and ML became a continuation of that path: useful only when framing, data, evaluation, trust, and product context connect to the work being supported.
Get in touch
If the perspective here connects with a question you are working through, a few lines of context are fine.
The contact page is open when it helps.
Go to contact