<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/ae818b7d058343c1ad6caf8deee2e430&quot; frameborder=&quot;0&quot; width=&quot;1108&quot; height=&quot;831&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>831</height><width>1108</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>831</thumbnail_height><thumbnail_width>1108</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ae818b7d058343c1ad6caf8deee2e430-00001.gif</thumbnail_url><duration>300.03</duration><title>Improving Logging and Shaping Response in Node.js</title><description>Hey there! In this Loom, I&apos;ll walk you through some improvements I made to a standard Node.js file. I&apos;ll show you how to enhance logging using a small logger package and shape the response to make it more readable. I&apos;ll also demonstrate how to log the prompt, system messages, content, and response, and how to preserve these logs throughout the codebase. Additionally, I&apos;ll discuss some nuances to be aware of and a convenient feature for stringification. Finally, I&apos;ll explain how to push the logs to a production storage instead of storing them locally. So, let&apos;s dive in and make our Node.js file more efficient and organized!</description></oembed>