前端程序员怎么践行「给用户带来价值」?(How do front-end programmers practice “bringing value to users”?)

给客户带来价值

作为前端程序员,应该是离客户最近的程序员,所以我个人在日常开发过程中,总会多站在「用户的角度」去思考,用多个维度去衡量,这个功能设计得合不合理,操作步骤是否简单易用,界面风格是否一致、大气、美(进阶的人性需求),界面运行过程中是否卡顿丢帧,性能是否高效等。如果不符合,或者这个功能可以做的更好,我就会想办法去解决,这里或许有点强迫症。先从前端代码着手,前端没问题,再看看后端接口是否存在瓶颈,最后再看看前后端整体技术方案设计是否合理等。如果是产品和设计不够完善,我也会向他们提出我的建议,与他们一起讨论,我相信有更好的设计方案,大家都是喜闻乐见的,毕竟大家的出发点和价值观是一致的给客户代码价值,我觉得作为前端程序员,开发高性能,少占客户设备资源的应用也是很重要的。有时候性能问题不太明显,肉眼看不到界面的卡顿和不流畅,但有一些高端优质客户通过查看系统资源,会觉得运行你的网站或 App 特别占(CPU+ 内存+ IO)资源,用的越久电脑越卡;或者用你的应用,就不能开更多其他应用,慢慢的会给客户留下非常不好的印象,很容易丢掉这些客户群体且留下不好的口碑。所以给客户带来价值,作为一线技术人员,开发出来程序能少占一点内存,让 CPU 少执行一条指令,少让 UI 界面无畏的重复渲染,拥有这种「微优化」意识,凑少成多,最终输出的产品就会运行得更流程,资源占用更少。我的理解这也给客户带来了价值

————————

“< strong > bring value to customers < / strong >“

As a front-end programmer, I should be the programmer closest to the customer. Therefore, in my daily development process, I always think from the “user’s point of view” and use multiple dimensions to measure whether the function design is reasonable, whether the operation steps are simple and easy to use, whether the interface style is consistent, atmospheric and beautiful (advanced human needs), whether the interface is stuck and lost frames during operation, and whether the performance is efficient. If it doesn’t meet the requirements, or this function can be done better, I will find a way to solve it. There may be a bit of obsessive-compulsive disorder here. Start with the front-end code, the front-end is OK, then check whether there is a bottleneck in the back-end interface, and finally check whether the overall technical scheme design of the front and rear ends is reasonable. If the product and design are not perfect enough, I will also put forward my suggestions to them and discuss with them. I believe there is a better design scheme, which is loved by everyone. After all, everyone’s starting point and values are consistent, which gives customers code value. I think as a front-end programmer, it is also very important to develop applications with high performance and less occupation of customers’ equipment resources. Sometimes the performance problems are not obvious and the interface is not smooth. However, some high-end and high-quality customers will feel that running your website or app takes up a lot of (CPU + memory + IO) resources by viewing the system resources. The longer they use, the more stuck the computer becomes; Or if you use your application, you can’t open more other applications. It will slowly leave a very bad impression on customers. It’s easy to lose these customer groups and leave a bad reputation. Therefore, it brings value to customers. As a front-line technician, the developed program can occupy less memory, let the CPU execute less instructions, and let the UI interface render repeatedly without fear. With this awareness of “< strong > micro optimization” < / strong >, the final output products will run more processes and occupy less resources. I understand that this also brings value to customers