The anecdote regarding the Xcode + Swift compiler speed benchmarks leads one to suggest that, while you may have felt bullied by your colleague, he was, in fact, taking the correct approach, given the wider picture of Xcode and its developer experience on slower Apple hardware (including those devices with Fusion drives).
Sometimes, quiet confidence is a good rule to follow at the outset, even if you feel your opinion has merit - it's much easier to navigate quiet success than public failure in a politicized work environment. This is particularly important when you're new to a career and may not yet have the confidence and/or experience to endure the fallout from an irate colleague whose "style" (intentionally quoted, btw) precludes the niceties you may have been used to in your previous work / research environment.
I've been there, on both sides, though it always helps to be kind whenever possible, to be able to traverse the graph of complexity within the appropriate public discussion or private one-on-one.
The anecdote regarding the Xcode + Swift compiler speed benchmarks leads one to suggest that, while you may have felt bullied by your colleague, he was, in fact, taking the correct approach, given the wider picture of Xcode and its developer experience on slower Apple hardware (including those devices with Fusion drives).
Sometimes, quiet confidence is a good rule to follow at the outset, even if you feel your opinion has merit - it's much easier to navigate quiet success than public failure in a politicized work environment. This is particularly important when you're new to a career and may not yet have the confidence and/or experience to endure the fallout from an irate colleague whose "style" (intentionally quoted, btw) precludes the niceties you may have been used to in your previous work / research environment.
I've been there, on both sides, though it always helps to be kind whenever possible, to be able to traverse the graph of complexity within the appropriate public discussion or private one-on-one.