Looking at the screen full of code, Zack couldn't help but exclaim, "Holy crap, you wrote this?"
"Stop marveling and get to work!" Nick urged, patting him.
Zack grabbed his arm, then looked him up and down with an expression of disbelief, saying, "Who are you, and where is Nick?"
"Get lost!" Upon hearing this, Nick rolled his eyes and pulled his arm away, saying, "Stop messing around, get to work, we have limited time."
"No, seriously, did you actually write this? I don't believe it. This code is on an entirely different level from what you wrote before. This level is far better than that Tesla engineer who came to school for the presentation last time," Zack said, looking incredulous.
"Especially this part, or iteration..."
Seeing Zack's surprised expression, he couldn't help but interrupt, "There's a lot you don't know yet, you'll find out in time."
"Really?" Zack asked, half-doubting.
Nick smacked the back of his head and retorted irritably, "When have I ever lied to you?"
Zack shook his head and said, "That's hard to say. For instance, when we were sophomores welcoming new students, we met a pretty freshman, and when you asked her out to dinner, you lied to me saying..."
"Boss, come take a look at this," Terry shouted at him.
"Boss?" Nick asked, slightly stunned.
"Yeah, what else would I call you if not boss? You want me to call you 'Don'? Don Nick?" Terry asked him.
Nick rubbed his nose and said, "Call me whatever you want. What is it?"
"This is the drone I designed, along with the list of related components. Take a look," Terry said, handing him the blueprints.
"Based on your requirements, I've referenced some swarm drones currently on the market, so I think a quadcopter, which is relatively stable and easy to control, is our best choice."
Terry showed him the schematic diagram of the drone drawn in the picture, saying, "Look, these are the four axes for mounting the motors and propellers. The middle section is for carrying the flight control system, battery, and other payloads."
"What size can this type of drone be made into?" Nick asked, looking at the design drawing.
Terry shook his head and said, "That depends. The size range for these quadcopters is huge. Large ones can be five or six meters in diameter and carry people. As for small ones, it's said they can now be made the size of a thumb and are used by the US Military for battlefield reconnaissance."
"Of course, it depends on our purpose. If it's just for flight, it can be made very small. But if we want to carry a payload and stay airborne for a long time, it needs to be a bit larger. Given our current intended use, I think a small drone with a diameter of about ten to fifteen centimeters is appropriate."
"So, how much does it cost to build one of these drones?" Nick asked after some thought.
Terry looked at the component list and replied, "That's not certain; it depends on the quality of our components. Generally speaking, if we assemble a fist-sized drone like this ourselves, it will cost at least three or four hundred."
"What if we buy one?" Nick pressed.
Terry thought for a moment and said, "If we buy one, it's cheaper. On Ebay, a fist-sized drone like this with a camera and remote control costs only two or three hundred, and they are quite well-made."
Seeing Nick's puzzled expression, Terry smiled and explained, "It's a matter of production costs. They produce in large quantities, so naturally, the cost comes down. Plus, they get components directly from manufacturers, so the price is definitely much cheaper."
"Two or three hundred? Can we buy these drones and modify them?" Nick asked after some thought.
"Modify?"
Terry thought for a moment, then nodded at him, "It's possible, but we don't know how good these drones actually are. We need to buy some samples from different brands to take a look, then pick one that suits us."
"We need a large quantity, at least one or two hundred. An order like that can definitely be placed directly with their factory, and we can even have them produced according to our requirements. For example, removing the camera, not needing the remote control, etc."
"Alright, I'll leave this to you. You pick some samples to test first and see if they meet our needs. For funding, go directly to Jamie, and I'll sign off on it when the time comes," Nick nodded and said.
"Got it!" Terry made a gesture and immediately got busy.
Watching Terry continue working, Nick smiled and went back to his own work; there was still a lot of work waiting for him.
This set of drone swarm array control systems was further divided into several subsystems. The frameworks for these subsystems needed to be built by him; with Zack's capabilities, he could only refine and perfect them.
Of course, this wasn't just transcribing directly; it was compiling and summarizing relevant information from his mind based on their needs, with appropriate deletions and modifications to fit their requirements.
"Barney, take another look at these two units: positioning error measurement and 3D normal distribution. I don't know where to start," Zack shouted at him.
"Let me see." Nick slid his swivel chair over to Zack's side and carefully examined the computer screen.
"Right here, you have a bug. Just modify this and it'll be fine," Nick said, pointing at the code on the computer screen.
Zack said, somewhat discouraged, "I knew it, I kept feeling something was wrong. So it was another bug. It would be great if the programs I wrote never had bugs."
"In your dreams. How can anyone who writes programs not have bugs? Even God couldn't do that," Nick joked.
"I just wish... Wait, no, Barney, you've written so much code, how come I haven't found a bug in it?" Zack suddenly realized.
Uh... Nick was stunned for a moment. He couldn't exactly say that all this stuff was ready-made in his brain and he was just copying it. Even if he was editing it, it was like a college student doing third-grade elementary school math; how could there possibly be errors?
"Who says there aren't? There are plenty. Some I modified myself, others you just haven't discovered yet. When we test it later, all the bugs will appear."
While saying this, Nick couldn't help but break into a cold sweat. It seemed he would have to be more careful in the future; it was necessary to include a few more errors in the code he wrote.
"That's true, some bugs can't be found until the final test. Even after testing, they might not be found. Otherwise, why would Cyberpunk have so many patches?"
Just as the two were talking, Tyler walked out in a rush, carrying a large pile of boxed lunches, and happily said to everyone, "Come, come, everyone, time to eat! I picked out what you all like."
"Big man, why are you so happy? Is there some good news?" Zack teased Tyler.
Usually, Tyler would retort, but today he didn't seem to care. Instead, as he took the boxed lunches out of the bag, he excitedly said to the group, "Let me tell you, our company registration has been approved."
"Really?"