The programmer and his woman

Chapter 118: Offending Again

"Director Wang, you really don't have to keep a close eye on our backend team." Lao Gao's words were filled with dissatisfaction and reminder. "Our team has already gone all out to carry out the module you requested last time. I know you are anxious, but maybe you should also spend some time to urge the front-end mobile team. After all, their work is also an indispensable part of the entire project."

Lao Gao's words made me think deeply. Indeed, I have always focused on the development and progress of the backend, and have not paid enough attention to the situation on the client side. I recalled the recent communication with my boss, and he was indeed more concerned about the display effect on the client side, because it is more directly related to the user experience and the final presentation of the product.

I took a deep breath and said to Lao Gao, "You are right. I should pay more attention to the progress of the entire project." I stood up and decided to take action immediately.

I walked to the vice president's office, knocked on the door and entered, and explained my thoughts and concerns to the vice president one by one. After listening, the vice president expressed his understanding and agreement with my views. He quickly organized a meeting and invited the heads of the Android and Apple development teams to participate.

At the beginning of the meeting, I first introduced the modules that the backend team had completed, and explained in detail the importance and role of these modules in the entire project. Then, I emphasized the urgency of the project and hoped that everyone could work together to ensure the smooth progress of the project.

I turned to the two client managers and said sincerely: "At present, the backend server has been fully prepared for you. This module already has basic calling functions. Next, you need to adapt and develop it according to the characteristics of your respective platforms."

The vice president glanced at the two platform managers in the conference room, and her eyes revealed her attention and expectation for the next discussion. She leaned forward slightly and asked, "Regarding the development cycle of this new module, how long do you two managers think it will take to complete?"

The person in charge of the Android platform did not answer directly, but turned to look at a young programmer next to him, who was the technical backbone of their team, named Long Er. He patted Long Er on the shoulder with trust and said, "Long Er, you are the technical core of our team, you can estimate the development cycle of this module."

Long Er nodded, closed his eyes, and seemed to quickly simulate the development process and possible problems in his mind. After a moment, he opened his eyes and said seriously: "Based on my understanding of this module and previous experience with similar projects, I think a week should be enough to complete the development of this module."

I listened to Long Er's answer and couldn't help but feel relieved. I have a deep understanding of the client development process and know that a week is indeed a reasonable estimate for such a module. However, just as I was about to nod in agreement, the person in charge of the Android platform suddenly changed his expression.

He stared at the programmer with wide eyes and said sternly: "Long'er, you have to think about it carefully! How can it be completed in a week? Do you know how many other modules this module will interact with in the future? If you don't think carefully, many problems may arise in the future. Have you considered all these?"

Long Er was obviously startled by the sudden attack from the person in charge. He scratched his head and said awkwardly, "Boss, I really haven't thought about it that much. But from a technical perspective, a week should be enough."

"Enough? Do you think enough is enough? Let me tell you, this project is very important to our company, and we can't be careless or take chances. A week is too short. I think it will take at least a month to ensure the stability and compatibility of this module." The person in charge's tone was unquestionable, and he had obviously made up his mind.

Another Apple platform manager also nodded in agreement. Their attitudes made the atmosphere in the conference room tense. I realized that if this issue was not properly handled, it might have a serious impact on the progress of the entire project.

I couldn't sit still any longer, so I decided to speak up for the programmer. I cleared my throat and said, "I understand everyone's worries and concerns. However, from a technical point of view, one week is indeed a reasonable estimate. Of course, we also need to consider the correlation between modules and future scalability. However, I believe that as long as we do a good job of early planning and testing, we can ensure the stability and compatibility of the modules. At the same time, we can also consider iteration and optimization during the development process to deal with possible problems."

Before I finished speaking, the technical manager shook his head with a disdainful smile, his eyes revealing his disdain and contempt for our product department. He slowly spoke with a mocking tone in his voice: "You people in the product department always think that everything is simple and don't understand the complexity of our programming. The time you gave, in my opinion, is simply a joke and has no reference at all."

His words were like a sharp knife, piercing my heart. I took a deep breath and tried to keep myself calm. I looked up at him and said firmly, "I'm sorry, both of you. I want to clarify that it's not that I don't understand programming. Before I became a product director, I was indeed a client development engineer and also served as a technical manager. Therefore, I have a deep understanding and judgment of the development cycle of such a program. I firmly believe that the time given by this colleague is very accurate."

My words made the technical manager's face change slightly. He didn't seem to expect that I would refute him so directly. His eyes widened and his tone became more sharp: "Oh, really? You are really good. You know both design and development. Then I think you can handle this project by yourself. Why do you need our R&D department to hold a meeting? Just do it yourself!"

His words hit me like a hammer. I felt angry and dissatisfied, but I suppressed my emotions and didn't lose my temper. However, the technical manager's temper seemed to be even worse than I thought. He stood up angrily and slammed the door. Seeing this, others followed him out of the meeting room, leaving the vice president and I staring at each other.

I watched the technical manager slam the door and leave, feeling helpless and angry. His words and attitude made me feel extremely disrespected.

"If they don't do it, I will do it." I said to the vice president firmly, with determination in my voice. I knew that I couldn't back down at this time, otherwise it would only make other departments look down on our product department even more.

