I so wish I could "kill stupid things before they cause damage", "set direction" and have people follow, but it seems especially difficult for technical people.
We spend all-day every-day talking to our subservient (a compiler) but a human is fuzzy and unreliable which is compounded by team size. Carmack can realize something in an instant but it is amazing how long it can take an entire team.
One thing I've noticed that really does not work is "complaining", if Carmack thinks he is complaining, then magnify that by 10 for others on the team.
Rather than attacking an idea directly, I'm wondering if ignoring the idea may be more effective. This way there's no one to fight and the idea can slip away without any ego or drama, there's no face to lose.
If you really can't help the situation, then leaving is the last resort. Oh well, on to the next thing, very curious to see what Carmack gets into next.
It's very confusing that a company by that name [1] seems to exist already, in an adjacent/near area ("Keen Technologies Pvt Ltd. is a comprehensive repository for online courses offering high quality state-of-the-art IT and Business related e-learning and training related courses.").
We spend all-day every-day talking to our subservient (a compiler) but a human is fuzzy and unreliable which is compounded by team size. Carmack can realize something in an instant but it is amazing how long it can take an entire team.
One thing I've noticed that really does not work is "complaining", if Carmack thinks he is complaining, then magnify that by 10 for others on the team.
Rather than attacking an idea directly, I'm wondering if ignoring the idea may be more effective. This way there's no one to fight and the idea can slip away without any ego or drama, there's no face to lose.
If you really can't help the situation, then leaving is the last resort. Oh well, on to the next thing, very curious to see what Carmack gets into next.