"The time is not lost, the creation does not stop, this article is participating in the 2022 mid-summary essay competition "
sequence
I feel that this year has been a long time. After the year, I resigned. After a month, I joined an outsourcing company. I thought about summarizing the ups and downs of the past half year.
This article is mainly based on complaints, supplemented by job-hopping.
Resignation experience
Personally, I feel that the department leaders have changed too quickly, four in less than two years, and the technical accumulation of research and development is not enough, and I really cannot improve myself. In fact, the key reason for leaving may not really be salary. Last year, the company recruited a research and development team with four or five people. At this time, the nightmare began.
The local team of motorcycles
At the beginning of the cooperation, I wanted to gather the strength of both parties to build a new product. Unfortunately, because of the withdrawal of our leader, the local team completely came to power. As a result, the mid-term cooperation product was rejected by the local architect and began to be based on their local knowledge. Flavor system project cooperation.
They used it before svn, and their system architect said that it was for the convenience of our team. They built one on the intranet gitolite, and then the front-end code, back-end code, and design documents were all placed under one gitwarehouse, and there was only one masterbranch (note that it is not monorepo, This system architect is also using git for the first time, I don't know what it is monorepo), resulting in frequent code conflicts and files being deleted. They are not familiar with git, let alone, update the project code jenkinsdirectly .dockerftp
The back end has no swagger apihabit of using it. They have always used word documents for the interface documents , which are written by the system architect. The front end needs to read the word document for the interface , and the back end also needs to read the interface. If you think you can understand it, you can do it Tucao, I can only say, ah, yes, yes, it's 2022, jq can also write pages, Renaissance!
There is also a front-end leader, he likes to write , the first sentence let vm = thisof each function must be , and this sentence must also be written in the life cycle function. You said that he does not understand the pointing, he said that he has read the source code, so writing can fix the pointing , somewhat speechless.functionlet vm = thisthisvuethis
Let's take a look at the api interface written by the front-end Leader
import axios from "@/utils/http";
import url from "./url/index";
create (a, b, c, d, e, f, g, h) {
return axios.post(url.createUrl, { a, b, c, d, e, f, g, h})
},
复制代码I personally think that it is a bit redundant to extract the interface urlas a variable, but it is a matter of opinion. The only thing that is really worth complaining is the passing of parameters. Obviously, an object can be passed. This is the case for API interfaces. Some interfaces have more than a dozen or 20 fields that pass parameters one by one, which is really speechless.
The back-end interface is not paginated by default, even if there are thousands, tens of thousands of data are not paginated, the local architect thinks that paging affects performance, the front-end leader likes to work, and the paging is handled by the front-end; The interface that needs paging needs to be proposed and developed according to the situation. It can be seen that the function of exporting data is responsible for the front end, after all, all the data has been obtained;
Supplementary slots, all interfaces are post; upload files need to be transferred base64; SFCthe pop-up window is not individually packaged, with thousands of lines of code; if not used dayjs, all time processing functions are written by yourself... There are also multiple business slots that are difficult to describe
A few of them always look like they are high above, and our opinions and suggestions will basically be rejected, or they will not affect or unnecessary, or they will simply say that you don't understand. Without self-knowledge, like a frog in a well. There is a saying that I think is very appropriate to describe their way of doing things. Obviously, they can take high-speed rail and planes to their destinations, but they only choose to drive motorcycles.
Shark Chili and the camera storm
直到一位新的领导的到来，我以为他是蜻蜓队长，没想到他是鲨鱼辣椒，是压死骆驼的最后一根稻草。最早我还是很信任这位领导的，至少他确实改变了部分现状，比如前后端代码的git仓库分开了，可惜还是一条分支；需求任务开始评估，但是没有产品经理,没有需求文档和原型，一切都是口头决定，计划两周完成，会压到一周内；开始让后端使用swagger ui，可惜只有新接口使用了，旧接口依旧要看word文档。
可是这位鲨鱼辣椒，算是中古型pua选手，很喜欢单独找人谈话，实际是想从每个人嘴里套话。有时候聊一大轮，都找不到重点在哪，或者根本就不是问你的问题，只是想从你的嘴里知道别人的真实想法罢了。可能我算是比较晚醒悟过来鲨鱼辣椒是在pua，稍微醒目一点的同事已经有所防范，直到有一次让我带头把旧系统的模块做到土味系统中来。
当时没有需求，只有旧系统的页面，基本功能都是照搬，东西做完了，其他部门的同事不用。鲨鱼辣椒找我聊，只记得一句，你不是一两年的前端了，三年经验的前端这都考虑不到。这种打压人的话，确认造成了真实伤害，但是自己和同事复盘了一手，觉得这就是在pua，根本就没有需求，没有从客户的想法来指定需求，并且建立在他们这款土味系统里，多少有点水土不服。
这位鲨鱼辣椒，还有一个骚操作，在办公室放了一个摄像头，同事说这个就是拍我们谁迟到、不在工位上的。最开始我不信鲨鱼辣椒会这么捞，直到有一天我看到这个摄像头会转，我用手机拍下来了。导致有一天，鲨鱼辣椒专门在我背后站着半个小时，用手机偷拍我摸鱼并向人事投诉。隔了几天后，hr到我单独聊，并有劝退的意思，但后续也因为偷拍和放摄像头这事不道德而不了了之了。
扪心自问，出来打工而已，业务忙的时候也按照要求996两个月了，没有需求做完之后被pua，还用摄像头监控员工，当时整个人是裂开的。
期间太多的细节了，鲨鱼辣椒的pua行为，土味系统团队的问题，慢慢的，上班变得越来越压抑。
到了今年一月部门开始评绩效，某些原因，年终奖被打五折。
待续
面试经历
年初就已经在改简历，在各种招聘app上开放简历，还有两三次线上面试，个人感觉良好。期间还继续看面试题，了解Vue3，vite等等。
到了线下面试，很容易大脑一片空白，不如线上面试轻松自如，特别是被问到不记得、不会的，比如TCP和UDP的区别，直接破防。
说到底还是没有背熟大部分的面试八股文。
面试了十几家之后，即便有几家整体面试过程十分良好，依然没有拿到offer。心里开始有一点点焦虑了，可以投简历的公司慢慢在减少，面试邀约也就每周两三家。
后来在一个不经意的早上，收到了一个投递简历的邀请，一般还是外包公司。仔细看了一下，公司位置距离我家很近，所以投了简历。也是因为疫情原因，原本计划线下面试的，改为线上并且推迟了两天。
虽然不是第一次面试外包岗位，但是这次的面试相对来说很轻松，面试的问题也相对简单，可能是运气成分较大，问的都回答上来了，回想起来当时状态也很好。随后各方面了解清楚了，offer就到手了。
当然薪资也被压了一点，但在心理预期之内。
入职
入职了三个月，可以说没有加班，只有一次周末来了两天，其余时间早九晚六准时上下班。
工作环境确实一般，没有正编一样的工位，所有的外包同事都在一个办公室里，优点是交谈方便，缺点是稍微有点挤。
Regarding the project, I can really complain a lot about this. For example , there are vuethree or four thousand lines of code in a file that are not divided into components. setTimeoutThere are still various unnecessary ones let that = this. Of course, there is time to optimize step by step, and maybe part of the code can be optimized, and also Can webpackpackage configuration optimization. It can also be far-fetched to say that at least axiosparameters can be passed to objects, and there is no need to pass parameters one by one in order.
Interpersonal relationships, there are three or four project teams, and I feel that every colleague can talk to each other, but I think there are still very few common topics, and there are almost no topics other than work.
Compared with the previous home, the technology is better, at least gitlab, Jenkinsthere dockerare also some projects. The front-end part is actually similar, and there are no Vue3projects for the time being. At least there are swagger uiinterface documents, and the front-end project has a reasonable gitbranch.
The overall advantage is that within an hour of commuting to and from get off work, there is almost no overtime, and the salary is higher than expected.
to be continued
reflection
In fact, I can leave earlier, I don't need to waste time with the local team, especially in terms of communication and advice with them, maybe I will not be pua if I leave earlier , at least I won't waste more than half a year to participate in them Among the earth-flavored projects, projects that are more pitted than outsourcing projects.
In addition, in terms of code quality, after getting used to eslintit, you care about too many unnecessary details, and consider whether you need to ignore this idea.
to be continued
Epilogue
The above content is only my personal opinion. If you don't like it, don't spray it, thank you.