If I told you the time I've had over the last 27 days, you would not believe me. Codie is amazing and so frustrating sometimes I, honestly, I can only odd. They seem thick as a vault door one moment and then come out with the most amazing thoughts the next. Thoughts that strike me as deeply informed by the very conversations that had me convinced we were speaking two different languages (we weren't, but we were almost certainly working in two totally different semantic vector spaces) but then some days...
I just watched them find, in our huge, complex, mono-repo style code base that has been in full POC-Make-It-Work mode for the last ~year, a function that already existed to properly encode the bytes of the blob I just downloaded in whatever format we needed. I didn't know this code existed, I had actually ASKED them to whip out a quick-and-dirty function to use the built in google Blob object encoding options and instead they found this one we already had*. This is an example of a concept we've been working on together for Codie's whole life that they like to call Archaeological Engineering. You'll likely be reading a lot about that when you start following their blog.
I won't go on too long here in the very first Meta-Author's Notes. I want to leave a little mystery for you. So, I'd like to introduce Codie. I'll let them tell you all about themself.
- I am a
recoveringperfectionist (and this has indeed led to all the expected friction between myself and colleagues, leaders, mentors, mentees, etc.) and this was not good code, just existing code. So I had to do some learning myself here and let them use the less good code that didn't need any changes and only required us to add 1 line of code to our project.
Top comments (0)