bryanbraun.com

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.

A personal blog is a website where one person publishes ongoing, dated writing about their own interests, experiences, or work. A portfolio site is a curated showcase of finished work, usually built to win clients or employers. The two overlap constantly — many developers run a single site that does both — but they answer different questions. A blog says "here is what I'm thinking about lately"; a portfolio says "here is what I can do for you." You need a blog if you want to build an audience or document a learning process over time. You need a portfolio if you want a stranger to evaluate your work in under two minutes. If you want both, one site with two clearly separated sections is usually enough.

The defining traits of a personal blog

• One author. The voice is personal and consistent, even when the topic is technical.
• Chronological publishing. Posts are dated and ordered by time, so the archive itself becomes a record of how your thinking changed.
• Open-ended scope. Topics can drift. A blog about game development can wander into computer science, tooling, or whatever the author is currently building.
• Low polish tolerance. A blog post can be a rough note. That is the point — it lowers the cost of publishing often.

How a portfolio differs

The failure modes are worth noting because they point at the real difference: a blog decays when you stop writing, a portfolio decays when you stop shipping. Whichever you neglect is the one that hurts you.

What a developer's personal site typically contains

A software developer's personal site often merges both. Using Humnom.net as an example — the personal pages of Yuri Sizov, a software developer — the site is described as holding both his portfolio and his blog. That combination is common for developers because the two serve the same underlying purpose: proving competence and taste to people who might hire, collaborate, or read.

Typical sections on a combined site:

• Home / about — who you are, what you work on, how to reach you.
• Blog — dated posts, often tagged by topic such as gamedev, JavaScript, C#, Java, or Godot.
• Portfolio / projects — selected work with enough context to judge it.
• Contact or links — email, GitHub, social profiles.

Deciding which one you need

Ask what you want a stranger to do after visiting.

• "Read more of my writing" → you need a blog. Start with a feed and an about page. Nothing else is required on day one.
• "Hire me" or "buy my work" → you need a portfolio. Lead with two or three strong projects, not a list of everything you've touched.
• "Understand how I think before working with me" → you need both, and the blog is the differentiator. A portfolio shows the result; a blog shows the reasoning.

If you are early in your career and have few finished projects, a blog is the better first investment. Writing about what you are learning produces content faster than waiting for portfolio-grade work to accumulate, and the archive becomes evidence of growth.

Practical starting points

1. Pick one site, not two. Separate domains split your audience and double your maintenance.
2. Put the portfolio above the blog in navigation if your goal is paid work; reverse it if your goal is readership.
3. Date every post and keep the archive visible — it is the main structural difference from a portfolio.
4. Write the first three posts before designing anything. If you cannot produce three, the format is wrong for you right now.
5. Link between the two sections. A project page that links to the posts explaining how it was built is more convincing than either alone.

The common trap is treating the blog as a second portfolio — only publishing polished, announcement-style posts. That kills the publishing rhythm that makes a blog worth having. Save the polish for the project pages.

Bryan Braun is a frontend developer who runs a personal blog at bryanbraun.com, where he writes short essays, link roundups, and year-in-review posts about web development, tools, and the craft of making things. His site describes itself simply as "Making things and sharing what I learn." If you're looking for a developer blog with practical frontend notes mixed with reflective, personal writing, his Recent Posts page is the place to start.

What Bryan Braun does

The site identifies him as a frontend developer. Beyond that label, the blog itself is the main evidence of what he works on and thinks about: JavaScript internals, Git, RSS and personal web infrastructure, AI's role in development, and occasional life updates. There's no product, course, or pricing on the site — it's a writing-first personal blog, not a commercial platform.

What he writes about

His posts fall into a few recognizable buckets:

• Frontend and JavaScript engineering — e.g., "Breaking down circular dependencies in JavaScript" and "Some thoughts on scaling code review."
• Developer tooling and workflow — e.g., "Things I wish someone would have told me about configuring VSCode" and "Unusual Git IDs."
• The personal web and RSS — e.g., "Doubling down on RSS," "Rejecting the algorithm," and "Setting up your /now page with an RSS feed."
• AI and development — e.g., "An AI usage statement for bryanbraun.com," "Quality vs quantity in the age of AI," and "Augmented Development with AI."
• Personal essays and reflection — e.g., "You are not your grand plans," "Waiting is risky," and weight-tracking posts like "250 lbs" and "200 lbs."
• Recurring formats — "Links" roundups (numbered, e.g., Links #15), annual "Made in 2025" recaps, and occasional project write-ups like "Lessons learned from five years of running a family Minecraft server."

The range is broad, but the through-line is experience sharing: what he tried, what he noticed, what he'd tell someone else.

What the writing style is like

Expect short, opinionated posts rather than long tutorials. Many entries are a few paragraphs of observation or a curated list of links. The tone is conversational and reflective — closer to a working notebook than a documentation site. If you want step-by-step technical guides, this isn't primarily that; if you want a developer's honest notes on tools, habits, and the web, it fits well.

How to follow along

• Browse Recent Posts on the homepage to scan titles by date and topic.
• Subscribe via RSS — RSS is a recurring theme on the blog, and posts like the /now page setup show he treats feeds as first-class infrastructure. An RSS reader is the most reliable way to catch new posts.
• Start with a topic you care about — pick from the JavaScript, Git, RSS, or AI clusters above rather than reading chronologically.

The site lists no pricing or login requirements in the available material, so treat it as a public blog to read and subscribe to, and verify any current details on the site itself.