WorthWatch homeWorthWatchSpend less time searching. Watch better.

Technology

Mario Carrion

Mario Carrion is an English-language software engineering channel focused on Go, software architecture, and systems design. Mario Carrion has a clear practitioner orientation, emphasizing production software, scalable systems, and enterprise engineering rather than broad tech commentary. Its regular every-other-Monday cadence and sizable back catalog make it a credible learning source for engineers seeking applied architecture and Go-focused guidance.

Highly recommendedTechnology

Editorially reviewed:

Mario Carrion channel banner
Mario Carrion channel avatar
Audience scale17K followers
Videos116 videos
Active since01 July 2007

Recent videos

Latest from the source

Golang 1.26 Changed How I Write Go: Performance, Generics, Error Handling

11 May 2026

Watch

Golang 1.25: What is new?

08 September 2025

Watch

Three Things I don't like about Golang - Part 1

17 March 2025

Watch

Deep Dive

Mario Carrion: Go, Architecture, and Systems Design

Main focus

Mario Carrion is a software engineering channel focused on Go, software architecture, and systems design. Mario Carrion centers on building production software, with attention to performance, scalability, enterprise systems, and long-term maintainability.

Why it matters

This is a focused source for engineers who want applied technical guidance rather than broad technology commentary. Its value is strongest for viewers working with Go or thinking through architecture decisions in complex software systems.

Style

Mario Carrion has a practitioner-led feel, shaped by hands-on engineering and architectural experience. The presentation is positioned around practical lessons from building systems across startups, larger companies, and enterprise environments.

Consistency

Mario Carrion states a regular publishing rhythm of a new video every other Monday at 9:00 AM Eastern. With more than 100 videos, it offers a substantial back catalog for viewers who want to explore related engineering topics over time.

Editorial note

Architecture and Go guidance should be evaluated against each team’s codebase, constraints, infrastructure, and production requirements before being adopted.