<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Regex on ilham.dev</title><link>https://ilham.dev/tags/regex/</link><description>Recent content in Regex on ilham.dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0700</lastBuildDate><atom:link href="https://ilham.dev/tags/regex/index.xml" rel="self" type="application/rss+xml"/><item><title>How I test a regex before putting it into code</title><link>https://ilham.dev/posts/how-to-test-regex-before-using-it/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-test-regex-before-using-it/</guid><description>Regex is powerful, but it is also easy to get almost right. “Almost right” is the problem. A regex can match too much, too little, or the right thing in your test but the wrong thing in production.</description></item><item><title>How I use grep without fighting the flags</title><link>https://ilham.dev/posts/how-to-use-grep-without-fighting-regex/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-use-grep-without-fighting-regex/</guid><description>grep is the command I use when I know some text exists somewhere, but I do not remember which file contains it.
The basic idea is simple:
grep &amp;#34;database&amp;#34; app.log Plain meaning:</description></item></channel></rss>