3 ms·
The quantitative ux research team at Google was created for exactly this problem: a service which became popular before the right metrics existed, meaning metri
by stevenae 6mo ago
The quantitative ux research team at Google was created for exactly this problem: a service which became popular before the right metrics existed, meaning metrics need to be derived first, then optimized. We would observe users (irl), read their logs, then generate experiments to improve the behavior as measured by logs, and return to see if the experiment improves irl experiences. There were not many of us and we are around :)
- ajma 6mo agoI worked with Boris in the past and in my experience, Boris cares deeply about the customer. I'd vouch that Boris really cares about the issue people are running into.
- thejazzman 6mo ago“ Hello. My name is Mr. Sirob,” https://amphetamem.es/meme/?id=the-simpsons_04_12_89×tamp=0%3A5%3A10.768&text=Hello.%0AMy+name+is+Mr.+Sirob%2C&dimensions=1440x1080&series=The+Simpsons&season=4&episodeNumber=12&episodeTitle=Marge+vs&at=%2Fthe-simpsons%2F04%2F12%2F0-5-10-768 https://amphetamem.es/meme/?id=the-simpsons_04_12_89×ta...
- dkersten 6mo ago[flagged]
- stingraycharles 6mo agoAnthropic can't win in this case. They don't use Claude Code, they get accused that they don't even trust it themselves. They use Claude Code, they get accused the code is shit because it's slop. I think dogfooding is known to be a legitimate approach here.
- visarga 6mo agoAnd they don't use our version of CC, or with our settings. They have flags for internal use only.
- latexr 6mo ago> Anthropic can't win in this case. Sure they can. The solution is pretty simple and in your own post. Choose either: * Make the product good to the point code is no longer slop and shit. * Stop hyping the quality when it isn’t there. * Do a hybrid approach. Use their own product but actually have competent humans in the loop to make the code good. This is not hard. Be honest and humble and that criticism goes away. It’s no one’s fault but Anthropic’s that they hype up their product to more than it can do and use it carelessly to build itself. It’s not a no-win scenario if you’re the one causing your own obviously avoidable problems.
- Toutouxc 6mo agoThe idea is that Claude Code is surprisingly buggy and unrefined for something created by the very tool and processes that are supposed to be replacing us as we speak.
- KptMarchewa 6mo agoThe idea is that sculpted ideal code is rarely the best choice.
- embedding-shape 6mo agoBut no other user has yet come and said "I worked with ajma in the past ..." so how can we trust your judgement about Boris?
- jmalicki 6mo agoI saw this guy named Claude saying ajma is a genius!
- bodegajed 6mo agoNice try boris
- Traubenfuchs 6mo agoGoogle products ux is widely acknowledged to be a steaming pile of shit though, so I am not sure you should follow their example. Many of the metrics they use are obviously actively user hostile.
- TheLegace 6mo agoMetrics and quantitative ux results in really bad software, making it rigid while optimizing for the wrong things. The most obvious example is Google creating multiple steps for Login where you have to enter your password after you put in your user. I wonder what metric lead to that decision or was it a political decision to make it seem like their "old" software has some new feature.
- saltcured 6mo agoIf you mean Google website login, that step is needed because the email address is used to determine which identity provider to use. E.g. I have three different accounts that branch off from that same initial login flow. One is my person "gmail.com" account, and the other two go through enteprise identity providers related to my employment and their G-Suite licenses. So after I put in one of these three email addresses, I get prompted for the appropriate next step. Only one of them involves giving a password to a Google server. The other two are redirects to completely separate login systems operated by my employer.
- TheLegace 6mo agoI mean I get it logically makes sense. But it still seems like a waste of time for a small percentage of use cases. Maybe a better approach is put in your login have it automatically detect if it requires an identity provider. Gray out the password to signal to the user password is not necessary and automatically redirect. Less clicking, don't break flow and think of a smoother solution.