@cjzafir — add a docs folder to cut AI coding tool hallucinations
Here's the Master Trick to work with Cursor and Windsurf.
It will remove 80% of AI hallucinations and 60% less code errors.
You need to create a 'Documentation" folder in the root directory.
Then you need to attach all your project docs to that folder
Let me explain....
Smart, because the root cause of most AI coding tool hallucinations is context poverty — the model is guessing at your project's conventions instead of reading them. A Documentation/ folder that you actively keep in sync gives Cursor and Windsurf something concrete to attach to the conversation. The percentages feel made up, but the underlying mechanic is sound: the more grounded the context, the less the model needs to invent.
@rwieruch — React component composition to escape prop drilling
React Architecture Insight
Deeply nested components can hinder scalability and maintainability in React applications. Rather than relying on ...
❌ tightly coupled feature components ❌ excessive nesting ❌ prop drilling
... adopt component composition to lift shared logic
This is the pattern that separates codebases that stay maintainable from ones that turn into spaghetti around the six-month mark. Component composition — passing components as props or using children — is the move. Context is a sledgehammer; composition is a scalpel. Robin's visual is worth saving for the next time someone argues for prop drilling "just this once."
@adamsilverman — AI Agents weekly roundup
Here is everything that happened in AI Agents this week 🧵
(save for later)
Honestly just saved this because the AI agents space moves fast enough that a curated weekly thread is actually useful. If you're building anything with agentic workflows right now, the signal-to-noise on individual announcements is brutal — a compiled thread cuts through that.
@DIGITALEARN_1 — hacker search engines
HACKER search engines 🤯
The title is hypey but the underlying content is a useful reference. Shodan, Censys, Greynoise, FOFA — knowing these exists matters if you do any security work, pen testing, or just want to understand your own exposure surface. Worth a bookmark for the next time someone asks "how do attackers find this stuff."
@rexan_wong — if your app doesn't support Google auth, reconsider
i never realized it, but if ur app doesn't support @Google auth, you're ngmi
nobody wants to spend their time and energy entering their email and thinking of a strong password
oftentimes google auth is all you need
that's why in my auth, I display a nice oil paining
The oil painting detail is a non-sequitur but the core point holds — OAuth with Google as the single provider is a perfectly reasonable default for most B2C products. Fewer fields, no email verification loop, no password resets. The replies pushed back hard on lock-in and enterprise use cases, which is fair, but for early-stage apps where your users are primarily Google Workspace people, just ship it.
