3 ms·
This is exactly the concern I'm trying to solve for—not against. You're right that optimizing for reach creates influencer theater. What if the product optimiz
by dlukdsza 1y ago
This is exactly the concern I'm trying to solve for—not against.
You're right that optimizing for reach creates influencer theater. What if the product optimized for credibility within a smaller, technical audience instead?
Instead of "broadcast to everyone," what if it was:
- Daily check-ins capture real work
- Weekly digest shared to niche communities (Dev.to, HN, technical Slack/Discord)
- Audience: 100 devs who understand your domain > 10,000 LinkedIn randos
Re: automated evaluation of real progress—that's fascinating. How would you validate "novel work" vs "performance theater"? Is it context (where shared), substance (depth of notes), or something else?
Your smaller-audience point resonates. Would you use a tool that helped you share technical progress with ONLY people who'd understand it, while filtering out the influencer noise?
- alganet 1y ago> How would you validate "novel work" vs "performance theater"? I don't know. That's future shit, no one invented this yet. But I think someone will. Otherwise, hiring will become very difficult. As code becomes more and more commoditized, it should become easier to see. > Would you use a tool that helped you share technical progress with ONLY people who'd understand it, while filtering out the influencer noise? I wouldn't trust it today.
- dlukdsza 1y agoFair. Trust has to be earned, not claimed. How about having some guardrails, like requiring code snippets, and "lessons learned" before even seeing proposed AI-enhanced content? Obviously, people are people, and every tool can be abused (in a good and a bad way).
- alganet 1y agoFor the trust thing, don't use me as a benchmark. I am extremely distrustful of anything. Other people aren't, you're probably fine.