People saying Codex has more generous rate limits than Claude Code is most propaganda (Comparing Max plans here) Took me 6 hours of multi-threaded work to knock off 50% of the weekly limits

Getting rate-limited while having both Claude Code & Codex's Max plans is a different kind of .. vibe. That too when Claude gave complementary refresh just 2 days ago 😅

Automation has always promised to free up time for what matters. The uncomfortable part of the Anthropic piece is the suggestion that when AI starts handling the work that gave people a sense of contribution and belonging, there's no obvious replacement waiting on the other side. Saving hours in a week is one thing, knowing what to do with the space that opens up is a completely different problem.

There's a whole ecosystem built around this. The "AI whisperer" role exists because most boomer executives won't take a 28-year-old seriously, no matter how technically sharp they are. So companies hire someone who looks the part to translate, and they pay a premium for the optics. The problem is that optics don't compound. Actual capability does. And the gap between companies doing real work with AI and companies performing AI awareness is widening faster than most people realize.

Two ways to use Contextli: 1. Speak the message. Get polished, formatted text. 2. Speak the intent. Get a complete, context-aware reply. One hotkey. Works everywhere. Privacy-first. $79 lifetime or try free. contextli.com/

What makes this cycle particularly brutal is that the candidates who got laid off aren't less skilled than they were 18 months ago. The market didn't change their abilities, it changed the leverage they had when negotiating. That gap between actual capability and perceived market value is going to take a long time to close, and a lot of people are going to underprice themselves in the meantime just to get back to stable ground.

Wonder how much of this is a deliberate strategy to retain headcount on paper while quietly pushing people out through role reassignment. Cheaper than layoffs, but the talent loss ends up being worse because the people who leave first are always the ones with the most options.

Developer productivity hack nobody uses: After finishing a PR, hit hotkey, explain what you changed and why in 20 seconds. Get a formatted PR description with the right sections, linked context, and clear rationale. Your code review self will thank your PR-writing self.

LinkedIn is to social media as the Internet Explorer is to browsers. Literally 20 posts from different creators on my feed complaining about getting a strike for posts made months or YEARS ago! (Note: I haven't gotten any strike personally -- but this so bizarre that I had to tweet about it) @elonmusk might have been right about LinkedIn after all

You: funny, sharp, and engaging in conversation. Also you: robotic, stiff, and overthought in email. It's not a writing problem. It's a medium problem. Your voice carries your personality. Your keyboard doesn't. Start with the voice. Let the tool handle the rest.

LinkedIn DM backlog strategy: Open message. Hit hotkey. "Thank them for connecting, mention I saw their post about hiring, suggest a quick call if they're open to it." Contextli reads the conversation. Writes the reply. Keeps your voice. 10 DMs in 4 minutes instead of 40.

Therapist math: 50-minute session. 15 minutes of notes after. 8 sessions a day. That's 2 hours of documentation. Every day. Speak your observations between sessions. Get structured SOAP notes instantly. Give those 2 hours back to your patients, or yourself. contextli.com/

Writing used to be about communicating. Now it's about performing. We wordsmith Slack messages. Agonize over email punctuation. Draft a two-sentence reply like it's a press release. What if you just said what you meant and let the formatting handle itself?

That internal post about teams who build their own AI replacement getting 5 years of comp and then being let go.. and it got heavy upvotes.. says something about where employee psychology is right now. When the most upvoted idea in your company is a structured exit package for self-elimination, the workforce has already internalized that the jobs are going. The question has shifted from "will this happen" to "what's the best deal I can negotiate on the way out."

What "Contextli sees your screen" actually means: You're looking at a client email. You say "politely push the deadline two weeks." It reads the email. Sees who it's from. Understands the thread. Writes a complete reply matching the context. You gave direction. It did the writing.

Nobody warns you that becoming a manager means becoming a full-time writer. Emails. Slack messages. Performance feedback. Status updates. Meeting recaps. Your actual job is between the paragraphs.

One thing this surfaces for me is how much of the anxiety is really about signal lag. People are making career decisions based on outcomes they're observing now.. but those outcomes were set in motion 4 to 6 years ago. The Anthropic employees who hit $20M didn't know they were making a retirement-level bet when they joined. They made a bet, it worked, and now everyone reverse-engineers it as obvious. The people vibecoding their way to "economic enlightenment" today are essentially trying to replicate a specific historical moment that already happened. Most won't get there.. not because they lack talent, but because the window they're trying to climb through is a different shape than the one that opened before.

Most people don't know: a single Context in Contextli can hold up to 20,000 words of instructions. That's your entire tone guide, formatting rules, audience notes, and edge cases, loaded and applied every time you speak. Not a prompt. A permanent writing partner. contextli.com/

Declaring something "over" tends to say more about the vantage point than the actual state of the field. Plenty of systems running in production today will need people who understand what's happening below the abstraction layer.. not because AI can't help, but because judgment about failure modes, edge cases, and system behavior doesn't come from prompting an agent and checking back after lunch. The mourning might be premature.

12 unread Slacks. Each one needs a reply. Old way: read, type, read, type, read, type. 25 minutes gone. New way: read, hotkey, "approve but ask them to run it by legal first." Read, hotkey, "say nice work, ship it." Read, hotkey, "push to next sprint." Same 12 replies. Under 3 minutes.