About This Site

This site is a personal tech blog centered on Python and ffmpeg, with a strong focus on implementation, experimentation, and verification.
It covers topics such as custom tool development, automation, audio and video processing, and AI-related experiments, based on things I have actually tested myself.
Rather than publishing abstract summaries, I aim to document code, commands, and procedures in a way that other people can reproduce.

About the Author

I am an independent developer who enjoys solving everyday friction with simple systems and building things that actually work.
My main areas of interest are Python automation, audio and video processing with ffmpeg, local AI experimentation, and practical PC and development-environment setups.
I run this site to organize what I learn through hands-on work and to preserve that knowledge in a form I can reuse later.

Main Topics on This Site

ffmpeg

I write about practical ffmpeg use cases such as audio loudness adjustment, LUFS, loudnorm, and media conversion.
The goal is not just to explain the commands, but also to document the assumptions, pitfalls, and decisions that matter in actual use.

Python

This site also covers automation, ffmpeg integration, small utility development, implementation notes, and sample code.
I place particular emphasis on code and workflows that are easy to reproduce.

AI

I also cover local AI experiments, model runtime setup, and records of inference and validation work.
The goal is to document real configurations and procedures, including what worked and what did not.

Development Logs

I also publish longer-running development logs, including tool development, AI-related experiments, and validation records.
The goal is to keep not only the final result, but also the trial-and-error process and the reasoning behind each decision.

Editorial Policy

The articles on this site are primarily based on things I have actually tested and verified myself.
Rather than posting summaries, I prioritize reproducible steps, code, and command examples.
When results depend on the environment or software version, I try to state those assumptions and test conditions as clearly as possible.
If information becomes outdated, I update or supplement the article when needed.

Contact and Policies

If you need to get in touch, please use the contact page.
For details about personal data handling, advertising, and analytics, please see the privacy policy.