# Radar Digital Comunicaciones — supporting editorial workflows

At Radar Digital Comunicaciones, I worked on a Press Media Publisher designed for journalists and editors who needed to manage content with speed and reliability. The project included both desktop and web application workflows and supported publishing and bulletin generation for daily editorial operations.

The system helped teams prepare and send newsletters by email on a daily basis. It was a practical example of software built to reduce operational friction: content could be organized, reviewed, and distributed without relying on manual, error-prone steps.

# Designing around the work people already do

The value of the platform was not in the technology alone—it was in the way it fit the rhythm of a newsroom. Editors needed a streamlined process for content preparation, review, and dissemination while staying focused on the message rather than the tooling.

I worked with C#, ASP.NET MVC, WCF APIs, Angular, TFS, Azure SQL, T-SQL, and Google Drive to support a workflow that connected publishing operations, content storage, and distribution. The product was built to support real editorial needs rather than simply showcase technical functionality.

# Why this project mattered

This role reinforced an important engineering principle: the best workflows are the ones that reduce friction without adding complexity. When software supports the daily work of users, it becomes genuinely valuable because it makes the process faster, clearer, and more dependable.

Last updated: 8/31/2026, 8:09:42 PM