Pål Brattberg 👨‍💻

Building to save the world! Builder, founder, father of 3, husband of 1 and patter of our CFO - Chief Furry Officer 🐾

[Pål Brattberg 👨‍💻 @pal]

“The ability to learn faster than your competitors may be the only sustainable competitive advantage.”
-Arie de Geus

[Pål Brattberg 👨‍💻 @pal]

@danshipper @every Ah! Just got started reading, but this uncloseable popup stopped me dead in my tracks. #okboomer

[Pål Brattberg 👨‍💻 @pal]

@benln AND OPEN SOURCE!!! 🤞

[Pål Brattberg 👨‍💻 @pal]

@felixrieseberg Very nice! I’d love to bring one of those cute sticks with me on my AI adventures! 🥰

[Pål Brattberg 👨‍💻 @pal]

@eternaltxts Love the one you’re with. With all your heart.

[Pål Brattberg 👨‍💻 @pal]

@mpawlo Helt enig. Jag tror vi är många som kan göra nytta här lokalt. Kör en hands-on session med lokala företag att få in AI i Excel, inspirera mellancheferna på kommunen, hjälp en skolklass göra något kreativt med AI eller skriv insändare i lokaltidningen. Alla kan bidra med något.

[Blink.new @blinkdotnew]

Introducing Blink Claw - the first platform to hire unlimited AI employees that run your business 24/7.

180+ AI models included. Gmail, Slack, LinkedIn, HubSpot - one-click connect. No API keys, no $600 Mac Mini.

Reply "Claw" + RT. Your first agent is on us. ($50 - 200 creds)

[Pål Brattberg 👨‍💻 @pal]

@blinkdotnew Claw

[Pål Brattberg 👨‍💻 @pal]

@askOkara ✗ Error: Failed after 3 attempts. Last error: This request would exceed your organization's rate limit of 2,000,000 input tokens per minute (org: db45096a-0f1d-4aa0-97df-9303d7f0d022, model: claude-sonnet-4-6). For details, refer to: https://t.co/rcfZdaTna9.

[Pål Brattberg 👨‍💻 @pal]

This is absolutely true, and if your company doesn’t have this role embodied in a single person, make sure you build this as a first priority!

[signüll @signulll]

the most underrated hire right now is a great product person.

when i say product person i'm def not talking about a product manager. perhaps i think there has to be somewhat of a new role. i don't have a good name for it yet but maybe something like "product thinker".. someone with an intuitive grasp of the product as it exists, where it's soft, where it sings, & how to iterate it toward something even sharper. in some sense, this person has to cohesively hold in their head where this product should be 2 years from now & work backwards from that.

i say this cuz when building was hard, engineering was the bottleneck & the status hierarchy often reflected that. building is no longer hard. which means the variance in outcomes has shifted almost entirely to judgment on what to build, how to sequence it, & how to talk about it.

& the story matters as much as the thing. internally, it organizes the team around a shared model of why. externally, it shapes the interpretive frame users bring to their first experience. you can't retrofit narrative onto a product & expect it to land, it has to be load bearing from the start.

the rarest version of this person sits at the intersection of culture & deep technology. someone genuinely bilingual. they know what's technically possible & they know which cultural currents are real vs. ephemeral. that combo is what separates products that feel inevitable from products that feel assembled.

before ppl clap back with this person has always been valuable, i know.. i am just saying now they might be the most *important* person in the room. their value compounds like never before.

[Aaron Levie @levie]

This is the question every software company is asking themselves right now. What happens to our roadmap if an engineer can produce 2X or 5X more output.

The general direction will be roadmap expansion. Companies that just use this leverage to cut costs will be outcompeted by those that decide to do more.

As a result, this will mean we will see more competitive battles between companies, but also the expansion of many more categories since software can touch more surface area.

The limiter then becomes how rapidly your customers can actually adopt new software, how good you make that software (vs. it becomes slop because it’s so much easier), and whether you can get paid for more software or if customers’ expectations just go up over time for what they get from each vendor.

As an aside, building up a brand, ecosystem, and distribution moat ends up being critical. If software development cost per unit go down, then the new game is how you can get customers to adopt and remain sticky. GTM becomes a critical factor in all this.

[Pål Brattberg 👨‍💻 @pal]

@bnj @variantui Hell yes! 🙌

[Pål Brattberg 👨‍💻 @pal]

@p_misirov @tbpn @sonyatweetybird I would rather respect Accept: text/markdown

[Pål Brattberg 👨‍💻 @pal]

Great list, lots of alpha here!

[rahul @rahulgs]

yes things are changing fast, but also I see companies (even faang) way behind the frontier for no reason.

you are guaranteed to lose if you fall behind.

the no unforced-errors ai leader playbook:

For your team:
- use coding agents. give all engineers their pick of harnesses, models, background agents: Claude code, Cursor, Devin, with closed/open models. Hearing Meta engineers are forced to use Llama 4. Opus 4.5 is the baseline now.

