<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dates on ilham.dev</title><link>https://ilham.dev/tags/dates/</link><description>Recent content in Dates 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/dates/index.xml" rel="self" type="application/rss+xml"/><item><title>How I convert time zones for logs and meetings without doing mental math</title><link>https://ilham.dev/posts/how-to-convert-time-zones-for-logs-and-meetings/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-convert-time-zones-for-logs-and-meetings/</guid><description>Time zone mistakes cause confusing incident timelines and missed meetings. I prefer converting explicitly instead of doing the offset in my head.
The Time Zone Converter tool is useful because it lets me check the result in a small, controlled place before I use it in a bigger workflow.</description></item><item><title>How I read Unix timestamps without guessing seconds or milliseconds</title><link>https://ilham.dev/posts/how-to-read-unix-timestamps-without-guessing-seconds-or-milliseconds/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-read-unix-timestamps-without-guessing-seconds-or-milliseconds/</guid><description>A timestamp bug often starts with one question: is this value in seconds or milliseconds? Getting that wrong can move dates to 1970 or far into the future.
The Timestamp Converter tool is useful because it lets me check the result in a small, controlled place before I use it in a bigger workflow.</description></item></channel></rss>