<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pseudocode on Scholion</title><link>https://scholion.thluiz.com/tags/pseudocode/</link><description>Recent content in Pseudocode on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/pseudocode/index.xml" rel="self" type="application/rss+xml"/><item><title>How To Solve Coding Problems Like A Pro</title><link>https://scholion.thluiz.com/notes/how-to-solve-coding-problems-like-a-pro/</link><pubDate>Sat, 09 Apr 2022 17:04:45 -0300</pubDate><guid>https://scholion.thluiz.com/notes/how-to-solve-coding-problems-like-a-pro/</guid><description>The article lays out a four-step approach to solving coding problems: understand the problem, divide it into subproblems, research what is missing, and write pseudocode before coding.</description></item><item><title>5-Step Strategy You Can Use for Your Next Coding Interview</title><link>https://scholion.thluiz.com/notes/5-step-strategy-for-coding-interviews/</link><pubDate>Wed, 26 Aug 2020 19:31:11 +0000</pubDate><guid>https://scholion.thluiz.com/notes/5-step-strategy-for-coding-interviews/</guid><description>The post proposes a five-step interview routine: clarify the problem, test examples, ask about constraints, pseudocode the approach, then code while talking and optimize after reaching a working solution.</description></item></channel></rss>