Ernesto

Product developer at @todoist. Always learning.
Building @klipstack, @pixamp and more

[Ernesto @gnapse]

“If you’re thinking without writing, you only think you’re thinking.”
― Leslie Lamport

This quote lives rent-free in my head these days, now that delegating our writing to AI is more and more common.

[Ernesto @gnapse]

@js_craft_hq What podcast was it? I’ve had the same idea for a couple of years now, and wrote about it here https://t.co/W2i5bBw3Dj

[Ernesto @gnapse]

@parkerwightman @TrevMcKendrick Check out @pixamp if you use macOS.

[Ernesto @gnapse]

@TrevMcKendrick Winamp. I liked it so much that I made it for macOS and named it @pixamp

[Ernesto @gnapse]

@thorstenball Thanks for an article instead of an image. Much nicer to read! Good read, I agree with everything.

[Ernesto @gnapse]

AI doesn’t want anything. You’re the one in charge. That’s why we need agency more than ever today.

[Lauri Lännenmäki @laurilllll]

AI isn't the designer. It's the tool.

You're the designer. The art director.

It can't design without your direction.

[Ernesto @gnapse]

@8pq

[Ernesto @gnapse]

@8pq

[Ernesto @gnapse]

@financedystop The car wash, of course

[Ernesto @gnapse]

@historyrock_ Well, she didn't do it alone, did she?

[Ernesto @gnapse]

@coryalthoff What if we do the cyber-patching first? AIs help both ways.

[Ernesto @gnapse]

@ItsKieranDrew The Count of Montecristo

[Ernesto @gnapse]

@neerajjj6785 "Read AGENTS.md instead"

[Ernesto @gnapse]

@kapilansh_twt the salesperson, of course!

[Ernesto @gnapse]

@raycast, apps created via Safari's "Add to Dock" are not found when I search for them. Any workaround?

[Ernesto @gnapse]

@b1rkh0ff Marketing of course!

[Patrick McKenzie @patio11]

The “as a Service” part of SaaS remains underrated.

[Ernesto @gnapse]

@ryanflorence @mnmldmg And also, who says that 200 people teams are the future? My bet is that those are dead. Smaller teams will move faster and be super productive with AI, and need less coordination.

[Ernesto @gnapse]

Oh sure. If we go deep enough into the future, all bets are off about anything. It's just a matter of how deep into the future. I do not imply to say that traditional human-computer interfaces will last forever. Things go fast enough that what I'm saying is maybe relevant for who knows how long. But I do not think that we'll ditch rich UIs in the next 5 years. Screens will still exist, and there are things that are faster to do manually than telling an AI (e.g. selecting from your photo library the pictures you want to send to your family vs. describing each photo verbally).

[Ernesto @gnapse]

User interfaces will not disappear. We're visual animals. If anything, what will happens is that they'll migrate to increasingly be generated dynamically by AI in its responses, as it is already happening in some apps. See @openuidev

[Ryan Florence @ryanflorence]

One of the best UX's the web ever produced is no longer useful.

If anything you're doing right now has to do with traditional UI/UX, you've got maybe a decade of utility in tech. User interfaces will eventually disappear.

Agents, chat, voice, infra, videos, games--that's it

[Ernesto @gnapse]

One guy tweets that his team cancelled their @linear plan, and some people go rushing to declare SaaS and UI/UX dead.

But the guy that cancelled its @linear plan is building a SaaS with lots of UI/UX in it.

Also, this 👇 https://t.co/vA9U1lRalE

[Karri Saarinen @karrisaarinen]

Issues created in @linear by people and via MCP are up 400% this year.

Another fast growing trend: more customers are building their own internal agents and using Linear as the shared layer for workflows, communication and context between people and agents.

As teams move faster, connecting goals, requests, reasoning and the work matters more, even if it sometimes happens after the fact in the review.

Here is one customer oriented example we can do in our Linear:
- Pick a top-10 customer. Ask the agent for a brief of their top requests and the reasoning we've captured
- Write it to a doc in Linear and decide what to build with some people
- Have the agent turn the decisions into projects and issues, carrying the customer requests and meeting notes with them
- Teams send their agents to work on them
- At the QBR, ask agent to generate a report and show the customer what has actually landed or them, how and why

Now multiple these kind of workflows 100 or 1000 times where someone is learning something worth fixing, or trying ideas and finding beta customers for it. Or just aligning across the team or cross function.

Not posting our revenue chart, but it looks a lot like this one