someone shipped my exact feature 19 days after i posted the schema and the screenshots
I've been posting weekly build updates for about five months. Two of those posts had the actual database schema in them and a screenshot of the thing that makes my tool different - a diff view for two versions of a config file, with a specific way of grouping the changes so people stop skimming.
Nineteen days after the second post, an account that had liked both of them shipped the same view in a product that already has an audience. Same grouping. Similar labels.
I'm not naming anyone and I don't think there's anything to do legally. What I want is the practical version: do people who build in public actually hold back the interesting part, and if so what's left to post? Half the point was the accountability.
@colorgrade_cleo · last mo. · 3 replies
Posted openly for two years. My rule now is that I post the problem, the decision and the mistake, and I don't post the mechanism. 'Spent four days figuring out how to group config changes so people stop skimming past them' is a great post. The screenshot of the actual grouping is a spec.
Nobody follows you for the spec. They follow you because you keep showing up and because your reasoning is interesting. You lose almost nothing by cropping.
Reply
Report
@goroutine_gil · last mo.
This is the distinction I've been trying to make for months and couldn't. Problem yes, mechanism no.
Reply
Report
@rough_draft_rob · last mo.
Counterpoint: the mechanism is what gets shared. My most-shared post ever was a screenshot of a query plan, and everything else got twelve views. There's a real trade here and pretending there isn't is how people end up posting into a void for a year.
Reply
Report