The vice president looked at me with a frown on his face. He obviously felt my anger and dissatisfaction. He was silent for a while, then slowly said, "Xiao Wang, I understand your feelings, but we must deal with this problem calmly. You may be able to complete the development of this module by yourself, but have you ever thought about the consequences of doing so?"

I was stunned for a moment and didn't answer immediately. The vice president continued, "First, you will offend the entire R&D department by doing this. They will feel that our product department does not respect their technology and work. Secondly, even if you can complete the development of this module, the subsequent maintenance and optimization work still requires the support of the R&D department. If we have a falling out with them now, it will be difficult to carry out future work."

I listened to the vice president's words and gradually calmed down. I realized that my impulsiveness and anger might make things worse. I took a deep breath, calmed myself down, and then said, "Vice president, you are right, I was too impulsive just now. But we can't just let them bully us like this."

The vice president nodded, agreeing with my point of view. She said, "I understand how you feel, but we can't just go head-to-head. We need to find a better way to solve the problem. We can communicate with the R&D department again, try to understand their concerns and difficulties, and then work together to find a solution that both sides can accept."

"Okay, I see." I sighed and said to the vice president, "Maybe I'm not used to the way our company works." I handed over a dozen pre-pasted invoices and added, "I have sorted out these invoices. There is a detailed list on the paper, listing the specific uses of each expense."

The vice president took the invoice, glanced at it casually, and then put it on the table. However, just a few seconds after putting it down, she seemed to suddenly remember something, quickly picked up the invoice on the table again, looked at the amount on it, and exclaimed: "More than 2,000? What did you do to spend so much money?"

I explained, "It's like this, Vice President. A few nights ago, I invited colleagues from the R&D department to dinner on behalf of the product department. They said this was normal communication between the team, just like menstruation, which happens once a month." I tried to describe it in a relaxed tone, but I could feel that the vice president's brow was furrowed.

"There's no need to spend so much money!" the vice president said anxiously, "The product department previously treated the heads of other departments to a meal, and it was only a few hundred yuan at most. I really can't ask the boss to reimburse you for more than 2,000 yuan!"

I frowned and explained, "Actually, I really didn't want to invite him to dinner. It was Lao Gao who said he knew the limits and insisted that I treat him. He also said that this was the entertainment expenses of the product department. Xiao Chen from the product department went with me that day. You can also go and ask Xiao Chen." I thought back to what happened last night and felt helpless.

"This Old Gao!" The vice president slammed the table angrily. "He sees that you are a newcomer and don't know anything, so he deliberately bullies you. I'm going to settle the score with him right now!" Her tone was filled with anger.

I quickly pulled her back and reminded her, "Vice President, don't be impatient. Didn't you advise me not to confront each other head-on? If you quarrel with the architect now, how will our product department carry out its work in the future?"

After hearing what I said, the vice president calmed down a little. She sighed and said, "Well, what you said makes sense. Forget it, I'll try to solve this matter first and see if I can get the reimbursement. Xiao Wang, our budget has exceeded this month. Try not to spend any more next month. We have to be frugal in the next two months."

I nodded to show that I understood. I know that as a newcomer, I still have a lot to learn and adapt to. At the same time, I also expressed my gratitude to the vice president for her help and support when I encountered difficulties.

Although the vice president verbally said that he would not hold Lao Gao accountable, it was clear that the news had reached Lao Gao's ears. That day, Lao Gao came to me on purpose. His face was gloomy, and he seemed to be suppressing his dissatisfaction. He asked me directly: "Xiao Wang, why did you go to the vice president to complain about me?"

I was slightly stunned, then pretended to look innocent and asked, "Mr. Gao, what are you talking about? I don't understand." I pretended to be confused on purpose, trying to test Mr. Gao's opinion.

Obviously, Lao Gao didn't buy my trick. He glared at me and raised his voice a little: "Don't play dumb with me! The meal cost a little more last time, but you also saw that we were very fast when we did the work for you. I was very nice, right? And that day I taught you how to make money. If you come to the company every night, the money will come out. But you actually went to the vice president to complain about me!"

I was a little surprised by what Lao Gao said. I didn't expect him to say it so bluntly. I explained, "Boss Gao, you misunderstood. I didn't sue you. I just followed the company's regulations and took the invoice to get reimbursed. This is the company's normal process. I didn't mean anything else."

Lao Gao's expression softened a little after hearing what I said, but he still had no intention of letting me go: "Humph, let me tell you, no one in this company is a fool. You'd better not play these little tricks and do your job well."

I nodded and said nothing more, because I knew that arguing with an old-timer like Lao Gao would be futile. His way of thinking and style of doing things were already deeply rooted and could not be changed by just a few words. So I left on the pretext of something, leaving Lao Gao standing there alone, his face so gloomy that water could almost drip out of it.

He stayed alone for a while, his eyes wandering in the empty office, as if he was looking for something, or just emptying himself. Then, as if he had made up his mind, a sneer appeared on the corner of his mouth, and a hint of ruthlessness flashed in his eyes. He murmured in a low voice, his voice full of threats and dissatisfaction: "You are waiting for me, kid, you dare to do this to me, you offend me, you will suffer the consequences."

His words were full of threats and warnings, as if he had planned a future full of traps for me. But I knew that I would not back down. I would stick to my principles and do my job well. At the same time, I would be more cautious so as not to fall into Lao Gao's trap again.