Stacknote Demo

Welcome to Stacknote

Mon, 24 Aug 2026 00:00:00 +0000

Stacknote is designed for technical writing that values clarity and character. It gives a personal engineering blog a recognizable visual voice without turning every page into a product landing page.

A complete reading experience

The reading page keeps the article at the center while still providing a table of contents, highlighted code, responsive tables, related articles, and strong keyboard focus states.

func main() {
 fmt.Println("field-tested notes")
}

The same design carries through the homepage, archives, tags, search results, and author page. Local covers are processed by Hugo into responsive WebP variants, while articles without images keep a deliberate text-first layout.

Trace the Request Before You Tune the Service

Mon, 17 Aug 2026 00:00:00 +0000

A slow endpoint is rarely one indivisible wait. It is a chain: connection setup, queueing, application work, storage, and the trip back to the caller. The useful question is not simply “why is this request slow?” but “where did this request spend its time?”

Start with one trace

Pick one real slow request and write down its stages before changing a timeout or adding a cache.

gateway 18 ms
queue 142 ms
application 31 ms
database 24 ms
response 6 ms

The application function is not the bottleneck in this example. Making it twice as fast saves about 15 milliseconds while the request still waits 142 milliseconds before the function starts.

The Queue Is Part of Your API Contract

Mon, 10 Aug 2026 00:00:00 +0000

Moving work behind a queue changes latency, ownership, and failure semantics. It does not make those concerns disappear.

Acknowledgement is not completion

An HTTP 202 Accepted response says the server accepted responsibility for attempting the job. It should not imply that the job succeeded, or even that a worker has started it.

Clients need a durable job identifier and a status model they can understand:

{
 "job_id": "job_7f31",
 "state": "queued",
 "status_url": "/jobs/job_7f31"
}

Retries create duplicates

A worker can finish the side effect and crash before acknowledging the message. The queue then delivers the same message again. That is ordinary at-least-once delivery, not an exotic edge case.

Measure the Tail, Not Just the Average

Mon, 03 Aug 2026 00:00:00 +0000

An average compresses a distribution into one comfortable number. Production latency is rarely comfortable or evenly distributed.

Suppose 99 requests finish in 40 milliseconds and one request takes four seconds. The average is about 80 milliseconds. That number describes almost nobody: most users saw half of it, while the unlucky user waited fifty times longer.

Keep the distribution

Track at least a few percentiles and request volume together:

Metric	Value
P50	40 ms
P95	58 ms
P99	4.0 s
Requests	100

Percentiles also need enough samples. A P99 calculated from a tiny window is mostly a story about one request, so retain histograms and compare equivalent traffic windows.

A Small Checklist for Shipping Technical Notes

Mon, 27 Jul 2026 00:00:00 +0000

A publishing checklist should be short enough to use every time. Mine asks five questions.

Does the opening state the problem without requiring a page of background?
Do commands and code samples still run?
Do external claims link to the original source?
Does every informative image have useful alternative text?
Does the production build complete without warnings?

For a Hugo site, the final check can remain pleasantly boring:

hugo --panicOnWarning --minify

Preview the generated site at both narrow and wide viewport sizes. Long titles, tables, code blocks, and navigation labels expose layout assumptions faster than placeholder text ever will.

About

Mon, 01 Jan 0001 00:00:00 +0000

I am Example Author, a software engineer who writes about systems that have survived contact with production.

Stacknote is designed for notes that combine practical experience with enough technical depth to remain useful after the week they were published. This example site demonstrates the theme’s article typography, navigation, search, archives, taxonomies, responsive covers, and structured metadata.

The name, role, biography, links, homepage sections, and article collection are all configured by the site rather than hard-coded into the theme.

Search