How do you measure success as a developer ? Is it how good your code looks ? Is it how well covered it is by unit tests ? We think that while those are required, that's not it.

Could it be the opposite of the opened bugs then ? Someone actually bothered to open a bug / issue on it... Sorry to burst your bubble, but that's still not it; usually, projects without bugs just mean … they're not being used.

Thus, in our humble opinion, the code must matter to someone, and it must be used in production by as many people as possible - to the point they contribute, request features, and report broken “things”.

Now the thing is how do you get end users to use your stuff ? It's a non-trivial problem: unless you come up with something useful - and entirely new - odds are you're hoping people will replace one existing component of their stack (sure ... it had its problems …) by your new shiny toy. ... which only you care about !
And we all know migrations have their downsides … It usually requires a big improvement for people to be willing to pay the price.

Join us in this talk as we discuss strategies to get your pet project out there in the wild, and being used as it should / deserves.