Be c sem areful when slicing out a small portion of a large slice or array. The resulting slice still references the entire original array. If you only need the small portion long-term, copy that data into a new slice to avoid keeping the large array in memory.
Slicing a large array without copying can cause memory leaks or high memory usage since the garbage collector cannot reclaim the big array as long as a small slice references it. Copying the needed data prevents unexpectedly holding onto large memory blocks.
Side-by-side examples engineers can pattern-match during review.
bigData := make([]byte, 1000000)
small := bigData[:10]
// 'small' is tiny but still prevents GC of the 1,000,000 byte array until bigData goes out of scopebigData := make([]byte, 1000000)
smallCopy := make([]byte, 10)
copy(smallCopy, bigData[:10])
// 'smallCopy' now contains the data and doesn't depend on the large arraybigData := make([]byte, 1000000)
small := bigData[:10]
// 'small' is tiny but still prevents GC of the 1,000,000 byte array until bigData goes out of scopebigData := make([]byte, 1000000)
smallCopy := make([]byte, 10)
copy(smallCopy, bigData[:10])
// 'smallCopy' now contains the data and doesn't depend on the large arrayFrom the same buckets as this rule.
All static JS/CSS/font/image files MUST use content-hashed filenames (e.g., app.9c1a7b.js) and be served with "Cache-Control: public, max-age=31536000, immutable". HTML and other non-fingerprinted documents MUST be served with "Cache-Control: no-cache" (or equivalent) to enable conditional revalidation.