2019 year-end summary New Year 2020 Outlook
1, following the timeline
| time | Agenda |
|---|---|
| April 15th | Large paper School Audit |
| April 19th | Large paper submitted for review |
| Mid-April | Essay delivery |
| 5 mid-May | Go internship |
| In late May | Thesis Defense |
| June 21 | graduation |
| July 1 | Internship turn the trial period |
| In mid-August | Small paper were accepted |
| November 15 | Probation positive |
2, school graduation season
Large papers were revised 5 draft, in the third draft, the third chapter of the single point calibration algorithm and the implicit calibration algorithm to string together the fourth chapter, the basic thesis With such a large overall sense, the experts behind blind trial scores were 80 points or more;
then the essay , it is more knock knock sill, and write when Kenji "single-point calibration algorithm" small paper quality tests are mentors to death, and then after the big thesis, wrote the first two essay "implicit calibration algorithm" cast "computer science." In mid-April submission, because the magazine did not reply to a message in early June when graduation season, so just take a diploma. Until the end of July to get the job offer, then pay a sum of expedited fee, and finally published a paper in August, September, successfully got the degree certificate. At this point, reading career come to an end.
Lesson :Essay ready too late, general domestic small papers published in the period of three months or more, so be sure to vote in a reply three months ago to go out, if you can not make sure that would be accepted, it would be much longer in advance. Do not put at risk future, if not get a degree certificate before the positive, offer no, I was the only student graduating from our college in September, all college students are delaying graduation more than 30 months.
3, entering the workplace
Since the little things in school, we only have a graduation reply, beginning on May 15, to the internship. In the specific company to do these things
| time | project | value |
|---|---|---|
| June to August | Docking operational requirements : develop operational tools, Improve Efficiency, tools (offline brand, category sorting, marking query tools, etc.), existing code performance optimization | The successful completion of all kinds of tools to solve some of the pain point operations,Scheme introduced hierarchical data written Patent "A method of hierarchical data deduplication, apparatus and media" |
| September to October | Shanghai Project: Reconstruction of library property, property management, property management library, Lynx attribute synchronization | Value: 1, the property value of id, easy management, 2, expanding the property, the property value data volume, 3, add the attribute level concept |
| October - December | Shanghai Project: Reconstruction of property categories, back-end category property, the agreement category property. | Value: 1, Category property has a conceptual level, the 2, the concept of the new protocol category attributes to meet the individual needs of different instances of institutions |
Growing pains entering the workplace continued for about two months, at school and in the company's laboratory difference is still quite large, especially in regard with the brain, feeling the beginning of the work day with a brain volume in the company is worth at school one week time, the company has a morning meeting, a progress report on the project every day, the school will only open once a week, the deepest feeling is that a lot of the great God is, what will be the team leader and consequently, unlike in school, are a bunch of rookie . After the company to adapt to the rhythm back, to enhance efficiency, overall it is a lot easier.
| Compared | laboratory | jobs |
|---|---|---|
| Daily routine | 9 am to 10 pm | As early as 9:30 to 6 pm, the general added 9:15 of overtime, a taxi report |
| Intensity of work | Less intense during the day to see the papers, write code, you can do your own thing at night | Great strength, inverted the project, had to report progress every day |
| Sense of accomplishment | To tell the truth, no sense of accomplishment graduate admitted to graduate large, a problem can not be solved people, low productivity, stepped endless pit | Full harvest, made rapid progress, problems encountered stuck for 10 minutes, you can ask the god |
| reward | The harvest is the theory of knowledge, innovation | Harvest is practical skills, ability |
4, 2019 completion flag
| 2019 flag: | Complete schedule | Remark |
|---|---|---|
| 1: Every two weeks to write a technical blog, original content, mainly in-depth understanding of the technology-oriented face questions of | This amount is less than complete, full-time tm used in overtime, with an estimated blog wrote 10 articles, mainly some of the problems encountered in the development process, such as stream-flow calculation, mysql index, NIO and the like | |
| 2: The need to learn techniques: spring-depth understanding of ecology, spring boot / spring cloud / mybatis plus and spend in the project | 1, springboot finished school instructional videos, also were using the actual production, but the underlying source code, and design patterns have not yet mastered, have to continue to learn. 2, for micro-services architecture, the company is using Ali dubbo, springcloud no access to, or have to follow-up study, compared with all aspects dubbo, learn from each other. 3, mybatis plus spend, and the use of a plug mybatis, commonly generated code, reduce development time | |
| 3, stop and do good scientific research, since about March have submitted papers, as well as essays was published, the next time something busy; | over，我tm再也不用写论文了 | |
| 4、技术学习的最终路线：我想成为一名能独当一面的架构师 | 还远得很，慢慢来，先cover住需求，把自己负责的标准中心做深做精。 |
5、2020努力的方向
-
bug数据较多：全年bug数量79个，排名共享业务第八名；reopen 13个
原因：对下游业务了解不够充分，部分逻辑没考虑到；经验不足，不停踩坑，reopen全部发生在第三季度，原因是不熟悉联调提测流程，第四季度没有一例reopen
如何避免：多做code review，并请教经验丰富的同事 -
现在的状态是能够cover需求，有吃力感，也没有很多的时间停下来思考，担心的点：完成任务的同时有没有兼顾个人成长
延期原因： 对需求的时间、难度判断还需要提升开发项目估时不准，导致延期，开发效率还不足，正在为coding得又快又好而努力
如何避免：将任务更加细粒度的分解，每个小点单独估时；考虑问题全面，性能问题，下游业务的需求，历史数据的迁移都得考虑
如何兼顾个人成长：每天看一篇技术博客(专注于数据库，各类中间件，分布式架构)，每两周写一篇技术博客，与小组交流讨论，提升技术深度与广度 -
假定明年让你独立拎标准中心， 你觉得你还差(工程、技术)在哪里？需要朝哪些方向努力并刻意练习的，能落地的点有哪些？
在工程方面需要提高的点：学习解决问题的思路和方法。多去解决问题，珍惜每一次线上的故障，看到问题到解决问题。越久的项目，坑越多，你不能让这些坑持续下去，不然会越做越累，给自己定个小目标，每个月解决一到两个坑点。
需要朝哪些方向努力并刻意练习的：数据库性能瓶颈分析，应急响应策略学习
能落地的点有哪些：第一步：做技术文档时全面考虑各种逻辑，历史数据的迁移；第二步：和业务方第一时间定义好接口，避免时间浪费，将好的设计思想用在自己的项目中；第三步：做好代码review，避免慢SQL等各类性能问题 -
技术栈的学习
| 技术 | 功能 | 学习途径 |
|---|---|---|
| canal | 用于mysql增量日志数据的订阅、消费和解析，阿里巴巴开发并开源 | b站+官网 |
| elastic-job | 分布式任务调度框架，当当开源 | 官网+b站教学视频 |
| rocket-mq | 处理高并发的消息流转，能处理万亿级别的消息 | b站教学视频+代码 |
6、程序员工作法(来自郑晔《10x 程序员工作法》)
1. 精力放在哪儿
设计算法、改进系统、优化系统等富有创造性和成就感的本职工作中
2、本质复杂度和偶然复杂度
本质复杂度：解决一个问题时：无论怎么都必须做的事情 eg：开发网站
偶然复杂度：因为选用的做事方法不当，而导致要多做的事。 eg：选用了错误工具
精力聚集在本质复杂度上，提高工作效率，摆脱直觉的束缚。
3、原则：
-
以终为始: 确定好真实目标
在工作的一开始就确定好自己的目标。我们需要看到的是真正的目标，而不是把别人交代给我们的工作当作目标 -
任务分解：找到实施路径
大目标拆分成一个一个可行的执行任务，工作分解得越细致，我们便越能更好地掌控工作 -
沟通反馈：解决与人打交道出现的问题
疏通与其他人交互的渠道。一方面，我们保证信息能够传达出去，减少因为理解偏差造成的工作疏漏；
另一方面，也要保证我们能够准确接收外部信息，以免因为自我感觉良好，阻碍了进步。 -
自动化：解决与机器打交道出现的问题。
是将繁琐的工作通过自动化的方式交给机器执行，这是我们程序员本职工作的一部分，我们擅长的是为其他人打造自动化的服务，但自己的工作却应用得不够，这也是我们工作中最值得优化的部分。
生命里没有人会一直陪伴你，陪伴你一个月、一年、十年都是你生命中经历的一部分。所以，对于生命中的匆匆过客，不要去纠缠过去，放眼将来。做最好的自己，等待你生命中的她出现时，才不会错过。弃我去者，昨日之日不可留。乱我心者，今日之日多烦忧
