Hello readers, I have been blogging for more than a month, everyone’s answer is… (You must know better than me, because you are the person who gives feedback). I have been inactive for a long time at work. People say “Xianxin is the devil’s studio”, and I want to change it to “Xianxin is a tester’s studio”. Before leaving my current organization, I was thinking about what slowed down my work so that I could make a better contribution to the company. Can I land? [I’m still searching:(, is anyone interested?] When I made the list, I encountered something that really slowed down the work of software engineers! (including my developers) most of you have encountered When it comes to the same question, did you guess right? Tools! __ Tools that slow you down at work! ___ “Now tools are used to increase the speed of work, not to slow down, shut your mouth, don’t let your The devil reigns over you” If you plan to say something similar after reading everything…please don’t continue reading…even so, if you want to read, I’m (not) lucky: D! Port Okay, I was working on a tool to access the product through a USB port. As long as another tool is installed on my PC, which can also access the USB port for different purposes, it will work. I have a hard time figuring out how to get them to cooperate with each other. Finally I ate some of my food, for example, 2 hours. If I did not leave this information to my teammates, a total of 2 * 4 = 8 working hours, or even more or less, I would find the same. Inconsistency problem No good, once my colleague complained that a certain tool did not work on his PC, but it worked well on my PC (I mean, on my PC). He is sitting in front of my computer to deal with it. Of course he is also facing a deadline. If he starts looking for a solution for a specific tool that cannot run on his computer, more time will pass, but I will still lose an hour work. Now, considering that every PC has the problem of working for tools, 4 * 1 = 4 hours of working time are lost in a day. (Of course it is an approximation, after all, I will not report anyone giving the exact number) Now restart! When some tools do not work, the usual thing to do is about 10 minutes, and it happens at least twice a day every 2 days a week, so 10 * 2 * 4 (number of days of the week) * 4 (person) = 4 Lost working hours per week. Send report! Whenever there is a problem, Microsoft wants to see who is competing with them, you will see this submission report message, and we usually do not send it. This ignorance of all of us prevents Microsoft from obtaining the necessary data to solve any problem, if any, due to its products. (Assuming this adds a very trivial part and ignore it) Limited Licensed Tools This is something everyone can agree on. All the companies I have been in lack a tool license, which generally results in a loss of 1 hour per person per week in the company. So it is 1 * (number of your workers) = time lost due to this factor. Tools that work on the server Some tools are designed to work on the server, and you are just another customer. You just keep it waiting, sometimes you will see a “timeout” message. In fact, it is “our timeout” rather than “server timeout”. A person spends at least once a week for 10 15 minutes and then a person starts working, therefore 10 minutes * (number of workers) * 5 (working days) = one week of time lost by this factor. Building machines Building machines are a big factor, I don’t use them a lot, but I see a lot of people start the build overnight, and in the morning they see the build fail midway, if it’s a full release of the product, then build should take almost 46 hours to complete. Assume this happens once a week for each developer or a small group of testers or release engineers. 5 hours * (number of people starting build) * 5 (working days) = the total time wasted waiting for build during the day . This is very important because the developers are building sometime in the afternoon, and the testers are forced to finish their work before the COB! I pray that all machines built work properly at night. Drivers I want to know that most of the tools I use to connect to hardware have driver issues. Whenever I find that the hardware is not detected, I need to uninstall and reinstall the driver to use the tool. Why don’t people create another tool to uninstall and reinstall drivers? Simply put, each meeting takes 10 minutes and I happen at least twice a week. 10 minutes * 2 (number of occurrences) * (half the number of workers) * 5 (working days) = the total time lost in a week due to this factor. __ End __ Tools that slow down your work! ___My God! In general, about 30% of our time is wasted on management issues using tools, and the rest … There is always… a meeting. In all this, we contribute to the following benefitsBtw, I wanted to talk to you about https://bugasura.io . Its a tool that modern teams use to track bugs. I recommend you take a look at it and see if its suitable for your needs*