The problem was fixed. The goal was reached.
Not everything in life is about getting a golden star in your grade book.
Not everything in life is about getting a golden star in your grade book.
There is no need to try and take explicit credit when you get implicit credit simply from the visibility of leading the project.
Having spoken to a lot of low level leaders I'd disagree. It does create unhappiness because in the end they are no less human. That unhappiness may be worth it for the other benefits and the happiness they gain from them but saying they don't experience unhappiness is dismissing their very human emotions. But often the unhappiness dominates, they burn out and then get replaced by some narcissist/sociopath. That person is fully happy and rises up the ranks.
Of course if you happen to do IC work as well it makes sense to take credit for that, but I think that mixing leadership and IC work tends to result in burnout.
The project maintainer surely would have not felt bad giving credit to someone ? Exhibiting this kind of leadership usually makes me feel great !
On the contrary, as we see from the article, the lack of credit really did create unhappiness from thin air…
the secret of a happy life is trying to be happy, whatever that means to you, and making it, the secret of a sad life is trying to be happy and failing at it.
regardless of the expectations.
So no, it isn't always the opposite. For many of us, our pessimistic attitude has been extremely damaging.
Someone else here said
> You have control over the inputs but not the outcomes :)
I can't speak for others, but for me personally, having low expectations has caused me to become lackadaisical or even destructive with my inputs. What is the point if it will just go wrong?
EDIT: I can't reply because /u/dang has blocked my account again
> That... isn't what I mean by low expectations? For me, it means to be grateful for what you've got, to question feelings of envy and to not feel that you deserve something.
That's called "gratitude", not "low expectations"
"Low expectations" means you expect low, i.e. bad. It's pessimism.
Regardless of all that I hope you work out your depression, it sucks.
No thanks.
Not being able to accept that shows immaturity.
The world would be a much much much much much much shittier place if everyone accepted things and never pushed back.
>Not being able to accept that shows immaturity.
I find not being able to accept that other's have a different but equally valid approach to life shows immaturity.
He found a bug (even that is questionable because it got reported prior), copy&paste-developed a fix and is angry that it doesn't get merged and now throws a hissy fit that he got attributed with the exact thing he did. Looking at his employer makes this even funnier.
Is it so wrong to not be awarded a medal everytime someone does something?
The title says "I got robbed", the reality is the solution has been discarded for something the maintainer, who's going to maintain that code, liked better.
The handling wasn't great, sure, but the real appreciation comes from within, from knowing you found a solution to the problem, not from others.
It is like going to the doctor with the solution and being upset if the doctor replaces it with something he can trust
- diagnosed a longstanding bug
- contributed an initial patch
- actively reached out to the maintainer, who said they would reach out in private
- contributed additional versions that were reviewed
just to have the maintainer take over the contribution wholesale. How would you feel when you put in all that work and receive basically no recognition for it? Maybe you are truly ascetic and have no need for it, but most people appreciate being credited and being encouraged to contribute again.
I would feel that nothing bad happened and that my code was actually reviewed by a kernel maintainer, that acknowledged the problem, and found a solution based on mine, which is in itself a big ego boost.
But probably it's just because I have been programming for over 25 years, because I like solving problems, and I don't do it for the recognition, which is basically a false coin. The recognition at work is the salary, the recognition when I volunteer is that I contribute to help people when I can, not that the people I help are grateful to me. Sometimes they are ungrateful too, but that's not why I do it, so I don't care.
In my opinion it is childish otherwise, you do things you think they are right because you think they are right, not for some prize.
Never let your sense of morals prevent you from doing what is right.
> ----------------
- diagnosed a longstanding bug
- contributed an initial patch
- actively reached out to the maintainer, who said they would reach out in private
- contributed additional versions that were reviewed
That's basically what I used to do when my car had a problem and I brought it to the mechanic, because I grew up in my uncle's body shop.
but the mechanic does it professionally and of course he wants to do all the process again, so he can be sure what the real problem is. At that point he probably found a solution which is slightly better than mine or that solves the root of the problem, not just the symptom.
So now I just go there and tell him what is that I feel it's wrong (e.g. the motor keeps stalling) and I let him fix it. If I wanted to become a real contributor, I would start from the bottom, as everyone does: changing oil (here's a bug you can fix)
> Not everything in life is about getting a golden star in your grade book.
One of the prides that I can discuss in job interviews are my contributions to upstream software stacks (mostly PHP frameworks such as Laravel and Magento). I have had a patch rewritten by a maintainer that arguably made the patch worse - that left a very sore feeling for me and I think that it was the very last patch that I sent to that particular project (Wordpress, which I am glad to be rid of).
This post is literally about not getting credit for one’s work. If you don’t believe that the author deserved recognition for their work then you should say that outright.
Last year I spent the whole friday night debugging an issue in a lib I've been using at work. I found an issue, wrote tests to demonstrate it, fixed the issue, write more tests and opened a PR. Maintainer months later closed an issue and I saw it has been fixed within one of his owns PRs. It did sting a bit, but I remembered I learned A LOT while debugging it and I fixed an issue that was bugging us on work.