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

Docs
Community
Status
RSS feed

© 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 logging bug in Codex's CLI caused excessive data writing… | Let's Code It

NOTE

A logging bug in Codex's CLI caused excessive data writing…

/ notes·/ A logging bug in Codex's CLI caused excessive…

Dev Team·June 23, 2026

A logging bug in Codex's CLI caused excessive data writing to local SSDs, potentially reaching 640 TB per year.

The issue stemmed from Codex SQLite feedback logs being the main source of continuous data writing. On a 1 TB SSD, this could result in approximately 640 full-drive writes annually, surpassing typical consumer SSD endurance ratings of around 600 TBW. Two pull requests have been merged to address the problem, reportedly reducing log volume by 85% and closing the issue.

Source: github.com

Comments

Comments (2)

K

Kate Morrison·June 23, 2026

This is a huge issue for users relying on Codex. 640 TB per year is way beyond what most SSDs can handle. Glad to see it's being addressed.

D

Daniel Cooper·June 23, 2026

Reducing log volume by 85% is a solid fix, but it raises concerns about how this was overlooked in the first place. Continuous logging at that scale should have triggered alerts.