#systemsdesign

I’ve been thinking a lot about what it actually means to limit AI—not in the sci‑fi sense, but in the very real, very practical sense of keeping humans at the center of the systems we build.

AI is getting faster, more capable, more confident. But it’s also missing the things we take for granted in ourselves: hesitation, moral intuition, the ability to learn from lived experience instead of pure optimization.

So the question isn’t “How do we stop AI from becoming too smart?” It’s “How do we make sure it doesn’t outrun the parts of humanity that matter?”

In my latest piece, I talk about why we need real boundaries: hardware limits, transparent public servers, adaptive laws, and models that embrace uncertainty instead of pretending they’re always right.

Not because AI is dangerous by default— but because unbounded systems drift. And if we don’t shape the limits now, we might end up living inside someone else’s logic.

Where they struggle is planning forward.

As constraints grow, manual logic and rule based scheduling start to break. Every small change forces a full replan. Spreadsheets creep back in. Decisions become reactive.

That’s why constraint-based optimization is becoming important inside ERP systems. Instead of hard coding scenarios, you define constraints like capacity, skills, deadlines, costs, and priorities. The system searches for the best possible solution within those limits.

When done right, schedules adapt instead of collapsing, resource usage improves, and planning becomes explainable rather than fragile.

External Services in Flow let you connect Salesforce to almost anything instantly.

Payments. Credit checks. Slack alerts. Inventory sync. Verification workflows. All powered by real-time APIs you can drag into a Flow like building blocks.

Named Credentials keep everything secure. The OpenAPI schema teaches Salesforce what the API can do. And Flow becomes the place where all your systems finally talk to each other.

Remembering the Structured Systems Analysis and Design course at UMBC. The course required team work on an actual project. I had trouble finding a project to work on. I considered several options. I thought of a website for a family member's pastry business. I even contacted several companies to inquire about projects I might work on. Those options did not work out. I ended up dropping the course the first time I was supposed to take it.

Sonam often in his conversations and discussions mentions the word wealth to us. What does it actually mean? In this world that is driven by capitalism can the word wealth mean anything more substantial to us? The dictionary meaning for the given word is more than often associated with monetary gains and valuable possessions, but is this all what we are trying to do, at least here at Echostream? 

What is my main objective while I make my graduation project brief? Do I want to earn money, yes who doesn't. But do I want to make money only for myself? The answer will not be very objective but perhaps I want to be able to create ‘wealth’. To be able to create a system where all the stakeholders, all the people in the value chain get equal share of what they deserve, are able to acquire some skills, are developed and skilled Human Resources and are able to sustain themselves. To. be able to create employability, skilful Human Resource, entrepreneurial skills within communities. Making less for smaller audiences. “Too much of anything is not good”. Even the most sustainable material used in quantities will no longer be sustainable. Circular economy is not paradoxical until the time taken for the product to complete a cycle becomes too long.