diff --git a/content/log/2022/uber-mock-interview-retrospective.md b/content/log/2022/uber-mock-interview-retrospective.md index c2025fe..d87dd39 100644 --- a/content/log/2022/uber-mock-interview-retrospective.md +++ b/content/log/2022/uber-mock-interview-retrospective.md @@ -51,9 +51,9 @@ Cro][loris] keeps telling the me and The Internet that Zig is not suitable for coding challenges. Well, after a couple of months of working with him, I can finally say he is wrong! Even though my colleagues tell me Zig was tripping me (e.g. memory leaks in the unit tests, for which I had to add `defer -hash_map.deinit()`), I think this was due to lack of experience in a coding -challenge setting. Next time the first thing I will do is construct an area and -be done with memory management. +hash_map.deinit()`), I think this was due to lack of experience in a particular +"coding challenge setting". Next time I will construct an [arena][arena] and be +done with memory management. Exercise was taken from [Cracking the coding interview][cracking]: @@ -277,11 +277,12 @@ to code it. The main criteria is, of course, lines of code. :) ## Thanks -Many thanks to Courtney Cox, Mantas Mikšys, Brigita Žemgulytė and Ignas -Kaziukėnas for making this meetup happen. I would do it again. +Many thanks to Brigita Žemgulytė, Courtney Cox, Ignas Kaziukėnas and Mantas +Mikšys for making this happen. I would do it again. [loris]: https://kristoff.it/ [meetup-page]: https://www.meetup.com/uber-engineering-events-vilnius/events/286542203/ [jakub]: https://www.jakubkonka.com/ [pastebin]: https://paste.mozilla.org/ [cracking]: https://www.crackingthecodinginterview.com/ +[arena]: https://github.com/ziglang/zig/blob/0.9.1/lib/std/heap/arena_allocator.zig#L6-L7