Tweet ghim
“The ability to learn faster than your competitors may be the only sustainable competitive advantage.”
-Arie de Geus
English
Pål Brattberg 👨💻
1.1K posts
Pål Brattberg 👨💻
@pal
Building to save the world! Builder, founder, father of 3, husband of 1 and patter of our CFO - Chief Furry Officer 🐾
Sweden Tham gia Aralık 2006
1.5K Đang theo dõi545 Người theo dõi
@felixrieseberg Very nice! I’d love to bring one of those cute sticks with me on my AI adventures! 🥰
English
To approve your Claude's requests for permissions, I recommend using a little desk buddy.
Mine lives off tokens and gets upset if you don't approve things quickly enough. It's connected to the app via bluetooth.
English
I’m 21. Give me oddly specific life tips. No general ”surround yourself with positive people” tips. I want the most random, specific advice possible.
English
@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.
Svenska
När vi drev igenom hem-PC-reformen och byggde ut bredband tidigt skapade satt en hel befolkning med verktyg i händerna och ett incitament att använda dem. Det kanske inte går att fullt ut leda det i bevis, men vi fick Skype, Spotify, Klarna, iZettle med mera. Det skedde inte inte för att staten planerade fram dem, utan för att tillräckligt många svenskar blev digitalt kompetenta tillräckligt tidigt. Jag skulle hävda att det hade betydelse på samma sätt som den ”kommunala musikskolan” hade betydelse för framväxten av det svenska musikundret.
AI är samma möjlighet, men tidsfönstret är mycket snävare.
Problemet är adoption. De flesta människor har fortfarande inte byggt en vana kring AI – en del testar, tycker det är “kul” med chatgpt eller motsvarande, och går tillbaka till gamla arbetssätt. Här finns hävstången: att gå från nyfikenhet till beteendeförändring i stor skala.
Eftersom staten är långsam och tbh – usel - måste initiativet vara distribuerat. Företag, entreprenörer och organisationer måste behandla AI som en produkt att “rulla ut” till hela befolkningen.
Gör AI konkret och nyttigt. Bygg enkla, vertikala verktyg för specifika behov. hantverkare som vill skriva offerter, småföretagare som vill förstå sin bokföring, föräldrar som vill planera vardagen. Inte generiska “chatbots”, utan lösningar som sparar tid direkt. Bygg en agent för att planera dina familjemiddagar eller semestrar. Låt en agent hjälpa dig med övningar till dotterns fotbollsträning eller grabbens balett.
Skapa en marknadsdriven folkbildning. Studiecirklar 2.0, men organiserade via arbetsgivare och föreningar. “En timme AI i veckan” som norm. Eller nej, en timme AI om dagen, menar jag naturligtvis! Inte kurser i teori och ”så här fantastiskt kan ett samhäll med ai bli” , utan praktisk användning: skriv detta mejl, analysera denna fil, bygg detta flöde.
Distribuera genom befintliga nätverk. Sverige är ett land av föreningar, arbetsplatser och digitala plattformar. Varje arbetsgivare borde kräva att alla anställda använder AI i minst en arbetsuppgift.
Vi behöver faktiskt inte vänta på en nationell strategi eller utvärdera och påverka den. Vi behöver istället en folkrörelse. Det här kan vi i Sverige. Tusentals små initiativ som tillsammans skapar ett nytt normalläge där AI inte är ett verktyg för några få, utan en självklar del av vardagen för många.
Och precis som med PC-reformen är det inte tekniken i sig som avgör utfallet. Det är hur snabbt och brett den tas i bruk. Jeffery Ding har visat det i Technology and the Rise of Superpowers.
Det land som vinner behöver inte vara det som uppfinner AI. Där är vi redan efter. Men vinnaren är det land som får flest människor att faktiskt använda AI först.
Se även:
breakit.se/artikel/41347/…
Svenska
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)
English
Giveaway:
To celebrate the launch, we're deploying the next 1,000 agents for free.
RT + comment "Claw" on the post below and we'll DM you a free month to hire your first AI employee.
x.com/blinkdotnew/st…
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)
English
@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: docs.claude.com/en/api/rate-li….
English
Today we're introducing the world's first AI CMO.
Enter your website and it deploys a team of agents to help you get traffic and users.
Try it now at okara.ai/cmo
English
Pål Brattberg 👨💻 đã retweet
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.
Gergely Orosz@GergelyOrosz
Interesting thought experiment: Let's run with the assumption that AI makes creating software ridiculously fast + cheap, and quality doesn't suffer (I know, I know, but let's assume) What would this mean for software businesses? Would eg they all expand scope w new products?
English
Introducing @variantui
Enter an idea and get endless (beautiful) designs as you scroll
No canvas, no skills or MCP, no constant prompting
Reply if you'd like 200 free designs to give it try
English
English
English
Sequoia partner @sonyatweetybird says we're going from the age of product-led growth to the age of agent-led growth.
"You see this most clearly if you're using Claude Code actively. It says, 'Hey, for a database, you should use Supabase. For hosting, use Vercel.' It's choosing for you, the stuff you should be using."
"Product-led growth brought us closer to the vision of 'best product wins,' but ultimately people are still lazy. They can't read all the reviews, and they kind of default to what looks cool on the website."
"Whereas your agent has infinite time to go and make these choices for you. It can go and read all the documentation, read all the user comments, and figure out [what you need] for your use case."
English
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, agents.md, linting, and code rules. Tell it how you want things. Every manual edit you make is an opportunity for agent.md 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?
English
@nikitabier Just a slight title change would do the trick 😂
English
Lovable just got called out for not paying VAT in Europe yet. Many came to our defense saying the EU isn't built for hypergrowth startups.
I appreciate it, but that's not my takeaway. We can build a generational company from Europe, and I want to prove it. I'm not asking Europe to stop being Europe.
I don’t know the perfect solution, but there are advantages to a high trust society and systems that don't bankrupt people when they get sick.
Lovable WILL – and has always planned to – be compliant and pay any fees from being late. We pay our taxes and hope to pay billions more in taxes over the years to come.
Building from Europe is a bet I'm proud of.
English
Pål Brattberg 👨💻 đã retweet
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? 🤷🏾♂️
Peter Yang@petergyang
Cursor scaled to $29B without any full-time PMs. Ryo (Cursor's Head of Design) walked me through how they work and it's the opposite of every big tech best practice: 1. Roles are muddy PM work is spread across designers and engineers. Everyone does what fits their strengths and uses AI to fill the gaps. 2. Most designs start with code directly Ryo barely uses Figma except for initial exploration. Most features start as live Cursor prototypes because "it feels more real than pictures." 3. No annual roadmap theater Just a "fuzzy direction" and features shipped to concentric circles (e.g., staff, nightly beta users, consumers, enterprises) to polish. Ryo also showed me exactly how he designs and codes new features using Cursor and how he avoid creating generic purple AI slop. 📌 Subscribe to watch our full tutorial tmr: @peteryangyt?sub_confirmation=1" target="_blank" rel="nofollow noopener">youtube.com/@peteryangyt?s…
English
Pål Brattberg 👨💻 đã retweet
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
Bun@bunjavascript
Bun v1.2.23 - Fixes 119 issues (addressing 412 👍) - `bun install` migrates `pnpm-lock.yaml` → `bun.lock` - pub/sub in Bun.redis - concurrent `bun test` - `sql.array` for postgres client - Node.js compatibility improvements Thanks to 16 contributors! bun.com/blog/bun-v1.2.…
English
In the next version of Bun
When AI agents like claude code run `bun test` with a filter that finds 0 matches, the error reminds them the current working directory
English