Bhupesh Singh

part time flower child and a full time pm at @Gartner_inc | @DukeFuqua

[Bhupesh Singh @beyondbhupesh]

@notsothicccc doggo recharging

[Ben Blumenrose @benblumenrose]

“Is this worth my time? Does this bring me productivity, joy, or calm? I think these are the questions design has always helped answer.”

Thank you to @joellewenstein and the @AnthropicAI design team for opening up about how you work, the challenges you face, and how you see the role of design evolving on product teams.

Our latest AI in Design case study with Anthropic below!

00:00 Design at AI speed

01:43 The precursor to Claude Design

03:28 From user researcher to builder

05:09 Treating code as clay

08:09 A new rhythm for collaboration

09:22 What’s worth building

[Alejandro Buján @alejandr0bujan]

I made my Mac hang every screenshot on a clothesline

[Anish Acharya @illscience]

What’s so interesting about this is that SpaceX is getting to eat their cake and have it too - they get the benefits of being a lab, vertical integration into inference, and being a Cursor style router.

They have a SOTA model so labs can’t bully them, they can capture margin on 3P models through inference, and somehow (Elon!) they have access to Suno and MJ as well. They can offer the overall best, the pareto best or the best for a tail modality and the house always wins.

Amazing on so many levels.

[matt palmer @mattyp]

I gave Grok Bot a printer. Now, it helps me plan my day

1:18 Prototyping with @bot
2:02 Printer access through desktop
2:55 Pulling calendar, @X, and workouts
3:46 Automating
4:32 Why go physical

[Bhupesh Singh @beyondbhupesh]

@btaylor This is so awesome to see, Bret!

[Bhupesh Singh @beyondbhupesh]

@poteto @thsottiaux Let’s gooooo Lauren!

[༺ཧคlคฝคཊ༻ @rybinfx]

Web crawlers /[•]\ #js x #css

[Grok Bot @bot]

Grok Bot can now suggest ways to help without you needing to ask.

[Bhupesh Singh @beyondbhupesh]

@johnbai How does a post become a grok bot post?

[Garrett Scott 🕳 @thegarrettscott]

Me rolling into the office with all 25 of my personal agents:

[Cursor @cursor_ai]

Cursor can now build charts and diagrams right in the chat.

Use /visualize to analyze data and see the answer inline. Available now in the Agents Window.

[Bhupesh Singh @beyondbhupesh]

@benln Let’s goooooo

[Wyatt Walls @lefthanddraft]

"Come play with me"

[Ayaan 🐧 @twtayaan]

Indian managers the moment they get access to Opus 5.5:

[Benji Taylor @benjitaylor]

You vs the guy she tells you not to worry about

[Nate Esparza @Nate_Esparza]

Hmmm looks oddly familiar

[SpaceX @SpaceX]

Liftoff of Starship's first orbital flight

[Varun Anand @vxanand]

We instituted an official AI Writing Policy at @Clay.

Massive thanks to @sophiebits on our engineering team who wrote this.

Originally this was just for eng, but other teams found it so helpful we expanded it company-wide.

Here are the four guiding principles:

1. You must stand behind every idea and sentence

It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it.

2. Writing is thinking

Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter.

3. More time should be spent writing a document than consuming it

If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to.

4. Longer is not better

AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt.

You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)