I am trying to convince him in an attempt to produce better code by separating concerns, isolate logic and following best practices.

He wants to produce readable/shareable code but is not entirely convinced that opening it is a good idea.

What other arguments can i use?

  • 2
    "opening"? As in, going open source? Going open source won't solve you anything at all if your team is unable to keep it up with the skills required by the project. I'm not sure what you mean by that.
    – T. Sar
    Jul 11 '17 at 19:02
  • 6
    You'll want to write it with detachable business logic even if you don't open source it (I mean, best practices shouldn't be driven by whether the project is open source or not... if it takes the threat of others seeing the code to make your team do well with it, maybe there's a more fundamental issue that should be addressed?)
    – jleach
    Jul 11 '17 at 19:14
  • 2
    Open source is a license not a requirement. I can open source my mothers recipe for lasagna. Not much in the way of business logic there (just layers, and indirection when I lose my grip on the fork) but the sauce is incredible. Jul 11 '17 at 19:15
  • 4
    I think you need to stop conflating two separate issues. Why do you think going open source will help with anything at all? Jul 11 '17 at 19:24
  • 1
    see How do I explain ${something} to ${someone}?
    – gnat
    Jul 11 '17 at 19:51

Well, why do you think opening is a good idea, in the first place?

Open Source has nothing to do with code quality - it is just a license, nothing else.

Going open source definitely wont help you to increase your code quality - you need a good team with good skills and good management to accomplish that. You can very easily find several open source pieces of garbage for every shinning gem out there on the dark depths of GitHub.

Unless you are thinking about cooperative effort to build a open-source project, like what is done with several flavors of *nix systems, going open source won't help you at all.

If you are thinking about getting free, cooperative effort from your community, you better have a very good product already. We as developers love to build stuff and to solve problems, but we won't code for anyone for free unless we have a very damn good reason.

Like virtual internet cookie points. We love virtual internet cookie points.

Nevertheless, without knowing why you think going open will help you, we can't give you any answer different from "it won't" with any semblance of accuracy.

  • 4
    Not to mention that managing an active open source project is an art in and of its own...
    – jleach
    Jul 11 '17 at 19:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.