[Mastering Business Analysis 81] David Hussman - User Story Mapping http://masteringbusinessanalysis.com/mba081-user-story-mapping-david-hussman/
- A map is simply a collection of information with orientation
- User stories aren’t just a pile of things to do. There’s an underlying structure that helps you see the big picture from the customer’s point of view.
- By organizing the story cards into a map, we can better understand the customer journey and identify small slices of value to deliver.
- User Story Maps are an arrangement in which story cards from left to right follows people’s interaction with the system and top to bottom to decompose that interaction
- An introduction to event storming https://ziobrando.blogspot.co.uk/2013/11/introducing-event-storming.html
[AudioBookPodcasts.Microservices] Adrian Cockcroft - State of the Art in Microservices https://www.youtube.com/watch?v=nMTaS07i3jk
[YouTube] Kent Beck - The Return of the Waterfall https://www.youtube.com/watch?v=w4IncnNVzMA&feature=youtu.be
[ASP.NET Monsters - Channel 9] Configuration From Any Source in ASP.NET Core https://channel9.msdn.com/Series/aspnetmonsters/ASPNET-Monsters-Episode-50-Configuration-From-Any-Source-in-ASPNET-Core
[SE-Radio 263] Camille Fournier - Real-World Distributed Systems http://www.se-radio.net/2016/07/se-radio-episode-263-camille-fournier-on-real-world-distributed-systems/
- CAP Theorem https://en.wikipedia.org/wiki/CAP_theorem
- Fallacies of distributed computing https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
- Limit nested quantifiers
- Ensure only one way to do the matching
- Use atomic grouping
- Use DefaultRegExMatchTimeout in .net apps
- Always, always consider the failure cases (esp. the almost but not quite matches)
No comments:
Post a Comment