letscodeit.devnotes from the build

HERO

SHORT NOTES

Quick takes, product updates and stray thoughts — the length of a tweet.

NOTES

FOOTER

letscodeit.devnotes from the build

A blog about code, design and the slow art of shipping software that people actually want to use.

PRODUCT

Changelog
Roadmap
API

COMPANY

About
Blog
Notes

RESOURCES

Guest post
RSS feed
Docs

© 2026 letscodeit.dev© 2026 letscodeit.dev — Built in public.

Terms·Privacy·Cookies·License

NOTE

·

Comments

FEATURED POSTS

03 / 03

June 19, 2026

17 min read

We skipped Contentful: GitHub as a CMS for our Next.js blog

We publish letscodeit.dev blog posts from a separate GitHub repository. The Next.js app fetches markdown at runtime with a one-hour cache,…

Dev Team

June 17, 2026

10 min read

GEO for developers: what gets cited by ChatGPT and Perplexity

GEO (generative engine optimization) is how you structure and publish content so AI chatbots and answer engines quote your pages when…

Dev Team

May 28, 2026

9 min read

Token Economics: What Your Text Actually Costs

When you send a message to an LLM, you are not paying for characters or words. You pay for tokens . A token is the unit the model splits…

Dev Team

A recent exploration into optimizing Postgres… | Let's Code It

NOTE

A recent exploration into optimizing Postgres…

/ notes·/ A recent exploration into optimizing Postgres…

Dev Team·July 24, 2026

A recent exploration into optimizing Postgres LISTEN/NOTIFY-backed data streams has demonstrated scalability, achieving 60,000 writes per second on a single Postgres server with millisecond-scale latency.

LISTEN/NOTIFY allows for efficient notification-based streaming, avoiding the resource-intensive polling method. The initial implementation faced throughput limitations due to a global lock during NOTIFY, capping performance at 2.

Source: dbos.dev

Comments

Comments (0)

No comments yet. Be the first to share your thoughts.