<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Bom dia ☀️</title><link>https://inespereira.me/tags/tools/</link><description>Recent content in Tools on Bom dia ☀️</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Inês Pereira</copyright><lastBuildDate>Wed, 24 Jun 2026 17:10:12 +0200</lastBuildDate><atom:link href="https://inespereira.me/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Tools for Code Review</title><link>https://inespereira.me/posts/code_review_llms/</link><pubDate>Wed, 24 Jun 2026 17:10:12 +0200</pubDate><guid>https://inespereira.me/posts/code_review_llms/</guid><description>&lt;p&gt;In my previous post, I shared a &lt;a
href="https://www.preprints.org/manuscript/202510.0133"
target="_blank"
&gt;preprint&lt;/a&gt;
proposing a structured checklist to facilitate code review in mental health research. Our motivation to write this paper was straightforward: code review can improve the reliability of research results and fosters a culture of transparency and continuous learning.
Yet, in practice it is often difficult to implement consistently. Getting started, if you&amp;rsquo;ve never done it before, can be hard. That is why we shared our experience and checklists.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://inespereira.me/posts/code_review_llms/featured.png"/></item></channel></rss>