An interesting post from Howard #endjin using #rx to observe file system changes. https://endjin.com/blog/2024/05/observe-file-system-changes-with-rx-dotnet
@idg10 does a deep dive into the Quiescent operator in our free ebook on RX.
https://introtorx.com/chapters/key-types#linq-operators-and-composition
It was great to see my #endjin co-founder Howard at the IOC launch of the #olympic #ai agenda today.
He is a member of the IOC AI expert working group that has been informing and advising this programme, aiming to guide the IOC’s efforts to maximise the opportunities and manage the risks of the transformative power of artificial intelligence, to support athletes and drive the development of sport and the Olympic Games.
https://olympics.com/ioc/news/ioc-takes-the-lead-for-the-olympic-movement-and-launches-olympic-ai-agenda
We were chatting about this at the #endjin Xmas dinner the other week. It is notable, I think, that every single attempt to build a better #WPF has ended up in some significant way less good.
Any UI framework is a balance of compromise but WPF is remarkably well poised. Props to #Avalonia which seems to be achieving much the same balance.
If only we'd had a couple more years of "real" Moore's Law rather than the "more cores at the same clock speed" version we've had since WPF first shipped...
A quick video culled from one of our internal "show and tell" sessions at #endjin. Ian Griffiths talks about #tensors and #GPT with #TorchSharp.
Data Mesh is the latest approach for delivering data-driven value at scale. Microsoft Fabric has been heavily influenced by Data Mesh, but there are gaps that you will need to address. This article will help you assess how much support Microsoft Fabric will give to enabling a Data Mesh inspired vision.
Over at #endjin we're publishing customer interviews about Microsoft Fabric and the data landscape.
They capture the perspective of senior business decision makers (think CxO or Director-of) and take a risk/benefit perspective, in the context of the competitive landscape.
The first looks at adoption challenges, and how to place your bets.
The second considers the impact of Generative AI on technologists and users.
Welcome to the first part in a new series of interviews with real-world Decision Makers (CTOs, CIOs, Heads of / Directors of Software Engineering, Data & Analytics) about how they manage their strategic roadmap and evaluate new technologies to simplify their portfolio, deliver better outcomes for stakeholders, or give them a competitive advantage. In a 3-part interview we talk to Tom Peplow about his assessment of Microsoft Fabric. TLDR; Tom Peplow, Principal & Senior Director Product Strategy at Milliman, chats with Ian Griffiths & Ed Freeman from endjin about how Microsoft Fabric is a disruptive technology. Milliman has been using Azure since 2010, building a bespoke actuarial solution which incorporates big compute and big data technologies to perform petabyte scale data processing. Milliman are currently evaluating whether Fabric can solve their problems more efficiently than their current implementation. Tom is impressed with Microsoft's internal Finance Team's digital transformation case study, which exemplifies the improvements and productivity gains his customers desire, and believes Fabric could deliver the same type of outcome. However, there are concerns that this transformation may lead to historic headaches (like Microsoft Access) all over again, causing apprehension on the IT side. Tom believes that standards are a significant enabler and that openness is key. The talk contains the following chapters: 00:00 Introduction 00:57 What does Fabric offer? 03:11 Costs and benefits of change 05:11 Fabric, Power BI and the end user experience 07:02 New enabling technology in Fabric (OneLake) 08:55 Open Table Format 10:20 Fabric's end user focus 11:53 Fear of Fabric 13:15 Guard rails for end users 13:55 DevOps & FinOps 16:16 Version Control
Oho! @brianrandell has just announced at #vslive that "Essential DevOps" - a collaboration between #endjin and #github - will be published "soon".
We've been keeping this under our hat for a while and have been bursting to get it out there.
It's our distillation of thinking about DevOps philosophy and practice in 2023, and how it has changed and developed since the term was coined 15 years ago.
Matthew Adams
