Hacker News Reader

Comment by jargon | Hacker News Reader

That is one way to look at it.

Another way would be to create a portfolio. Spend $25/mo or whatever on a web server, build some web apps and put them online for people to see.

Don't work for free.

How do you feel about working on open source projects for free?

View on HN

I think working on open source projects for free is different. There usually isn't really a client.. for a lot of people who work on open source projects, the client is themselves.. so in a sense, they're not working for free.. they're putting in effort, and getting a return. That said, some of the "Don't work for free" challenges still hold.. like motivation. For many people, it helps to have money on the table, and a timeline committed to. Loads of open source projects fall down because interest and motivation wax and wane. It's helpful to have an outside force keep you moving forward, and someone else's money is a big outside force.

Working on OSS "for free" is different than working for some guy's startup without pay. At least with OSS, you can usually find a link to the commits you contributed, provide an explanation of how you solved that particular problem and why, and stick it in a portfolio.

You can't do that with proprietary software that may or may not even be running in a year from now.

Startups can open their source as well.

It makes sense for various tools which we can't guarantee will be supported if the business doesn't survive. I'm much more likely to work with and contribute to code I know will be around independent of a business.

Reply on news.ycombinator.com