4 ms·
As engineers, we are hardwired to nitpick. Coming up with counter-examples is the default response. Instead, I try to say a supporting example first. This helps
by kelukelugames 11y ago
As engineers, we are hardwired to nitpick. Coming up with counter-examples is the default response. Instead, I try to say a supporting example first. This helps me learn from other people's point of view.
Edit: Though I admit I don't do the best job on HN. :/
- evincarofautumn 11y agoI agree. Programming is an applied form of constructive logic. A program that works is an example (existence proof) that its specification (a theorem) can be fulfilled (proven). When we review code, we’re generally trying to disprove—looking for ways in which the program doesn’t fulfill the specification.
- erikpukinskis 11y agoIf that's true you're missing lots of opportunities to strengthen good behaviors and ideas.
- evincarofautumn 11y agoI removed all the hedges from my comment. Apparently that was too much. I agree with you too.
- mhurron 11y ago> As engineers, we are hardwired to nitpick. This is just not true. You are not 'hard wired' to react in such a specific manner, and being an engineer does not mean ripping things apart. You may be an engineer and choose to make a joke about something. You may be an engineer and something may make you go off and learn about something you didn't know about before. You may be an engineer and react in all sorts of ways to soemthing, nitpick is only one possible outcome.
- deleted 11y ago[deleted]
- angersock 11y agoYour comment here rather illustrates the point, I think. :)
- iamcurious 11y agoInteresting. So to convince people to disagree I should voice agreement?
- tremon 11y agoYou are not 'hard wired' to react in such a specific manner, and being an engineer does not mean ripping things apart. Maybe it's not true for engineering in general, but it certainly is true in software development. When writing code, I am continuously guarding for the totality of my implementation. When reviewing code, I am mainly looking for ways it can fail, corner cases that have been missed, non-total evaluations, etc. Maybe it's not exactly hardwired, but my nitpicking skills are carefully and purposefully honed.
- vectorjohn 11y ago> Coming up with counter-examples is the default response. > Instead, I try to say a supporting example first. I like what you did there. Not just you, it seems many of the comments are coming up with nitpicks or counterexamples. I don't know what that means, I just found it ironic.
- dkarapetyan 11y agoI once had a discussion like this with a marketing VP. She didn't understand engineers and how they talked to each other. Conversations between engineers always seemed like arguments to her when in reality they were just poking holes in logic and programs to make things better.
- kelukelugames 11y agoWhich is great for code reviews, but terrible for sensitive topics like diversity, etc.
- erikpukinskis 11y agoAre you sure? I think there are a lot of good, but fragile ideas, even in software. And culturally, the tech world tends to destroy them.
- kelukelugames 11y agoThat's a good point. I don't know. I don't know how software would change if we were more diplomatic like lawyers or consultants.