Readify TV is a place to collect videos by Readifarians. We don't actively produce content for this site as a company, however Readify people pop up at so many conferences and events that we end up with quite a bit anyway. This site provides an index to it all. Some are just from internal barcamps and the like, so they're not all the best quality, but they're content we think is still worth sharing.

We also use this site internally to share ideas, internal presentations and training.

Readifarian? Sign in to see internal content, and contribute. Not a Readifarian yet? Try knocking.

  1. All Audiences 57
  2. Consultant 55
  3. Developers 9
  4. Manager 4
  5. Sales Person 4
  6. Marketer 3
  1. All Tags 57
  2. C# 9
  3. Web 9
  4. F# 7
  5. ASP.NET 6
  6. ALM 5
  7. Azure 4
  8. JavaScript 4
  9. Domain-Driven Design 3
  10. Functional Programming 3
  11. Scrum 3
  12. Windows Phone 3
  13. Windows8 3
  14. Agile 2
  15. ALT.Net 2
  16. Android 2
  17. CQRS 2
  18. Functional programming 2
  19. ideas 2
  20. IIS 2
  21. iOS 2
  22. learning 2
  23. Math 2
  24. Presenting 2
  25. VSO 2
  26. Xamarin 2
  27. Alt.Net 1
  28. Arduino 1
  29. ASP.Net 1
  30. ASP.Net-5 1
  31. ASP.NET-vNext 1
  32. Asynchronous programming 1
  33. Azure Service Bus 1
  34. Brisbane Azure User Group 1
  35. Collaboration 1
  36. ColorTheory 1
  37. consultancy 1
  38. Continuous Delivery 1
  39. CSS 1
  40. Customers 1
  41. D3.js 1
  42. Design 1
  43. DevOps 1
  44. DocumentDB 1
  45. Engagements 1
  46. Estimation 1
  47. Event sourcing 1
  48. fear-of-failure 1
  49. Git 1
  50. GitHub 1
  51. Hardware 1
  52. HTTP 1
  53. Internet Explorer 1
  54. IoC 1
  55. IoT 1
  56. Johnny-Five 1
  57. knowledge 1
  58. Lean Startup 1
  59. Messaging 1
  60. Micro Services 1
  61. Neo4j 1
  62. NodeBots 1
  63. NodeJs 1
  64. NoSQL 1
  65. OWIN 1
  66. Pact 1
  67. Pact.NET 1
  68. Pact-Net 1
  69. PowerShell 1
  70. PRINCE2 1
  71. Pull Requests 1
  72. Refactoring 1
  73. REST 1
  74. SharePoint 1
  75. SignalR 1
  76. skill 1
  77. Testing 1
  78. TypeScript 1
  79. Typography 1
  80. Universal Apps 1
  81. VisualDesign 1
  82. VS 1
  83. Windows 1
  84. Windows Store 1

Public: This video is open for anyone on the internet to see.

JavaScript, Web

Consultant

Aaron Powell

A short look at what you can do with JavaScript, from creating a DOM API to the basis of the TPL from .NET.

Public: This video is open for anyone on the internet to see.

ALT.Net, Web, OWIN

Consultant

Aaron Powell

My talk from September ALT.Net Sydney on OWIN, a new approach to doing ASP.Net web applications. Slides - https://presentboldly.com/AaronPowell/owin/ My blog series on OWIN - http://www.aaron-powell.com/tagged/owin.html

Public: This video is open for anyone on the internet to see.

Internet Explorer, Web

Consultant

Aaron Powell

For August's SydJS I presented about some of the new features coming in Internet Explorer 11. Slides can be found here - http://AaronPowell.github.io/talks/ie11-what-s-new/

Public: This video is open for anyone on the internet to see.

Web, ASP.NET, DevOps

Consultant

Tatham Oddie

