top of page
Search
  • katzaliha2013

HACK Bit Che V1.0.0.60 Guevara Ed. Portablel Latekala







Sharing source code for the project is going to be your job. This way, others can contribute to the project or extend it. Also, making your code available is a benefit to your project as well, because others will see how the project has been structured and can find patterns and write better code. A: We need to be careful about the quality of what we put in our datasets. If we want to be honest with ourselves, we should be asking ourselves if the data we are releasing is the best we could come up with. So, if you don't have that kind of data, then it is perfectly fine to not release it. The same thing goes with code. It is certainly not as bad to not share code as it is to have bad code. If I want to review your code, what I want is an open source repo with good practices. I like to read about the code my people wrote. Is it clean and well documented? Is it open source so that I can ask people to help me fix the problems they find? If I can see that someone is passionate about what they are working on and that they are trying to be open about what they are doing, I can see myself contributing to that project as well. For the record, one of the goals of my group is to always push open source development. The main reasons why we do this are: Some people are good at coding and good at creating good software, but they don't have the time to share their code with the world. That's why we create a github repo, so that we can just give it to them. We want to enable others to contribute. Asking people to join a team is a lot easier than opening an email and asking them to join. If your project is good, people will contribute and help you improve it. We want to create an ecosystem. We want to make the most of the open source, and we want others to use that as well. The best way to know if you are doing it right is to talk to your user base. And, if possible, you should make sure to know the "why" as well. There are good reasons to share code, but not every project can or should share code, especially code that is critical to the business. One good reason not to share code is if the code contains business secrets, which is why it is generally a good idea to release lots


Related links:

5 views0 comments

Recent Posts

See All
bottom of page