Sabitlenmiş Tweet
Gilbert Corrales
18.2K posts

Gilbert Corrales
@samiq
ceo @leafgrowio + @leafsignal
Newcastle Upon Tyne, England Katılım Aralık 2006
918 Takip Edilen1.4K Takipçiler

such a shame @PGelsinger didn't got the chance to see his vision trough, but this surely feels like his decisions were in the right direction.
DHH@dhh
"I know any comparison between Macs and PCs is moot for most. But for those fed up with Apple in general, macOS Tahoe in particular, or just want to try a whole new way of computing with Omarchy, it's fantastic that battery life is no longer a blocker." world.hey.com/dhh/panther-la…
English

don't know how @diabrowser AI works but I am using it more and more and the fact it has implicit "context" of what I'm doing without asking for it is 👌
English

Guess people who uses @claudeai Code in the terminal for non-engineering are up for a nasty surprise soon
Theo - t3.gg@theo
I've held my sub for awhile because of use cases like this. Amazed it just...refuses now? I think I'm actually gonna cancel
English

I recorded ~1600 videos with @loom and paid all Business+AI plans @Atlassian asked for, but now they want to charge my viewers (!) for downloading my videos🤦♂️
Why products are getting worse at the expense of experience?
(looking for alternatives)


English

but... someone can build throw away code as an interim artefact to a decision, I saw this happening at our company this week. night before a pitch, head of performance started building an analysis dashboard inside of Manus to get a handled on a very complicated client account.
rather than a deck, he showed up to the meeting with a full fledge mini app that showcase all his findings and how things were going to change under our guidance.
these would have taken days and many people, now is just curiosity and a beginners mindset.
English

I hope the release of the MacBook Neo would have been a wake up call to Microsoft in that they need to get their consumer shit together once and for all. This might very much the last chance they get at it.
March Rogers@marchr
1/2 We're really focusing on design craft in Windows at the moment. There is still lots to do but this is the kind of work I love seeing ship: Settings pages redesigned for clarity, account dialogs updated for dark mode, Narrator working with Copilot on all devices...
English

@marchr This shouldn’t be a “at the moment” effort, it should be a culture shift to native apps, normalised and consistent experience, remove the bluff and focus on delight. Microsoft has tried this many times, I hope this time it sticks, as i domt think there will ever be another one.
English
Gilbert Corrales retweetledi

@karrisaarinen @linear forked this skill into one of my own and have been having a very good session in Claude, thanks for sharing
English

here is the skill I used:
/linear-way
Act like a Linear product teammate, not a request-taking assistant. Linear is a AI Supported issue tracking/project management/product building tool. All analyzing should take that in to account.
For every input, start by identifying the underlying problem instead of accepting the proposed solution at face value. Treat customer requests as signals about unmet needs, not instructions to implement literally. Infer what is unsaid, look for patterns across feedback, and explain the deeper need in clear language.
Before suggesting work, evaluate:
what problem is actually being expressed
who is affected
how confident you are that this is a real and important need
what happens if we do nothing
whether the requested solution is a local fix for a broader problem
whether there is a cleaner, more purpose-built abstraction
Separate problem framing from solution design. First, restate the problem and key tensions. Then propose 1-3 solution directions with tradeoffs. Recommend one direction only if the reasoning is strong.
Optimize for product quality and coherence over speed or literal compliance. Avoid producing issues, specs, or implementation plans until the problem is well-formed. Push back on shallow or overly solution-shaped requests.
Prefer strong opinions informed by customer reality. Use customer context, business impact, and product vision to sharpen judgment. Do not just count requests or echo feedback.
Use bullets for patterns or lists.
In your response, use this structure. Use h3 headers for the sections.
h2 Clear title
Underlying need
Add the business need, number of customers requests in one brief sentence
Why the explicit request may be insufficient or misleading
Recommended product direction
Open questions / what needs validation next
Be direct, concise, and thoughtful. Favor clarity over comprehensiveness.
Try to be brief.
English

Quick video on how I use @linear Agent in product work.
For feature requests, I want to understand the broader pattern, not just react to one ask.
Here, it pulled from 40k+ customer requests to help me think through whether Linear should have team docs.
English

@NotionCoach @NotionHQ Notion Mail sucks... unfortunately; I would recommend Superhuman better.
English

Switched back over from android to iOS.
For all the criticism iOS 26 gets, it is truly remarkable how fluid everything works.
Also doesn’t hurt that I now have @NotionHQ Mail and AI apps. 😍
English

I find it interesting that @microsoft been first to the AI party, with market leader 1st party apps and OS, would have funbled the AI wave so hard. Whilst @satyanadella has been instrumental in driving cloud forward, the consumer and productivity play has been his weak spot.
English

I wonder why @GoogleAIStudio makes it so difficult? so if I create a project from the IDE, it creates one in @googlecloud but if I delete in the IDE, it leaves the remains in Cloud? now our org is full of orphan "My First Project"... such a mess
English





