广场

Fragments: October 28

Andrej Karpathy sees a widening gap in how people see LLM capabilities. The general public has mostly not interacted with these systems. When they have, it looks like a derpy chatbot. The majority of professionals still see only a modest uplift. And a small sliver of professionals are experiencing the vertigo of the curve going vertical. And it is all happening at the same time. Many of my colleagues are living in a world where LLM capabilities are stunning, but it’s easy to forget that’s not what most people experience. One thing I do is use free-tier LLM chatbots, and I’m still finding that while most of the time they are useful, their unreliability undermines much of that usefulness. Yes,…

Martin Fowler开发技术英文

Announcing a Maintainer in Residence: Scott Schafer for the Cargo team

At the end of August, we announced our first Maintainers in Residence, Rust Project contributors who are funded for their upstream contributions and maintenance work from the Rust Foundation Maintainers Fund (RFMF). Since then, the Rust Leadership Council has dedicated more funds from its Project Priorities budget to RFMF, and together with AWS also providing additional funds, this allowed us to open a new full-time Maintainer in Residence (MiR) position to support the Cargo team. We would like to thank the Rust Leadership Council, AWS, and also the Rust Foundation for providing us with this opportunity! If you would like to help us hire more maintainers to improve Rust, consider donating to…

Rust Blog开发技术英文

FDE 看现场:用户说的和做的,为什么总是不一样

用户跟你说的流程和实际操作的流程,往往不是一回事。FDE进场第一周在现场看到的常规操作、异常处理、工具组合、协作方式和人的因素,比后面三个月的访谈和分析都要值钱。 去年在一个大型企业做AI项目,刚进场那周,和业务方开了三场会,HR、IT、一线操作员都坐过。他们跟我说流程是这样的:员工提交申请→审批→系统录入→通知发放,文档里写得清清楚楚。 但第一次去现场,我在工作台坐了一下午,看到的完全是另一回事。 早上10点,一个员工走到HR姐姐桌前,递了张纸。HR没看系统,直接拉开抽屉翻纸质申请单。翻了五分钟,找到了上周的一张。员工在纸上改了个数字,HR就签了字——整个过程没打开过电脑。 我当时就懵了,这不按流程走啊。 后来才明白,系统在三年前上线,但审批权限一直有问题。某个人权限设了一半就离职了,新来的人没人教怎么改,就只能回到纸质操作。现在每周都有一堆纸质单据堆在那儿,系统里的数据其实已经对不上了。 这就是为什么我会认真对待现场观察的原因。 01 访谈说不出来的东西 在之前的项目里,我做过N次访谈(标配技能,对吧?)。拿着提纲,问用户现在怎么做的,有什么痛点,想要什么样的解决方案。用户回答得很仔细,笔记记得也很满。但真正上线以后,还是会发现一些意料之外的问题。 问题在哪呢?用户说的是他们“以为”自己在做的事。 一个很现实的例子:有个流程,用户跟我说是这样的:第一步做A,第二步做B,第三步做C,线性的,逻辑清楚。但我去现场看,发现他们经常是先做B,然后根据B的结果决定要不要做A,C有时候放在最后,有时候穿插在中间。 为啥? 因为系统的限制:B必须先跑起来生成数据,他们才能判断A值不值得投…

人人都是产品经理产品设计中文