All week: state machines, migrations, dependency graphs. Friday evening: two glasses on the table, a jug of water, a bucket of ice.
And every time, somebody asks “shall we put the ice in now?”
The order is not tradition
Rakı goes into the glass. Water on top — roughly two measures to one. The liquid turns white at that instant. The ice goes in after that.
The reason is entirely physical.
The main component of anise oil dissolves in alcohol and not in water. With only rakı in the glass the alcohol fraction is high, the oil is dissolved, the liquid is clear.
Add water and the alcohol fraction drops. The oil can no longer stay dissolved and spontaneously separates into sub-micron droplets — with no stirring at all. Those droplets scatter light. That is the whiteness.
In the literature it is the ouzo effect: spontaneous emulsification. No emulsifier, no energy input — just a drop in solubility.
Why the ice waits
Temperature changes solubility. Put the ice in first and the liquid cools fast; with the alcohol still concentrated the oil partly separates in the cold, and when the water arrives you get an oily film on top and patches of clear liquid below instead of that even cloud.
So the problem is not the taste — it is the sequence. Same three components, same ratios, different result.
This felt very familiar
Because it is exactly what I do the rest of the week: find out how correct components combined in the wrong order silently produce a wrong result.
- Run the migration after the code change and the application looks for a column that does not exist.
- Read the language setting after the dynamic interface is built and half the page comes out in one language and half in the other — this happened to me exactly, and the fix was a tiny inline script in the
<head>. - Send commands to a device before it is ready and the first frames are swallowed. That is precisely what happened with the lighting interface.
In none of them was a component wrong. In all of them the order was.
Knowing a system’s parts is not understanding it. Knowing the order in which they combine is.
And the table itself
The whole table does not arrive at once. Cold dishes first — seafood, things in olive oil. Hot starters in the middle. Fish last, and unhurried.
The reason is not arbitrary: the light flavours set the palate. Let the heavy ones go first and nothing after them can be tasted. Exactly like putting your strongest image at the top of a page and making everything below it invisible.
A table is a system. Systems have an order.
Nobody talks while a glass is being poured, and nobody pours while someone is talking. Everything else is preference — the ratio included.