📝 Add new threads 2025-08-31

Author: AnandChowdhary

threads/2025/constraints-shape-the-architecture.md

@@ -0,0 +1,25 @@
+---
+title: Constraints shape the architecture
+date: 2025-08-30T13:45:09.641Z
+url: https://x.com/AnandChowdhary/status/1961787239169683563
+---
+
+Pre- Flexbox and CSS Grid, equal height cards in a responsive grid meant floats, clearfix, and a bit of JS. On Dec 25, 2015 I shipped One Grid, under 1 KB, for fixed-height infinite blocks. Christmas day hack, yes really. The quiet lesson: constraints pick the architecture. 📐👇  
+  
+How it worked:  
+• Layout: floats plus a micro clearfix. Gutters with negative container margins and child padding using border box.  
+• Height: tiny JS grouped cards by visual row via offsetTop and set the max height inline.  
+• Behavior: debounced resize and reflow. No deps.  
+  
+Tradeoffs:  
+• Source order controlled layout  
+• Forced reflow on measure, thrash on long lists  
+• Late images and webfonts needed another pass  
+  
+What aged well vs not:  
+• Well: a strict bytes budget under 1 KB forced clarity. Zero tooling kept adoption simple.  
+• Not: floats, clearfix, and JS equalization. Today I would reach for Grid or Flex with gap, align items stretch, grid auto rows, aspect ratio, and object fit. Less jank and better a11y. Bigger lesson: pick primitives that are converging and design to delete code later.  
+  
+If I built it today I would use grid template columns repeat auto fill with minmax, gap for gutters, aspect ratio for tiles, and maybe container queries instead of page wide breakpoints.  
+  
+Here's the project: <https://github.com/AnandChowdhary/one-grid>

threads/2025/pronouns-decide-product-voice.md

@@ -0,0 +1,25 @@
+---
+title: Pronouns decide product voice
+date: 2025-08-30T21:15:12.561Z
+url: https://x.com/AnandChowdhary/status/1961900485507678574
+---
+
+My take after reading the great [@adamsilverhq](https://x.com/adamsilverhq): "My" vs "Your" sets the product's point of view. Pronouns decide who's talking and who owns the data. Get that wrong and nav, support copy, and i18n go sideways.  
+  
+For navigation, drop pronouns when the object is obvious. Orders. Cases. Settings. Clean and consistent.  
+  
+When scope matters, bind it in state, not labels. Cases \[All | Assigned to me\]. The label should reflect the query. "Your cases" hides the real rule. The system must actually filter to the current user.  
+  
+Adam's rule is solid: When the system speaks to the user, use second person. When the user speaks to the system in controls, first person can help signal ownership.  
+  
+I still lean on a clear question with concise options. Better for screen readers and localizers. Let the legend or label carry the pronoun so options stay short.  
+  
+Edge cases need more than a rule of thumb. Delegated access, shared inboxes, role switching, impersonation. "Your" is fuzzy unless you show who is active.  
+  
+Treat pronoun binding as state. Make the actor of record visible and keep copy and filters in sync with that state.  
+  
+What I would measure next: cross channel instruction errors, time to complete role switch tasks, and localization defects around formal vs informal "you".  
+  
+Until then, use neutral nouns in nav, "your" in guidance, and "my" only when the user is clearly speaking.  
+  
+Adam's post: <https://adamsilver.io/blog/your-vs-my-in-user-interfaces/>

threads/api.json

@@ -1,4 +1,26 @@
 [
+  {
+    "slug": "pronouns-decide-product-voice",
+    "path": "threads/2025/pronouns-decide-product-voice.md",
+    "source": "https://github.com/AnandChowdhary/notes/blob/main/threads/2025/pronouns-decide-product-voice.md",
+    "title": "Pronouns decide product voice",
+    "date": "2025-08-30T21:15:12.561308Z",
+    "excerpt": "My take after reading the great @adamsilverhq: \"My\" vs \"Your\" sets the product's point of view. Pronouns decide who's talking and who owns the data. Get that wrong and nav, support copy, and i18n go sideways.",
+    "attributes": {
+      "twitter": "https://x.com/AnandChowdhary/status/1961900485507678574"
+    }
+  },
+  {
+    "slug": "constraints-shape-the-architecture",
+    "path": "threads/2025/constraints-shape-the-architecture.md",
+    "source": "https://github.com/AnandChowdhary/notes/blob/main/threads/2025/constraints-shape-the-architecture.md",
+    "title": "Constraints shape the architecture",
+    "date": "2025-08-30T13:45:09.641473Z",
+    "excerpt": "Pre- Flexbox and CSS Grid, equal height cards in a responsive grid meant floats, clearfix, and a bit of JS. On Dec 25, 2015 I shipped One Grid, under 1 KB, for fixed-height infinite blocks. Christmas day hack, yes really. The quiet lesson: constraints pick the architecture. 📐👇",
+    "attributes": {
+      "twitter": "https://x.com/AnandChowdhary/status/1961787239169683563"
+    }
+  },
   {
     "slug": "codex-unifies-the-workflow",
     "path": "threads/2025/codex-unifies-the-workflow.md",