Novice Adam

gutter kludge

[Novice Adam @NoviceAdam]

Synthesized wisdom of the day - “A validation built to produce a yes is not validation.”

[Novice Adam @NoviceAdam]

Back in my day we used to have to use Midjourney through Discord! 😂

[Midjourney @midjourney]

Announcing a new division of Midjourney called "Midjourney Medical"

[Novice Adam @NoviceAdam]

@maxkolysh Yep, and that leads to post-deployment managed services aka recurring revenue

[Novice Adam @NoviceAdam]

@LatentLich Same here

[Novice Adam @NoviceAdam]

@steipete @_ARahim_ @bcherny 01001000 01101001

[Novice Adam @NoviceAdam]

@edzitron Ed, how would you describe the taste of validation?

[Novice Adam @NoviceAdam]

Learning very quickly that the focus is not agents or tools. It’s the knowledge base. Extreme diligence in the metadata tagging and harness structure let you fly

[Jake @JustJake]

The problem with this, and why I think people are frustrated:

Nobody has taught folks how to do this

It feels both evidently the future and also somehow gatekept

[Novice Adam @NoviceAdam]

Mid 90s, my father purchases a used hot tub.
Problem - How do we get this across the yard?
Solution - pipe rolling: roll it forward, grab the pipes from the back, and repeat.
It worked!
He was beaming,
‘This is how the Egyptians built the pyramids!’

That’s agentic workflow
Don’t brute-force the heavy lift. Set your stack, manage your harness and deploy your agents like those pipes. Let them handle the load, cycle the tools forward as you progress, iterate relentlessly.

Build pyramids, not hernias

Side note - The Egyptians had interdimensional help. 😜

[Novice Adam @NoviceAdam]

@hthieblot Newgrounds & absolutepunk!

[Novice Adam @NoviceAdam]

@edzitron Silver lining- Financial roadblocks lead to innovation… that will eventually be gobbled up by the AI overlords 😃

[Novice Adam @NoviceAdam]

a lil OS native webkit cooked up for Hermes chat. ready to roll @NousResearch @Teknium

[Novice Adam @NoviceAdam]

Offically made the jump
@NousResearch

[Novice Adam @NoviceAdam]

@MichaelGannotti Me too brotha!

[Novice Adam @NoviceAdam]

@gkisokay It’s called the vibe hub, bro

[Novice Adam @NoviceAdam]

@babaliauskas @ghumare64 Foundational structure and tool calls

[Novice Adam @NoviceAdam]

What I’m learning about Git Proficiency

Basic/Junior (many vibe coders lack)
Init repo, add/commit/push/pull
Create/switch branches (main vs feature branches)
Resolve simple merge conflicts
Decent commit messages
Clone + set up remotes

Intermediate (what companies expect)
Branching strategies (Git Flow, trunk-based)
Atomic commits (no giant “WIP”)
Comfy merge conflicts
Intentional rebase vs merge (rebase -i to clean history)
stash, cherry-pick, reset (soft/hard/mixed)
.gitignore, hooks, basic CI/CD
Effective PRs/MRs + reviews
bisect to find when a bug was introduced

Advanced/Senior+
Git internals (objects, refs, index, packfiles)
Adv rebasing, reflog recovery, history rewriting
Submodules or monorepo management
Git hooks for enforcing standards
Optimizing large repos, LFS, partial clones Designing team workflows & Git policies

[slash1s @slash1sol]

HARVARD RELEASED A 65-MIN MASTERCLASS ON GIT & GITHUB BECAUSE VIBE-CODERS STILL DON'T KNOW HOW TO COMMIT

1 hour and 5 minutes of raw, no-nonsense version control architecture from the creators of CS50.

-> The moment you watch it, you realize why most modern developers are breaking their production branches.

Every tier-1 tech company is now filtering candidates who can't handle basic merge conflicts.

Git isn't a "nice-to-know" anymore -> it's compliance.

Your AI can write the code.
That wasn't the problem.

The problem is you don't know how to merge it without breaking the repo.

Don’t forget to bookmark it.

[Novice Adam @NoviceAdam]

What I’m learning about Git Proficiency

Basic/Junior (many vibe coders lack)
Init repo, add/commit/push/pull
Create/switch branches (main vs feature branches)
Resolve simple merge conflicts
Decent commit messages
Clone + set up remotes

Intermediate (what companies expect)
Branching strategies (Git Flow, trunk-based)
Atomic commits (no giant “WIP”)
Comfy merge conflicts
Intentional rebase vs merge (rebase -i to clean history)
stash, cherry-pick, reset (soft/hard/mixed)
.gitignore, hooks, basic CI/CD
Effective PRs/MRs + reviews
bisect to find when a bug was introduced

Advanced/Senior+
Git internals (objects, refs, index, packfiles)
Adv rebasing, reflog recovery, history rewriting
Submodules or monorepo management
Git hooks for enforcing standards
Optimizing large repos, LFS, partial clones Designing team workflows & Git policies

[Novice Adam @NoviceAdam]

Same ol same ol making the act of reducing headcount look like visionary leadership rather than operational cleanup

[Zeb Evans @DJ_CURFEW]

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.