Programmers working in technology is not enough to copy and paste it? Many people have misunderstood

The nature of the programmer is to solve practical problems, and is not paste the copied had little to do, especially in the ratio of application-level development must ultimately copy and paste in the actual programming, especially in some common programming mode or method, if there are ready-made codes of course you can come and took the direct use, there is no need to re-write it in many years of experience in software development, programmers write common code is generally now have several ways

1. The primary entry stage programmers

The main experience is also thinking about how to achieve, are still struggling in a clothing line of code to achieve some simple features and anxious, junior programmers to implement a simple sorting also search the Internet example, it is best to find examples can be used to direct the use of, and then facing examples of how to achieve, if let alone to write their own is not able to complete, joined the line a year basically programmers are of this state, most of the code is from search on the web to some source in the case of not sure, take over verification use, still wondering how to achieve the most basic functions and frustration.

2. The independent engineers do module unit

Software engineers at this stage already has the ability to do small independent modules, probably know how to do it, their first idea of ​​a basic framework, or simply all of the code directly to get all of their own, or find their own code to function and matching online and then enter into it, according to their own ideas do not affect the overall functionality, copy and paste the code this time already for our own use, and for common code that already have their own independent thinking, has been slowly penetration is not better implementation code, wondering how the code can be efficiently implemented at this stage for the time code implementation has been compared to a lot of the first stage of compression. At present, the vast majority of programmers in this stage.

3. Place the code as a tool to use

编程思路为主导的阶段,这个阶段的程序员基本上很少提及代码的实现,琢磨着实现的功能如何高效有用,在表面上这帮人平时就是上网看看资料或者看看别人写的代码很少拿出大块的时间在琢磨着如何写代码,代码到了一定层面就是工具般的存在,为了实现一种场景可以不受到编程语言的限制,很多人觉得掌握的编程语言越值钱的这种理论是不存在的,编程里面最值钱的是编程思想以及实际解决问题的能力,可能我们在平时的编程工作中经常有这么一帮人在公司就是定海神针般的存在,只要遇见难的问题就推给他们,基本上都能给出解决问题的方案。

4. 研究轮子甚至造轮子的工程师

这种属于架构师级别,有点夸张的甚至都没怎么写过代码,完全的设计模式,当然绝大部分的架构师都是写代码出身,而且本身代码基本功非常强,常见的大大小小的功能实现起来也不在话下。平时就是研究框架的如何实现,如何能够稳定的运行起来,是不是能够构造出新的组合或者框架,平时大部分的时间不一定是在盯着代码看,主要还是分析软件运行内在规律。

复制粘贴在平时的工作中使用的非常常见,也没有必要拿出来大作文章,编程最直接的结果是最简单方式解决问题,没有必要为了显示自己能力的强大而去所有的代码都要自己去写。编程目的是打造产品,为生活提供更多的便利。

推荐阅读:

学Python的程序员,编程能力都“退化”成什么样了?

学习前端开发的路线是什么?互联网趋势,技能需求

选择程序员,意味着终生学习,眼前的安逸,不过是迷惑人心的温床

Guess you like

Origin blog.csdn.net/zhizhun88/article/details/92433682