I just published a guide on automating image compression across macOS, Linux, and CI/CD workflows.
<a href="https://www.ramijames.com/thoughts/on-automating-image-compression" target="_blank" rel="noopener nofollow">https://www.ramijames.com/thoughts/on-automating-image-compression</a>
Stop shipping unoptimized images. Automate it.
Image compression is one of those things everyone knows they should do… and then forgets once the app ships.
I wrote a practical guide on automating PNG &amp; JPG compression across:
<ul>
<li>macOS and Linux</li>
<li>Local dev environments</li>
<li>CI/CD pipelines (with a GitHub Actions example)</li>
</ul>
It covers:
<ul>
<li>pngquant vs jpegoptim (and when to use each)</li>
<li>Idempotent commands that won’t recompress images endlessly</li>
<li>How to make image optimization a default, not a cleanup task</li>
</ul>
If you care about performance, this should live in your repo TODAY and not your TODO list.

Learn. Share. Grow. By devs for devs - a place for sharing information useful to any developer no matter what path they are on. 

Devs Together Strong

A practical guide demonstrates how to automate PNG and JPG image compression across macOS, Linux, and CI/CD pipelines. The guide covers tools like pngquant and jpegoptim, explains idempotent compression commands to prevent endless recompression, and provides a GitHub Actions example. The approach shifts image optimization from a manual cleanup task to an automated default in development workflows.

On automating image compression