Lesson: Before adding complexity, check if the platform has already solved your problem for you.

#developer #coding #programming

The browser does the hard work:

- Supports AVIF? → loads AVIF
- Doesn't? → falls back to WebP
- Still in the past? → falls back to JPEG

✨ Result: 40% smaller payloads, higher Lighthouse scores, with no infrastructure complexity.

I haven't found a definitive answer, but it looks definitive to me.

Honestly, I would prefer a standard upgrade to the old package.

Next time you start a new project or refactor an existing one, check your tests, global usings can save you hours of repetitive work. Most IDEs can even automate this for you: highlight a 'using' → convert to global using. ⚡

The result? Your test files are smaller, easier to read, and you reduce the risk of typos or missing references. All in minutes, zero risk. ✅

With global usings, you declare those common namespaces ONCE, and they're available in all files. No more clutter at the top of every file.

Typically, test files repeat references to your domain, core, or testing frameworks (`Xunit`, `Moq`, etc.). It's tedious and adds boilerplate.

Lesson?

Don't let your developer's tunnel vision push you towards complex solutions.

Step outside your comfort zone → sometimes the most straightforward fix is the best.

Switching formats cut my payload by 40%.

No infra changes.

No new tools.

No complexity.

👉 Enter WebP & AVIF

- WebP: ~30% smaller than JPEG
- AVIF: up to 50% smaller (with no visible quality loss)

I was still serving JPEGs and PNGs like it was 2015.

Even compressed, they’re no longer optimal.

When I rebuilt my site, Lighthouse flagged performance issues.

My instinct? "I need a CDN or smarter caching."

But the root cause wasn't infra. It was… images.

Video here → youtu.be/LC1nukDZNN8?...

Hey Jason!
Check this out: bsky.app/profile/guif...

Hi Jason! That’s correct. Currently (limited time offer) there’s a monthly subscription available, which is a great deal. I hope that helps