It seems as part of the take home that you spend 45 minutes discussing your implementation and defending your choices in person with the interviewer. This is a much more realistic "on the job" stressor than being able to code out loud / on a white board.
This article is so short sighted, it's hard to know where to start. My advice is to delete it, as you may have trouble hiring engineers in the future and anyone will find this when they google your name / research your company. As an engineer, weighing the options you suggest in public is a massive red flag and I would always have a seed of distrust in the back of my head.
Regardless of the fact that the culmination of the article is that you don't REALLY want to be an asshole (I'm not so sure), it shows that:
A) You imply engineers are just people to build your dreams and dispose of when you're done. "I'll just not fire them". Good engineers can make or break your company.
B) You're hanging out with terrible advisors (camp 1? wtf)
> "You don’t get to the top without making a few enemies, though."
Most people don't make enemies of their employees or show such blatant disrespect.