Skip to content
New York
Sherwin Rubio.

About

Build for the people you have, not the people you wish you had.

I’m an Enterprise Data Engineer at Newsday Media Group. I build reliable data platforms and automated workflows, but I’ve learned that technology is only part of the work.

My story

I didn’t start in technology. In 2008 I joined Newsday Media Group in cash application, reconciling payments and resolving account issues.

Later, in circulation billing, I began building the tools the work in front of me needed: automated financial adjustments, a payment-archiving system, and a web-based registration process. I was still working inside the operations those tools served.

That experience gave me a practical understanding of both sides of enterprise technology: the people who build systems and the people whose work depends on them. From there my work moved through reporting, systems analysis, application development, and workflow automation, and into enterprise data engineering.

The tools have changed many times along the way. What I build around hasn’t: a system only lasts if it fits the people who use it, how they actually work, and what they already know.

The full path, role by role

Principles

What I believe

  1. People First Innovation

    Technology, process, and profit are means. People are the source of value and the reason systems exist.

    Automation is not about replacing jobs but empowering individuals to operate analytically rather than mechanically. When I weigh a new automation, I consider whether it’s in everyone’s best interest, not just IT’s.

    In practice, that means building systems that cut down on confusion and repeated effort, removing needless friction without taking away people’s ownership of their work, and writing things down so others can pitch in and pick up where someone left off. When it works, the time saved goes back to people. On my team, rather than filling that time with more tasks, we’ve been able to focus on proactive work and have the mental space for informed decision-making.

  2. Design for Reality

    Design for the people, systems, constraints, skills, and responsibilities that actually exist, not for an ideal organization that exists only in a diagram.

    In my experience, good design starts with knowing the lay of the land: who the process is for, what needs to happen, when and how often, where it happens, and why it needs to happen at all. Legacy systems and existing constraints should inform a design, but they shouldn’t dictate it.

    It also means being honest about limits. While I’m clearly a fan of automation, I recognize it’s not always the answer. Some processes cost more to automate than they give back, and a system designed for a team that doesn’t exist won’t be adopted by the one that does.

  3. Data Governance Starts at the Bottom

    Durable governance begins when the people closest to the work recognize the value of shared standards and help shape them.

    Good standards and new ideas rarely take hold because someone ordered them. They grow when the people doing the work have the tools, relationships, and support they need to improve the systems around them.

    That doesn’t mean leadership doesn’t matter. It’s about the order things happen in: a real need on the ground, someone close to the work taking the first step, colleagues picking it up, trust growing across teams, and results people can see. Leadership support and formal rules come after, built on something people already use.

  4. Think in Systems

    Look at the whole: how people, processes, and technology affect one another over time, not just the part in front of you.

    I try to separate symptoms from the structure underneath them. A single failed job is a symptom. The same kind of failure showing up across many jobs, because each one was built a different way, is a structural problem, and that’s the one worth fixing.

    Small changes in the right place multiply: a shared standard, a reusable template, a page of documentation. That’s why I think systems thinking matters even more as AI enters the workplace. The question isn’t only what a new tool can do, but what it changes for the people and processes around it.

How I lead

Leading alongside people

I lead through craftsmanship and relationships more than through a title: building things others can rely on, and helping the people around them understand and use what’s been built.

  1. Served as a technical bridge across infrastructure, development, reporting, Data Science, and business teamsLead Programmer Analyst
  2. Mentored colleagues and provided technical guidance on reporting analysis, design, testing, and implementationReporting Systems Analyst
  3. Led training sessions, system demonstrations, and documentation efforts to support adoption of new toolsCirculation Billing Coordinator
NextWritingWhere I write about these ideas.AlsoExperienceEvery role, from 2008 to today.AlsoContactCompare notes on the work.