G-J van Rooyen<p>- Finally got round to doing <a href="https://c.im/tags/AoC2023" class="mention hashtag" rel="tag">#<span>AoC2023</span></a> Day 3 before work.<br />- Starting to actively box in "greedy" commitments that demand attention and time, and disrupt the well-behaved projects. I'm working towards a much less reactive daily workflow. Keep <a href="https://c.im/tags/sente" class="mention hashtag" rel="tag">#<span>sente</span></a>, avoid gote.<br />- A fun aspect of <a href="https://c.im/tags/AdventOfCode" class="mention hashtag" rel="tag">#<span>AdventOfCode</span></a> is the second part of each day's puzzle which you don't get to see until you successfully complete the first part. If you write your code for Part 1 in a modular way that's easy to reuse and refactor, Part 2 is sometimes really easy. Happy that this worked out for me today ⭐⭐<br />- A year ago I would have been very uncertain about the role of an Industrial Engineer in a technology development firm like Octoco. We've just hired our second one, and my current "golden ratio" is 1 IE per ~20 Software/Electronic engineers – for us, these are the people who engineer our work processes; both internal and external.<br />- Some admin before bedtime, then finished AoC Day 4, Part 1. Set types in <a href="https://c.im/tags/OCaml" class="mention hashtag" rel="tag">#<span>OCaml</span></a> are finicky at first, what with comparator witnesses and all, but really powerful and concise.</p><p><a href="https://c.im/tags/lifelog" class="mention hashtag" rel="tag">#<span>lifelog</span></a></p>