Home About Blog GitHub 中文

CHEN.TAO · ink notes

Sketch the idea
into the code

Chen Tao's site. Notes on Rust and Go, design patterns.
The path is left for whoever comes next.

Open source Rust Design Patterns and Best Practices · GitHub @hilerchyn

Blue-ink line drawing of a desk with an open notebook, fountain pen, coffee cup, and laptop

desk plan · ink

Rust design patterns Go engineering notes Graphs and translation

Sketch the problem first Then write the answer into the repo

The gap

The process hides in commits

Patterns, translations, and graphs scatter across repos. Later you have to dig through history to find the path again.

Lay the path out

Write design patterns as readable notes. Keep DAG, web, and translation work on one line so they can be compared.

Public and searchable

No account wall. Open GitHub to read the source, ask a question, and walk back through the commits.

What you take with you

Three things you can use right away

Blue-ink line drawing of an open technical notebook with code marks and flow diagrams

Notes you can compare

Rust Design Patterns and Best Practices is open in the repo, with the pattern next to the code.

Blue-ink line drawing of a compass resting on a folded map

From the original to Chinese

A Chinese translation of Writing Web Applications from the Go site, following the original structure.

Blue-ink line drawing of a directed acyclic graph with nodes and arrows

A graph you can run

A directed acyclic graph in Go. Seeing how the nodes connect is clearer than a definition alone.

How to use this site

Three steps, no signup

1

Read one page of notes

Start from the home page or a README and see how the problem was written down.

2

Open the matching repo

The patterns, graphs, and translations in the notes all have source you can clone.

3

Ask on GitHub

Open an Issue. It is all public. You do not leave an email.

Questions

A few answers first

Whose site is this?

Chen Tao, GitHub username hilerchyn. I write Rust and Go, and I translate technical writing.

What will I find here?

Open source repos, design pattern notes, a graph implementation, and a Chinese translation of the Go web app article.

Do I have to pay for the code?

No. The repos are public. Clone them, leave whenever you want, and you never leave a card.

How do I get in touch?

[email protected] +86 159 5480 3856 You can also open an Issue on GitHub @hilerchyn .

What is this site built with?

Rust, Axum, and Askama. Static files are packed into the binary. Pages are server rendered templates.

Why blue ink and straight lines?

Design patterns and graphs start with edges. Straight lines work like a drawing: structure before ornament. The abstract part sits in the grid and the empty space, then it goes into the code.

Open a repo. Start with one page of notes.

Source is public. Questions are public. No signup, and no email to leave.