|
No, not really.
Sometimes I go "Wow this works!!"
but that is probably it.
I'd rather be phishing!
|
|
|
|
|
I think that attachment is proportional to time spent on it. If it's a program that I whipped up in a couple of hours or a day, I really don't care. Now, if it's code that I spent months working on it, of course I get a little attached.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
You have to learn to let it go
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
If only it would! 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onllokers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
is that Latin in all your code comments?
|
|
|
|
|
I long for the day my code lets ME go...
|
|
|
|
|
That is why I eventually threw out the punch cards and paper tape.
|
|
|
|
|
I do but just a little. The vast majority of what I have done has been automation systems and it is interesting to find that most of them are still in operation today, making the chips that go into our computers, phones, tablets, and who knows what else. I guess that's not exactly emotional attachment. They are thoughts similar to wondering how the kids are today.
|
|
|
|
|
One of our team developer had a logger class which was wrote so many years ago and uses in every project needed.
It used to open a file every time log method is called write line and close the file, another dev in my team modified the implementation for improvement purpose, and the original author didn't like that, the statement was :
"I had been using this class since xx years ago and i am used to it, why have you modified it"
and that dev then had to undo the changes to get it back to the original version 
|
|
|
|
|
|
|
No. I never get attached to the code I write. I might be proud or apologetic about my accomplishment, but the code itself, no.
Emotional attachment to the code itself usually means people start to act protective of it and create a boundary to keep others out. That kind of behavior is a red flag to me to get someone else into that code pronto. In every case I've seen where there's code that's considered off limits because it's someone's "baby", it has meant that they're doing it to hide how poor of a developer they are.
|
|
|
|
|
No, it's more like a fling, where if the other code finds out there's hell to pay, and like a fling, it gets dull pretty quick, at least until the next cool piece of code. Any long term relationship is quite rare.
Latest Article - Code Review - What You Can Learn From a Single Line of Code
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Yes. And it one of the biggest mistakes coders make.
|
|
|
|
|
No, I don't get attached. My preference is to write clean, easy to read, low defect code that others can easily maintain. I don't need credit for anything.
I do get ticked off when someone makes a change to my code and decides to reformat it or not follow the coding standards. The typical reply I get is "it works!"
|
|
|
|
|
Having others work on 'your' project can be both good and bad.
I was really attached to my previous project at my old job. I had worked on it for 5+ years and it was my 'baby' and I put in a lot of effort to make it a top notch product. I am pedantic about code formatting and how I think code should be written, so when another developer also worked on the code and didn't do code formatting and left out some things like window icons I wasn't too happy.
But it can get too much and make you arrogant, thinking that nobody else can do the job properly. On a recent project I was glad to have some help and I actually found some respect for my fellow workers - they did a very nice job with the code and styling work and I can learn from their code.
modified 26-Jan-18 2:54am.
|
|
|
|
|
Sure, if you ask about the first "big" subsystem I was "product responsible" for, in my first job after my graduation in 1983: Sure. I have always known where I keep the box with the source code printout, and every now and then I feel a slight urge to glance through it, one more time.
Your firstborn is always special. Yet I hope that parents with five or six kids have stronger emotional ties to #5 and 6 than I have to the fifth and sixth product I worked on. And nowadays, 30+ years later? I am so happy if someone wants to take over my code. My experience is that whenever someone seizes control over someone else's code, they will "clean it up" - that is, reformat it, remove "unneccessary" comments and add others, join or split classes, rename variables... All of this may of course be limited by company coding standards, but everybody is eager to mould the code into their own style as far as possible.
When I see the code again, a year later, I hardly recognize it as originally being my code. So I never weep "What did you do to MY code, you cruel code molestor??" - that isn't my code. You do whatever you want to it.
Actually, I feel more emotional ties to architectures and designs. What really bugs me is when I have been fighting in vain for some major architectural change over a long time, but it is rejected (usually due to cost), then when I leave that project, three months later it is decided that "it seems like we simply have to impement that change / design"... That has happened to me several times - and in every case, it is presented as a contribution of the reorganized project team with no reference to the work done earlier. But since I wasn't involved at the time the architecture / design was finally accepted, there is nothing that I can attach to as "mine".
|
|
|
|
|
Yes, there is strong feeling of attachment. I still miss all the code that i had written long ago and lost it (8 inch floppy disks)
Do
Read();
Research();
Experiment();
UnTil You Inspire!
|
|
|
|
|
Yesterday I came across some code that I wrote at least 25 years ago and is still being shipped as a part of my company's products. I would write it differently today, but I've got to admit that it gave me a bit of the warm & fuzzy knowing that's it's still doing its' job in countless medical labs around the world today.
It's a hard life.
But somebody's got to live it, if only to act as an inspiration to others.
|
|
|
|
|
haha, remember spending four years writing in 8086 assembler code, until the C compilers generated useful code.
Remember spending four months writing a Base 10,000 math package, sort/merge using qsort, pcode interpreter runtime for a Cobol compiler. I loved doing it and still remember it as some of the best fun I had at the time.
For me it was always about the challenge, of course the stock options and bonuses made the IRS and me very happy.
Lost a girlfriend after I started and gained girlfriend before the next task, repeat as needed until death.
Lyle
|
|
|
|
|
It is projects that I become knowledgeable about the domain of that I turn into an emotional wreck and get attached to the code that I write.
Its at that point my creativity neurons start activating and I (try) to design and write elegant software, and thus become an emotional wreck whenever someone else decides to fix a "bug".
|
|
|
|
|
Both.
We have a major cleanup branch about to start that will remove hundreds if not thousands of obsolete classes due to an architecture update.
The old code served us well for more than a decade, but its time has come to ride into the sunset. (or be buried in SCM)
|
|
|
|
|
...to convince ladies not to eat Tide pods.
But it's harder to deter gents! 
Better get my coat...
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onllokers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
I think you should have posted that in the soapbox instead...
|
|
|
|
|
Soap the postbox?
I have lived with several Zen masters - all of them were cats.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
