Skip to content

Comment on If I can't see your work - you're crapparent

Comments

My competitors also love my software. By giving them (at least part of) the source they solve bugs and add features for free. A good developer generally has far more than one good idea or library up their sleeve.

I begin work with clients with the explicit understanding that I am using public code that may be improved during the course of their project. I sell them on the benefit that they effectively get the project foundation for free, thanks to using this process with previous clients. Open code is better tested and guarantees that their business and codebase is sustainable towards the future, if something happens to me or our relationship otherwise ends. This security is invaluable to a client.

Closed-source, private code is a much harder sell even with a long list of happy clients. What guarantee can be given that the software will be sustainable going forward?

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.