知鸦日报2022-10-26

设计师从用户的视角剖析运动需求的本质，满足用户不同阶段的诉求，本文将带你了解设计师怎样对学生运动场景探索与尝试的过程中发挥自己的价值。

作为设计师，我们除了在色形字构质上下功夫，除了在导航、流程、链路上做简化，还有哪些更底层的设计思维，可以帮助用户决策，提升商家ROI呢？一起来跟淘宝设计师们取取经吧~

Aha moment是啥意思？那些让你“灵光乍现”、“顿悟”、“茅塞顿开”、“突然开窍”的某个瞬间。（aha本来就是一个感叹词，当人们恍然大悟的时候可能会不由自主地感叹“啊哈，原来如此”）。Glen今天不是来跟大家分享心理学感受的，而是整个“Aha moment”可以很实用的联系到互联网的产品设计理念里。作为产品经理，最大的目标或者说梦想是做的产品能够吸引用户，为用户创造价值或者提升价值。但我们在设计产品时，往往很难预测用户是否喜欢这个产品。

当代智能监控平台不乏功能强大的产品，但由于涉及模块、组件多，产品容易臃肿，对私有化场景增加了一定的阻碍。于是，轻量化智能监控平台很有必要。

本文介绍了阿里 Log Scan 的设计与实践。

If you’re paying attention to Salesforce technology, you’ve no doubt heard about Hyperforce, our new approach to deploying Salesforce on public cloud providers. Start with a look at Hyperforce’s architecture. There are many compelling reasons to move to Hyperforce, both for us and our customers. We’re excited to do it in the way that only Salesforce would — with trust, availability, and security at the forefront from day one. Building a unified infrastructure platform for Hyperforce meant relooking at our automation tools to scale our operations with a fresh lens.

Salesforce has been around for over two decades. In 1999, when the company was founded, if you wanted to run a public internet software service (Software as a Service, or SaaS), you first had to get some servers and hook them up to the internet. So we built a few tools to perform our releases and database maintenance operations using SSH. Fast forward to 2015, when Salesforce took a very early bet on Kubernetes (K8s) to help manage an extensive suite of microservices. We’re proudly using it today across product lines and business units. And with our transformation to Hyperforce, building and using cloud-native tools, security and process made the most sense.

To leverage the scale and agility of the world’s leading public cloud platforms, our Technology and Products team has worked together over the past few years to build a cloud-native task execution system to execute remote operational tasks at scale. Because we believe you may need to walk down this path, too, we’d like to share some challenges we faced and the solutions we identified.

前端开发中经常会遇到大数据量列表展示的性能问题，即大数据量一次性展示时前端渲染大量 Dom，触发渲染性能问题，造成初始加载白屏，交互卡顿等。解决这类问题的方案也有很多，使用虚拟列表展示是一个比较常见的解决方案。今天我们来介绍如何使用 IntersectionObserver 这个 API 来自定义实现虚拟列表。

Code Review 的好处虽然被广泛认可，但想做好 Code Review 并不容易。首先团队需要对开展 Code Review 达成共识，然后针对自己团队的特性，采用相匹配的实践方式。关于工具，可以尝试文中提到的插件以及电子看板。

在“永远做不完的需求”面前如何沟通和取舍？

那些水平很棒的技术人为什么在创业后常常碰的头破血流?

为什么说技术 leader 都要能做自己-2的事情？

团队越大干实事的人越少怎么破？

AI 技术的红利吃到尽头了吗？

算法工程师以后会不“香”了？

“工程师文化”就是“衣着休闲、时间自由、不修边幅、免费三餐和华丽装修”吗？

适配器模式(Adapter Pattern)：是指将某个类的接口转化成客户端期望的另一个接口，主要目的是兼容性，让原本因接口不匹配不能工作的两个类可以协同工作。

MapStruct，将CV工作量从O(n)降为O(1)的工具。

从催逼盯，到串推破的进化；从点线面，到突破认知的格局；做认为对的事，心态定乾坤。

20世纪70年代前后，“领导情境理论”初步形成。该理论认为，不存在一种绝对的最佳管理方式，管理的效果与管理者所处的具体情境和环境有关，即在A情况下能高效发挥作用的管理者，在B情况下却可能无效。

现在看来，“领导情境理论”是并不是完美的，它低估了人类主观能动性作用——只要有对的方式和充分的资源，人是可以发展出新技能的，包括领导能力。要知道，“好管理者”的关键不在于技能，更在于TA在特定情况下的意识与适应能力。而拥有这样能力的前提，则是对自己的优势、劣势充分了解的同时，还有更强的心智能力，进一步能够有针对性地扬长避短。

但是，它让大众换了一个全新的视角来看待领导力。它跳过了“好管理者”与“坏管理者”的定义，将管理的重点放在了让领导力与领导情境相匹配上。我们如果能够在工作中恰当使用它，就能够找到匹配的工作模式，从而更好地发挥管理作用。

Application reliability is critical. Service interruptions result in a negative customer experience, thereby reducing customer trust and business value. One best practice that we have learned at Amazon, is to have a standard mechanism for post-incident analysis. This lets us analyze a system after an incident in order to avoid reoccurrences in the future. These incidents also help us learn more about how our systems and processes work. That knowledge often leads to actions that help other incident scenarios, not just the prevention of a specific reoccurrence. The mechanism is called the Correction of Error (COE) process. Although post-event analysis is part of the COE process, it is different from a postmortem, because the focus is on corrective actions, not just documenting failures. This post will explain why you should start implementing the COE mechanism after an incident, and its components to help you get started.