Live data from Hacker News

Dad and the ten commandments of egoless programming (2012)

blog.stephenwyattbush.com

71–80 of 110 posts

Re: Dad and the ten commandments of egoless programming (2012)

#72
post #18
post #10

Earlier quoted context omitted.

That is how I mean it too. For me it means not caring, as I said. I have also found that accepting all criticism from other developers makes me the submissive one. They are not always correct, pushing back when they are not matters a lot. Otherwise you get more and more absurd complaints.

Maybe by seeing it that way: imagine you are emotionally invested, «caring», but the only thing that change is the way you interact with others, directly, or through the code you push. Examples • I don’t like this code style , I’ll post mine -> I’ll replicate the code style, maybe I’m missing something, and if not I’ll discuss it and propose my pref on next review • reviewer suggested a change that would introduce an…

> reviewer suggested a change that would introduce an error, or something smelly - treat it as welcomed feedback, make sure to perfectly understand the seemingly subtle difference in approaches, and with a thorough explanation

I used to do that. The team dynamic went wrong every time. I ended up being the one people picked on the most, complaining about things they had no issue other people to do. And half the time it was not genuine code quality anything. It was asserting dominance or thinking I like it. The team dynamic is a thing. And all of this "be thankful" may be good advice for very aggressive people. I am not, for someone like me it is very bad advice.

When I was younger I read and followed advice like this. It was literally opposite of what I needed. Fact is, people react to what you do.

The thing that helped me was starting to push back on these systematically. Even when I feel bad about pushing bad. Or if it feels rude. And it really helped.

-----

If it is subtle difference in approach, then my way is as good as yours. If you want to change team approach, open it on meeting, get freaking consensus from all. Don't sneak it in my code reviews without any prior discussion. And do it for everyone, not just for the most accommodating person on team (which I am no longer and intend to never become again).

Re: Dad and the ten commandments of egoless programming (2012)

#73

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can d…

Is there any detailed explanation on these points? I only find this exact quoted list in my searches. Seems that the original was also only a list of these points.

"Give up blood sport" - Why? Did martial arts for 10 years, helped a lot with some other points in these list, especially the self-awareness and decency (humble-ness?). Or do i misunderstand this point?

"Live memorably" - That's straight up a wall tattoo quote, isn't it? /s

Re: Dad and the ten commandments of egoless programming (2012)

#74

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can d…

Is there any detailed explanation on these points? I only find this exact quoted list in my searches. Seems that the original was also only a list of these points. "Give up blood sport" - Why? Did martial arts for 10 years, helped a lot with some other points in these list, especially the self-awareness and decency (humble-ness?). Or do i misunderstand this point? "Live memorably" - That's straight up a wall tattoo q…

To be out for blood is to seek revenge. I read "Give up blood sport" as a caution against doing so.

Re: Dad and the ten commandments of egoless programming (2012)

#75

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can d…

> Expect no more of anyone than you can deliver yourself.

The problem is I can deliver a lot and others can't so I quite often expect more of them since I expect them to deliver as much as me.

Re: Dad and the ten commandments of egoless programming (2012)

#76

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can d…

Is there any detailed explanation on these points? I only find this exact quoted list in my searches. Seems that the original was also only a list of these points. "Give up blood sport" - Why? Did martial arts for 10 years, helped a lot with some other points in these list, especially the self-awareness and decency (humble-ness?). Or do i misunderstand this point? "Live memorably" - That's straight up a wall tattoo q…

the way I've understood 'blood sport' was that the particular sport never matters, the important parts are the viciousness and cruelty involved. so for me, martial arts = sports, and cockfighting = blood sport.

Re: Dad and the ten commandments of egoless programming (2012)

#77
post #57

Earlier quoted context omitted.

I LOVE this frame of mind and I love this statement but it is usually only used in the negative alignment of expectations: don't take critique personally. No disagreement. But let's get pedantic: The umbrella "you are not your code" would dismiss improvement as well. And praise. Ok, so I am not my code. But if I don't learn from my mistakes my code will not improve. I... I... I... Anyway, I much prefer to reframe it…

> Programming is a very intimate experience. >The same as creating art. It is the manifestation of your thoughts and opinions, small and large, put out in to the world. I respectfully disagree. This thought process is why other people are left holding the bag at 11pm on a Friday fixing the 'art' of someone else. Computer Science is a derivative of mathematics. Math is not art. Math IS beautiful, explicitly because it…

Computer Games are art and games are one result of computer science. Can a science create an art? I guess color theory can explain why we enjoy colors. But the science came after the art.

I agree that data structures and algorithms are not art, but when combined in unique ways they create art.

I think the problem is the field is so new and these terms aren’t well defined.

Re: Dad and the ten commandments of egoless programming (2012)

#78

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can d…

In HN formatting you need newline for paragraph lists:

1. Be patient. No matter what.

2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him.

3. Never assume the motives of others are, to them, less noble than yours are to you.

4. Expand your sense of the possible.

5. Don’t trouble yourself with matters you truly cannot change.

6. Expect no more of anyone than you can deliver yourself.

7. Tolerate ambiguity.

8. Laugh at yourself frequently.

9. Concern yourself with what is right rather than who is right.

10. Never forget that, no matter how certain, you might be wrong.

11. Give up blood sports.

12. Remember that your life belongs to others as well. Don’t risk it frivolously.

13. Never lie to anyone for any reason. (Lies of omission are sometimes exempt.)

14. Learn the needs of those around you and respect them.

15. Avoid the pursuit of happiness. Seek to define your mission and pursue that.

16. Reduce your use of the first personal pronoun.

17. Praise at least as often as you disparage.

18. Admit your errors freely and soon.

19. Become less suspicious of joy.

20. Understand humility.

21. Remember that love forgives everything.

22. Foster dignity.

23. Live memorably.

24. Love yourself.

25. Endure.

Re: Dad and the ten commandments of egoless programming (2012)

#79
post #57

Earlier quoted context omitted.

I LOVE this frame of mind and I love this statement but it is usually only used in the negative alignment of expectations: don't take critique personally. No disagreement. But let's get pedantic: The umbrella "you are not your code" would dismiss improvement as well. And praise. Ok, so I am not my code. But if I don't learn from my mistakes my code will not improve. I... I... I... Anyway, I much prefer to reframe it…

> Programming is a very intimate experience. >The same as creating art. It is the manifestation of your thoughts and opinions, small and large, put out in to the world. I respectfully disagree. This thought process is why other people are left holding the bag at 11pm on a Friday fixing the 'art' of someone else. Computer Science is a derivative of mathematics. Math is not art. Math IS beautiful, explicitly because it…

Code exists on a continuum. It’s not correct or incorrect. It is better or worse.

Unless you consider anything less than perfect to be wrong, but that’ll just make nobody want to work with you.

Re: Dad and the ten commandments of egoless programming (2012)

#80

This reminds me a lot of the advice of John Perry Barlow. 1. Be patient. No matter what. 2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him. 3. Never assume the motives of others are, to them, less noble than yours are to you. 4. Expand your sense of the possible. 5. Don’t trouble yourself with matters you truly cannot change. 6. Expect no more of anyone than you can d…

Is there any detailed explanation on these points? I only find this exact quoted list in my searches. Seems that the original was also only a list of these points. "Give up blood sport" - Why? Did martial arts for 10 years, helped a lot with some other points in these list, especially the self-awareness and decency (humble-ness?). Or do i misunderstand this point? "Live memorably" - That's straight up a wall tattoo q…

Give up unnecessary conflict, or, give up conflict where the goal is to make the other person suffer or bleed.
Post reply on HN