andreasbm.github.io

Alfred Gutierrez (alfg) is a software architect and principal engineer who works on streaming video technologies, currently on the Video Engineering team at NBCUniversal, PeacockTV, and SkyUK. He is also a prolific open source developer, building tools and libraries focused mainly on video and audio. If you want to know whether to follow his work, use his projects, or reach out for collaboration, the short answer is: he is a credible, deeply technical developer whose public work is most relevant to you if you work with media pipelines, encoding, or backend infrastructure.

What He Does Day to Day

His current role is Software Architect / Principal Engineer, focused on video engineering. According to his own description, he designs software for large-scale streaming applications and infrastructure that deliver video to millions of customers. That places his professional work squarely in the streaming media domain rather than general web front-end development.

His stated specialties include:

• Streaming multimedia technologies
• Minimalistic design and architecture
• Modular, minimal, well-documented code
• Backend, infrastructure, and low-level programming
• Building and designing performant, large-scale applications
• Debugging and troubleshooting technical incidents quickly

He also holds a US patent as an inventor for ad transcoding multimedia technologies.

Languages and Tech Stack

Gutierrez works across a broad set of languages rather than specializing in one. His listed languages are:

He also states he is knowledgeable and experienced with many AWS services, and well-versed in many web technologies and frameworks. So while he is described as a web developer, his actual range spans backend, infrastructure, and low-level systems work — useful context if you are evaluating him for a role that is purely front-end.

Open Source Projects

Gutierrez says building open source software is his passion, and he creates applications, libraries, and tools for others to use. Most of his work centers on video and audio technologies. His featured projects include:

• FFmpeg Commander — an FFmpeg command generator
• Open Encoder — a cloud encoding platform for FFmpeg
• GuildBit — free Mumble hosting

Beyond those, he also builds MP4 inspection tools, test players, MP4 libraries, CLI tools, and Docker images. More of his featured projects are listed at github.com/alfg.

If your interest is in media tooling — generating FFmpeg commands, encoding in the cloud, or inspecting MP4 files — his open source work is directly relevant. If you need general web application frameworks, his public project list is less focused on that area.

Where to Find Him

• GitHub: github.com/alfg
• LinkedIn: linked via his site
• Email: listed on his site

He currently lives in Tokyo, Japan, which is worth noting if you are considering time-zone overlap for collaboration or hiring.

How to Decide Whether to Follow or Reach Out

Use these conditions to judge fit:

• Follow or use his projects if you work with video/audio pipelines, FFmpeg, encoding, or MP4 tooling, or you want examples of minimal, well-documented Go/Node/Rust code.
• Reach out for collaboration if your project involves streaming infrastructure, backend architecture, or large-scale media delivery, and you can work with a Tokyo-based schedule.
• Look elsewhere if you need a dedicated front-end or general-purpose web app developer — his public profile emphasizes backend, infrastructure, and media systems rather than UI work.

His combination of production-scale streaming experience at major platforms and an active open source portfolio makes him a reasonable person to follow for anyone in the media engineering space.

GitHub is a web platform for hosting Git repositories and collaborating on code. For open-source projects like mailcow, it serves as the place where source code lives, releases are published, bugs are reported, and contributions are reviewed. You can use GitHub without writing any code — browsing a project's repository, reading its changelog, or filing a bug report are all legitimate uses. The one thing to keep straight up front: Git is the version-control tool that tracks changes to files, while GitHub is a hosting and collaboration service built around Git. You can use Git without GitHub, and GitHub hosts projects that use Git.

The core concepts you'll actually encounter

A repository's history is a chain of commits. Branches let people work on changes without disturbing the main line. When a change is ready, it's proposed as a pull request, reviewed, and merged. Issues are the separate track for problems and discussion — they aren't code, but they often drive it.

Finding a project's source, releases, and changelog

For a project like mailcow, the repository is the authoritative source for what's in a given version. A practical path:

1. Open the project's repository page. The file listing and README are the front door — the README usually states what the project is and how to install it.
2. Check the Releases section (often a link in the sidebar) to see tagged versions. Release notes typically list component version bumps and security fixes. mailcow's own blog, for example, publishes entries such as "Mootember 2026 | Unbound 1.26.1, SOGo 5.12.11 & Redis 7.4.11" and "Mooly 2026 | Postfix 3.10.12, Rspamd 4.1.0 & Nginx 1.30.3," each tied to a dated update release.
3. Look for a CHANGELOG file or a changelog link. This is where you confirm exactly which component versions and fixes landed in a release.
4. Use the commits view when you need to know when something changed, not just that it changed.

This matters when you're deciding whether to upgrade. A release note that says it "addresses several security-related issues" and "strongly recommend[s] updating" is a different signal than a routine dependency bump.

Reporting a bug or contributing a change

The workflow is the same across most projects:

• Before filing an issue, search existing issues. Duplicates get closed, and the answer may already be there.
• When filing, include what you did, what you expected, and what happened — plus version numbers. For a Docker-based project, that means the image or release version and relevant logs.
• To contribute code, the usual path is: fork the repository, create a branch, make commits, push, then open a pull request against the upstream project. Maintainers review, request changes, and merge.

You don't need commit access to any of this. Forking and pull requests exist precisely so outside contributors can propose changes without direct write access to the main repository.

GitHub vs. Git, in one example

Say you want to fix a typo in a project's documentation. Git, running on your machine, records your edit as a commit and tracks the branch you made it on. GitHub is where you push that branch and open a pull request so the maintainers can see and merge it. Git did the version tracking; GitHub did the hosting and the collaboration. If you only ever browse a project's releases or read its issues, you're using GitHub and never touching Git directly — which is fine.

Where this leaves you

If your goal is to use a project like mailcow, you mainly need the Releases and changelog views to pick and verify a version. If your goal is to report or fix something, you need issues and pull requests. And if you're trying to understand what changed between two versions, commits and release notes are the record — not the marketing page.