v0 and production: which responsibilities still need checking?
Review the February and June 2026 announcements with an operations checklist, separating documented features from untested capabilities.
Read the articleCode, projects and ideas. What I learn while building applications, and what I want to share.
Review the February and June 2026 announcements with an operations checklist, separating documented features from untested capabilities.
Read the articleA dependency moves from 1.2.2 to 2.0.0. The first number signals a change that may require adapting your code. How should you read these numbers?
Read the articleWhere do you start with existing code? A business flow helps choose a first fix and verify its effect.
Read the articleWhen a project has few tests, starting with behaviour that would be costly to break helps choose the first scenario to protect.
Read the articleSomeone discovering your pull request should be able to understand the problem and verify the fix. Here is how to provide that context.
Read the articleA page seems slow: how can you identify the wait that affects users and measure a correction's effect under the same conditions?
Read the articleName the problem before comparing solutions, then consider adoption and maintenance costs beyond the initial installation.
Read the article