Presented in Manila, Philippines on Wed 12th Dec 2012. Big websites fail in spectacular ways. In this session, five-time awarded ASP.NET/IIS MVP and ASP Insider Tatham Oddie will share the problems that he and fellow Readify consultants have solved on large scale, public websites. The lessons are applicable to websites of all sizes and audiences, and also include some funny stories. (Not so funny at the time.) — A tiny subset of your users can’t login: they get no error message yet have both cookies and JavaScript enabled. They’ve phoned up to report the problem and aren’t capable of getting a Fiddler trace. You’re serving a million hits a day. How do you trace their requests and determine the problem without drowning in logs? Marketing have requested that the new site section your team has built goes live at the same time as a radio campaign kicks off. This needs to happen simultaneously across all 40 front-end web servers, and you don’t want to break your regular deployment cycle while the marketing campaign gets perpetually delayed. How do you do it? Users are experiencing HTTP 500 responses for a few underlying reasons, some with workarounds and some without. The customer service call centre need to be able to rapidly evaluate incoming calls and provide the appropriate workaround where possible, without displaying sensitive exception detail to end users. At the same time, your team needs to prioritize which bugs to fix first. What’s the right balance of logging, error numbers and correlations ids? Your application is running slow in production, causing major delays for all users. You don’t have any tools on the production servers, and aren’t allowed to install any. How do you get to the root of the problem?

Public: This video is open for anyone on the internet to see.

ASP.NET, CSS, JavaScript, TypeScript, Web

Consultant

Tatham Oddie

Good quality web development is hard at the best of times, but it only gets harder when you’ve got a whole team of developers. Reusable components are a simple starting point, but then you need to work out how to manage all of the assets (markup, CSS, JS, server-side logic) whilst still being performant. You’ll also need an architecture that allows components to be combined or extended as required, and be ready to be amazed at how many different ways developers will find to call your components. In this session, web-pro Tatham Oddie will present how we’ve handled these challenges on a large scale, public facing web app (100 developers, millions of customers).

Public: This video is open for anyone on the internet to see.

Web

Consultant

Aaron Powell

The heterogeneous nature of the web makes it extremely powerful, but also ensures that it fails in spectacular ways. Through a multitude of networks spanning land, air, sea and space, you’re expected to deliver a working web page that runs on multiple versions of hundreds of browsers and devices. Harder yet, you’re expected to work out why it broke and fix it fast. Oh, and make it load quickly while you’re at it please. In this session, web-pros Aaron Powell and Tatham Oddie will show you their toolbox of debugging tips. From the client to the server and the network in between, we’ll cover it all.

Public: This video is open for anyone on the internet to see.

ASP.NET, IIS, Web

Consultant

Tatham Oddie

The heterogeneous nature of the web makes it extremely powerful, but also ensures that it fails in spectacular ways. Through a multitude of networks spanning land, air, sea and space, you’re expected to deliver a working web page that runs on multiple versions of hundreds of browsers and devices. Harder yet, you’re expected to work out why it broke and fix it fast. Oh, and make it load quickly while you’re at it please. In this session, web-pros Aaron Powell and Tatham Oddie will show you their toolbox of debugging tips. From the client to the server and the network in between, we’ll cover it all.

Public: This video is open for anyone on the internet to see.

ASP.NET, IIS, Web

Consultant

Tatham Oddie

In the competition against native code, the web is going realtime. ‘Save’ buttons are disappearing. Even AJAX is starting to feel slow and clunky. Still polling for changes? That’s sooo 2010. Some solutions have been around for a few years now, however they’ve been hacked on top of long polling, network timeouts and heavy protocols. Further detracting from their use: they’ve been hard to support and sale on the server-side. In this session, networking-pro Tatham Oddie will show you the lightweight, binary-level protocols that are now available to web developers. We’ll walkthrough OS level support in IIS 8, platform support in ASP.NET 4.5, and the library that makes it all easy: SignalR. Finally, we’ll answer the dreaded question, “but how do I make this work everywhere today?”

Public: This video is open for anyone on the internet to see.

ASP.NET, Web

Consultant

Tatham Oddie

A tiny subset of your users can’t login: they get no error message yet have both cookies and JavaScript enabled. They’ve phoned up to report the problem and aren’t capable of getting a Fiddler trace. You’re serving a million hits a day. How do you trace their requests and determine the problem without drowning in logs? Marketing have requested that the new site section your team has built goes live at the same time as a radio campaign kicks off. This needs to happen simultaneously across all 40 front-end web servers, and you don’t want to break your regular deployment cadence while the campaign gets perpetually delayed. How do you do it? Users are experiencing 500 errors for a few underlying reasons, some with workarounds and some without. The customer service call centre need to be able to rapidly triage incoming calls and provide the appropriate workaround where possible, without displaying sensitive exception detail to end users or requiring synchronous logging. At the same time, your team needs to prioritize which bugs to fix first. What’s the right balance of logging, error numbers and correlations ids? These are all real scenarios that Tatham Oddie and his fellow consultants have solved on large scale, public websites. The lessons though are applicable to websites of all sizes and audiences.