- give your agents tools to ALL dev tooling: Linear, GitHub, Datadog, Sentry, any Internal tooling. If agents are being held back because of lack of context that’s your fault.

- invest in your codebase specific agent docs. stop saying “doesn’t do X well”. If that’s an issue, try better prompting, https://t.co/SOjpn47yxo, linting, and code rules. Tell it how you want things. Every manual edit you make is an opportunity for https://t.co/S1ZvtYQwta improvement

- invest in robust background agent infra - get a full development stack working on VM/sandboxes. yes it’s hard to set up but it will be worth it, your engineers can run multiple in parallel. Code review will be the bottleneck soon.

- figure out security issues. stop being risk averse and do what is needed to unblock access to tools.

in your product:

- always use the latest generation models in your features (move things off of last gen models asap, unless robust evals indicate otherwise). Requires changes every 1-2 weeks - eg: GitHub copilot mobile still offers code review with gpt 4.1 and Sonnet 3.5 @jaredpalmer. You are leaving money on the table by being on Sonnet 4, or gpt 4o

- Use embedding semantic search instead of fuzzy search. Any general embedding model will do better than Levenshtein / fuzzy heuristics.

- leave no form unfilled. use structured outputs and whatever context you have on the user to do a best-effort pre-fill

- allow unstructured inputs on all product surfaces - must accept freeform text and documents. Forms are dead.

- custom finetuning is dead. Stop wasting time on it. Frontier is moving too fast to invest 8 weeks into finetuning. Costs are dropping too quickly for price to matter. Better prompting will take you very far and this will only become more true as instruction following improves

- build evals to make quick model-upgrade decisions. they don’t need to be perfect but at least need to allow you to compare models relative to each other. most decisions become clear on a Pareto cost vs benchmark perf plot

- encourage all engineers to build with ai: build primitives to call models from all code bases / models: structured output, semantic similarity endpoints, sandbox code execution. etc

What else am I missing?

[Pål Brattberg 👨‍💻 @pal]

@TodayinHistory @nikitabier Meet the new VP Product

[Pål Brattberg 👨‍💻 @pal]

@nikitabier Do good

[Pål Brattberg 👨‍💻 @pal]

@antonosika Class act response Anton! 💪

[Rohan Varma @TheRohanVarma]

I become Cursor’s first full-time PM 4 months ago.

What I am NOT doing:
- Manage a product sprint
- Grooming
- PRD

What I am doing:
- Help build, price, market, and launch our first second product: Bugbot
- Customer support for Bugbot for the first couple months - I’ve responded to literally thousands of emails
- Enable and help our rapidly scaling GTM to sell Bugbot and Cloud agents to enterprise
- Spend lots of time with our biggest customers who are least similar to our engineering team
- Talk to hundreds of users for competitive analysis and UXR
- Advocate for and help kick off some of the features that became Cursor 2.0 (agent layout + plan mode)
- Architect and scope a new platform product we’ll be releasing soon
- Help GTM close deals and expand our footprint in our enterprise contracts directly in the sales process
- Travel across the world to visit our customers, help with enablement, and see where we can improve
- Helping with misc random things: evaluating strategic acquisitions, “thought leadership” events, lots of recruiting, product/content marketing, devrel, and more

Am I PM-ing correctly? 🤷🏾‍♂️

[Pål Brattberg 👨‍💻 @pal]

@Jobvo Best kind of happy! 👌

[Pål Brattberg 👨‍💻 @pal]

Next level release notes process! 💪

[Jarred Sumner @jarredsumner]

our process for writing the release notes has changed a lot in the last 6 months

Now it’s:

1) for each commit, send the code + message + github PR and linked issues to Gemini 2.5 to read and decide if “paragraph-worthy” or “bullet point worthy” or if it’s a CI thing to skip and write an initial draft. Post processing step includes the commit link associated in an HTML comment for us to verify.
2) use a keyword similarity sorter script to combine them into one file that loosely groups
3) spend about 2 hours editing and checking for accuracy

doing it 100% manually used to take 4-6 hours and we regularly forgot to include things in the release notes. we’ve been doing this for like 10 releases now

[Jarred Sumner @jarredsumner]

our process for writing the release notes has changed a lot in the last 6 months

Now it’s:

1) for each commit, send the code + message + github PR and linked issues to Gemini 2.5 to read and decide if “paragraph-worthy” or “bullet point worthy” or if it’s a CI thing to skip and write an initial draft. Post processing step includes the commit link associated in an HTML comment for us to verify.
2) use a keyword similarity sorter script to combine them into one file that loosely groups
3) spend about 2 hours editing and checking for accuracy

doing it 100% manually used to take 4-6 hours and we regularly forgot to include things in the release notes. we’ve been doing this for like 10 releases now