4 ms·
While looking at a co-worker's UI code the other day, I commented out loud to him and our other cubicle dwellers that "I would have coded it very defensively "
by wallflower 19y ago
While looking at a co-worker's UI code the other day, I commented out loud to him and our other cubicle dwellers that "I would have coded it very defensively " and told him "that he took risks programming and that was why he was more likely to start a business than I (the conservative programmer) was (he's got an entrepreneurial long-term outlook).
Some of the things he was coding seemed relatively risky (e.g. relying on binding to work flawlessly with a complex, deep nested model - we've had hard-to-debug issues with ssome Flex UI-field binding in the past)
- ericb 19y agoBad, difficult-to-debug programming is not moving against the herd, it's moving with it. Are you implying poor programming makes one more likely to start a business? That will float like a lead balloon here. Am I misunderstanding your post, or feeding a troll, perhaps?
- mrtron 19y agoI would go with either a troll or a jerk. If someone intentionally loudly told me my code was irresponsibly risky and stated my future ambitions for all to hear, I would not be impressed.
- wallflower 19y agoMy intention was not to imply that bad, difficult-to-debug programming makes someone more likely to start a business. The issues with Flex in the past with viewing/editing attributes on a complex parent.child.subchild model are in the past (they fixed the issues). His code was not "bad, difficult to debug" it was "risky" in the sense that Flex didn't support it in a previous release. When I told him that his code was risky, I said it with a half-serious tone (e.g. half joking). Rereading the post indicates that the tone of the post and the tone of the original comment never carried through. I apologize.
- SwellJoe 19y agoSounds a little passive aggressive to me.