Re^2: OT: Why Hackers dont do well in Corporate World

"...working on fixing a crashing bug in the inhouse editor instead of..."

Of course, companies that insist on creating their own in-house editors, mail clients, programming languages, etc. are a whole class of problems unto themselves!

Comment on Re^2: OT: Why Hackers dont do well in Corporate World

Replies are listed 'Best First'.
Re^3: OT: Why Hackers dont do well in Corporate World by hv (Prior) on Jun 10, 2005 at 11:13 UTC
This was in the days when the PC was just coming on the market - the hardware was also designed and built inhouse. Another programmer that started around the same time as our hacker brought his own PC in to work, and insisted on doing all his development on that. But by avoiding using the system he was writing for as much as he possibly could, he ended up learning nothing about the system. It isn't clear whether that was the only reason his code was crap. Hugo	[reply]

Replies are listed 'Best First'.

Re^3: OT: Why Hackers dont do well in Corporate World
by hv (Prior) on Jun 10, 2005 at 11:13 UTC

This was in the days when the PC was just coming on the market - the hardware was also designed and built inhouse.

Another programmer that started around the same time as our hacker brought his own PC in to work, and insisted on doing all his development on that. But by avoiding using the system he was writing for as much as he possibly could, he ended up learning nothing about the system. It isn't clear whether that was the only reason his code was crap.

Hugo

[reply]