| ▲ | quadrifoliate an hour ago | ||||||||||||||||||||||||||||
Stripe is the company I usually hold up as the exemplar of polished internal tools. Hopefully this is taken the right way and I don't want to be negative towards the teams working on this, but I see a distinct lack of polish in these tools and presentations. Some examples: - Unnecessary AI copy throughout the interfaces like "Browse, discover, and manage skils for your agents", "No favorites yet — hover a card and click the star to pin it here", "One execution environment, shared across agents". These instantly read as AI copy and decrease my enthusiasm. - Inconsistent, AI-sloppy look-and-feel with different typefaces spattered across the interface - The session metrics slide looks busy and AI-generated. It repeats 360,014 sessions in one of the cells at the top, but also has a "360K sessions" in the heading I don't know if I'm the only one that notices this stuff, or whether others see it too. | |||||||||||||||||||||||||||||
| ▲ | reticulates 37 minutes ago | parent | next [-] | ||||||||||||||||||||||||||||
I think there’s been somewhat of a mask-off moment post-AI in which we’ve realized that a lot of the careful and considered output we’ve come to expect of some companies wasn’t out of a respect for the craft or desire to produce “good work”. Pre-AI the attitude was: if we are going to do something, it is going to use up our precious resources, so we should do it well, because our staff are capable and the marginal cost of doing it well vs. doing it at all is negligible. Post-AI: we can churn out things quickly, we don’t have to worry about resource allocation, churn churn churn! Ultimately, it is pragmatic for businesses to behave this way, but it is a shame for those who love the craft. I think we took for granted the beautiful ornate hand carved furniture era of software engineering. We are now in the ikea era. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
| ▲ | ashkankiani 15 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||
That's funny, because I recall in 2015 hitting their endpoint for a large-ish customer, and if you added a boolean to get the total result count, it would 500 every time, presumably because it was doing some kind of "SELECT count(1)" over a postgres table. IIRC, Stripe was ruby internally for a long time, no? Also their documentation was frequently just straight up incorrect (as in the described json schema for a response was violated. keys missing, different field names, etc.). But it's been over 10 years, has it improved since then? I'm still in my impression of their stack from back then, although they were decently mature by then as well. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
| ▲ | ilaksh 35 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||
Maybe they have jobs to do so they offloaded a lot of the presentation work to AI, assuming reasonable people would not judge based on surface level copy style. | |||||||||||||||||||||||||||||
| ▲ | anthonypasq an hour ago | parent | prev [-] | ||||||||||||||||||||||||||||
> Stripe is the company I usually hold up as the exemplar of polished internal tools. unless you work there how would you know this? | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||