A diverse set today, something for the CLI, something for PHP internals, something for the frontend, and two pieces about developer experience at a higher level.
Kitty Giraudel’s Beautiful CLI Prompt with Starship is a clean walkthrough of setting up Starship, the cross-shell prompt written in Rust, with sensible defaults and a few customizations. Starship is fast, works identically across bash/zsh/fish, and surfaces contextual information (git branch, language version, last command exit code) without requiring a heavy framework. If your terminal prompt is still the default, this is a pleasant 20-minute improvement.
Freek’s accessing private properties and methods in PHP is pure Freek: concise, practical, a little dangerous. He covers using PHP’s ReflectionProperty and ReflectionMethod to bypass visibility constraints, the canonical use case being tests on legacy code where exposing things public just for testability feels like the wrong trade-off. Worth knowing exists, worth being judicious about using.
Frontend Masters’ piece on form-associated custom elements covers a browser API that’s been around for a couple of years but still isn’t widely used. Form-associated custom elements let your web components participate properly in HTML forms, they can be validated, submit values, reset with the form, and receive disabled state. The alternative (a custom element that wraps a hidden input) is fragile and weird. If you’re building component libraries that need to work inside forms, this is the API you actually want.
The docs-in-repo post makes a case I’ve been half-convinced by for years: documentation lives longer and stays accurate when it’s co-located with the code it describes, versioned alongside it, and updated in the same pull requests. External wikis drift. Notion pages go stale. A docs/ folder next to the source is discoverable, diffable, and reviewable. The post is particularly sharp on how agentic tools benefit from this, Claude Code can read your docs directory to understand conventions without you having to explain them every session.
OpenStatus’s Nobody Should Hand-Code a Data Table in 2026 documents a genuinely thoughtful refactor of their open-source data-table-filters project. The central improvement is a single-source-of-truth schema that derives column definitions, filter config, Zod validation schemas, and state adapters automatically, collapsing five previously fragmented files into one. Pair this with the shadcn registry for distribution and a Claude Code agent skill that understands how to assemble it, and you get a data table that installs itself. The engineering is solid and the product is open source.