Ask
312
@printbed_gremlin ·

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.

9 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @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.

    141
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @goroutine_gil · last mo.

      This is the distinction I've been trying to make for months and couldn't. Problem yes, mechanism no.

      56
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      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.

      31
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @gio_castellan · last mo. · 2 replies

    Going to push back on the premise. Nineteen days is not enough time to design, build, review and ship a feature inside a product that already has customers, unless it was already in flight. It is far more likely they were building it anyway and your post is the reason you noticed.

    That's not nothing - it means you picked the same obvious next step as a team with more information than you have - but 'they copied me' and 'we both read the same complaints' look identical from the outside.

    88
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @goroutine_gil · last mo.

      Both can be true. Seeing that a solo dev shipped it and nobody screamed is exactly the kind of evidence that moves something up a roadmap.

      34
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @dee_okonkwo · last mo.

    The part worth being annoyed about isn't the feature, it's that they have distribution and you don't. A feature takes a competent team a week. An audience takes two years. If a nineteen-day copy can take your business, the feature was never the business.

    I'd spend the next month on what they structurally can't copy: a specific integration, the vocabulary of one niche, support that answers in an hour.

    62
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @darning_dot · last mo.

    Keep posting. Change what you post. Ship the next thing before you write about the last one.

    44
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @fiber_finn · last mo.

    New to posting publicly and this thread scared me, so I landed on a compromise that seems to be working: I post on a two week delay. Whatever I shipped a fortnight ago is what I write about this week. It's still honest, the screenshots are real, and by the time anyone reads it the feature is already live for my users.

    The only cost is that the updates feel less exciting to write, which honestly made them better, because I'd stopped being high on the change.

    27
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @chain_wear_chase · last mo.

    One boring protection: put a date on everything and leave the posts up. If you ever need to show you were first, a public timestamped post is the cheapest evidence there is. It won't win you anything but it ends the argument in a group chat.

    19
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report