I'd like to get feedback on the writing style of this post. I want to try to write up bi-monthly updates but don't enjoy sinking time into writing. I've never really stuck with blogging despite it being valuable for sharing what I'm working on as I'm a bit of a perfectionist. I end up spending hours combing over the posts I make. I'd like my posts to only take 30 minutes, so my current ideas are to write quickly and post as is, or to have an AI edit out my mistakes. Which of the two do you prefer? Do you have any suggestions on ways to make quick blog posts without potentially attaching poor communication or AI slop to myself? My original post. My prompt. Claude's edit of my post: ------ My Two-Month Deep Dive into AI Safety: From Imposter Syndrome to Clarity How ARBOx and ARENA helped me navigate a career transition into AI Safety—and what I learned about myself along the way Two months ago, I committed to spending my summer diving headfirst into AI Safety. As someone with a background in Swift development and traditional software engineering, the world of Transformers, Linear algebra, and AI alignment research felt like an entirely different universe. Here's what happened when I threw myself into ARBOx and ARENA—the good, the challenging, and the surprisingly clarifying moments that helped shape my career transition. Week 1-3: ARBOx in Oxford - Swimming in the Deep End ARBOx accepted me for their intensive program: one week of prerequisites, followed by two weeks of in-person training in Oxford. The reality check was swift. During pair programming sessions, I was often the weaker partner. While my colleagues brought post-grad experience with deep learning or career backgrounds in ML, I was frantically trying to remember basic PyTorch syntax. My years of Swift development, unit testing, and design patterns suddenly felt irrelevant when staring at Jupyter notebooks full of tensor operations. However, being the "slower" partner was actually incredibly v

Two days ago, I published a Substack article called "The Epistemics of Being a Mudblood: Stress Testing intellectual isolation". I wasn’t sure whether to cross-post it here, but a few people encouraged me to at least share the link. By background I’m a lawyer (hybrid Legal-AI Safety researcher), and I usually write about AI Safety to spread awareness among tech lawyers and others who might not otherwise engage with the field. This post, though, is more personal: a reflection on how “deep thinking” and rationalist habits have shaped my best professional and personal outputs, even through long phases of intellectual isolation. Hence the “mudblood” analogy, which (to my surprise) resonated with more people than I expected. Sharing here in case it’s useful. Obviously very open to criticism and feedback (that’s why I’m here!), but also hoping it’s of some help. :)