Create templates to quickly answer FAQs or store snippets for re-use.
Cool post, but I need to ask you an unrelated question. I use canonical URLs for my xposts but I don't see anything like the "Originally published at csrhymes.com on Feb 29, 2020" that this post has between the title and tags. I've seen a few authors that have it. How do you do that? (I'm pretty sure mine are working in general cause I see the HTML tag if I fetch the page, and Google search console also suggests they're working, so I'm not sure what I'm doing differently.)
Hi Ryan, my site has an RSS feed and I’ve connected it to dev.to in my settings. When I add a new post to my website it adds it as a draft to dev.to automatically. It sets the canonical url but I don’t know what else it does differently to generate the “originally posted at” bit.
Thanks for your answer! I will have to look into RSS.
Another key thing about story points (in addition to everything above) is that the range of story points tells its own story...
Typically teams will use a power-of-two (1, 2, 4, 8) or Fibonacci sequence (1, 2, 3, 5, 8, 13) to generate their story point range. The common characteristic here is that the gaps between the numbers get bigger as the numbers get bigger. This "increasing distance" characteristic is intended to shine light on the fact that estimation of bigger things gets much harder, so our accuracy is likely to be much lower. This means there's no point using 12 (in the power-of-two) or 16 (in Fibonacci) because we're inherently unlikely to gain anything from the implied extra precision.
A far better approach is to split stories down (across meaningful seams) and estimate separately. Many teams will refuse to work on any story with an estimate greater than 10, for example.
We as a team use both story points and time based estimates.
Stories are initially estimated in story points in order for a release and iterations to be planned, but then when we're down at the current iteration and have broken down the planned stories in to tasks we look to put a time estimate.
Time estimates are just that though: estimates not expectation.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.