I remember playing it on newsgroup. Good format (with threads and subthreads) and people using correctly actual convention.
Too bad I don't see a running game anymore.
By chance!
I was working in a company that needed a mail templating that could send a large amount (yeah... I learned it was spam alike after)
And one of my coworker came with a solution of programming by actors with Akka actors, based on scala.
So to help this coworker maintaining and evolving this application, I learn the language and the concepts under the language.
Now I chose my current job partly for the language (and because there is a strong connection with open source contribution)
Really, for my job, it depends on the subject. Next feature: the CTO (small structure, so he has the PO cap). Small library dependency to add in our project, the dev that need it. Big refactoring: the one that had the idea validated by the whole team (to be sure it's the path we want to take). Process/documentation: a team specific meeting.
Usually, small nits to change to sustain all team members.
For current next big feature, it's the fourth proposal and we don't agree yet. So was have more proposals to come.
I don't understand why "title"s are so partitioning?
Obviously, the PO is accountable for the user stories, but they are not to write them all by themselves.
Let the PO decide what is the next big feature, then pair them with a dev to split into manageable stories.
Such stories will be then smaller and still have to be split in task. But at least, the user story will be small enough to be develop as is.
PO will have the last word about the big picture and the details (user facing) but the means are in dev hands.
