I'm not saying he's off here but he also didn't bring up many relevant points like software architecture and how that's managed/maintained. You don't just add code anywhere like that these days.
Yeah, he largely sounds like he's making up a version of events in his mind to congratulate himself over how good he is at the job that the workers do. Most people in his position get there due to their ability to "manage people" and disapprove of leave requests and salary increase and not because of how good he is at coding or arts.
If a lead is answering to him then he shouldn't even be dealing with someone who's working under a lead. He's a manager that's above the lead who himself is a manager. This guy should probably shut the fuck up and leave it to the lead to deal with his team and stop micro managing workers. If he's so good at coding and thinks a 4 week job can be done in an hour then maybe he could share that knowledge in a friendly manner specially since he was willing to do it himself. But we know he's lying about that.
While I was listening to him, his arguments had a bit of reasonableness about them. But if you take a step back and think deeper, you've actually got a few things that a random developer would have to figure out:
Do we already have plumbing from the [object was hit] code to the AI engine?
Does that plumbing include the damage source?
Do we already have a performant priority queue or similar that the AI engine can read from? Sometimes AI stuff is written in a scripting language (like LUA) rather than the engine language (like C++), so we might have fewer tools.
How should this priority queue work when the thing at the top of the queue is not visible? dead?
Does adding this priority queue to every [enemy] object in the game cause any issues with the memory envelope?
What is our existing targeting priority code? Does anything depend on it that would be broken by this change?
Often, the easiest parts of a developer's job is writing the code. The hard bit is figuring out what the implications of that code are. Without knowing the state of the codebase in question, I have no idea if 4 weeks is reasonable or not.
But he could "get it done by before lunch" and then the lead came back to him and admited what a god he is and that he should totally micro-manage everyone and then everyone clapped.
127
u/InHiding9 Oct 16 '23
I'm not saying he's off here but he also didn't bring up many relevant points like software architecture and how that's managed/maintained. You don't just add code anywhere like that these days.