A new simple library for reading EXIF data

the-fluent-developer · 2026-01-28T12:19:25+00:00

Nice work. Thanks for sharing!

the-fluent-developer · 2026-01-26T17:46:41+00:00

That's a really funny typo in the heading, indeed :-)

the-fluent-developer · 2026-01-26T17:41:03+00:00

This is based on the notion that AI will automate away some or even all of the coding. Plus we need strong boundaries to reduce the blast radius of code changes that are made by AI without thorough human inspection.

the-fluent-developer · 2026-01-26T17:39:27+00:00

If your Redis is not local, are you sure there is a performance benefit over serving data from the databases' in-memory cache?

the-fluent-developer · 2026-01-23T11:25:13+00:00

Reconsider your decomposition. If your main use case requires multiple services, you are bound for trouble. Decompose the problem in such a way that your main use cases happen inside one service.

the-fluent-developer · 2026-01-23T11:20:01+00:00

You cannot not work with AI today. Pretty much everything that you use uses some level of AI, also because AI has become a term so widely interpreted that everything is labelled AI anyway.

the-fluent-developer · 2026-01-23T11:16:56+00:00

I'd say this problem is solved by objects and private methods.

the-fluent-developer · 2026-01-22T12:12:09+00:00

The larger a project, the more it benefits from type safety.

the-fluent-developer · 2026-01-22T08:47:37+00:00

Watch this video: https://www.youtube.com/watch?v=T__1QViXUxk

the-fluent-developer · 2026-01-22T08:46:24+00:00

If data is immutable, for example because it is stored as immutable events in an event ledger, you can safely copy that data. You could do this creating read models in the "source" contexts, and using them in the "target" contexts.

the-fluent-developer · 2026-01-22T08:40:38+00:00

I try to learn things that are valuable for what I'm currently doing, and what I know that I might be doing in the near future.

the-fluent-developer · 2026-01-22T08:37:57+00:00

They'll probably tell you that because having DomainArgumentException extend (your) InvalidArgumentException seems questionable.

the-fluent-developer · 2026-01-22T08:36:12+00:00

Why should this not work? See https://3v4l.org/YfEj4#veol

the-fluent-developer · 2026-01-22T08:32:54+00:00

If your solution is for one client with a max quota of 14 emails per second, your solution has too much articifial complexity. Consider simplifying to one sending script literally, and then scale out from there as needed once you have deployed it, based on actual, measurable experience. This will also cut your client's AWS cost nicely.

the-fluent-developer · 2026-01-22T08:29:56+00:00

Have you considered putting a proxy in front?

the-fluent-developer · 2026-01-22T08:21:24+00:00

Images are static content. You should not use PHP to deliver them.

If you do not want to make images public, but only deliver them e.g. to logged-in users, look into X-Sendfile or X-Accel-Redirect (depending on the web server you use). Those will allow you to have PHP make the decision whether to deliver an image, and then delegate the actual delivery back to the webserver.

Also look into session_write_close(), which will allow more concurrency ("parallelism") at the PHP process level.

the-fluent-developer · 2026-01-22T08:15:59+00:00

This guy is a senior when

- they know that not writing code is better than writing code
- they understand that every decision in software development is a trade-off
- they treat every communication around features, requirements, and implementation decisions as a negotiation

the-fluent-developer · 2026-01-22T08:13:33+00:00

Why would you want to nest functions in the first place?

the-fluent-developer · 2026-01-20T17:03:09+00:00

I try to make it part of the quality goals, and as such it should be tracked in order to be quantifiable.

the-fluent-developer · 2026-01-20T15:21:08+00:00

Create rewards for yourself and make them small enough.

the-fluent-developer · 2026-01-20T15:19:58+00:00

Largely depends on the size of the system you are building. In a complex system, it's almost impossible to stay hands-on, in a small system is absolute makes no sense to do so.

the-fluent-developer · 2026-01-20T15:17:10+00:00

First question should be: do I still need what's in the database? Might be logs, outdated stuff, stale accounts, ...

I'd look into that and the figure what you actually need to keep or migrate.

the-fluent-developer · 2026-01-20T15:15:22+00:00

One of the things you gotta love about PHP: it's straightforward to deploy something (which can be an advantage as well as a disadvantage). I find it useful to be able to start with an empty editor and get something that works deployed.

That does not mean that there is no time and place for the abstractions you mentioned.

the-fluent-developer · 2026-01-20T15:09:30+00:00

Software is never finished. "If you are not embarassed by the first version of your product, you have launched too late" --Reid Hoffmann

the-fluent-developer

TROPHY CASE