Irving’s Newest Computing Chapter Opens with a Tech Talk That Means Business

ACM Irving Chapter
ACM Irving Chapter

Dallas–Fort Worth has never lacked for technology talent. Corporate headquarters, sprawling tech campuses, and a deep bench of working engineers have been here for years. What the region hasn't had is an intellectual home for the people who build, research, and push computing forward inside that ecosystem.

The newly chartered ACM Irving Chapter, an affiliate of the Association for Computing Machinery, the world's largest and oldest computing society, set out this month to close that gap with its inaugural Tech Talk. The virtual session pulled in technology leaders, academic researchers, industry practitioners, and curious community members from well beyond Texas. Several technical sessions anchored the program, including ones on AI observability, secure payment architectures, distributed cloud systems, and next-generation wireless. For a chapter that didn't exist a year ago, the ambition on display was striking and, on the evidence of the afternoon, earned.

The chapter is the work of four founding members, Tejas Pravinbhai Patel, Sandeep Shivam, Gajendra Babu Thokala, and Viswanathan Ranganathan, who, between them, have spent decades inside the working engineering culture of the region.

A Chair Who Knows Why This Matters

The ACM Irving Chapter held its inaugural session under the leadership of its founding Chair, Tejas Pravinbhai Patel, a distinguished computing practitioner, IEEE Senior Member, and prolific applied AI researcher recognized for his contributions to large-scale distributed systems and machine learning. Mr. Patel established the chapter to address a gap that had long gone unmet across the Dallas–Fort Worth technology corridor. Despite Irving's remarkable concentration of technology professionals and research talent, the region had lacked any formal, dedicated platform for structured dialogue between computing practitioners, researchers, and students. Mr. Patel identified that void and moved to close it.

The chapter's inaugural Tech Talk series, positioned by Mr. Patel as the opening instalment of a sustained and recurring forum, drew an enthusiastic audience of industry engineers, academic researchers, and graduate students, all of whom recognized the initiative as a significant and timely contribution to the regional computing ecosystem. The session carried a quiet authority, reflecting the vision of someone who built the institution he was standing in. For those in attendance, it was unmistakably clear that the ACM Irving Chapter is not a ceremonial launch but a durable contribution to the field, built by a leader who saw what the DFW computing community was missing and had the commitment to provide it.

Placing Irving on the Map

Picking up where Mr. Patel left off, Vice Chair Sandeep Shivam used his opening minutes to reframe how the local technology community might think about itself. Irving, Mr. Shivam argued, sits at the heart of one of the country's fastest-growing technology corridors, surrounded by Fortune 500 employers, fast-moving smaller firms, and a talent pool that runs the gamut from new graduates to deeply specialized veterans.

The missing piece, in Mr. Shivam's telling, has been connective tissue, the kind of community infrastructure that turns a roster of capable individuals into a self-reinforcing ecosystem. Pointing to the pace of change in AI, cloud, and data systems, Mr. Shivam argued that structured learning and collaboration aren't perks anymore; they're the cost of staying current. Mr. Shivam named Vint Cerf, an architect of the modern internet, and Donald Knuth, whose work on algorithms still shapes how the field thinks about computation, not as ornamentation, but as a way of locating the new chapter inside a longer global tradition.

That positioning didn't go unnoticed beyond Texas. Participants joined from chapters and technology communities across the country, an early signal that the Irving affiliate is already drawing interest well outside its own geography.

Engineering the Room

Holding the program together was Co-Chair and Communication Chair Gajendra Babu Thokala, who brought 18 years of large-scale data platform engineering experience to the host's role and, importantly, used it. Mr. Thokala's introductions did more than move the agenda along; they framed the stakes of each session before the speaker had said a word, and threaded a through-line across talks that, on paper, ranged from antenna physics to SaaS tenancy models.

That through-line wasn't accidental. Mr. Thokala laid out what amounted to the chapter's working theory: progress in computing is fundamentally social. It depends on different perspectives meeting and rubbing against each other, academic researchers in conversation with working engineers, senior practitioners in conversation with people earlier in their careers, specialists in one domain forced to explain their assumptions to specialists in another. The Tech Talk series, in Mr. Thokala's framing, exists to engineer those collisions on purpose.

Mr. Thokala described ACM Irving as a community committed to advancing computing as both a science and a profession, a phrase that carried weight precisely because it refused to choose between the two. That posture showed up in how Mr. Thokala handled the speakers' introductions. Each one was framed not as a credential recital but as a placement: why this person, on this topic, at this moment in the field. By the time the first speaker began, the audience already knew why they were listening, and it is the kind of small thing that distinguishes a well-run program from a forgettable one.

A Few of the Talks Worth Surfacing

The Tech Talk lineup was denser, in truth, than a single afternoon could comfortably hold, and not every session can be done justice in a single feature. What follows are the talks that, from a reporter's seat, lingered most after the session ended: the ones whose framing of the field felt fresh, or whose technical claims seemed likely to age well.

The Infrastructure Beneath Everything Else

The afternoon's Distinguished Speaker session made a quiet but unmistakable argument: the AI and machine learning systems generating most of the industry's headlines are sitting on top of physical-layer infrastructure the broader public almost never sees, and that infrastructure is in the middle of a difficult, expensive transition.

