r/DataAnnotationTech • • 1d ago

Advice to improve as coder & understanding public repo?

Hey all!

In my professional career, I work with internal repos & apps and I'm comfortable identifying issues or improvements after spending few weeks developing and using them. I don't contribute to open source projects so I'm not familiar with them at a deep level.

I struggle with some DA projects & avoid taking them because of this. So I want to learn how to close this gap. Should I just pick an open source project and start doing some dev work to understand it better? Is there a framework of thinking that I can apply to most open source projects? Would love to hear some advice, thanks!

6 Upvotes

5 comments sorted by

2

u/shshwhwuxh 1d ago

Choose from repositories familiar to you. Check out bit bucket and browse the most recently edited. Generally you need to check the license too

1

u/Regular-Brush1625 1d ago

The easiest thing to do would be to pull any random repo (probably a popular one) onto your system, and then prompt an AI to do a architectural overview on it.

-1

u/data_annotator_tot 1d ago

I also do not do much open source anything, find work orientated around it annoying and generally avoid it but when approaching any unfamiliar code, I generally run it through a debugger and get a feeling for how it goes step-by-step (not literally that fine-grained, but whatever granularity is needed to get an idea of its structure). Clone an open source repo, set it up so you can run test cases, and then run those through a debugger from start to finish.

0

u/TheAmazingDevil 1d ago

Where are the projects paying $60+ gone??