djake

I’m building www.movegoalpost.com. It’s a team based system for managing project requirements of any sort, but I’m focusing on software and product managers since it’s a segment I know.

The basic idea is that ticket (or chat) based workflows loose tons of context over time. During periods of rapid iteration, even the tickets themselves can’t always keep up with changes in the requirements. Goalpost projects are lightly structured documents. Due to that structure, it can easily give you a view of what changed in any particular update, or you can search or browse the overall up to date spec if you are just looking to get context on something.

There are some nice quality of life features. Changes live in batches which can (optionally) be subjected to customizable approval rules. Email notifications to stakeholders when requirements change. The ability to move changes to different batches, pre-approval.

Still WIP, but I’d love any feedback!

If I want to try developing an app for this, should I just wait for the thing to be generally available and try to buy one? Would Apple ever offer some kind of developer preview device?

I joined the sourdough bandwagon during the pandemic. I was committed to whole wheat, and had inconsistent (to put it generously) results until I came across Hendrik's Whole Wheat Sourdough Master class[0]. Really great content, and all of the experimentation really showed. I'm happy to see it here!

[0] https://www.youtube.com/watch?v=ImVvQMvGZKE

My understanding is the motivation for Q1 is that vendors will stop including ODB ports since they can rely on OTA mechanisms [1], thus bypassing the intent of the previously enacted right to repair bill. The Globe editorial [2], despite being in favor of Question 1, acknowledges many of the concerns you've laid out. They suggest, as a possible remedy, that the Legislature amend the law if and when voters approve it, and propose "a compromise that requires all cars, including electric vehicles, to keep their OBD ports — which mechanics can currently plug into to retrieve diagnostics data ."

1: "More than 90% of new cars transmit real-time repair information wirelessly, and independent repair shops will soon have limited or no access." https://massrighttorepair.org/ 2: https://www.bostonglobe.com/2020/10/13/opinion/vote-yes-ques...

Why don't npm/yarn/github/etc have explicit support for premium packages that cost money? It can provide revenue for the registry, too.

Napster and LimeWire were cool because people got something for free and, all else being equal, people prefer free to not free; but all else is not equal because free is not necessarily sustainable. If there were literally no way to monetize music at scale, it would not have worked out well for consumers in the long wrong, because there would be far less to consume.

People pay for software regularly. Package managers are marketplaces for software, so it doesn't seem like a huge leap for them to facilitate the exchange of funds. Then feross can charge money for standard if he wants, and people that don't think it's worth it won't pay him and won't see an ad and won't use the software.

A Report SPAM button on calendar invites would seem to be in order, so I don't have to manually delete each of these from the same address, and so Google can ban the offending account quickly.

Edit: it appears you can do this on desktop but not mobile: https://support.google.com/calendar/answer/6110973?co=GENIE....

Can you recommend where I can see such data? It would be a very useful reference.