Fifty years later, Barry Merrill still remembers where it all started.

In an interview, Merrill reflected on discovering SAS through a small notice in Datamation magazine. At the time, the software was new, largely unknown and available for $100.

"North Carolina State University's statistics department announces the availability of the Statistical Analysis System," Merrill recalled reading. The software package contained roughly 100,000 lines of code and represented a new way to analyze and understand data.

What happened next left a lasting impression.

Finding value from the start

Merrill remembers putting SAS to work almost immediately.

One of the first analyses he performed involved a computer billing system. By examining the data, SAS revealed a significant discrepancy in how charges were being calculated.

"The very first day we ran it, absolutely the first day," Merrill said. "It got a very nice blessing immediately."

The experience demonstrated something that would become familiar to many SAS users over the decades: the ability to uncover insights hidden within data.

As Merrill continued using SAS, it became an important tool for measuring performance and supporting data-driven decision making.

Getting to know the people behind the software

Merrill's memories aren't limited to the technology itself.

As an early SAS customer, he spent time with members of the company's founding team, including John Sall and Jane Helwig. Looking back, he remembers a company filled with talented people who were committed to helping customers succeed.

"I don't think I appreciated how big it was going to be," Merrill said.

What stood out most to him was the level of support he received.

"It never failed," he said. "And the technical support was so superior to any of the other products that I had to deal with."

Even as SAS grew, Merrill said that commitment remained unchanged.

"They still carried the same characteristic of really smart people who were really willing to work with you," he said.

More than technology

When Merrill reflects on SAS after 50 years, the lasting impression isn't a particular feature or technical breakthrough.

Instead, it's the people.

"It's the thing that really makes the company stand up," he said. "The attitude toward people."

Technology has changed dramatically since the early 1970s, but Merrill's memories point to something more enduring. Beyond the software itself, he remembers a culture built around curiosity, collaboration and a willingness to help customers solve problems.

As SAS celebrates its 50th anniversary, Merrill's reflections offer a unique glimpse into the early years and the qualities that continue to define it today.

Watch the video above to hear Barry Merrill share his story in his own words.

Read more stories in our 50th anniversary series
Share

About Author

Caslee Sims

I'm Caslee Sims, writer and editor for SAS Blogs. I gravitate toward spaces of creativity, collaboration and community. Whether it be in front of the camera, producing stories, writing them, sharing or retweeting them, I enjoy the art of storytelling. I share interests in sports, tech, music, pop culture among others.

2 Comments

  1. Carl Sommer on

    I had the pleasure of interacting with Barry when I originally joined SAS in 1994, as I was on the SAS/CPE team (which later became IT Service Vision, which then became IT Resource Management). He's an amazing personality, and his MXG product (really a set of SAS programs) to read a vast amount of IBM mainframe data (and non-mainframe data was essentially an open source project, in that users would contribute enhancements and fixes (and thus be noted in his code sharks page https://www.mxg.com/codesharks/ - I'm still listed there, but my ranking has slipped precipitously over the years.

    I enjoyed watching this video, especially in the fact that if it sounds like everything Barry said was all with one breathe, that's exactly the way he talks. I would have voicemail messages back from late at time, discussing / answering questions I'd raised about his code. Most of these would fill up the allotted time for a voicemail message, and I would replay them multiple times in order to catch the flood of information that came back. And yes, it seemed even for a 3 minute voicemail message, he didn't take a breathe.

Leave A Reply