Remix.run Logo
noodletheworld 7 hours ago

If someone wants to pat themselves on the back with how great they think they are, thats cool, but I dont think its really worth talking about.

…unless they have something to show, specifically?

Demos? Code? Details?

Nothing?

coderintherye 3 hours ago | parent | next [-]

Admittedly, more detail would be better, but this high-level stuff is mostly the level that engineering leaders are discussing this topic currently (and it is by far the most discussed topic).

They actually revelead an interesting tidbit where they are with AI adoption and how they are positioning it now to new hires, e.g. "we made AI fluency a baseline expectation for engineers by adding it to job descriptions and hiring expectations".

It seems inevitable now that engineering teams will demand AI fluency when hiring, cuious though what they are doing with their existing staff who refuse to adopt AI into their workflow. Curious also if they mandated it or relied solely on incentives to adopt.

zek 7 hours ago | parent | prev [-]

This was just our first post FWIW, and we definitely want to follow up with more concrete demos/details/etc here. I am working on another post specifically about how we leverage our internal RPC system to make adding AI tools super easy so expect more from us.

noodletheworld 7 hours ago | parent [-]

You know that thing that you get when you ask a model to summarize and page or come up with a plan and you get:

- generic advice heading 1

- generic advice content

- generic advice heading 2

- provide better tools

You know how thats the kind of response that you copy paste in a slack message and your co worker is like “If I wanted an AI summary Id have done it myself. I was asking why…”

Yeah. …yeah.

Could you be less generic about the process you went through?

What tools do you use? How did you get past the critics?

Are you 90% “uses AI for 50% of coding” or 90% “codes via claude code”?

More AI coding, no extra incidents? How are you measuring that?

The post under this one on your blog is literally called:

> HubSpot Incident Report: August 7th 2025

Come onnnnn~

Zagreus2142 4 hours ago | parent [-]

To be fair, if you read the incident report it is a better than average one on details and it was a 20 minute outage without data loss. I've seen many major companies simply not acknowledge that level of outage on their public status page, especially lately