Microsoft Podcasts. Audience: Developer/ Product: Architecture Part 2 of Patrick Weikle’s interview with Pat Helland where he talks about the framing of unreliability and eventual consistency of transactions.
ARCast.TV: Pat Helland on Memories, Guesses and Apologies
Tagged with architecture technical transactions consistency
Possibly related…
-
EconTalk: Munger on Exchange, Exploitation and Euvoluntary Transactions
Mike Munger of Duke University talks with EconTalk host Russ Roberts about the psychology, sociology, and economics of buying and selling. Why are different transactions that seemingly make both parties better off frowned on and often made illegal? In theory, all voluntary transactions should make both parties better off. But Munger argues that some transactions are more voluntary than others. Munger lists the attributes of a truly voluntary transaction, what he calls a euvoluntary transaction and argues that when transactions are not euvoluntary, they may be outlawed or seen as immoral. Related issues that are discussed include price gouging after a natural disaster, blackmail, sales of human organs, and the employment of low-wage workers.
-
Podcast: A Practical Guide to Information Architecture, with Donna Spencer | I'd Rather Be Writing
Donna Spencer is the author of A Practical Guide to Information Architecture as well as two other books (on card sorting and writing for the web). She’s an experienced information architect, based in Australia, who gives regular workshops on information architecture at conferences such as the IA Summit and also runs the UX Australia conference. In this podcast we talk about information architecture, especially in the context of technical communication. Some of the topics we cover include the following:
What information architecture is, especially in contrast to content strategy and user experience Why writers are well suited for information architecture Reasons for doing user research prior to building your information architecture Determining user terminology (and dangers of choosing the wrong terms, even if people use them) Evaluating browse versus search, and the problem of looking for information without knowing the right terms Strategies for dealing with overlapping categories and difficult-to-fit topics Why organizing content by audience can be tricky Using focused entry points to serve different audiences Finding what you need when you don’t know what you need Organizing content by popularity, and other alternative classification schemes Scenario driven testing with index cards Card sorting strategies, tools, and limits Reasons for brainstorming IA off-screen, without your computer. Determining the number of top-level navigation options Providing navigation through next and related links Beginning the information architecture at the content page rather than the home page The kind of content to add to your home page I highly recommend this book as well as learning more about information architecture in general. For more information about Donna Spencer, see her site, Maad Mob. For more information on her book, see A Practical Guide to Information Architecture. You can follow Donna on Twitter @maadonna.
-
Episode 47: Interview Grady Booch | Software Engineering Radio
In this Episode we are happy to talk to Grady Booch. We started off by discussing his Architecture Handbook, how it came into being, the progress, and how it will look like once it’s finished. In this context we also looked at the issue of how to distinguish architecture from design. We then asked him about how "professional" software architecture is these days, as well as about the ubiquity of software product lines in industry. The next couple of minutes looked at the question of whether software development is an engineering discipline, craftsmanship or an art form, and we discussed the key qualifications of software developers. Grady then elaborated on the problems of developing in large teams as well as the potential limits of complexity we can tackle with software.
We then got back to a more technical discussion, where we looked at model-driven development, DSLs, etc. and the role of the UML in that context. Next was a discussion about scripting languages, and the current trend towards new languages. We then looked at component marketplaces and other forms of reuse, as well as the importance of OO these days and the relevance of AO. We concluded with a (small) outlook to the future.
Tagged with se-radio software development architecture