Practitioners in Lenny's subscriber Slack are working through four concrete problems this week: countering a lowball job offer without torching the negotiation, getting design voices into product decision rooms, and sourcing vetted resources for building MCP servers from scratch.
The negotiation thread is the one to read in full. Members share specific counter-offer language, the exact timing of when to push back, and how to frame competing offers when you only have one. The design seat discussion goes beyond the usual 'get a seat at the table' advice and into org structure specifics: who owns the meeting, who owns the doc, and what changes when design reports to product versus engineering.
The MCP server thread is early but useful, covering which SDKs are production-ready and which are still tutorials dressed up as documentation. If you are building agent tooling or evaluating the Model Context Protocol for internal use, the community's field notes beat the official docs on practical edge cases.
[READ ORIGINAL →]