![]() In a Corporate environment, the procurement for such services can be off-putting, integration setup can be an up-hill battle, and there can be strong restrictions regarding external services. CI, static analysis, dependency auditing, etc is one click/integration away. Third, people working on OSS projects are generally a bit more motivated, either because it's their subject of interest, or because of the general appeal of OSS.įorth, often with OSS, you actually have more resources/service available to help with code quality. You can also spend time on things like unit tests, fuzzing, etc.īasically, you can more easily work on all these things that are "valuable" but difficult to "quantify/measure". Second, You have far more time/freedom, specially if it's a personal project, to think about design/code architecture, and to rework things if required. In contrast, in a corporate environment, the code is not seen by so many eyes if at all, and even if read, the readers are roughly a known quantity. Here are my though on it:įirst, with Open Source software, you expose (potentially) what you write to the while world, as a consequence, you don't want to feel ridiculous by publishing atrociously bad code. Developing an Open Source software can have some incentives to have cleaner code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |