When you’re a solutions architect juggling multiple projects, no two days look the same. Just ask Dan Ellis, one of Synergex’s seasoned PSG solutions architects based in the UK. With years of experience helping customers modernize and extend their software systems, Dan’s days are a mix of deep technical work, cross-team collaboration, and an occasional round of what he calls “code archaeology.”

Morning: Setting priorities and getting in sync

Dan starts each day by checking the DevOps boards for the projects he’s working on. He’s currently a member of three different customer development teams, in addition to working on other engagements with Synergex team members, helping customers adopt new technologies and Visual Studio.

“Priorities change all the time,” he explains. “There’s a lot of waiting for other people or projects to start, and then suddenly, all the buses come at once.”

He uses the boards to review the status of tasks—his own and others’—and to spot blockers before they escalate. Then it’s on to reviewing pull requests, ensuring the new code meets standards and integrates smoothly with the existing system.

Midday: From code to collaboration

Once the day’s priorities are clear, Dan partitions his time across multiple projects. Some mornings are dedicated to customer standups or discovery and design calls, where he helps teams figure out the best way to deliver a solution or estimate what that delivery will require.

Other days, he’s neck-deep in the code itself, implementing Harmony Core or Streaming Integration Platform, migrating an application to Linux, or doing a bit of that “code archaeology” he mentioned.

“Sometimes I’m looking at a system where the people who originally wrote the code are long gone,” he says. “You have to piece together how everything works before you can improve or modernize it.”

Afternoon: Building, writing, wrapping up

Dan’s afternoons often include a mix of hands-on development for PSG projects and writing process documentation for internal teams or customers. These docs often serve as long-term guides, helping customers maintain and extend their systems after the initial project wraps up.

He’s also meticulous about tracking his work. PSG uses Kimble for timesheets, something Dan’s happy about after years of managing separate spreadsheets for each customer. “Kimble makes it so much easier,” he declares.

Before wrapping up, Dan updates his daybook, a personal log of notes, ideas, and reminders. It’s a habit that’s served him well over the years. “I’ve got a big stack of them in my garage,” he laughs.

All in a day’s work

For Dan, the variety of the work is what keeps things fun. One hour he’s immersed in code, the next he might be mapping out a new solution or syncing up with a customer team. It’s a constant balancing act, but Dan’s success at it is why colleagues and customers alike really enjoy working with him.