Many of us write opensource code in a void: nobody ever looks at it, uses it nor reviews it. We are the only users and authors.

In order to improve, where can we get our code reviewed? I don’t mean professionally, just from like-minded individuals.

  • varsock@programming.dev
    link
    fedilink
    arrow-up
    17
    ·
    edit-2
    11 months ago

    There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.

    1. Just build a proof of concept
    2. Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
    3. Build something internally that you yourself will use
    4. Only once something is good enough and is used internally, then release it to beta.

    So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.