unix
5 minUnix Log Sorting: Normalize Offset Timestamps Before Ordering Events
Build a bounded investigation pipeline that preserves malformed records and avoids lexical sorting across mixed offsets.
Search the library
37 matching resultsArticles and interview answers
python
5 minPython Event Times: Normalize Offsets Without Losing Elapsed Time
Build a small timestamp boundary that rejects naive input, normalizes aware values, and measures latency with the right clock.
Q&A
Q&AHow do you confirm and fix an ORM N+1 query?
Count repeated statements per request, then batch-load without changing result cardinality.
Read the concise answer
Trace or log normalized SQL for one request and look for the same child lookup repeated once per parent row. Replace the loop with an eager/batch load or a query at the correct grain. Verify query count and returned rows; a broad join can fix round trips while accidentally multiplying results.
Q&A
Q&AWhat should an async Python task do when it receives cancellation?
Release owned resources in cleanup and normally propagate cancellation after cleanup.
Read the concise answer
Cancellation is delivered at an await point. Use finally blocks or async context managers to close resources, then re-raise CancelledError unless there is a deliberate reason to suppress it. A blocking synchronous call may not respond promptly, so keep the event loop cooperative and bound background work.
databases
10 minFix Slow SQL: N+1 Queries, Missing Indexes, and Bad Cardinality Estimates
A systematic approach to diagnosing ORM query explosions and slow database plans without guessing at indexes.
Q&A
Q&AHow do you safely recover a Terraform state lock after a crashed job?
Verify the lock holder is truly gone and preserve state before force-unlocking.
Read the concise answer
Inspect lock metadata, backend state, and the pipeline that acquired it; confirm no apply is still running. Preserve a state backup and compare cloud reality before force-unlocking the specific stale lock. Then run and review a plan. Force-unlocking a live writer can permit competing state updates and corrupt tracking.
Q&A
Q&AWhen is map or reduce clearer than a Python comprehension or loop?
Use the form that makes transformation, laziness, and accumulator state easiest to understand.
Read the concise answer
map is lazy and can be concise with an existing named function; a comprehension often reads better when transformation and filtering are simple. reduce is appropriate for a well-defined associative fold, but sum, any, all, or an explicit loop often communicates intent better. Avoid hidden side effects because they make ordering and debugging difficult.
Q&A
Q&AHow does CompletableFuture composition work, and what causes stalls?
Completion stages form a dependency graph; blocking the wrong executor can starve that graph.
Read the concise answer
CompletableFuture represents a value that may complete later, with dependent stages triggered on completion. Async methods without an explicit executor commonly use a shared pool; blocking calls there can starve unrelated work. Prefer non-blocking composition, choose an executor suited to the task, set timeouts, and observe exceptional completion rather than calling join() throughout request paths.