Articles in this category. Show all categories
An organisation chart that changes by regulation is still master data for relational records. I keep it in SQL as a table that points at itself, with versions per agency and effective dates, read it with one query and recursive CTEs, and leave drawing it to the interface.
A personnel database that never enforced its rules had to become clean data for a new system while the old one kept running. Ordered, repeatable phases behind a read-only door, explicit maps, honest placeholders and a report instead of a crash made that possible.
A 4 GB GPU pushed the heavy work onto a borrowed Colab runtime, so a laptop and that runtime had to share one store. Storing the data was easy. Believing it was not: seven of the ten obstacles were successes that were false, and the most useful fix removed an entire layer.
A storage server that answers a connection only proves a process is listening. I check each capability separately — browser uploads via presigned URL, private buckets refusing strangers, large files through the proxy — before any application depends on it.
Get an email when a new article is published.