Answer the question
In order to leave comments, you need to log in
How to explain to a girl what "ugly" code is?
Hi all. My girlfriend is constantly interested in what I do for an unknown number of reasons to me)))) One of the problems for me, as always, is to explain what ugly code is. Of course, I showed the shitty code in the ide and the beautiful code there, but apart from the character set and other things, she does not see it. Well, surprise constantly from the fact that she does not see the differences) Who had the same thing? How did you crucify? There are interesting simple options? I don't want to give McConnell and Kernigan Ritchie books here) Thank you .
Answer the question
In order to leave comments, you need to log in
If ugly code cannot be seen by programmers, then why do you think that a girl who is not a programmer at all can see it?
Beautiful code is about understanding the nuances of programming. It is possible that you will find a couple of examples that are visual enough to demonstrate the difference by spending half an hour explaining. But to teach to see - will not work.
I would venture to suggest that your code doesn't matter to her. The purpose of the interviews is to show interest in your activity. It is not necessary to dedicate to the essence of the matter, just show that you appreciate her interest.
You are using the girl incorrectly. Read books at least, or ask mom and dad what, where and how.
You have a girlfriend, so take her to a cafe and feed her ice cream.
If you soar her brain, then later you will sit at home and write beautiful code :)
No need to explain this to her, better show her ugly sex and draw an analogy, she will definitely understand
Code is text. A well-written text is pleasant to read, everything is immediately clear in it and the author’s thought is clear. Shit code is like a second grader with dyslexia was forced to write a postcard for an unloved stepmother.
PS Sexism rushes from all cracks. And then they wonder why there are so few girls in IT, and why girls don't like nerds.
Start by saying that code is a blueprint. Only. And the drawing itself can be beautiful. Of course, looking at an even, diligent, neatly drawn architectural solution is more pleasant than looking at a semblance of a drawing made hastily on toilet paper without tools with your left foot. But behind both lies the same architectural solution. And a completely different question is the elegance, harmony and banal performance of this solution.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question