"Was he fired?"
No. On most tasks his performance was on or above par. This only is proof that the manager is just new. Programming and the time to complete is variable as well as Joe may do better or worse than Jane. It doesn't mean they are LUCKY (?) or better or worse.
The text later in the reply is about hardware and such. For that you do want to test on a server machine. But I want to segue into an area I find new programmers get too invested in. Ready?
OVER OPTIMIZING.
That is, in a commercial environment you run the risk of dismissal if your code is just slow all the time as well as you spent too much time optimizing. It's a sliding scale of how much to invest (time or hardware) versus delivering a working MAINTAINABLE app(s).
It does not one any good if you have the fastest implementation of a zed core reduction function when no one can understand what you wrote. (Nod to APL and the one line of code for "Life.")
So let's say your code runs, you optimized it and it's the end of the week. It passes muster, time to ship it.
HERESY.
To some this is heresy. That is, I run across designers, coders, engineers that are stuck in "I can make it better" mode for too long. Read the specs, try to exceed them but avoid over optimizing.