The subject was millimeter-wave communication and advanced antenna design for next-generation wireless. As lower-frequency bands grow more congested, the telecom industry is being pushed up into the 23–40 GHz range, a shift with implications across 5G, the early 6G agenda, vehicle-to-vehicle systems, satellite communications, and the immersive applications coming behind them. The engineering difficulty is substantial, but the antenna architectures now under development are starting to make reliable, high-capacity wireless feasible at those frequencies.

The point that landed hardest was a connective one. AI workloads, autonomous systems, real-time inference at the edge, distributed agentic platforms, all of it depends on wireless infrastructure that can move enormous amounts of data with predictable latency. Without the work happening at the physical layer, the speaker argued, the more glamorous applications further up the stack simply do not function at scale. The headlines belong to the models. The constraints belong to the radios.

The session's Distinguished Speaker was Dr. Tanweer Ali, a professor at Manipal Institute of Technology in Karnataka, India, a Senior Member of IEEE, and, for three consecutive years, a Stanford-recognized top 2% scientist globally. Dr. Ali set an intellectual bar that the chapter will, in effect, be measured against.

When AI Meets the Real World

If Dr. Ali's session pointed toward the physical layer of the future, the next talk dragged the conversation squarely into the present.

Its opening was a provocation: the monitoring frameworks organizations have spent decades refining are structurally unsuited to AI workloads, where behavior is probabilistic, data-dependent, and often resistant to clear explanation. The talkEngineering Observability for Production AI Systems at Scalesketched a practical architecture for capturing the signals that actually matter for AI: model drift, hallucinations, prompt flows, agent decisions, data lineage.

The broader argument was that observability for AI can't stop at performance metrics. Governance and data protection have to be wired in from the start, so that sensitive content in logs, prompts, and conversational interfaces gets the same rigor any regulated data environment would demand. Drawing on engagements across more than ten industries, financial services, healthcare, and telecommunications, among them, the speaker, Sasi Kiran Malladi, Principal Technical Account Manager at Amazon Web Services, gave the session the texture of someone who has been on the wrong end of an AI incident and has thought carefully about how to avoid the next one.

The Architecture of Trust in Payments

The conversation shifted again to one of the highest-stakes domains in modern computing: secure transaction authorization in distributed payment architectures.

As payment platforms move off centralized systems and into microservices, the engineering problem compounds. Security, scalability, latency, fraud prevention, and regulatory compliance all have to hold simultaneously, typically at high transaction volume, and against an evolving threat landscape. The session walked through design principles, including tokenization, zero-trust patterns, and secure authorization flows, and made a case for embedding DevSecOps and observability into the architecture from the outset rather than retrofitting them later.

The cross-industry credibility was hard to miss. The speaker, Tarun Kalwani, Principal Engineer and System Architect at Verizon, drew on nearly two decades of enterprise engineering across telecom, financial services, and aviation, and the audience, technically varied as it was, leaned in.

Designing Platforms That Scale Without Breaking

The final session of the afternoon took on the central tension of modern SaaS platform design: how to serve a large, varied customer base on shared infrastructure while preserving the isolation, security, and customization that enterprise buyers expect.

Using AWS services as a reference architecture, the talk worked through tenancy models, isolation boundaries, routing strategies, and observability patterns. What gave the session weight was its candor about trade-offs between cost, operational complexity, and resiliency that engineering teams have to negotiate every day, and that vendor marketing tends to gloss over. For anyone building, operating, or evaluating SaaS platforms, this was the kind of grounded, experience-backed material that's hard to come by outside a peer-level technical conversation.

It was delivered by Mythili Annamalai Sekar, a Solutions Architect at AWS, with more than 20 years across cloud architecture, serverless, and generative AI.

Looking Forward

Closing the program was Co-Chair and Treasurer Viswanathan Ranganathan, whose remarks balanced gratitude with forward motion. Mr. Ranganathan thanked the speakers, the attendees, and the organizing team, and then made what may have been the most consequential statement of the afternoon: the inaugural Tech Talk wasn't a destination; it was a departure point. The framing was deliberate. A launch event can easily become its own justification; Mr. Ranganathan was clear that this one was not.

The chapter, Mr. Ranganathan said, plans to expand its schedule of technical sessions in the months ahead, covering both emerging and applied areas of computing, from foundational research to the engineering realities of building and operating systems at scale. Beyond that, the leadership team is actively working toward in-person events that will let the Irving technology community connect, collaborate, and build relationships in shared physical space. Virtual sessions, Mr. Ranganathan acknowledged, can carry technical content. They are less effective at building the kind of trust between practitioners that turns a chapter into a community.

Why This Moment Matters

The launch of a local ACM chapter is not, on its face, the kind of story that breaks into mainstream technology coverage. But the conditions that produced ACM Irving concentrated engineering talent without a structured community to bind it, rapid AI and cloud adoption without enough forums for critical reflection, a widening gap between academic research and industry practice are not local. They show up in technology communities across the country.

What this chapter demonstrated in its first event is that a well-organized, intellectually serious local affiliate can start to address all those conditions at once. Whether it sustains that ambition will depend on the community that forms around it.

On the evidence of the inaugural session, that community is already taking shape.


The ACM Irving Chapter is an affiliate of the Association for Computing Machinery. For information on upcoming sessions and membership, contact the chapter leadership directly.

Join the Discussion

Recommended Stories