6/5/2026 at 8:04:12 PM
In my own tiny way, I applied this logic when trying to be a contributor to an existing and popular open source project. I found that puzzling out poorly-written bug report tickets, ignored by the extremely busy experts on the project, I could find work to do.I started by looking at well written tickets (to-the-point descriptions, minimal reproduction examples), but that method got me no work: some expert on the project would have a pull request for that kind of ticket in just a few hours, whereas I would need at least a week to figure out the root cause and another few days to craft a fix and a test.
So I started looking at ignored tickets, i.e., tickets that had been sitting around for weeks or months with no activity. Those often turned out to be very poorly written tickets with either very little information, or a huge wall of text with much business domain-specific info. If those tickets contained repro examples at all, they were often complex and very long, using external libraries I never heard of, and devoid of table schemas and example data. Sometimes I could get the author to provide more information, sometimes the author would not respond. I might have to infer schemas and make up my own data, try different things based on a stack trace, install libraries I would have preferred to not install, etc. I would work on trying to reproduce the problem for a few days, and at least a few times I struck gold. Then I would work on a self-contained, minimal reproduction case, followed by a week of sussing out the root cause. It was pretty time-consuming, but I was able to get a few fixes merged using that method, such that I was no longer a total stranger on the project (which helped me get other things merged into the code base).
by nabbed
6/5/2026 at 9:04:03 PM
Seems like you tore through some outdated Jira tickets, which is cool, but what was the impact of your work?Hard doesn't mean impactful. In fact that's one of the biggest mistakes I see junior engineers make! But glad you got that learning experience, as you become more senior you'll definitely develop a better understanding of what drives actual impact.
by steno132
6/5/2026 at 9:12:43 PM
Why are you being so condescending? A person wants to get into an open source project, so takes work he knows others won't finish before him, and you're talking to him like he's a noob (you have no clue how long ago this was). Hell, you don't even know if the tickets were outdated.by the-smug-one
6/6/2026 at 9:41:39 AM
>impactNot everything in life is correctly evaluated according to Meta performance review criteria, probably not even what people are doing at Meta.
by ahartmetz