<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unix-Philosophy on Scholion</title><link>https://scholion.thluiz.com/tags/unix-philosophy/</link><description>Recent content in Unix-Philosophy on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Fri, 19 Apr 2013 09:47:24 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/unix-philosophy/index.xml" rel="self" type="application/rss+xml"/><item><title>Unix Philosophy and Node.js</title><link>https://scholion.thluiz.com/notes/unix-philosophy-and-node-js/</link><pubDate>Fri, 19 Apr 2013 09:47:24 -0300</pubDate><guid>https://scholion.thluiz.com/notes/unix-philosophy-and-node-js/</guid><description>The post reframes the Unix Philosophy for Node.js: modules should do one thing well, compose through streams, stay small, and favor pragmatism, iteration, and maintainability over purity.</description></item></channel></rss>