Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Your identity ≠ Your code

collectiveidea.com

Post reply on HN
Print view View original

31–39 of 39 posts

Re: Your identity ≠ Your code

#31

Post by j_baker »

w0utert wrote: post #20
zmoazeni wrote: post #14

Earlier quoted context omitted.

I'm the original author, and I agree with your point. I do think the things you produce are part of your identity. It's when a person mentally replaces "part of" with "is" that it becomes dangerous. We can be so much more than the artifacts we create.

One thing you didn't mention in your article, but which I think is a relevant and interesting observation to make, is that 'your code =/= your identity' works both ways. It's not just that you should not project messy code onto someone's personality/identity, but you also cannot reliably do the inverse. I know people who are meticulously organized in everything they do in real life, who hate to be around a mess, who…

Likewise, I know people who are chaotic in every way, who don't adhere to many of the things almost everyone else considers to be the norm, who have little to no self-discipline for mundane tasks, who are non-conformist by choice, and who are often perfectly aware of these shortcomings.

You'd consider those to be shortcomings? I'd consider them to be strengths. Granted, you can take those strengths too far such that they become weaknesses. But as long as you're careful not to turn them into a Golden Hammer, I wouldn't count those as weaknesses.

Re: Your identity ≠ Your code

#32

Post by j_baker »

vibrunazo wrote: post #19
agentultra wrote: post #9

The easiest way to open yourself up to accepting criticism is to realize you are not the smartest person in the room, so to speak. It is never about being the smartest person because at some point even the smartest person will be replaced. I've learned to accept criticism by realizing that it's not about where I am now but where I am going. As long as I can look back on code I've written in the past and think to myse…

> The easiest way to open yourself up to accepting criticism is to realize you are not the smartest person in the room I think that's irrelevant. Every human being is stupid. Saying you're the smartest person on the room, in absolute terms, is analogous to saying you're the smartest termite in the planet. Even if you're much smarter than others, that's irrelevant. Suppose the smartest person on earth is right twice a…

Sorry, but I don't buy the "It is a truly wise man who believes he is not" meme. A truly wise man has confidence in his wisdom, and the humility to realize that it isn't infallible.

Re: Your identity ≠ Your code

#33

Post by w0utert »

j_baker wrote: post #31
w0utert wrote: post #20

Earlier quoted context omitted.

One thing you didn't mention in your article, but which I think is a relevant and interesting observation to make, is that 'your code =/= your identity' works both ways. It's not just that you should not project messy code onto someone's personality/identity, but you also cannot reliably do the inverse. I know people who are meticulously organized in everything they do in real life, who hate to be around a mess, who…

Likewise, I know people who are chaotic in every way, who don't adhere to many of the things almost everyone else considers to be the norm, who have little to no self-discipline for mundane tasks, who are non-conformist by choice, and who are often perfectly aware of these shortcomings. You'd consider those to be shortcomings? I'd consider them to be strengths. Granted, you can take those strengths too far such that…

In some ways I can imagine they could be strengths, or at least beneficial in some situations. For example being chaotic and non-conforming sometimes you learn something you would otherwise miss out on. Most of the other things I mentioned only work against me, such as lack of discipline, not finishing stuff I started, or lack of focus and not being systematic enough and getting hugely frustrated about forgetting where I left something.

I guess like always, truth is somewhere in the middle.

Re: Your identity ≠ Your code

#34

Post by georgieporgie »

michaelochurch wrote: post #15

Stop equating bad code with bad developers. Stop equating code criticisms as a knock against you as a person. To me, what I find jarring is how common bad code is and how incredibly rare well-designed systems and good code are. It seems obvious that the causes of bad code are numerous (only one of which is unskilled developers) and the conditions that allow good software to be created are very rare. You have a lot of…

To me, what I find jarring is how common bad code is and how incredibly rare well-designed systems and good code are

I've mentioned before my rule of three. That is, my code will pretty much suck until about the third time that I've solved (or refactored) a problem.

If I ever come across code that I think is particularly nice, it's quite likely that the developer either reworked said code or has solved a very similar problem multiple times. If, on the other hand, I come across bad code, I generally assume the developer was simply pressed for time and created as much value as possible under the constraints.

Re: Your identity ≠ Your code

#35

Post by limeblack »

padobson wrote: post #25

Everyone seeks validation. Everyone is looking to justify their existence. It is the very essence of the human condition to find something we can point to and say "I have value because of X" All too often, X = Someone else's flaws. This is the first great shortcoming in the human condition that we have to get over. Validating ourselves by pointing out the flaws of others cripples relationships and society as a whole.…

> The realization we all need to come to is that our value compared to one another does not determine our worth. The greatest human being is not substantially different from the least human being. And in realizing that the difference between human beings is unsubstantial, the only way to determine your worth as a human is how well you treated your fellows. > Feed a hungry person. Clothe a naked person. Shelter the shelterless. Cheer up the depressed. Comfort the mourning. That's where you'll find validation. That's where worth is derived.

