Evan Oman

@Tusharab2004 Apply everywhere Get rejected Randomly get inbound msg or know someone with an opening Repeat

how to survive in tech apply everywhere get rejected randomly get opportunity repeat

@andrewarruda Cool stuff @polyphilz 😎

someone should make a coffee table book of the billboards of san francisco

@JacobAShell Learning how you decide what counts as a tributary versus the main stem broke my brain while reading _Undaunted Courage_ Turns out the ‘Mighty Mississippi’ is really just a path-dependent historical accident

The "Mississippi River" designation should actually follow the Missouri, which is longer and more impressive than than upper Mississippi (which could be called the Minneapolis River or Mississippi North Fork or something or other)

claude navigating me around the code base

Opportunities everywhere for those with eyes to see

@its_joeyp @DJ_CURFEW Just gotta build a CLI for agents around their API :D github.com/EvanOman/click…

@DJ_CURFEW Gotta be honest, we recently left Clickup because there wasn’t an MCP or Webhook support for our openclaw. You guys built an Incredible product, truly was blown away at first, we just didn’t want to use the agent product. Watch how many customers stay if you add those.

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

They are clearly subsidizing power users relative to the API rates. The real question is whether it's an overall subsidy relative to their underlying cost.

@_colemurray @dexhorthy @GeoffreyHuntley Nuking tmux support would be the biggest self-own of all time

@dexhorthy @GeoffreyHuntley lol we live in the worst timeline inb4 tmux detection and block

hey surprise - you can just launch interactive in tmux and then tail the jsonl - shipped a small wrapper...ralph loop iterating to full parity rn github.com/dexhorthy/shan…

@dexhorthy @wschenk I mean who hasn't gone down the rabbit hole of controlling Claude Code via tmux pane input / output? 😂

@theo @ClaudeDevs Why should Anthropic subsidize 3rd party harnesses?

@ClaudeDevs Framing this as a free credit instead of a regression for users is wild. Now I have to make the Claude Code experience on T3 Code significantly worse in order to keep using the 25x subsidization provided on a Claude Code subscription. x.com/theo/status/20…

Starting June 15, paid Claude plans can claim a dedicated monthly credit for programmatic usage. The credit covers usage of: - Claude Agent SDK - claude -p - Claude Code GitHub Actions - Third-party apps built on the Agent SDK

who is building the dark forest for claude msgs?

lolol

@VazeKshitij We should keep a library with pre ai era books

Developers making their monthly migration to Claude Code from Codex

Effective today, we are: 1) Doubling Claude Code’s 5-hour rate limits for Pro, Max, and Team plans; 2) Removing the peak hours limit reduction on Claude Code for Pro and Max plans; and 3) Substantially raising our API rate limits for Opus models.

gpt 5.5 has goblins and can think. claude 4.7 doesn’t have goblins and can think. so it’s not the goblins that make the models think, it’s something else entirely

@cremieuxrecueil Very simple model w/ very simple thresholds (why 2 std dev?) -- not sure what there is to learn from this? Possessing the intersection of rare traits is rare?

I simulated 100,000 people to show how often people are "thrice-exceptional": Smart, stable, and exceptionally hard-working. I've highlighted these people in red in this chart:

@tayloramurphy Code _is_ data after all..

sweet baby jesus

Tremendous alpha in not going insane in the 20s