Dr. Cronkenstein
386 posts


@wahab_twts Exactly, a 20-minute lag already means the architecture failed the zero-RPO requirement.
English

@MolecularLab_ Fuck this boomer slop. Go back to Facebook. Muted
English

@Itsfoss One of our integration partners requires X9 certs, of which DigiCert literally has a monopoly on. Quite the racket!
English

You'll be surprised that SSL certificates are still being sold.
Erwin@Erwin_AI
Remember the days when you had to BUY an SSL cert?
English

@houseflipperny @Jacob_Naviaux You get how to be a jerk? Cool!
English

Fixer upper gets listed for $250k.
I offer $180k with 3% commission — I’m a licensed agent and my company is the buyer.
Plan is to wholesale it for $190k. Needs $75k in work and will be worth $320k after repairs.
Listing agent says too low.
4 weeks later our CRM notifies me the list price dropped to $225k. I follow up. Agent still says $180k is too low.
Another month goes by. CRM notifies me again — price drops to $210k. I follow up. Agent says they think it’ll work.
I draft the offer, send it over, and it gets accepted.
We price the deal at $190k and sell it — signed contract and EMD in hand.
While we’re still in DD, I tell the agent my buyer needs a $20k price reduction to move forward, but they’re ready to wire EM and waive the rest of DD.
Seller meets us halfway. Price drops to $170k.
We make $25k.
That’s the exact play we run wholesaling MLS properties.
English

@simonlast Let’s see some code from this workflow. This type of workflow is nothing new. It’s been the same play for how many years, and every time you look at the code it’s so oooo bad.
English

@0xADZ I think we are all lucky to have a handful
They are now indeed all worth $1m+. Far more if you are at scale.
English


@NaVuddyrinOT6 @HumanoidBits @DJ_CURFEW @Cleverbilling What are you comparing against? How can you say things are taking longer?
English

@DrCronkenstein @HumanoidBits @DJ_CURFEW @Cleverbilling You see instantly how the time to fix small problems is getting wider after laying off their personnel and still optimistic?
English

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.
English

@DJ_CURFEW ClickUp really needs to invest in paying off technical debt. I see feature after feature released, but the site is slow, GitHub integration needs many improvements, sprint reporting metrics continue to have issues. Really hoping to see improvements rather than “ClickUp 5.0”!
English

@NaVuddyrinOT6 @HumanoidBits @DJ_CURFEW @Cleverbilling I’m no shill for them, and I definitely have issues with ClickUp. I agree that we need to see results. I’m cautiously optimistic.
English

@DrCronkenstein @HumanoidBits @DJ_CURFEW @Cleverbilling The discourse and the results aren't matching.
English

@DrCronkenstein @NaVuddyrinOT6 @DJ_CURFEW @Cleverbilling You’re literally arguing that it’s ok to be oblivious and yet powerful.
English

@HumanoidBits @NaVuddyrinOT6 @DJ_CURFEW @Cleverbilling Do you think he personally picked each person. Come on man
English

@DrCronkenstein @NaVuddyrinOT6 @DJ_CURFEW @Cleverbilling yeah doesn't know the nitty gritty but proceeds to fire people claiming he KNOWS who to fire and who to keep.
English

@NaVuddyrinOT6 @DJ_CURFEW @HumanoidBits @Cleverbilling I don’t expect the CEO to know the nitty gritty. I’m sure it’s some refactors of architectural choke points. I don’t get the flack you’re giving him here.
English

@DJ_CURFEW @HumanoidBits @Cleverbilling 2 weeks for just certain patterns? This ain't the gotcha you think it is.
English

@22Lamb22 @KyleKulinski This pic is as real as it gets man.
English

@DickSinnya @KyleKulinski You’re so gay for him it’s sad
English

@the_matt @KyleKulinski Yes. The entire ideology rests on this fact. 😆
English

@QuinnyPig @vercel @Cloudflare @awscloud I was ready to read some over the top/unrealistic AI bro slop, but this is actually a really great list!
English

Been thinking about what an "agent-native cloud" actually needs to look like. Mentioned this, and @Vercel's CEO replied that it'll be them. Cool! Here's the spec they (or @Cloudflare, or some startup not yet invented) actually have to hit.
It won't be @awscloud.
Thread...
Guillermo Rauch@rauchg
@QuinnyPig It'll be ▲. Would love your feedback. This is our primary focus!
English

@streamingdeluxe @SomaKazima2 It’s faked to get engagement.
English


