I very much agree with your statement, but wonder how many students force themselves through school by comparing themselves to others.

For so many years, I would push myself in the desire of the shortcomings of others, and success of myself.

Now with this anxiety and comparison gone, I am no were near as committed. My performance has drastically decreased (practically failure in one class), and my selfish hopes have subsided.

Do you have any advice on how to overcome this complacency without comparing myself to others?

School feels insincere and not in agreeance with treating my fellow students kindly.

Re: Your identity ≠ Your code

#36

Post by jordhy »

matwood wrote: post #12
agentultra wrote: post #9

The easiest way to open yourself up to accepting criticism is to realize you are not the smartest person in the room, so to speak. It is never about being the smartest person because at some point even the smartest person will be replaced. I've learned to accept criticism by realizing that it's not about where I am now but where I am going. As long as I can look back on code I've written in the past and think to myse…

This is so true. I welcome criticism because it forces me to evaluate my work critically and make changes if need be. I agree with your comment about hiring the best. Would you rather have the 'best' [1] programmer who is also a team cancer or a group of good programmers who individually aren't better than the best guy, but as a group deliver better results? [1] 'Best' can be defined so many ways that without a defin…

This is very true. Also, the software development process is very empathetical. We need to be in constant touch with the end user and make sure we're pushing for the right features.

In regards to your second point, I think we should optimize for the best team, not necessarily for the best programmers. Ergo, try to hire the best team player, not the best lone ranger.

Re: Your identity ≠ Your code

#37

Post by diminish »

jordhy wrote: post #36
matwood wrote: post #12

Earlier quoted context omitted.

This is so true. I welcome criticism because it forces me to evaluate my work critically and make changes if need be. I agree with your comment about hiring the best. Would you rather have the 'best' [1] programmer who is also a team cancer or a group of good programmers who individually aren't better than the best guy, but as a group deliver better results? [1] 'Best' can be defined so many ways that without a defin…

This is very true. Also, the software development process is very empathetical. We need to be in constant touch with the end user and make sure we're pushing for the right features. In regards to your second point, I think we should optimize for the best team, not necessarily for the best programmers. Ergo, try to hire the best team player, not the best lone ranger.

You are what you code! If someone criticizes or changes your code, they want to change a trace of your soul or of your mind. If you accept their criticism it means you were wrong. And if you were wrong once, that means you can be wrong more in your new programming. If you once made a mistake, how can you not make more? And how can someone else or you, can trust yourself if they know you made a mistake and they caught you red handed? And if you accept any critic, that means noone will have confidence at your code (or at you, because you are what you code). If you welcome critics, and change your code, your personality will change again and again; instead of a respectable, rigid person, you will end up being the soft guy everyone will push anywhere.

What you said is not at all true, my parent commenters; it is my critic at you, and of course if you accept it.

ps: this is just a satire, and i fully agree with my parent commenter s.

Re: Your identity ≠ Your code

#38

Post by Confusion »

This is an example of the fundamental attribution error[1]. When confronted with bad code, we tend to attribute this to the dev being bad. This in turn[2] leads to the idea that the dev is bad in general: i.e. dumb, incompetent, incorrigible by nature. If you manage to forego such thoughts (and that requires active effort!), you will often find people are much better persons, capable of much more, than you would have thought otherwise.

[1] http://en.wikipedia.org/wiki/Fundamental_attribution_error

[2] Unfortunately, I can't think of the correct term for this effect

Re: Your identity ≠ Your code

#39

Post by matwood »

diminish wrote: post #37
jordhy wrote: post #36

Earlier quoted context omitted.

This is very true. Also, the software development process is very empathetical. We need to be in constant touch with the end user and make sure we're pushing for the right features. In regards to your second point, I think we should optimize for the best team, not necessarily for the best programmers. Ergo, try to hire the best team player, not the best lone ranger.

You are what you code! If someone criticizes or changes your code, they want to change a trace of your soul or of your mind. If you accept their criticism it means you were wrong. And if you were wrong once, that means you can be wrong more in your new programming. If you once made a mistake, how can you not make more? And how can someone else or you, can trust yourself if they know you made a mistake and they caught…

Interestingly enough, I have very little personal connection to my code [1]. I'm almost sure there are better ways to code everything I've ever coded in the last 15 years. I know this because when I look at old code that I have written I see better ways to do it, and that's just me!

I think my lack of personal code connection comes from the fact that I view code as a tool to solve a problem. My overall solution I will certainly defend and feel that it reflects who I am, but the code to implement it? Who cares. I love elegant code as much as the next programmer, but at the end of the day for many problems the code is just an implementation detail.

[1] I've worked with people who have a deep personal connection to their code, and it can be very challenging to change anything without upsetting them.

Post reply on HN