Particularly with technical writing, I think you can definitely get away with both.
“How I Reduced My Postgres Query Latency By 100x With A Single Index”
Even in the title, I can tell you the punchline (if you wanna make your DB access faster, use an index!)
but an interested reader still wants to figure out how exactly your solution works, and you can tell them some interesting details along the way
“just enforcing unique constraints does help certain data types, but it’s not a big performance boost most of the time”
while finishing on the kicker
“Since my hottest endpoint by far was for individual users querying orders which were still ongoing, I created an index on the user field for the orders table, and included a status filter in the index, which took p90 latency from 10s to <100ms!”
“How I Reduced My Postgres Query Latency By 100x With A Single Index”
Even in the title, I can tell you the punchline (if you wanna make your DB access faster, use an index!)
but an interested reader still wants to figure out how exactly your solution works, and you can tell them some interesting details along the way
“just enforcing unique constraints does help certain data types, but it’s not a big performance boost most of the time”
while finishing on the kicker
“Since my hottest endpoint by far was for individual users querying orders which were still ongoing, I created an index on the user field for the orders table, and included a status filter in the index, which took p90 latency from 10s to <100ms!”