Pages

Topics

Tools

↑↓navigate↵openescclose

About RYUSLOG DEV

A working library of programming syntax guides and browser-based developer tools, for developers who need the exact behaviour of one thing right now.

Last updated: November 16, 2026

01

What this site is

RYUSLOG DEV publishes short, practical guides about programming syntax: how a language feature actually behaves, what it returns, and where it breaks. Each guide covers one concept, usually with a runnable example, the edge cases that surprise people, and a comparison table when two constructs are easy to confuse.

The library covers Python, Java, C#, TypeScript, Go, Rust, and more, and it ships with 15 developer tools that run entirely in your browser.

02

How guides are written

Every guide is written around code you can run: the smallest working example first, then the details that matter in production, such as null handling, encoding, ordering, or version differences.

Guides are written in English for working developers who already know how to program and need the exact behaviour of one method, modifier, or configuration key. Pages are reviewed for accuracy and for the examples' output before they are published, and they are updated when a language or tool changes.

03

Developer tools

The tools cover formatting and data conversion, encoding and inspection, and time and text utilities: JSON, YAML, diffs, regular expressions, JWTs, Base64, URLs, hashes, UUIDs, timestamps, cron expressions, and colour contrast.

All of them run in your browser. Nothing you paste is uploaded, logged, or stored on a server.

04

Who runs it

RYUSLOG DEV is an independent project run by a single developer (@rshday). There is no company, agency, or editorial team behind it, so corrections and requests go straight to the person who writes the pages.

05

How it is funded

The site is supported by display advertising through Google AdSense. Advertisements are placed automatically and are kept separate from the guides.

Advertisers have no influence on what is published, and no guide contains paid placement or sponsored recommendations.

06

Corrections and requests

If a guide is wrong, out of date, or unclear, or you would like a syntax topic or a developer tool covered, write to rshday@gmail.com. Corrections that come with a source or a failing example are the fastest to resolve.

Topics covered

Get in touch

Email rshday@gmail.com for corrections, topic requests, or policy questions. Source and tooling questions are also welcome on GitHub at github.com/rshday.