J
Jessica Malakian
Guest
A 29-year-old developer from Utah exemplifies the path of a self-driven technologist. What began as a curiosity in basic tech projects evolved into full responsibility for software development at Trestlewood, a company that depends on the Progress OpenEdge development platform to power its mission-critical systems. His story is a testament to how the right tools, support and a passion for learning can empower developers to thrive—even as a small tech team.

In this Developer Spotlight, we feature Jason Cannon, a Chief Information Officer (CIO) and Software Engineer whose journey with the Progress OpenEdge platform began through hands-on experience. Over time, he’s come to value the platform’s performance, reliability and flexibility.
Discovering a Passion Through Opportunity
When Jason Cannon started college at Brigham Young University (BYU), software engineering wasn’t even on his radar. But after some encouragement from his dad, who has experience in the field, he enrolled in an introductory computer science class.
“I liked it, so I just kept taking CS classes and eventually switched my major,” he says. “I really enjoy the problem-solving aspect of software engineering—there are so many ways to approach coding something. It’s kind of cool that you can use your creativity to solve problems.”
By the end of 2020, Jason had graduated and transitioned into full-time software development. Now, with over four and a half years of experience, he’s not just writing code—he’s setting the technology direction as CIO of Trestlewood.
A Crash Course in Real-World Development
Jason began learning the ins and outs of the company’s systems—many of which were built on the Progress OpenEdge platform.
With support from team members and mentors, he learned how to write and maintain Advanced Business Language (ABL) code, troubleshoot issues and develop new features that directly supported business operations.
“I appreciated how easy it was to start using the basic features of ABL. It is a well-structured language and allows for beginners to start writing functional code pretty quickly. It definitely has advanced concepts that took more learning and experience to grasp, but I was surprised at how quickly I was able to start fixing current features and building new ones.”
Wearing Every Hat in the Room
In Jason's current role at a small business, his title says it all: Chief Information Officer. But day to day, his responsibilities go well beyond leadership. “I’d also just be considered a software developer,” he says. “At a small company, we wear different hats.”
From system strategy to hands-on coding, his work spans nearly every aspect of the organization’s technology operations. And at the center of it all: The OpenEdge platform. So, what’s it like being the only developer at the company?
“It’s definitely interesting,” he laughs. “I used to work for a big software company where I was on a team with a lot of other developers. This has a very different feel.”
The biggest difference? Autonomy. “I do like the fact that I have a lot more freedom to work on what I want and do it the way I want.”
A Day in the Life: Problem-Solving on Every Front
No two days are the same. Most of the time, Jason is juggling multiple projects, shifting between tasks based on the company’s evolving needs.
“I usually have a few different projects I’m working on at a time. Sometimes I’ll focus on just one for the day, but often I’ll switch between them depending on priorities.”
Here’s a look at a typical workday:
Working on the database application, developed using OpenEdge ABL and forming the backbone of many core business processes
Maintaining and improving the company website by connecting the web application to the OpenEdge database, built with Java on the backend and HTML/CSS/JavaScript on the front end
Leading digital transformation efforts , including recent projects that digitize wood products for architects, expanding the company’s reach through tech initiatives that go beyond coding
“It’s not always coding. Sometimes it’s more technology-oriented strategy work—figuring out how to make things more efficient, or how to bring our products to new audiences using digital tools.”
Discovering the OpenEdge Platform
Jason’s journey with the OpenEdge platform began during his college years. “When I was in college, I did an internship for Trestlewood where I was using OpenEdge ABL,” he recalls.
It wasn’t until 2022—after finishing school and gaining experience elsewhere—that he joined Trestlewood full-time and began working with OpenEdge ABL every day.
Learning OpenEdge coding wasn’t just about reading manuals; it was about diving into real-world code and solving problems in real time.
“I learned a lot just by looking at the existing code from the previous developers,” he explains. “Trestlewood previously had developers that who built much of the current database and web applications.”
Much of his learning came from exploring that legacy code and getting hands-on with it.
“I’d just look through the code, figure out how it worked, and then tweak or improve things in the existing system. Immersing myself in that codebase was the biggest part of how I learned.”
While practical experience was essential, Jason also tapped into available resources to support his learning.
“I did read some of the documentation online and we had a set of OpenEdge books from a previous version. Those books helped me get a basic understanding of how the language works.”
In the end, his approach was a blend of self-guided exploration, hands-on experimentation and utilizing documentation to fill in the gaps.
Time It Took to Build OpenEdge Understanding
When asked how long it took to get up to speed with the OpenEdge platform, Jason reflects on his journey—and how quickly he was able to contribute.
“I’d say within a month or so of looking at the code and learning, I was able to start working and fixing bugs,” he explains.
Even now, with years of experience under his belt, he sees learning as an ongoing process.
“I’m still learning, honestly. But after a few months, I felt pretty comfortable fixing things quickly and developing new features. A lot of my development now involves taking existing tools and adjusting the code to suit the new functionality I need. I can do that a lot faster now than when I first started.”
What He Loves About the OpenEdge Platform
When asked what stands out about the OpenEdge platform, Jason doesn’t hesitate: “I think the database management system—the way it’s run—is just really efficient. I’ve been impressed with how well the software holds up. It feels durable, especially when it comes to bugs and unexpected situations. The setup has clearly been built to handle a lot, and it does that really well.”
Another highlight: The ABL language.
“I like ABL a lot. It’s powerful, and I love how it combines Structured Query Language (SQL)-like syntax with business logic. That combo is really unique—and really useful.”
Advice for Young OpenEdge Developers
When asked what advice Jason had for young OpenEdge developers just starting out, he emphasized the importance of hands-on experience.
“I think the best way to learn OpenEdge is by getting your hands dirty with the code. Take existing code, work with it and jump into writing your own. The more you can immerse yourself in projects—whether that’s working on existing ones or creating simple ones yourself—the more you’ll learn. Studying documentation is helpful, but I think you’ll gain much more from actively experimenting and seeing what works.”
As someone who has built a career using the OpenEdge platform, his advice on pursuing this career path is grounded in the technology stack of the companies you work for. “I think it really depends on the company and its technology stack. If you’re interested in working at a company that uses OpenEdge, it could certainly be appealing to know the language. But I think it matters less which specific language you know and more about your ability to learn new ones quickly.”
He continues: “If I were hiring someone, I’d want to know that they could pick up a wide variety of languages and be adaptable, rather than focusing on whether they’re proficient in just one. The key is being able to learn and adapt to different technologies, not necessarily having deep expertise in just one language.”
Building Real-World Solutions That Matter
For this developer and CIO, the most rewarding part of his OpenEdge journey has been the ability to build applications that solve real problems. It’s a long way from that first college class—but every step has been driven by curiosity, a love of learning and a passion for making things work.
“I’ve always liked figuring out how to solve problems,” he says. “That’s what software engineering—and working with OpenEdge—is all about.”
As Jason continues to grow in his role, he’s excited about deepening his knowledge of OpenEdge, expanding the company’s use of technology and maybe even mentoring the next generation of developers who, like him, just need the right opportunity to shine.
Interested in becoming an OpenEdge developer? Visit our website to learn more about the OpenEdge Learning Path and Certification process.
Continue reading...