3 ms·

As I understand it's already third time he is been fired. This makes me believe that there something else at play. Either he is self-delusional and can't see th

by jyriand 10y ago

As I understand it's already third time he is been fired. This makes me believe that there something else at play. Either he is self-delusional and can't see the actual reason(cowboy programming,arrogance etc) or companies in France don't like talented people.

dx034 10y ago
As one of the commenters on SO said, good code is a question of your environment. The fact that he can produce very advanced code doesn't mean that it's good code where he works. It's crucial to write code that others will be able to understand and maintain. If he's hired into a company where most employees have little knowledge of the domain, he needs to be extra careful to structure the code as simply as possible. If you start somewhere and disagree with the programming languages or techniques they use, the answer is not to use what you think it's best. The answer is to either go with the company policy, or to try and change it. But not just producing what you think is great code, even though no one else can understand it.
pjc50 10y ago
Sounds like the "architecture astronaut" anti-pattern. Either he's choosing the wrong places to work (aim higher!), or he's insufferable to his colleagues and doesn't actually ship the right thing his bosses want. You can usually get away with either being insufferable but delivering, or faffing around with an air of pleasant cooperative helpfulness. But not both. I strongly suspect he was delivering what he thought people "really" wanted, not what they asked for or needed, and that made it easy to get rid of him when he annoyed people. (Also, team composition really does follow TVtropes narrative rules. You need a balance of character archetypes and you can't have two divas.)
crdoconnor 10y ago
It's entirely possible that he's only worked in companies that don't recognize talented people and treat them as just another cog in the machine. I think outside of a few tech hotspots (and even to a large extent, within them), this is pretty normal, and you can judge this by seeing the pretty terrible average quality of code in most companies.
wolfgke 10y ago
Never attribute to malice that which is adequately explained by stupidity: > https://en.wikipedia.org/wiki/Hanlon's_razor https://en.wikipedia.org/wiki/Hanlon's_razor Being surrounded by stupid people is a very typical situation.

by jyriand 10y ago

dx034 10y ago

As one of the commenters on SO said, good code is a question of your environment. The fact that he can produce very advanced code doesn't mean that it's good code where he works. It's crucial to write code that others will be able to understand and maintain. If he's hired into a company where most employees have little knowledge of the domain, he needs to be extra careful to structure the code as simply as possible. If you start somewhere and disagree with the programming languages or techniques they use, the answer is not to use what you think it's best. The answer is to either go with the company policy, or to try and change it. But not just producing what you think is great code, even though no one else can understand it.

pjc50 10y ago

Sounds like the "architecture astronaut" anti-pattern. Either he's choosing the wrong places to work (aim higher!), or he's insufferable to his colleagues and doesn't actually ship the right thing his bosses want. You can usually get away with either being insufferable but delivering, or faffing around with an air of pleasant cooperative helpfulness. But not both. I strongly suspect he was delivering what he thought people "really" wanted, not what they asked for or needed, and that made it easy to get rid of him when he annoyed people. (Also, team composition really does follow TVtropes narrative rules. You need a balance of character archetypes and you can't have two divas.)

crdoconnor 10y ago

It's entirely possible that he's only worked in companies that don't recognize talented people and treat them as just another cog in the machine. I think outside of a few tech hotspots (and even to a large extent, within them), this is pretty normal, and you can judge this by seeing the pretty terrible average quality of code in most companies.

wolfgke 10y ago

Never attribute to malice that which is adequately explained by stupidity: > https://en.wikipedia.org/wiki/Hanlon's_razor https://en.wikipedia.org/wiki/Hanlon's_razor Being surrounded by stupid people is a very typical situation.