https://www.moniquemudama.com/categories/engineering/Recent content in Engineering on Monique MudamaHugoenMon, 19 Jan 2026 14:05:56 -0700https://www.moniquemudama.com/posts/2026/cap-partitions/Mon, 19 Jan 2026 14:05:56 -0700https://www.moniquemudama.com/posts/2026/cap-partitions/<p>People who’ve spent some time around databases usually have an intuitive sense of ACID, even if the acronym slips their mind. And if you work with distributed systems, you usually have a rough idea of the CAP Theorem, even if the details are fuzzy. The first thing you remember about CAP is probably, &ldquo;Pick two out of three.&rdquo; And maybe you can even remember the letters without a search engine &hellip;</p>https://www.moniquemudama.com/posts/2025/fun-with-slices/Thu, 21 Aug 2025 13:44:24 -0600https://www.moniquemudama.com/posts/2025/fun-with-slices/<p>When I first encountered Go, I found <a href="https://golangdocs.com/slices-in-golang" class="external-link" target="_blank" rel="noopener">slices</a> puzzling. You can create slices from a starting slice or array, and the new slice will be a pointer to a portion of the original data. Got it. But wait, you can also append to the new slice - how does that even work? If you&rsquo;re appending something to the new slice, what&rsquo;s happening to the original slice? If it&rsquo;s modified, does that mean you&rsquo;re appending to the new slice while overwriting a value in the old one? If so, then what happens when you append past the end of the old slice? How would THAT work?</p>