Podcasts about implementations

Ryan Staley Featured on the CRO Spotlight PodcastRyan joins Warren Zenna for an in-depth conversation on the state of AI today—separating the hype from the real-world applications.They explore the various stages of AI integration in business, including augmentation, automation, and orchestration, and how these can transform roles, particularly for Chief Revenue Officers (CROs). Staley shares insights from his journey into AI consulting, emphasizing the importance of adapting to new technologies and the skills necessary for success in the evolving job market.Chapters00:00 Introduction to AI and Its Hype02:07 The Reality of AI Tools and Their Use Cases04:56 Challenges in AI Product Development07:48 The Future Landscape of AI Solutions10:48 Understanding AI Workflows: Augmentation, Automation, and Orchestration13:34 The Evolution Towards Autonomous Organizations16:18 Impact of AI on Employment and Job Roles21:50 The Evolution of AI Communication23:48 The Importance of Prompting Skills27:35 The Changing Role of Chief Revenue Officers29:36 Implementing AI Across Organizations32:58 Ryan Staley's Journey into AI

Francois Daost is a W3C staff member and co-chair of the Web Developer Experience Community Group. We discuss the W3C's role and what it's like to go through the browser standardization process. Related links W3C TC39 Internet Engineering Task Force Web Hypertext Application Technology Working Group (WHATWG) Horizontal Groups Alliance for Open Media What is MPEG-DASH? | HLS vs. DASH Information about W3C and Encrypted Media Extensions (EME) Widevine PlayReady Media Source API Encrypted Media Extensions API requestVideoFrameCallback() Business Benefits of the W3C Patent Policy web.dev Baseline Portable Network Graphics Specification Internet Explorer 6 CSS Vendor Prefix WebRTC Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: today I'm talking to Francois Daoust. He's a staff member at the W3C. And we're gonna talk about the W3C and the recommendation process and discuss, Francois's experience with, with how these features end up in our browsers. [00:00:16] Jeremy: So, Francois, welcome [00:00:18] Francois: Thank you Jeremy and uh, many thanks for the invitation. I'm really thrilled to be part of this podcast. What's the W3C? [00:00:26] Jeremy: I think many of our listeners will have heard about the W3C, but they may not actually know what it is. So could you start by explaining what it is? [00:00:37] Francois: Sure. So W3C stands for the Worldwide Web Consortium. It's a standardization organization. I guess that's how people should think about W3C. it was created in 1994. I, by, uh, Tim Berners Lee, who was the inventor of the web. Tim Berners Lee was the, director of W3C for a long, long time. [00:01:00] Francois: He retired not long ago, a few years back. and W3C is, has, uh, a number of, uh. Properties, let's say first the goal is to produce royalty free standards, and that's very important. Uh, we want to make sure that, uh, the standard that get produced can be used and implemented without having to pay, fees to anyone. [00:01:23] Francois: We do web standards. I didn't mention it, but it's from the name. Standards that you find in your web browsers. But not only that, there are a number of other, uh, standards that got developed at W3C including, for example, XML. Data related standards. W3C as an organization is a consortium. [00:01:43] Francois: The, the C stands for consortium. Legally speaking, it's a, it's a 501c3 meaning in, so it's a US based, uh, legal entity not for profit. And the, the little three is important because it means it's public interest. That means we are a consortium, that means we have members, but at the same time, the goal, the mission is to the public. [00:02:05] Francois: So we're not only just, you know, doing what our members want. We are also making sure that what our members want is aligned with what end users in the end, need. and the W3C has a small team. And so I'm part of this, uh, of this team worldwide. Uh, 45 to 55 people, depending on how you count, mostly technical people and some, uh, admin, uh, as well, overseeing the, uh, the work, that we do, uh, at the W3C. Funding through membership fees [00:02:39] Jeremy: So you mentioned there's 45 to 55 people. How is this funded? Is this from governments or commercial companies? [00:02:47] Francois: The main source comes from membership fees. So the W3C has a, so members, uh, roughly 350 members, uh, at the W3C. And, in order to become a member, an organization needs to pay, uh, an annual membership fee. That's pretty common among, uh, standardization, uh, organizations. [00:03:07] Francois: And, we only have, uh, I guess three levels of membership, fees. Uh, well, you may find, uh, additional small levels, but three main ones. the goal is to make sure that, A big player will, not a big player or large company, will not have more rights than, uh, anything, anyone else. So we try to make sure that a member has the, you know, all members have equal, right? [00:03:30] Francois: if it's not perfect, but, uh, uh, that's how things are, are are set. So that's the main source of income for the W3C. And then we try to diversify just a little bit to get, uh, for example, we go to governments. We may go to governments in the u EU. We may, uh, take some, uh, grant for EU research projects that allow us, you know, to, study, explore topics. [00:03:54] Francois: Uh, in the US there, there used to be some, uh, some funding from coming from the government as well. So that, that's, uh, also, uh, a source. But the main one is, uh, membership fees. Relations to TC39, IETF, and WHATWG [00:04:04] Jeremy: And you mentioned that a lot of the W3C'S work is related to web standards. There's other groups like TC 39, which works on the JavaScript spec and the IETF, which I believe worked, with your group on WebRTC, I wonder if you could explain W3C'S connection to other groups like that. [00:04:28] Francois: sure. we try to collaborate with a, a number of, uh, standard other standardization organizations. So in general, everything goes well because you, you have, a clear separation of concerns. So you mentioned TC 39. Indeed. they are the ones who standardize, JavaScript. Proper name of JavaScript is the EcmaScript. [00:04:47] Francois: So that's tc. TC 39 is the technical committee at ecma. and so we have indeed interactions with them because their work directly impact the JavaScript that you're going to find in your, uh, run in your, in your web browser. And we develop a number of JavaScript APIs, uh, actually in W3C. [00:05:05] Francois: So we need to make sure that, the way we develop, uh, you know, these APIs align with the, the language itself. with IETF, the, the, the boundary is, uh, uh, is clear as well. It's a protocol and protocol for our network protocols for our, the IETF and application level. For W3C, that's usually how the distinction is made. [00:05:28] Francois: The boundaries are always a bit fuzzy, but that's how things work. And usually, uh, things work pretty well. Uh, there's also the WHATWG, uh, and the WHATWG is more the, the, the history was more complicated because, uh, t of a fork of the, uh, HTML specification, uh, at the time when it was developed by W3C, a long time ago. [00:05:49] Francois: And there was been some, uh, Well disagreement on the way things should have been done, and the WHATWG took over got created, took, took this the HTML spec and did it a different way. Went in another, another direction, and that other, other direction actually ended up being the direction. [00:06:06] Francois: So, that's a success, uh, from there. And so, W3C no longer works, no longer owns the, uh, HTML spec and the WHATWG has, uh, taken, uh, taken up a number of, uh, of different, core specifications for the web. Uh, doing a lot of work on the, uh, on interopoerability and making sure that, uh, the algorithm specified by the spec, were correct, which, which was something that historically we haven't been very good at at W3C. [00:06:35] Francois: And the way they've been working as a, has a lot of influence on the way we develop now, uh, the APIs, uh, from a W3C perspective. [00:06:44] Jeremy: So, just to make sure I understand correctly, you have TC 39, which is focused on the JavaScript or ECMAScript language itself, and you have APIs that are going to use JavaScript and interact with JavaScript. So you need to coordinate there. The, the have the specification for HTML. then the IATF, they are, I'm not sure if the right term would be, they, they would be one level lower perhaps, than the W3C. [00:07:17] Francois: That's how you, you can formulate it. Yes. The, the one layer, one layer layer in the ISO network in the ISO stack at the network level. How WebRTC spans the IETF and W3C [00:07:30] Jeremy: And so in that case, one place I've heard it mentioned is that webRTC, to, to use it, there is an IETF specification, and then perhaps there's a W3C recommendation and [00:07:43] Francois: Yes. so when we created the webRTC working group, that was in 2011, I think, it was created with a dual head. There was one RTC web, group that got created at IETF and a webRTC group that got created at W3C. And that was done on purpose. Of course, the goal was not to compete on the, on the solution, but actually to, have the two sides of the, uh, solution, be developed in parallel, the API, uh, the application front and the network front. [00:08:15] Francois: And there was a, and there's still a lot of overlap in, uh, participation between both groups, and that's what keep things successful. In the end. It's not, uh, you know, process or organization to organization, uh, relationships, coordination at the organization level. It's really the fact that you have participants that are essentially the same, on both sides of the equation. [00:08:36] Francois: That helps, uh, move things forward. Now, webRTC is, uh, is more complex than just one group at IETF. I mean, web, webRTC is a very complex set of, uh, of technologies, stack of technologies. So when you, when you. Pull a little, uh, protocol from IETFs. Suddenly you have the whole IETF that comes with you with it. [00:08:56] Francois: So you, it's the, you have the feeling that webRTC needs all of the, uh, internet protocols that got, uh, created to work Recommendations [00:09:04] Jeremy: And I think probably a lot of web developers, they may hear words like specification or standard, but I believe the, the official term, at least at the W3C, is this recommendation. And so I wonder if you can explain what that means. [00:09:24] Francois: Well. It means it means standard in the end. and that came from industry. That comes from a time where. As many standardization organizations. W3C was created not to be a standardization organization. It was felt that standard was not the right term because we were not a standardization organization. [00:09:45] Francois: So recommend IETF has the same thing. They call it RFC, request for comment, which, you know, stands for nothing in, and yet it's a standard. So W3C was created with the same kind of, uh thing. We needed some other terminology and we call that recommendation. But in the end, that's standard. It's really, uh, how you should see it. [00:10:08] Francois: And one thing I didn't mention when I, uh, introduced the W3C is there are two types of standards in the end, two main categories. There are, the de jure standards and defacto standards, two families. The de jure standards are the ones that are imposed by some kind of regulation. so it's really usually a standard you see imposed by governments, for example. [00:10:29] Francois: So when you look at your electric plug at home, there's some regulation there that says, this plug needs to have these properties. And that's a standard that gets imposed. It's a de jure standard. and then there are defacto standards which are really, uh, specifications that are out there and people agree to use it to implement it. [00:10:49] Francois: And by virtue of being used and implemented and used by everyone, they become standards. the, W3C really is in the, uh, second part. It's a defacto standard. IETF is the same thing. some of our standards are used in, uh, are referenced in regulations now, but, just a, a minority of them, most of them are defacto standards. [00:11:10] Francois: and that's important because that's in the end, it doesn't matter what the specific specification says, even though it's a bit confusing. What matters is that the, what the specifications says matches what implementations actually implement, and that these implementations are used, and are used interoperably across, you know, across browsers, for example, or across, uh, implementations, across users, across usages. [00:11:36] Francois: So, uh, standardization is a, is a lengthy process. The recommendation is the final stage in that, lengthy process. More and more we don't really reach recommendation anymore. If you look at, uh, at groups, uh, because we have another path, let's say we kind of, uh, we can stop at candidate recommendation, which is in theoretically a step before that. [00:12:02] Francois: But then you, you can stay there and, uh, stay there forever and publish new candidate recommendations. Um, uh, later on. What matters again is that, you know, you get this, virtuous feedback loop, uh, with implementers, and usage. [00:12:18] Jeremy: So if the candidate recommendation ends up being implemented by all the browsers, what's ends up being the distinction between a candidate and one that's a normal recommendation. [00:12:31] Francois: So, today it's mostly a process thing. Some groups actually decide to go to rec Some groups decide to stay at candidate rec and there's no formal difference between the, the two. we've made sure we've adopted, adjusted the process so that the important bits that, applied at the recommendation level now apply at the candidate rec level. Royalty free patent access [00:13:00] Francois: And by important things, I mean the patent commitments typically, uh, the patent policy fully applies at the candidate recommendation level so that you get your, protection, the royalty free patent protection that we, we were aiming at. [00:13:14] Francois: Some people do not care, you know, but most of the world still works with, uh, with patents, uh, for good, uh, or bad reasons. But, uh, uh, that's how things work. So we need to make, we're trying to make sure that we, we secure the right set of, um, of patent commitments from the right set of stakeholders. [00:13:35] Jeremy: Oh, so when someone implements a W3C recommendation or a candidate recommendation, the patent holders related to that recommendation, they basically agree to allow royalty-free use of that patent. [00:13:54] Francois: They do the one that were involved in the working group, of course, I mean, we can't say anything about the companies out there that may have patents and uh, are not part of this standardization process. So there's always, It's a remaining risk. but part of the goal when we create a working group is to make sure that, people understand the scope. [00:14:17] Francois: Lawyers look into it, and the, the legal teams that exist at the all the large companies, basically gave a green light saying, yeah, we, we we're pretty confident that we, we know where the patterns are on this particular, this particular area. And we are fine also, uh, letting go of the, the patterns we own ourselves. Implementations are built in parallel with standardization [00:14:39] Jeremy: And I think you had mentioned. What ends up being the most important is that the browser creators implement these recommendations. So it sounds like maybe the distinction between candidate recommendation and recommendation almost doesn't matter as long as you get the end result you want. [00:15:03] Francois: So, I mean, people will have different opinions, uh, in the, in standardization circles. And I mentioned also W3C is working on other kind of, uh, standards. So, uh, in some other areas, the nuance may be more important when we, but when, when you look at specification, that's target, web browsers. we've switched from a model where, specs were developed first and then implemented to a model where specs and implementing implementations are being, worked in parallel. [00:15:35] Francois: This actually relates to the evolution I was mentioning with the WHATWG taking over the HTML and, uh, focusing on the interoperability issues because the starting point was, yeah, we have an HTML 4.01 spec, uh, but it's not interoperable because it, it's not specified, are number of areas that are gray areas, you can implement them differently. [00:15:59] Francois: And so there are interoperable issues. Back to candidate rec actually, the, the, the, the stage was created, if I remember correctly. uh, if I'm, if I'm not wrong, the stage was created following the, uh, IE problem. In the CSS working group, IE6, uh, shipped with some, version of a CSS that was in the, as specified, you know, the spec was saying, you know, do that for the CSS box model. [00:16:27] Francois: And the IE6 was following that. And then the group decided to change, the box model and suddenly IE6 was no longer compliant. And that created a, a huge mess on the, in the history of, uh, of the web in a way. And so the, we, the, the, the, the candidate recommendation sta uh, stage was introduced following that to try to catch this kind of problems. [00:16:52] Francois: But nowadays, again, we, we switch to another model where it's more live. and so we, you, you'll find a number of specs that are not even at candidate rec level. They are at the, what we call a working draft, and they, they are being implemented, and if all goes well, the standardization process follows the implementation, and then you end up in a situation where you have your candidate rec when the, uh, spec ships. [00:17:18] Francois: a recent example would be a web GPU, for example. It, uh, it has shipped in, uh, in, in Chrome shortly before it transition to a candidate rec. But the, the, the spec was already stable. and now it's shipping uh, in, uh, in different browsers, uh, uh, safari, uh, and uh, and uh, and uh, Firefox. And so that's, uh, and that's a good example of something that follows, uh, things, uh, along pretty well. But then you have other specs such as, uh, in the media space, uh, request video frame back, uh, frame, call back, uh, requestVideoFrameCallback() is a short API that allows you to get, you know, a call back whenever the, the browser renders a video frame, essentially. [00:18:01] Francois: And that spec is implemented across browsers. But from a W3C specific, perspective, it does not even exist. It's not on the standardization track. It's still being incubated in what we call a community group, which is, you know, some something that, uh, usually exists before. we move to the, the standardization process. [00:18:21] Francois: So there, there are examples of things where some things fell through the cracks. All the standardization process, uh, is either too early or too late and things that are in spec are not exactly what what got implemented or implementations are too early in the process. We we're doing a better job, at, Not falling into a trap where someone ships, uh, you know, an implementation and then suddenly everything is frozen. You can no longer, change it because it's too late, it shipped. we've tried, different, path there. Um, mentioned CSS, the, there was this kind of vendor prefixed, uh, properties that used to be, uh, the way, uh, browsers were deploying new features without, you know, taking the final name. [00:19:06] Francois: We are trying also to move away from it because same thing. Then in the end, you end up with, uh, applications that have, uh, to duplicate all the properties, the CSS properties in the style sheets with, uh, the vendor prefixes and nuances in the, in what it does in, in the end. [00:19:23] Jeremy: Yeah, I, I think, is that in CSS where you'll see --mozilla or things like that? Why requestVideoFrameCallback doesn't have a formal specification [00:19:30] Jeremy: The example of the request video frame callback. I, I wonder if you have an opinion or, or, or know why that ended up the way it did, where the browsers all implemented it, even though it was still in the incubation stage. [00:19:49] Francois: On this one, I don't have a particular, uh, insights on whether there was a, you know, a strong reason to implement it,without doing the standardization work. [00:19:58] Francois: I mean, there are, it's not, uh, an IPR (Intellectual Property Rights) issue. It's not, uh, something that, uh, I don't think the, the, the spec triggers, uh, you know, problems that, uh, would be controversial or whatever. [00:20:10] Francois: Uh, so it's just a matter of, uh, there was no one's priority, and in the end, you end up with a, everyone's happy. it's, it has shipped. And so now doing the spec work is a bit,why spend time on something that's already shipped and so on, but the, it may still come back at some point with try to, you know, improve the situation. [00:20:26] Jeremy: Yeah, that's, that's interesting. It's a little counterintuitive because it sounds like you have the, the working group and it, it sounds like perhaps the companies or organizations involved, they maybe agreed on how it should work, and maybe that agreement almost made it so that they felt like they didn't need to move forward with the specification because they came to consensus even before going through that. [00:20:53] Francois: In this particular case, it's probably because it's really, again, it's a small, spec. It's just one function call, you know? I mean, they will definitely want a working group, uh, for larger specifications. by the way, actually now I know re request video frame call back. It's because the, the, the final goal now that it's, uh, shipped, is to merge it into, uh, HTML, uh, the HTML spec. [00:21:17] Francois: So there's a, there's an ongoing issue on the, the WHATWG side to integrate request video frame callback. And it's taking some time but see, it's, it's being, it, it caught up and, uh, someone is doing the, the work to, to do it. I had forgotten about this one. Um, [00:21:33] Jeremy: Tension from specification review (horizontal review) [00:21:33] Francois: so with larger specifications, organizations will want this kind of IPR regime they will want commit commitments from, uh, others, on the scope, on the process, on everything. So they will want, uh, a larger, a, a more formal setting, because that's part of how you ensure that things, uh, will get done properly. [00:21:53] Francois: I didn't mention it, but, uh, something we're really, uh, Pushy on, uh, W3C I mentioned we have principles, we have priorities, and we have, uh, specific several, uh, properties at W3C. And one of them is that we we're very strong on horizontal reviews of our specs. We really want them to be reviewed from an accessibility perspective, from an internationalization perspective, from a privacy and security, uh, perspective, and, and, and a technical architecture perspective as well. [00:22:23] Francois: And that's, these reviews are part of the formal process. So you, all specs need to undergo these reviews. And from time to time, that creates tension. Uh, from time to time. It just works, you know. Goes without problem. a recurring issue is that, privacy and security are hard. I mean, it's not an easy problem, something that can be, uh, solved, uh, easily. [00:22:48] Francois: Uh, so there's a, an ongoing tension and no easy way to resolve it, but there's an ongoing tension between, specifying powerful APIs and preserving privacy without meaning, not exposing too much information to applications in the media space. You can think of the media capabilities, API. So the media space is a complicated space. [00:23:13] Francois: Space because of codecs. codecs are typically not relative free. and so browsers decide which codecs they're going to support, which audio and video codecs they, they're going to support and doing that, that creates additional fragmentation, not in the sense that they're not interoperable, but in the sense that applications need to choose which connect they're going to ship to stream to the end user. [00:23:39] Francois: And, uh, it's all the more complicated that some codecs are going to be hardware supported. So you will have a hardware decoder in your, in your, in your laptop or smartphone. And so that's going to be efficient to decode some, uh, some stream, whereas some code are not, are going to be software, based, supported. [00:23:56] Francois: Uh, and that may consume a lot of CPU and a lot of power and a lot of energy in the end. So you, you want to avoid that if you can, uh, select another thing. Even more complex than, codecs have different profiles, uh, lower end profiles higher end profiles with different capabilities, different features, uh, depending on whether you're going to use this or that color space, for example, this or that resolution, whatever. [00:24:22] Francois: And so you want to surface that to web applications because otherwise, they can't. Select, they can't choose, the right codec and the right, stream that they're going to send to the, uh, client devices. And so they're not going to provide an efficient user experience first, and even a sustainable one in terms of energy because they, they're going to waste energy if they don't send the right stream. [00:24:45] Francois: So you want to surface that to application. That's what the media, media capabilities, APIs, provides. Privacy concerns [00:24:51] Francois: Uh, but at the same time, if you expose that information, you end up with ways to fingerprint the end user's device. And that in turn is often used to track users across, across sites, which is exactly what we don't want to have, uh, for privacy reasons, for obvious privacy reasons. [00:25:09] Francois: So you have to balance that and find ways to, uh, you know, to expose. Capabilities without, without necessarily exposing them too much. Uh, [00:25:21] Jeremy: Can you give an example of how some of those discussions went? Like within the working group? Who are the companies or who are the organizations that are arguing for We shouldn't have this capability because of the privacy concerns, or [00:25:40] Francois: In a way all of the companies, have a vision of, uh, of privacy. I mean, the, you will have a hard time finding, you know, members saying, I don't care about privacy. I just want the feature. Uh, they all have privacy in mind, but they may have a different approach to privacy. [00:25:57] Francois: so if you take, uh, let's say, uh, apple and Google would be the, the, I guess the perfect examples in that, uh, in that space, uh, Google will have a, an approach that is more open-ended thing. The, the user agents has this, uh, should check what the, the, uh, given site is doing. And then if it goes beyond, you know, some kind of threshold, they're going to say, well, okay, well, we'll stop exposing data to that, to that, uh, to that site. [00:26:25] Francois: So that application. So monitor and react in a way. apple has a more, uh, you know, has a stricter view on, uh, on privacy, let's say. And they will say, no, we, the, the, the feature must not exist in the first place. Or, but that's, I mean, I guess, um, it's not always that extreme. And, uh, from time to time it's the opposite. [00:26:45] Francois: You will have, uh, you know, apple arguing in one way, uh, which is more open-ended than the, uh, than, uh, than Google, for example. And they are not the only ones. So in working groups, uh, you will find the, usually the implementers. Uh, so when we talk about APIs that get implemented in browsers, you want the core browsers to be involved. [00:27:04] Francois: Uh, otherwise it's usually not a good sign for, uh, the success of the, uh, of the technology. So in practice, that means Apple, uh, Microsoft, Mozilla which one did I forget? [00:27:15] Jeremy: Google. [00:27:16] Francois: I forgot Google. Of course. Thank you. that's, uh, that the, the core, uh, list of participants you want to have in any, uh, group that develops web standards targeted at web browsers. Who participates in working groups and how much power do they have? [00:27:28] Francois: And then on top of that, you want, organizations and people who are directly going to use it, either because they, well the content providers. So in media, for example, if you look at the media working group, you'll see, uh, so browser vendors, the ones I mentioned, uh, content providers such as the BBC or Netflix. [00:27:46] Francois: Chip set vendors would, uh, would be there as well. Intel, uh, Nvidia again, because you know, there's a hardware decoding in there and encoding. So media is, touches on, on, uh, on hardware, uh, device manufacturer in general. You may, uh, I think, uh, I think Sony is involved in the, in the media working group, for example. [00:28:04] Francois: and these companies are usually less active in the spec development. It depends on the groups, but they're usually less active because the ones developing the specs are usually the browser again, because as I mentioned, we develop the specs in parallel to browsers implementing it. So they have the. [00:28:21] Francois: The feedback on how to formulate the, the algorithms. and so that's this collection of people who are going to discuss first within themselves. W3C pushes for consensual dis decisions. So we hardly take any votes in the working groups, but from time to time, that's not enough. [00:28:41] Francois: And there may be disagreements, but let's say there's agreement in the group, uh, when the spec matches. horizontal review groups will look at the specs. So these are groups I mentioned, accessibility one, uh, privacy, internationalization. And these groups, usually the participants are, it depends. [00:29:00] Francois: It can be anything. It can be, uh, the same companies. It can be, but usually different people from the same companies. But it the, maybe organizations with a that come from very, a very different angle. And that's a good thing because that means the, you know, you enlarge the, the perspectives on your, uh, on the, on the technology. [00:29:19] Francois: and you, that's when you have a discussion between groups, that takes place. And from time to time it goes well from time to time. Again, it can trigger issues that are hard to solve. and the W3C has a, an escalation process in case, uh, you know, in case things degenerate. Uh, starting with, uh, the notion of formal objection. [00:29:42] Jeremy: It makes sense that you would have the, the browser. Vendors and you have all the different companies that would use that browser. All the different horizontal groups like you mentioned, the internationalization, accessibility. I would imagine that you were talking about consensus and there are certain groups or certain companies that maybe have more say or more sway. [00:30:09] Jeremy: For example, if you're a browser, manufacturer, your Google. I'm kind of curious how that works out within the working group. [00:30:15] Francois: Yes, it's, I guess I would be lying if I were saying that, uh, you know, all companies are strictly equal in a, in a, in a group. they are from a process perspective, I mentioned, you know, different membership fees with were design, special specific ethos so that no one could say, I'm, I'm putting in a lot of money, so you, you need to re you need to respect me, uh, and you need to follow what I, what I want to, what I want to do. [00:30:41] Francois: at the same time, if you take a company like, uh, like Google for example, they send, hundreds of engineers to do standardization work. That's absolutely fantastic because that means work progresses and it's, uh, extremely smart people. So that's, uh, that's really a pleasure to work with, uh, with these, uh, people. [00:30:58] Francois: But you need to take a step back and say, well, the problem is. Defacto that gives them more power just by virtue of, uh, injecting more resources into it. So having always someone who can respond to an issue, having always someone, uh, editing a spec defacto that give them more, uh, um, more say on the, on the directions that, get forward. [00:31:22] Francois: And on top of that, of course, they have the, uh, I guess not surprisingly, the, the browser that is, uh, used the most, currently, on the market so there's a little bit of a, the, the, we, we, we, we try very hard to make sure that, uh, things are balanced. it's not a perfect world. [00:31:38] Francois: the the role of the team. I mean, I didn't talk about the role of the team, but part of it is to make sure that. Again, all perspectives are represented and that there's not, such a, such big imbalance that, uh, that something is wrong and that we really need to look into it. so making sure that anyone, if they have something to say, make making sure that they are heard by the rest of the group and not dismissed. [00:32:05] Francois: That usually goes well. There's no problem with that. And again, the escalation process I mentioned here doesn't make any, uh, it doesn't make any difference between, uh, a small player, a large player, a big player, and we have small companies raising formal objections against some of our aspects that happens, uh, all large ones. [00:32:24] Francois: But, uh, that happens too. There's no magical solution, I guess you can tell it by the way. I, uh, I don't know how to formulate the, the process more. It's a human process, and that's very important that it remains a human process as well. [00:32:41] Jeremy: I suppose the role of, of staff and someone in your position, for example, is to try and ensure that these different groups are, are heard and it isn't just one group taking control of it. [00:32:55] Francois: That's part of the role, again, is to make sure that, uh, the, the process is followed. So the, I, I mean, I don't want to give the impression that the process controls everything in the groups. I mean, the, the, the groups are bound by the process, but the process is there to catch problems when they arise. [00:33:14] Francois: most of the time there are no problems. It's just, you know, again, participants talking to each other, talking with the rest of the community. Most of the work happens in public nowadays, in any case. So the groups work in public essentially through asynchronous, uh, discussions on GitHub repositories. [00:33:32] Francois: There are contributions from, you know, non group participants and everything goes well. And so the process doesn't kick in. You just never say, eh, no, you didn't respect the process there. You, you closed the issue. You shouldn't have a, it's pretty rare that you have to do that. Uh, things just proceed naturally because they all, everyone understands where they are, why, what they're doing, and why they're doing it. [00:33:55] Francois: we still have a role, I guess in the, in the sense that from time to time that doesn't work and you have to intervene and you have to make sure that,the, uh, exception is caught and, uh, and processed, uh, in the right way. Discussions are public on github [00:34:10] Jeremy: And you said this process is asynchronous in public, so it sounds like someone, I, I mean, is this in GitHub issues or how, how would somebody go and, and see what the results of [00:34:22] Francois: Yes, there, there are basically a gazillion of, uh, GitHub repositories under the, uh, W3C, uh, organization on GitHub. Most groups are using GitHub. I mean, there's no, it's not mandatory. We don't manage any, uh, any tooling. But the factors that most, we, we've been transitioning to GitHub, uh, for a number of years already. [00:34:45] Francois: Uh, so that's where the work most of the work happens, through issues, through pool requests. Uh, that's where. people can go and raise issues against specifications. Uh, we usually, uh, also some from time to time get feedback from developers and countering, uh, a bug in a particular implementations, which we try to gently redirect to, uh, the actual bug trackers because we're not responsible for the respons implementations of the specs unless the spec is not clear. [00:35:14] Francois: We are responsible for the spec itself, making sure that the spec is clear and that implementers well, understand how they should implement something. Why the W3C doesn't specify a video or audio codec [00:35:25] Jeremy: I can see how people would make that mistake because they, they see it's the feature, but that's not the responsibility of the, the W3C to implement any of the specifications. Something you had mentioned there's the issue of intellectual property rights and how when you have a recommendation, you require the different organizations involved to make their patents available to use freely. [00:35:54] Jeremy: I wonder why there was never any kind of, recommendation for audio or video codecs in browsers since you have certain ones that are considered royalty free. But, I believe that's never been specified. [00:36:11] Francois: At W3C you mean? Yes. we, we've tried, I mean, it's not for lack of trying. Um, uh, we've had a number of discussions with, uh, various stakeholders saying, Hey, we, we really need, an audio or video code for our, for the web. the, uh, png PNG is an example of a, um, an image format which got standardized at W3C and it got standardized at W3C similar reasons. There had to be a royalty free image format for the web, and there was none at the time. of course, nowadays, uh, jpeg, uh, and gif or gif, whatever you call it, are well, you know, no problem with them. But, uh, um, that at the time P PNG was really, uh, meant to address this issue and it worked for PNG for audio and video. [00:37:01] Francois: We haven't managed to secure, commitments by stakeholders. So willingness to do it, so it's not, it's not lack of willingness. We would've loved to, uh, get, uh, a royalty free, uh, audio codec, a royalty free video codec again, audio and video code are extremely complicated because of this. [00:37:20] Francois: not only because of patterns, but also because of the entire business ecosystem that exists around them for good reasons. You, in order for a, a codec to be supported, deployed, effective, it really needs, uh, it needs to mature a lot. It needs to, be, uh, added to at a hardware level, to a number of devices, capturing devices, but also, um, uh, uh, of course players. [00:37:46] Francois: And that takes a hell of a lot of time and that's why you also enter a number of business considerations with business contracts between entities. so I'm personally, on a personal level, I'm, I'm pleased to see, for example, the Alliance for Open Media working on, uh, uh, AV1, uh, which is. At least they, uh, they wanted to be royalty free and they've been adopting actually the W3C patent policy to do this work. [00:38:11] Francois: So, uh, we're pleased to see that, you know, they've been adopting the same process and same thing. AV1 is not yet at the same, support stage, as other, codecs, in the world Yeah, I mean in devices. There's an open question as what, what are we going to do, uh, in the future uh, with that, it's, it's, it's doubtful that, uh, the W3C will be able to work on a, on a royalty free audio, codec or royalty free video codec itself because, uh, probably it's too late now in any case. [00:38:43] Francois: but It's one of these angles in the, in the web platform where we wish we had the, uh, the technology available for, for free. And, uh, it's not exactly, uh, how things work in practice.I mean, the way codecs are developed remains really patent oriented. [00:38:57] Francois: and you will find more codecs being developed. and that's where geopolitics can even enter the, the, uh, the play. Because, uh, if you go to China, you will find new codecs emerging, uh, that get developed within China also, because, the other codecs come mostly from the US so it's a bit of a problem and so on. [00:39:17] Francois: I'm not going to enter details and uh, I would probably say stupid things in any case. Uh, but that, uh, so we continue to see, uh, emerging codecs that are not royalty free, and it's probably going to remain the case for a number of years. unfortunately, unfortunately, from a W3C perspective and my perspective of course. [00:39:38] Jeremy: There's always these new, formats coming out and the, rate at which they get supported in the browser, even on a per browser basis is, is very, there can be a long time between, for example, WebP being released and a browser supporting it. So, seems like maybe we're gonna be in that situation for a while where the codecs will come out and maybe the browsers will support them. Maybe they won't, but the, the timeline is very uncertain. Digital Rights Management (DRM) and Media Source Extensions [00:40:08] Jeremy: Something you had, mentioned, maybe this was in your, email to me earlier, but you had mentioned that some of these specifications, there's, there's business considerations like with, digital rights management and, media source extensions. I wonder if you could talk a little bit about maybe what media source extensions is and encrypted media extensions and, and what the, the considerations or challenges are there. [00:40:33] Francois: I'm going to go very, very quickly over the history of a, video and audio support on the web. Initially it was supported through plugins. you are maybe too young to, remember that. But, uh, we had extensions, added to, uh, a realplayer. [00:40:46] Francois: This kind of things flash as well, uh, supporting, uh, uh, videos, in web pages, but it was not provided by the web browsers themselves. Uh, then HTML5 changed the, the situation. Adding these new tags, audio and video, but that these tags on this, by default, support, uh, you give them a resources, a resource, like an image as it's an audio or a video file. [00:41:10] Francois: They're going to download this, uh, uh, video file or audio file, and they're going to play it. That works well. But as soon as you want to do any kind of real streaming, files are too large and to stream, to, to get, you know, to get just a single fetch on, uh, on them. So you really want to stream them chunk by chunk, and you want to adapt the resolution at which you send the stream based on real time conditions of the user's network. [00:41:37] Francois: If there's plenty of bandwidth you want to send the user, the highest possible resolution. If there's a, some kind of hiccup temporary in the, in the network, you really want to lower the resolution, and that's called adaptive streaming. And to get adaptive streaming on the web, well, there are a number of protocols that exist. [00:41:54] Francois: Same thing. Some many of them are proprietary and actually they remain proprietary, uh, to some extent. and, uh, some of them are over http and they are the ones that are primarily used in, uh, in web contexts. So DASH comes to mind, DASH for Dynamic Adaptive streaming over http. HLS is another one. Uh, initially developed by Apple, I believe, and it's, uh, HTTP live streaming probably. Exactly. And, so there are different protocols that you can, uh, you can use. Uh, so the goal was not to standardize these protocols because again, there were some proprietary aspects to them. And, uh, same thing as with codecs. [00:42:32] Francois: There was no, well, at least people wanted to have the, uh, flexibility to tweak parameters, adaptive streaming parameters the way they wanted for different scenarios. You may want to tweak the parameters differently. So they, they needed to be more flexibility on top of protocols not being truly available for use directly and for implementation directly in browsers. [00:42:53] Francois: It was also about providing applications with, uh, the flexibility they would need to tweak parameters. So media source extensions comes into play for exactly that. Media source extensions is really about you. The application fetches chunks of its audio and video stream the way it wants, and with the parameters it wants, and it adjusts whatever it wants. [00:43:15] Francois: And then it feeds that into the, uh, video or audio tag. and the browser takes care of the rest. So it's really about, doing, you know, the adaptive streaming. let applications do it, and then, uh, let the user agent, uh, the browser takes, take care of the rendering itself. That's media source extensions. [00:43:32] Francois: Initially it was pushed by, uh, Netflix. They were not the only ones of course, but there, there was a, a ma, a major, uh, proponent of this, uh, technical solution, because they wanted, uh, they, uh, they were, expanding all over the world, uh, with, uh, plenty of native, applications on all sorts of, uh, of, uh, devices. [00:43:52] Francois: And they wanted to have a way to stream content on the web as well. both for both, I guess, to expand to, um, a new, um, ecosystem, the web, uh, providing new opportunities, let's say. But at the same time also to have a fallback, in case they, because for native support on different platforms, they sometimes had to enter business agreements with, uh, you know, the hardware manufacturers, the whatever, the, uh, service provider or whatever. [00:44:19] Francois: and so that was a way to have a full back. That kind of work is more open, in case, uh, things take some time and so on. So, and they probably had other reasons. I mean, I'm not, I can't speak on behalf of Netflix, uh, on others, but they were not the only ones of course, uh, supporting this, uh, me, uh, media source extension, uh, uh, specification. [00:44:42] Francois: and that went kind of, well, I think it was creating 2011. I mean, the, the work started in 2011 and the recommendation was published in 2016, which is not too bad from a standardization perspective. It means only five years, you know, it's a very short amount of time. Encrypted Media Extensions [00:44:59] Francois: At the same time, and in parallel and complement to the media source extension specifications, uh, there was work on the encrypted media extensions, and here it was pushed by the same proponent in a way because they wanted to get premium content on the web. [00:45:14] Francois: And by premium content, you think of movies and, uh. These kind of beasts. And the problem with the, I guess the basic issue with, uh, digital asset such as movies, is that they cost hundreds of millions to produce. I mean, some cost less of course. And yet it's super easy to copy them if you have a access to the digital, uh, file. [00:45:35] Francois: You just copy and, uh, and that's it. Piracy uh, is super easy, uh, to achieve. It's illegal of course, but it's super easy to do. And so that's where the different legislations come into play with digital right management. Then the fact is most countries allow system that, can encrypt content and, uh, through what we call DRM systems. [00:45:59] Francois: so content providers, uh, the, the ones that have movies, so the studios here more, more and more, and Netflix is one, uh, one of the studios nowadays. Um, but not only, not only them all major studios will, uh, would, uh, push for, wanted to have something that would allow them to stream encrypted content, encrypted audio and video, uh, mostly video, to, uh, to web applications so that, uh, you. [00:46:25] Francois: Provide the movies, otherwise, they, they are just basically saying, and sorry, but, uh, this premium content will never make it to the web because there's no way we're gonna, uh, send it in clear, to, uh, to the end user. So Encrypting media extensions is, uh, is an API that allows to interface with, uh, what's called the content decryption module, CDM, uh, which itself interacts with, uh, the DR DRM systems that, uh, the browser may, may or may not support. [00:46:52] Francois: And so it provides a way for an application to receive encrypted content, pass it over get the, the, the right keys, the right license keys from a whatever system actually. Pass that logic over to the, and to the user agent, which passes, passes it over to, uh, the CDM system, which is kind of black box in, uh, that does its magic to get the right, uh, decryption key and then the, and to decrypt the content that can be rendered. [00:47:21] Francois: The encrypted media extensions triggered a, a hell of a lot of, uh, controversy. because it's DRM and DRM systems, uh, many people, uh, uh, things should be banned, uh, especially on the web because the, the premise of the web is that the, the user has trusts, a user agent. The, the web browser is called the user agent in all our, all our specifications. [00:47:44] Francois: And that's, uh, that's the trust relationship. And then they interact with a, a content provider. And so whatever they do with the content is their, I guess, actually their problem. And DRM introduces a third party, which is, uh, there's, uh, the, the end user no longer has the control on the content. [00:48:03] Francois: It has to rely on something else that, Restricts what it can achieve with the content. So it's, uh, it's not only a trust relationship with its, uh, user agents, it's also with, uh, with something else, which is the content provider, uh, in the end, the one that has the, uh, the license where provides the license. [00:48:22] Francois: And so that's, that triggers, uh, a hell of a lot of, uh, of discussions in the W3C degenerated, uh, uh, into, uh, formal objections being raised against the specification. and that escalated to, to the, I mean, at all leverage it. It's, it's the, the story in, uh, W3C that, um, really, uh, divided the membership into, opposed camps in a way, if you, that's was not only year, it was not really 50 50 in the sense that not just a huge fights, but the, that's, that triggered a hell of a lot of discussions and a lot of, a lot of, uh, of formal objections at the time. [00:49:00] Francois: Uh, we were still, From a governance perspective, interestingly, um, the W3C used to be a dictatorship. It's not how you should formulate it, of course, and I hope it's not going to be public, this podcast. Uh, but the, uh, it was a benevolent dictatorship. You could see it this way in the sense that, uh, the whole process escalated to one single person was, Tim Burners Lee, who had the final say, on when, when none of the other layers, had managed to catch and to resolve, a conflict. [00:49:32] Francois: Uh, that has hardly ever happened in, uh, the history of the W3C, but that happened to the two for EME, for encrypted media extensions. It had to go to the, uh, director level who, uh, after due consideration, uh, decided to, allow the EME to proceed. and that's why we have a, an EME, uh, uh, standard right now, but still re it remains something on the side. [00:49:56] Francois: EME we're still, uh, it's still in the scope of the media working group, for example. but the scope, if you look at the charter of the working group, we try to scope the, the, the, the, the updates we can make to the specification, uh, to make sure that we don't reopen, reopen, uh, a can of worms, because, well, it's really a, a topic that triggers friction for good and bad reasons again. [00:50:20] Jeremy: And when you talk about the media source extensions, that is the ability to write custom code to stream video in whatever way you want. You mentioned, the MPEG-DASH and http live streaming. So in that case, would that be the developer gets to write that code in JavaScript that's executed by the browser? [00:50:43] Francois: Yep, that's, uh, that would be it. and then typically, I guess the approach nowadays is more and more to develop low level APIs into W3C or web in, in general, I guess. And to let, uh. Libraries emerge that are going to make lives of a, a developer, uh, easier. So for MPEG DASH, we have the DASH.js, which does a fantastic job at, uh, at implementing the complexity of, uh, of adaptive streaming. [00:51:13] Francois: And you just, you just hook it into your, your workflow. And that's, uh, and that's it. Encrypted Media Extensions are closed source [00:51:20] Jeremy: And with the encrypted media extensions I'm trying to picture how those work and how they work differently. [00:51:28] Francois: Well, it's because the, the, the, the key architecture is that the, the stream that you, the stream that you may assemble with a media source extensions, for example. 'cause typically they, they're used in collaboration. When you hook the, hook it into the video tag, you also. Call EME and actually the stream goes to EME. [00:51:49] Francois: And when it goes to EME, actually the user agent hands the encrypted stream. You're still encrypted at this time. Uh, encrypted, uh, stream goes to the CDM content decryption module, and that's a black box well, it has some black, black, uh, black box logic. So it's not, uh, even if you look at the chromium source code, for example, you won't see the implementation of the CDM because it's a, it's a black box, so it's not part of the browser se it's a sand, it's sandboxed, it's execution sandbox. [00:52:17] Francois: That's, uh, the, the EME is kind of unique in, in this way where the, the CDM is not allowed to make network requests, for example, again, for privacy reasons. so anyway, the, the CDM box has the logic to decrypt the content and it hands it over, and then it depends, it depends on the level of protection you. [00:52:37] Francois: You need or that the system supports. It can be against software based protection, in which case actually, a highly motivated, uh, uh, uh, attacker could, uh, actually get access to the decoded stream, or it can be more hardware protected, in which case actually the, it goes to the, uh, to your final screen. [00:52:58] Francois: But it goes, it, it goes through the hardware in a, in a mode that the US supports in a mode that even the user agent doesn't have access to it. So it doesn't, it can't even see the pixels that, uh, gets rendered on the screen. There are, uh, several other, uh, APIs that you could use, for example, to take a screenshot of your, of your application and so on. [00:53:16] Francois: And you cannot apply them to, uh, such content because they're just gonna return a black box. again, because the user agent itself does not see the, uh, the pixels, which is exactly what you want with encrypted content. [00:53:29] Jeremy: And the, the content decryption module, it's, if I understand correctly, it's something that's shipped with the browsers, but you were saying is if you were to look at the public source code of Chromium or of Firefox, you would not see that implementation. Content Decryption Module (Widevine, PlayReady) [00:53:47] Francois: True. I mean, the, the, um, the typical examples are, uh, uh, widevine, so wide Vine. So interestingly, uh, speaking in theory, these, uh, systems could have been provided by anyone in practice. They've been provided by the browser vendors themselves. So Google has Wide Vine. Uh, Microsoft has something called PlayReady. Apple uh, the name, uh, escapes my, uh, sorry. They don't have it on top of my mind. So they, that's basically what they support. So they, they also own that code, but in a way they don't have to. And Firefox actually, uh, they, uh, don't, don't remember which one, they support among these three. but, uh, they, they don't own that code typically. [00:54:29] Francois: They provide a wrapper around, around it. Yeah, that's, that's exactly the, the crux of the, uh, issue that, people have with, uh, with DRMs, right? It's, uh, the fact that, uh, suddenly you have a bit of code running there that is, uh, that, okay, you can send box, but, uh, you cannot inspect and you don't have, uh, access to its, uh, source code. [00:54:52] Jeremy: That's interesting. So the, almost the entire browser is open source, but if you wanna watch a Netflix movie for example, then you, you need to, run this, this CDM, in addition to just the browser code. I, I think, you know, we've kind of covered a lot. Documenting what's available in browsers for developers [00:55:13] Jeremy: I wonder if there's any other examples or anything else you thought would be important to mention in, in the context of the W3C. [00:55:23] Francois: There, there's one thing which, uh, relates to, uh, activities I'm doing also at W3C. Um. Here, we've been talking a lot about, uh, standards and, implementations in browsers, but there's also, uh, adoption of these browser, of these technology standards by developers in general and making sure that developers are aware of what exists, making sure that they understand what exists and one of the, key pain points that people, uh. [00:55:54] Francois: Uh, keep raising on, uh, the web platform is first. Well, the, the, the web platform is unique in the sense that there are different implementations. I mean, if you, [00:56:03] Francois: Uh, anyway, there are different, uh, context, different run times where there, there's just one provided by the company that owns the, uh, the, the, the system. The web platform is implemented by different, uh, organizations. and so you end up the system where no one, there's what's in the specs is not necessarily supported. [00:56:22] Francois: And of course, MDN tries, uh, to document what's what's supported, uh, thoroughly. But for MDN to work, there's a hell of a lot of needs for data that, tracks browser support. And this, uh, this data is typically in a project called the Browser Compat Data, BCD owned by, uh, MDN as well. But, the Open Web Docs collective is a, uh, is, uh, the one, maintaining that, uh, that data under the hoods. [00:56:50] Francois: anyway, all of that to say that, uh, to make sure that, we track things beyond work on technical specifications, because if you look at it from W3C perspective, life ends when the spec reaches standards, uh, you know, candidate rec or rec, you could just say, oh, done with my work. but that's not how things work. [00:57:10] Francois: There's always, you need the feedback loop and, in order to make sure that developers get the information and can provide the, the feedback that standardization can benefit from and browser vendors can benefit from. We've been working on a project called web Features with browser vendors mainly, and, uh, a few of the folks and MDN and can I use and different, uh, different people, to catalog, the web in terms of features that speak to developers and from that catalog. [00:57:40] Francois: So it's a set of, uh, it's a set of, uh, feature IDs with a feature name and feature description that say, you know, this is how developers would, uh, understand, uh, instead of going too fine grained in terms of, uh, there's this one function call that does this because that's where you, the, the kind of support data you may get from browser data and MDN initially, and having some kind of a coarser grained, uh, structure that says these are the, features that make sense. [00:58:09] Francois: They talk to developers. That's what developers talk about, and that's the info. So the, we need to have data on these particular features because that's how developers are going approach the specs. Uh. and from that we've derived the notion of baseline badges that you have, uh, are now, uh, shown on MDN on can I use and integrated in, uh, IDE tool, IDE Tools such as visual, visual studio, and, uh, uh, libraries, uh, linked, some linters have started to, um, to integrate that data. [00:58:41] Francois: Uh, so, the way it works is, uh, we've been mapping these coarser grained features to BCDs finer grained support data, and from there we've been deriving a kind of a, a batch that says, yeah, this, this feature is implemented well, has limited availability because it's only implemented in one or two browsers, for example. [00:59:07] Francois: It's, newly available because. It was implemented. It's been, it's implemented across the main browser vendor, um, across the main browsers that people use. But it's recent, and widely available, which we try to, uh, well, there's been lots of discussion in the, in the group to, uh, come up with a definition which essentially ends up being 30 months after, a feature become, became newly available. [00:59:34] Francois: And that's when, that's the time it takes for the, for the versions of the, the different versions of the browser to propagate. Uh, because you, it's not because there's a new version of a, of a browser that, uh, people just, Ima immediately, uh, get it. So it takes a while, to propagate, uh, across the, uh, the, the user, uh, user base. [00:59:56] Francois: And so the, the goal is to have a, a, a signal that. Developers can rely on saying, okay, well it's widely available so I can really use that feature. And of course, if that doesn't work, then we need to know about it. And so we are also working with, uh, people doing so developer surveys such as state of, uh, CSS, state of HTML, state of JavaScript. [01:00:15] Francois: That's I guess, the main ones. But also we are also running, uh, MDN short surveys with the MDN people to gather feedback on. On the, on these same features, and to feed the loop and to, uh, to complete the loop. and these data is also used by, internally, by browser vendors to inform, prioritization process, their prioritization process, and typically as part of the interop project that they're also running, uh, on the site [01:00:43] Francois: So a, a number of different, I've mentioned, uh, I guess a number of different projects, uh, coming along together. But that's the goal is to create links, across all of these, um, uh, ongoing projects with a view to integrating developers, more, and gathering feedback as early as possible and inform decision. [01:01:04] Francois: We take at the standardization level that can affect the, the lives of the developers and making sure that it's, uh, it affects them in a, in a positive way. [01:01:14] Jeremy: just trying to understand, 'cause you had mentioned that there's the web features and the baseline, and I was, I was trying to picture where developers would actually, um, see these things. And it sounds like from what you're saying is W3C comes up with what stage some of these features are at, and then developers would end up seeing it on MDN or, or some other site. [01:01:37] Francois: So, uh, I'm working on it, but that doesn't mean it's a W3C thing. It's a, it's a, again, it's a, we have different types of group. It's a community group, so it's the Web DX Community group at W3C, which means it's a community owned thing. so that's why I'm mentioning a working with a representative from, and people from MDN people, from open Web docs. [01:02:05] Francois: so that's the first point. The second point is, so it's, indeed this data is now being integrated. If you, and you look, uh, you'll, you'll see it in on top of the MDN pages on most of them. If you look at, uh, any kind of feature, you'll see a, a few logos, uh, a baseline banner. and then can I use, it's the same thing. [01:02:24] Francois: You're going to get a baseline, banner. It's more on, can I use, and it's meant to capture the fact that the feature is widely available or if you may need to pay attention to it. Of course, it's a simplification, and the goal is not to the way it's, the way the messaging is done to developers is meant to capture the fact that, they may want to look, uh, into more than just this, baseline status, because. [01:02:54] Francois: If you take a look at web platform tests, for example, and if you were to base your assessment of whether a feature is supported based on test results, you'll end up saying the web platform has no supported technology because there are absolutely no API that, uh, where browsers pass 100% of the, of the, of the test suite. [01:03:18] Francois: There may be a few of them, I don't know. But, there's a simplification in the, in the process when a feature is, uh, set to be baseline, there may be more things to look at nevertheless, but it's meant to provide a signal that, uh, still developers can rely on their day-to-day, uh, lives. [01:03:36] Francois: if they use the, the feature, let's say, as a reasonably intended and not, uh, using to advance the logic. [01:03:48] Jeremy: I see. Yeah. I'm looking at one of the pages on MDN right now, and I can see at the top there's the, the baseline and it, it mentions that this feature works across many browsers and devices, and then they say how long it's been available. And so that's a way that people at a glance can, can tell, which APIs they can use. [01:04:08] Francois: it also started, uh, out of a desire to summarize this, uh, browser compatibility table that you see at the end of the page of the, the bottom of the page in on MDN. but there are where developers were saying, well, it's, it's fine, but it's, it goes too much into detail. So we don't know in the end, can we, can we use that feature or can we, can we not use that feature? [01:04:28] Francois: So it's meant as a informed summary of, uh, of, of that it relies on the same data again. and more importantly, we're beyond MDN, we're working with tools providers to integrate that as well. So I mentioned the, uh, visual Studio is one of them. So recently they shipped a new version where when you use a feature, you can, you can have some contextual, uh. [01:04:53] Francois: A menu that tells you, yeah, uh, that's fine. You, this CSS property, you can, you can use it, it's widely available or be aware this one is limited Availability only, availability only available in Firefox or, or Chrome or Safari work kit, whatever. [01:05:08] Jeremy: I think that's a good place to wrap it up, if people want to learn more about the work you're doing or learn more about sort of this whole recommendations process, where, where should they head? [01:05:23] Francois: Generally speaking, we're extremely open to, uh, people contributing to the W3C. and where should they go if they, it depends on what they want. So I guess the, the in usually where, how things start for someone getting involved in the W3C is that they have some

In this episode of the Astonishing Healthcare podcast, Tracey Rollins, CPM (Sr. Director, Client Implementations) and Kristen Morgan (Director, Health Plan Implementations) join Justin Venneri in the studio for a discussion about pharmacy benefit implementations and how switching to an aligned, transparent partner can be efficient and a pleasant experience, despite the complexities involved.Tracey and Kristen explain how employers and health plans can prepare for and manage the transition to a new pharmacy benefits partner, emphasizing the role that the PBM should play and the importance of making strategic decisions early in the process to build trust and ensure a seamless implementation. They highlight how the process improves with time and growth, offering more reassurance that clients' needs can be met, recent trends and enhancements to the process (e.g., that larger employers are starting the process earlier than ever and becoming more sophisticated), and the role advanced technology platforms like Judi play in maintaining flexibility and compliance in a rapidly evolving regulatory landscape.Related ContentPharmacy Benefits 101: Successful ImplementationsSigns it is time to change your PBM vendor, and how to overcome common hesitationsReplay: The Future of Health Benefit Design: How Judi® Powers Seamless Care and Better OutcomesWhy Savings Don't Materialize: The Truth About Pharmacy Benefit Procurement eBookFor more information about Capital Rx and this episode, please visit Capital Rx Insights.

In this episode, Craig Jeffery talks with Garry Capers of Deluxe about what really drives successful treasury implementations. They explore the roles of people, process, planning, and change management, going well beyond the technology itself. How can teams ensure smoother go-lives, user adoption, and long-term impact? Listen in for practical insights and leadership-level strategy.  

In this cutting-edge episode, we explore how Edge AI is transforming drug discovery and revolutionising laboratory workflows, real-time molecular analysis, and protein folding predictions—all at the source of data collection. Joining us is Nuri Cankaya, Vice President of Commercial Marketing at Intel Corporation, and a renowned thought leader in AI and healthcare innovation.You'll discover how AI at the edge—enabled by on-device NPUs, GPUs, and CPUs—is unlocking privacy-preserving, high-performance computing in the most sensitive environments, such as clinical labs and pharmaceutical R&D centers. Nuri shares his deep experience in AI, discusses hardware configurations for edge deployments, and provides real-world examples of AI accelerating high-throughput screening, compound discovery, and target validation.Key Topics:What is Edge AI and how it differs from cloud-based AIHow real-time AI in the lab enables faster, cheaper drug discoveryHardware requirements: NPU, GPU, CPU integration for edge computingThe role of AlphaFold and protein folding prediction in therapeutic developmentUse cases in molecular screening, genomics, and clinical trial simulationsHow Edge AI preserves data privacy and complies with GDPR and HIPAAPredictions for AGI (Artificial General Intelligence) and Quantum Computing in healthcareStrategic advice for pharma leaders and biotech innovators looking to pilot AIThe energy efficiency and sustainability gains from Edge AI vs. cloud AIAbout the PodcastAI for Pharma Growth is a podcast focused on exploring how artificial intelligence can revolutionise healthcare by addressing disparities and creating equitable systems. Join us as we unpack groundbreaking technologies, real-world applications, and expert insights to inspire a healthier, more equitable future.This show brings together leading experts and changemakers to demystify AI and show how it's being used to transform healthcare. Whether you're in the medical field, technology sector, or just curious about AI's role in social good, this podcast offers valuable insights.AI For Pharma Growth is the podcast from pioneering Pharma Artificial Intelligence entrepreneur Dr. Andree Bates created to help organisations understand how the use of AI based technologies can easily save them time and grow their brands and business. This show blends deep experience in the sector with demystifying AI for all pharma people, from start up biotech right through to Big Pharma. In this podcast Dr Andree will teach you the tried and true secrets to building a pharma company using AI that anyone can use, at any budget. As the author of many peer-reviewed journals and having addressed over 500 industry conferences across the globe, Dr Andree Bates uses her obsession with all things AI and futuretech to help you to navigate through the, sometimes confusing but, magical world of AI powered tools to grow pharma businesses. This podcast features many experts who have developed powerful AI powered tools that are the secret behind some time saving and supercharged revenue generating business results. Those who share their stories and expertise show how AI can be applied to sales, marketing, production, social media, psychology, customer insights and so much more. Dr. Andree Bates LinkedIn | Facebook | Twitter

From Strategy to Execution — Rob Smith on Unlocking Digital TransformationIn this episode, I sit down with Rob Smith — founder of Fractional Digital, strategic advisor, and fractional CMO — to unpack what digital transformation really means for mid-sized businesses and manufacturers. With a career spanning 3M, global marketing ops, and building four companies of his own, Rob has seen firsthand how companies waste millions chasing tools without a strategy.We cover:Why transformation fails when tech is bought before process and people are alignedThe “two-in-a-box” method to end the sales vs. marketing blame gameHow Ella, his SaaS platform, helps fractional CMOs compress 8 weeks of work into hoursWhy there's no bad technology, only bad implementationThe financial upside of fixing operations before scaling growthHow to align global tech stacks while staying agile in local markets

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   ERP Lessons from the Frontlines of SMB Implementations, Q&A (Darian Chwialkowski, Third Stage Consulting) Why SMBs Should Embrace Bots (Nate Stroeher & Geordie McDougall, Third Stage Consulting) Shocking Reason Tech Projects Fail Every Time   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

In this episode, Harish Chandramowli, Co-founder and CTO of Flaire, explores how AI is transforming the fashion and clothing industry—especially in streamlining operations and improving data management. He highlights the challenges brands face when relying on spreadsheets, and stresses the importance of data integrity for better decision-making. He also emphasizes the need for flexible pricing and the importance of adapting technology to fit each brand's unique workflows in the fashion and clothing industry. Topics discussed in this episode:  Why spreadsheets are secretly killing fashion brands' profitability. How AI is revolutionizing fashion operations. What data integrity mistakes cost fashion brands millions. Why most fashion ERP implementations fail. How to sanitize messy fashion data. What technical flexibility really means. Why pricing strategy determines software adoption. How AI visualizes complex fashion processes. What workflow understanding reveals. Why collaboration beats technology. Links & Resources Website: https://www.Flairesoftware.com/LinkedIn: https://www.linkedin.com/in/scharish/LinkedIn: https://www.linkedin.com/company/Flaire-softwareGet access to more free resources by visiting the show notes athttps://tinyurl.com/3c2b4vj4MORE RESOURCES Subscribe to our FREE Newsletter: https://newsletter.ecommercecoffeebreak.com/ Free Store Optimization Beginners Guide: Instant PDF Download!

In this What's Next with Aki Anastasiou interview, Peter Kerr discusses how retail logistics is being changed by cloud and AI technology. Kerr is the Founder and Director of Argon Supply Chain Solutions and is a 20+ year veteran in logistics and transport planning. Before founding Argon Supply Chain Solutions, Kerr worked at many other prominent companies in South Africa. This includes working as a SAP EWM Solution Architect and Consultant for Pick n Pay, a SAP EWM Consultant for Barloworld, a Mobile Specialist for OneArch Consulting, and a SAP WM Consultant for Pioneer Foods. Kerr is an SAP Certified Associate and Application Professional specialising in SAP solutions such as EWM, TM, SRM, WM, Mobility, and ATTP. He also boasts a strong understanding of data collection technologies and supply chain solution architecture. In this What's Next interview, Kerr explains what Argon Supply Chain Solutions does and how retailers can maximise the potential of SAP S/4HANA Cloud to streamline their operations and improve efficiencies. He unpacks why having SAP Supply Chain as part of the S/4HANA Cloud implementation is essential. Kerr also discusses how SAP improves vendor compliance and creates better retail practices. He concludes the interview by sharing how he sees automation and AI features impacting supply chain solutions.

Iversoft is a Canadian software company that builds custom solutions across industries, and industry executive Matt Strentse sits down with Canadian Manufacturing to talk about some of the misconceptions, pitfalls and opportunities that are possible as manufacturers consider investments during a trade war.

Want to use Atlassian tools but the Premium price is giving you sticker shock? Then, you'll want to join the TJL crew as they welcome Liz Tanner, who has 12 years of independent contracting experience squeezing every drop of performance from the Free Plans!Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!https://www.linkedin.com/company/the-jira-life/Become a member on YouTube to get access to perks:https://www.youtube.com/@thejiralife/joinHosts:- Alex "Dr. Jira" Ortizhttps://www.linkedin.com/in/alexortiz89/https://www.youtube.com/@ApetechTechTutorials- Rodney "The Jira Guy" Nissenhttps://www.linkedin.com/in/rgnissen/https://thejiraguy.com- Sarah Wrighthttps://www.linkedin.com/in/satwright/Producer:- "King Bob" Robert Wenhttps://www.linkedin.com/in/robert-wen-csm-spc6-a552051/Executive Producer: - Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codeshttps://www.youtube.com/c/monstercatOutro: Fractal - Atriumhttps://www.youtube.com/c/monstercatinstinct

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   How AI Tools Bring New Cybersecurity Threats, Q&A (Darian Chwialkowski, Third Stage Consulting) Lessons From Complex ERP Implementations (Walter Kolodziey, WaltKo Services) How ERP Almost Killed Gummy Bears   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

I'm joined by guests Rob Hamilton, Craig Raw & Matt Odell to go through the list.OP_RETURN Drama (00:00:52) Odell's thoughts (00:04:29) Craig's thoughts (00:05:59) NVK's thoughts (00:07:47) Rob's thoughtsBitcoin • Software Releases & Project Updates (00:22:10) COLDCARD (00:22:35) Cove Wallet (00:24:03) BTCPay Server (00:24:06) Nunchuk Android (00:24:12) Bitcoin Keeper (00:24:14) Bitcoin Safe (00:24:18) Wasabi Wallet (00:25:43) RoboSats (00:25:46) Umbrel (00:25:57) Zaprite (00:26:22) Blockstream Satellite (00:26:45) Stratum Work (00:26:58) SeedHammer II (00:27:11) ESP-Miner• Project Spotlight (00:27:34) Bitcoin Feature Matrix (00:27:41) secp256k1lab (00:28:00) GPGap (00:28:16) NVK Validation Tweet (00:28:54) BriberBrother (00:29:11) Stack MathVulnerability Disclosures(00:30:23) CVE-2024-52919(00:33:02) CVE-2025-43707(00:34:46) Hackers breach LockBitAudience Questions (00:35:12) What's the difference between test net and signet? And what are the benefits of each? (00:37:15) Can you explain, in simple terms, what OP_CHECKCONTRACTVERIFY does?Nostr • Software Releases & Project Updates (00:46:55) Nostr Messaging Layer Security (00:48:42) Primal (00:48:43) DamusBoosts (01:01:58) Shoutout to top boosters Rod Palmer, AVERAGE_GARY, pink money, user4, Wartime & btconboardTech Tip of the Day (01:03:51) A free online cryptography course repository by Alfred MenezesLinks & Contacts:Website: https://bitcoin.review/Substack: https://substack.bitcoin.review/Twitter: https://twitter.com/bitcoinreviewhqNVK Twitter: https://twitter.com/nvkTelegram: https://t.me/BitcoinReviewPodEmail: producer@coinkite.comNostr & LN: ⚡nvk@nvk.org (not an email!)Full show notes: https://bitcoin.review/podcast/episode-96

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   Oracle's New Role at the Top of the ERP Throne, Q&A (Darian Chwialkowski, Third Stage Consulting) Lessons From Government ERP Implementations (Ron Puccinelli, City of Menifee) How to Conduct a Digital Transformation at No Cost   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

Marty sits down with Jim Carucci to discuss AI as economic agents.CASCDR: https://cascdr.xyz/Jim Carucci on Nostr: https://primal.net/p/nprofile1qqsy2d24rfqzwxc9n2ujku084dlgwqqxrgkervxjpucna7p0q5htppgeluehw0:00 - Intro0:36 - Lacrosse and manifesting4:38 - Open vs centralized AI8:02 - Fold & Bitkey9:33 - LLMs and their biases13:32 - CASCDR basics17:52 - Unchained18:20 - Bitcoin AI synergy30:34 - Progress of the agentic framework36:08 - Implementations of agents41:41 - Nostr, DVMs, MCP46:52 - Open source vs panopticon51:35 - Ideal picture of future AI1:02:03 - Driving bitcoin adoption1:10:48 - PlugsShoutout to our sponsors:Foldhttps://tftc.io/foldCoinkitehttps://coinkite.comUnchainedhttps://unchained.com/tftc/Join the TFTC Movement:Main YT Channelhttps://www.youtube.com/c/TFTC21/videosClips YT Channelhttps://www.youtube.com/channel/UCUQcW3jxfQfEUS8kqR5pJtQWebsitehttps://tftc.io/Newslettertftc.io/bitcoin-brief/Twitterhttps://twitter.com/tftc21Instagramhttps://www.instagram.com/tftc.io/Nostrhttps://primal.net/tftcFollow Marty Bent:Twitterhttps://twitter.com/martybentNostrhttps://primal.net/martybentNewsletterhttps://tftc.io/martys-bent/Podcasthttps://www.tftc.io/tag/podcasts/

Why do technology projects often miss the mark?Join John Frehse in this episode of The Impact Exchange as he chats with Mirinda Lowe. Mirinda emphasizes the importance of treating technology implementations as business transformations to ensure success. Key elements for a successful technology rollout include:• A compelling reason for the initiative• Clearly defined roles• A strategic roll-out plan that considers organizational impacts

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   A New Autonomous AI Agent, Q&A (Darian Chwialkowski, Third Stage Consulting) Business Process Management in ERP Implementations, (Scott Adams, Victaulic) Why Business Process Standardization Fails in ERP Projects   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

Hong Minhee is an open source developer and the creator of the Fedify ActivityPub server framework. We talk about how applications like Mastodon and Misskey communicate with one another using ActivityPub. This includes discussions on built-in activites, extending the specification in a backwards compatible way, difficulties implementing JSON-LD, the inbox model, and his experience implementing the specification. Hong Minhee: activitypub profile fedify hollo Specifications: ActivityPub W3C specification JSON Linked Data Resource Description Framework W3C Semantic Web Standards ActivityPub and WebFinger ActivityPub and HTTP Signatures ActivityPub implementations: Mastodon Misskey Akkoma Pleroma Pixelfed Lemmy Loops GoToSocial ActivityPub support in Ghost Threads has entered the Fediverse ActivityPub tools: ActivityPub Academy BrowserPub fedify CLI -- Transcript You can help correct transcripts on GitHub. What's ActivityPub? [00:00:00] Jeremy: Today, I'm talking to Hong Minhee. He is the developer of Fedify. A TypeScript library for building ActivityPub server applications. The first thing I think we should start with is defining ActivityPub. what is ActivityPub? [00:00:16] Hong: ActivityPub is the protocol that lets social networks talk to each other and it's officially recommended by W3C. It's what powers this thing we call the Fediverse which is basically a way for different social media platforms to work together. Users of ActivityPub [00:00:39] Jeremy: Can you give some examples that people might have heard of -- either users of ActivityPub or things that are a part of this fediverse? [00:00:50] Hong: Mastodon is probably the biggest one out there. And you know what's interesting? Meta threads has actually started implementing ActivityPub this summer. So this still pretty much a one way street right now. In East Asia, especially Japan, there's this really popular microblogging platform called misskey. It's got so many forks that people actually joke around and called them forkeys. but it's not just about Twitter style microblogging, there's Pixelfed which is kind of like Instagram, but for the fediverse. And those same folks recently launched loops. Which is basically doing what TikTok does, but in the Fediverse. Then you've got stuff like Lemmy and which are doing the reddit thing up in the Fediverse. [00:02:00] Jeremy: Oh like Reddit. [00:02:01] Hong: Yeah. There are so much more out there that I haven't even mentioned. Um, most of it is open source, which is pretty cool. [00:02:13] Jeremy: So the first few examples you gave, Mastodon and Meta's threads, they're very similar to, to Twitter, right? So that's what you were calling the, the Microblogging applications. And I think what you had said, which is a little bit interesting is you had said Metas threads is only one way. So could you kind of describe like what you mean by that? [00:02:37] Hong: Currently meta threads only can be followed by other ActivityPub applications but you cannot follow other people in the fediverse. [00:02:55] Jeremy: People who are using another Microblogging platform like Mastodon can follow someone on Meta's Threads platform. But the other way is not true. If you're on threads, you can't follow someone on Mastodon. [00:03:07] Hong: Yes, that's right. [00:03:09] Jeremy: And that's not a limitation of the protocol itself. That's a design decision or a decision made by Meta. [00:03:17] Hong: Yeah. They are slowly implementing ActivityPub and I hope they will implement complete ActivityPub in the future. Interoperability through Activities [00:03:27] Jeremy: And then the other examples you gave, one is I believe it was Pixel Fed is very similar to Instagram. And then the last examples you gave was I think it was Lemmy, you said it's similar to Reddit. Because you mentioned the term Fediverse before and you mentioned that these all use ActivityPub and since these seem like different kinds of applications, what does it mean for them to interact? Because with Mastodon and Threads I can kind of understand because they're both similar to Twitter. So you're posting messages and replying, but, but what does it mean, for example, for someone on Mastodon to interact with someone on Lemmy which is like Reddit because they seem very different. [00:04:16] Hong: People in Lemmy and Mastodon are called actors and can follow each other. They have interactions between them called activities. And there are several types of activities like, create and follow and undo, like, and so on. So, ActivityPub applications tend to, use these vocabulary to implement their features. So, for example, Lemmy uses like activities for upvoting and like activities for down voting and it's translated to likes in Mastodon. So if you submit a post on Lemmy and it shows up on your Mastodon timeline. If you like that post (it) is upvoting in Lemmy. [00:05:36] Jeremy: And probably similarly with Pixelfed, which you said is like Instagram, if you follow someone's Pixelfed account in Mastodon and they post a photo in Pixel Fed, they would see it as a post in Mastodon natively and they could give it a like there. Adding activities or properties [00:05:56] Jeremy: And these activities that you mentioned -- So the like and the dislike are those part of ActivityPub itself? [00:06:05] Hong: Yes, and this vocabulary can be extended. [00:06:10] Jeremy: So you can add, additional actions (activities) or are you adding information (properties) to the existing actions? [00:06:37] Hong: It is called activity vocabulary, and there are, things like accept, add, arrive, block, create lead, dislike, flag, follow, ignore invite, join, and so on. So, basically, almost everything you need to build social media is already there in the vocabulary, but if you want to extend some more, you can define your, own vocabulary. [00:06:56] Jeremy: Most of the things that an Instagram or a Twitter, or a Reddit would need is already there. But you're saying that you can have your own vocabulary. So if there's an action or an activity that is not covered by the specification, you can create one yourself. [00:07:13] Hong: Yes. For example, Misskey and Pleroma defined emoji reactor to represent emoji reactions. [00:07:25] Jeremy: Because the systems can extend the vocabulary. What are some other examples of cases where mastodon or any other of these systems has found that the existing vocabulary is not enough. What are some other examples of applications extending it? [00:07:45] Hong: For example, uh, mastodon defined suspended -- suspended property. They are not activities, but they are properties in the activity. ActivityPub consists of several types of objects and there are activities and normal objects like, article. they can have properties and there are several existing properties, but they can be also extended. So Mastodon extended some properties they need. So for example, they define suspended or discoverable. [00:08:44] Hong: Suspended for to tell if an actor is suspended by moderators. Discoverable tells if an actor itself wants to be, searched and indexed, and there are much more properties. Mastodon extended. Actors [00:09:12] Jeremy: And these are, these are properties of the actor. These are properties of the user? [00:09:19] Hong: Yes. Actors. [00:09:21] Jeremy: Cause I think earlier you mentioned that. The concept of a user is an actor, and it sounds like what you're saying is an actor can have all these properties. There's probably a, a username and things like that, but Mastodon has extended the properties so that, you can have a property on whether you wanna be searched or indexed you can have a property that says you're suspended. So I guess your account, is still there, but can't be used anymore. Something we should probably talk about then is, so you have these actors, you have these activities that I'm assuming the actors are performing on one another. What does that data look like and what does the communication look like? [00:10:09] Hong: Actors have their own dereferencable URI and when you look up that URI you get all the info about the actor in JSON-LD format [00:10:22] Jeremy: JSON-LD? [00:10:23] Hong: Yeah. JSON-LD. linked data. (The) Actor has all the stuff you expect to find on a social account name, bio URL to the profile page, profile picture, head image and more. And there are five main types of actors: application, group, organization, person and service. And you know how sometimes on Mastodon you will see an account marked as a bot? [00:10:58] Jeremy: A bot? [00:10:59] Hong: Yeah. Bot and that's what an actor of type service looks like. And the ActivityPub spec actually let you create other types beyond these five. But I haven't seen anyone actually do that yet. JSON-LD [00:11:15] Jeremy: And you mentioned that these are all JSON objects. but the LD part, the linked data part, I'm not familiar with. So what different about the linked data part of the JSON? [00:11:31] Hong: So JSON-LD is the special way of writing RDF. Which was originally used in the semantic web. Usually RDF uses (a) format (that) is called triples. [00:11:48] Jeremy: Triples? [00:11:49] Hong: Yeah, subject and predicate and object. [00:11:55] Jeremy: Subject, predicate, object. Can you give an example of what those three would be? [00:12:00] Hong: For example, is a person, it's a triple. John is a subject and is a predicate [00:12:11] Jeremy: is, is the predicate. [00:12:12] Hong: Okay. And person is a object. That's great for showing how things are connected, but it is pretty different from how we usually handle data in REST for APIs and stuff. Like normally we say a personal object has property like name, DOB, bio, and so on. And a bunch of subject predicated object triples that's where JSON-LD comes in -- is designed to look more like the JSON we are used to working with, while still being able to represent RDF Graphs. RDF graph are ontology. It's a way to represent factual data, but is, quite different from, how we represent data in relational database. And it's a bunch of triples each subject and objects are nodes and predicates connect these nodes. Semantic Web [00:13:30] Jeremy: You mentioned the Semantic web, what does that mean? What is the semantic web? [00:13:35] Hong: It's a way to represent web in the structural way, is machine readable so that you can, scan the data in the web, using scrapers or crawlers. [00:13:52] Jeremy: Scrapers -- or what was the second one? Crawling. [00:13:59] Hong: Yeah. Then you can have graph data of web and you can, query information about things from the data. [00:14:14] Jeremy: So is the web as it exists now, is that the Semantic web or is it something different? [00:14:24] Hong: I think it is partially semantic web, you have several metadata in Your HTML. For example, there are several specification for semantic web, like, OpenGraph metadata. [00:14:32] Jeremy: Cause when I think about OpenGraph, I think about the metadata on a webpage that, that tells other applications or websites that if you link to this page: show this image or show this title and description. You're saying that specifically you consider part of the semantic web? [00:15:05] Hong: That's, semantic web. To make your website semantic web. Your website should be able to, provide structural data. And other people can make Scrapers to scan, structural data from your website. There are a bunch of attributes and text for HTML to represent metadata. For example you have relation attribute rel so if you have a link with rel=me to your another social profile. Then other people can tell two web pages represent the same person. [00:16:10] Jeremy: Oh, I see. So you could have more than one website. Maybe one is your blog and maybe one is your favorite birds or something like that. But you could put a rel tag with information about you as a person so that someone who scrapes both websites could look at that tag and see that both of these websites are by, Hong, by this person. JSON-LD is difficult to implement and not used as intended [00:16:43] Hong: Yeah. I think JSON-LD is, designed for semantic web, but in reality, ActivityPub implementations, most of them are, not aware of semantic web. [00:17:01] Jeremy: The choice of JSON Linked Data, the JSON-LD, by the people who made the specification -- They had this idea that things that implemented ActivityPub would be a part of this semantic web, but the actual implementation of a Mastodon or a Pixelfed, they use JSON-LD because it's part of the specification, but the way they use it, it ends up not really being a part of this semantic web. [00:17:34] Hong: Yeah, that's exactly.. [00:17:37] Jeremy: You've mentioned that implementing it is difficult. What makes implementing JSON LD particularly hard? [00:17:48] Hong: The JSON-LD is quite complex. Which is why a lot of programming language don't even have JSON-LD implementations and it's pretty slow compared to just working with the regular JSON. So, what happens is a lot of ActivityPub implementations just treat JSON-LD like (it) is regular JSON without using a proper JSON-LD processor. You can do that, but it creates a source of headache. In JSON-LD there are weird equivalences like if a property is missing or if it's an empty array, that means the same thing. Or if a property has one value versus an array with just that one value in it, same thing. So when you are writing code to parse JSON-LD, you've got to keep checking if something's an array how long it is and all that is super easy to mess up. It's not just reading JSON-LD that's tricky. Creating it is just as bad. Like you might forget to include the right context metadata for a vocabulary and end up with a JSON-LD document that's either invalid or means something totally different from what you wanted. Even the big ActivityPub implementations mess this up pretty often. With Fedify we've got a JSON-LD processor built in and we keep running into issues where major ActivityPub implementations create invalidate JSON-LD. We've had to create workaround for all of them, but it's not pretty and causes kind of a mess. [00:19:52] Jeremy: Even though there is a specification for JSON-LD, it sounds like the implementers don't necessarily follow it. So you are kind of parsing JSON-LD, but not really. You're parsing something that. Looks like JSON-LD, but isn't quite it. [00:20:12] Hong: Yes, that's right. [00:20:14] Jeremy: And is that true in the, the biggest implementations, Mastodon, for example, are there things that it sends in its activities that aren't valid JSON-LD? [00:20:26] Hong: Those implementations that had bad JSON-LD tends to fix them soon as a possible. But regressions are so often made. Yeah. [00:20:45] Jeremy: Even within Mastodon, which is probably one of the largest implementers of ActivityPub, there are cases where it's not valid, JSON-LD and somebody fixes it. But then later on there are other messages or other activities that were valid, but aren't valid anymore. And so it's this, it's this back and forth of fixing them and causing new issues it sounds ... [00:21:15] Hong: Yeah. Yeah. Right. [00:21:17] Jeremy: Yeah. That sounds very difficult to deal with. How instances communicate (Inbox) [00:21:20] Jeremy: We've been talking about the messages themselves are this special format of JSON that's very particular. but how do these instances communicate with one another? [00:21:32] Hong: Most of time, it all starts with a follow. Like when John follows Alice, then Alice adds both John and John's inbox URI to her followers list, and after John follows Alice, Whenever Alice posts something new that activities get sent to John's inbox behind the scenes. This is just one HTTP post request. Even though ActivityPub is built on HTTP. It doesn't really care about the HTTP response beyond did it work or not. If you want to reply to an activity, you need to figure out the standard inbox, URI and send or reply activity there. [00:22:27] Jeremy: If we define all the terms, there's the actor, which is the person, each actor can send different activities. those activities are in the form of a JSON linked data. [00:22:40] Hong: Yeah. [00:22:42] Jeremy: And everybody has an inbox. And an inbox is an HTTP URL that people post to. [00:22:50] Hong: Right. [00:22:52] Jeremy: And so when you think about that, you had mentioned that if you have a list of followers, let's say you have a hundred followers, would that mean that you have the URLs to all hundred of those follower's inboxes and that you would send one HTTP post to each inbox every time you had a new message? [00:23:16] Hong: Pretty much all ActivityPub implementations have, a thing called shared inbox, it's exactly what it sounds like. One inbox that all actors on a server share. Private stuff like DMs don't go there (it) is just for public posts and thoughts. [00:23:36] Jeremy: I think we haven't really talked about the fact that, when you have multiple users, usually they're on a server, right? That somebody chooses. So you could have tens of thousands, I don't know how many people can fit on the same server. But, rather than, you having to post to each user individually, you can post to the shared inbox on this server. So let's say, of your 100 followers, 50 them are on the same server, and you have a new post, you only need to post to the shared inbox once. [00:24:16] Hong: Yes, that's right. [00:24:18] Jeremy: And in that message you would I assume have links to each of the profiles or actors that you wanted to send that message to. [00:24:30] Hong: Yeah. Scaling challenges [00:24:31] Jeremy: Something that I've seen in the past is there are people who have challenges with scaling. Their Mastodon instance or their implementations of ActivityPub. As the, the number of followers grow, I've seen a post about, ghost one of the companies you work with mentioning that they've had challenges there. What are the challenges there and, and how do you think those can be resolved? [00:25:04] Hong: To put this in context, when Ghost mentioned the scaling, they were not using Message Queue yet. I'm pretty sure using Message Queue would help a lot of their scaling problems. That said it is definitely true that a lot of activity post software has trouble with scaling right now. I think part of the problem is that everyone's using this purely event driven approach to sending activities around. One of the big issues is that when their delivery fails it's the sender who has to retry and not the receiver. Plus there's all this overhead because the sender has to authenticate itself with HTTP signatures every time. Actually the ActivityPub spec suggests using polling too so I'd love to see more ActivityPub software try using both approaches together. [00:26:16] Jeremy: You mean the followers would poll who they're following instead of the person posting the messages having to send their posts to everyone's inboxes. [00:26:29] Hong: Yeah. [00:26:29] Jeremy: I see. So that's a part of the ActivityPubs specification, but not implemented in a lot of ActivityPub implementations, And so it sounds like maybe that puts a lot of burden on the servers that have people with a lot of followers because they have to post to every single, follower server and maybe the server is slow or they can't reach it. And like you said, they have to just keep trying and trying. There could be a lot of challenges there. [00:27:09] Hong: Right. Account migration [00:27:10] Jeremy: We've talked a little bit about the fact that each person each actor is hosted by a server and those servers can host multiple actors. But if you want to move to another server either because your server is shutting down or you just would like to change servers, what are some of the challenges there? [00:27:38] Hong: ActivityPub and Fediverse already have the specification for an account move. It's called FEP-7628 Move Actor. First thing you need to do when moving an account is prove that both the old and new accounts belong to the same person. You do this by adding the all accounts, add the URI to the new account's AlsoKnownAs property. And then the old account contacts all the other instances it's moving by sending out a move activity. When a server gets this move activity, it checks that both accounts really do belong to the same parts, and then it makes all the accounts that, uh, were following the, all the accounts start to, following the new one instead. that's how the new account gets to keep all the, all the accounts follow us. pretty much all, all the major activity post software has this feature built in, for example, Mastodon Misskey you name it. [00:29:04] Jeremy: This is very similar to the post where when you execute a move, the server that originally hosted that actor, they need to somehow tell every single other server that was following that account that you've moved. And so if there's any issues with communicating with one of those servers, or you miss one, then it just won't recognize that you've moved. You have to make sure that you talk to every single server. [00:29:36] Hong: That's right. [00:29:38] Jeremy: I could see how that could be a difficult problem sometimes if you have a lot of followers. [00:29:45] Hong: Yeah. Fedify [00:29:46] Jeremy: You've created a TypeScript library Fedify for building ActivityPub powered applications. What was the reason you decided to create Fedify? [00:29:58] Hong: Fedify is (a) ActivityPub servers framework I built for TypeScript. It basically takes away a lot of headaches you'd get trying to implement (an) ActivityPub server from scratch. The whole thing started because I wanted to build hollo -- A single user microblogging platform I built. But when I tried, to implement ActivityPub from (the) ground up it was kind of a nightmare. Imagine trying to write a CGI program in Perl or C back in the late nineties, where you are manually printing, HTTP headers and HTML as bias. there just wasn't any good abstraction layer to go with. There were already some libraries and frameworks for ActivityPub out there but none of them really hit the sweet spot I was looking for. They were either too high level and rigid. Like you could only build a mastodon clone or they barely did anything at all. Or they were written in languages I didn't really know. Ghost and Fedify [00:31:24] Jeremy: I saw that you are doing some work with, ghost. How is Ghost using fedify? [00:31:30] Hong: Ghost is an open source publishing platform. They have put some money into fedify which is why I get to work on it full time now. Their ActivityPub feature is still in private beta but it should be available to everyone pretty soon. We work together to improve fedify. Basically they are a user of fedify. They report bugs request new features to fedify then I fix them or implement them, first. [00:32:16] Jeremy: Ghost to my understanding is a blogging platform and a a newsletter platform. So what does it mean for them to implement ActivityPub? What would somebody using Mastodon, for example, get when they follow somebody using Ghost? [00:32:38] Hong: Ghost will have a fediverse handle for each blog. If you follow them in your mastodon or something (similar) then a new post is published. These post will show up (in) your timeline in Mastodon and you can like them or share them. Andin the dashboard of Ghost you can see who liked their posts or shared their posts and so on. It is like how mastodon works but in Ghost. [00:33:26] Jeremy: I see. So if you are writing a ghost blog and somebody follows your blog from Mastodon, sort of like we were talking about earlier, they can like your post, and on the blog itself you could show, oh, I have 200 likes. And those aren't necessarily people who were on your ghost website, they could be people that were liking your post from Mastodon. [00:33:58] Hong: Yes. Misskey / Forkey development in Asia [00:34:00] Jeremy: Something you mentioned at the beginning was there is a community of developers in Asia making forks of I believe of Mastodon, right? [00:34:13] Hong: Yeah. [00:34:14] Jeremy: Do you have experience working in that development community? What's different about it compared to the more Western centric community? [00:34:24] Hong: They are very similar in most ways. The key difference is language of course. They communicate in Japanese primarily. They also accept pull requests with English. But there are tons of comments in Japanese in their code. So you need to translate them into English or your first language to understand what code does. So I think that makes a barrier for Western developers. In fact, many Western developers that contribute to misskey or forkey are able to speak a little Japanese. And many of the developers of misskey and forkey are kind of otaku. [00:35:31] Jeremy: Oh otaku okay. [00:35:33] Hong: It's not a big deal, but you can see (the) difference in a glance. [00:35:41] Jeremy: Yeah. You mentioned one of the things that I believe misskey implemented was the emoji reactions and maybe one of the reasons they wanted that was so that they could react to each other's posts with you know anime pictures or things like that. [00:35:58] Hong: Yeah, that's right. [00:36:01] Jeremy: You've mentioned misskey and forkey. So is misskey a fork of Mastodon and then is forkey a fork of misskey? [00:36:10] Hong: No, misskey is not a fork of mastodon. (It) is built from scratch. It's its own implementation. And forkeys are forks of Mastodon. [00:36:22] Jeremy: Oh, I see. But both of those are primarily built by Japanese developers. [00:36:30] Hong: Yes. Whereas Mastodon (is) written in Ruby. Ruby on Rails. But misskey is built in TypeScript. [00:36:40] Jeremy: And because of ActivityPub -- they all implement it. So you can communicate with people between mastodon and misskey because they all understand the same activities. [00:36:56] Hong: Yes. Backwards compatible activity implementations [00:36:57] Jeremy: You did mention since there are extensions like misskey has the emoji reactions. When there is an activity that an implementation doesn't support what happens between the two servers? Do you send it to a server's inbox and then the server just doesn't do anything with it? [00:37:16] Hong: Some implementers consider backwards compatibility. So they design (it) to work with other implementations that don't support that activity. For example misskey uses like activity for emoji reaction. So if you put an emoji to a Mastodon post then in Mastodon you get one like. So it's intended behavior by misskey developers that they fall back to normal likes. But sometimes ActivityPub implementers introduce entirely new activity types. For example Pleroma introduced the emoji react. And if you put emoji reaction to Mastodon post from Pleroma in Mastodon you have nothing to see because Mastodon just ignores them. [00:38:37] Jeremy: If I understand correctly, both misskey and Pleroma are independent implementations of ActivityPub, but with misskey, they can tell when or their message is backwards compatible where it's if you don't understand the emoji reaction, it'll be embedded inside of a like message. Whereas with Pleroma they send an activity that Mastodon can't understand at all. So it just doesn't do anything. [00:39:11] Hong: Yes, right. But, Misskey also understands (the) emoji react activity. So between pleroma and misskey they have exchanged emoji reactions with no problem. [00:39:27] Jeremy: Oh, I see. So they, they both understand that activity. They both implement it the same way, but then when misskey communicates with Mastodon or with an instance that it knows doesn't understand it, it sends something different. [00:39:45] Hong: Yeah, that's right. [00:39:47] Jeremy: The servers -- can they query one another to know which activities they support? [00:39:53] Hong: Usually ActivityPub implementations also implement NodeInfo specification. It's like a user agent-like thing in Fediverse. Implementations tell the other instance (if it) is Mastodon or something else. You can query the type of server. [00:40:20] Jeremy: Okay, so within ActivityPub are each of the servers -- is the term node is that the word they use for each server? [00:40:31] Hong: Yes. Right. [00:40:32] Jeremy: You have the nodes, which can have any number of actors and the servers send activities to one another, to each other's inboxes. And so those are the way they all communicate. [00:40:49] Hong: Yeah. Building an ActivityPub implementation [00:40:50] Jeremy: You've implemented ActivityPub with Fedify because you found like there weren't good enough implementations or resources already. Did you implement it based off of the specification or did you look at existing implementations while you were building your implementation? [00:41:12] Hong: To be honest, instead of just, diving into the spec. I usually start by looking at actually ActivityPub software code first. The ActivityPub spec is so vague that you can't really build something just from reading it. So when we talk about ActivityPub, we are actually talking about a whole bunch of other technical standards too, WebFinger, HTTP signatures and more. So you need to understand all of these as well. [00:41:47] Jeremy: With the specification alone, you were saying it's too vague and so what ends up being -- I'm not sure if it's right to call it a spec, but looking at the implementations that people have already made that collectively becomes the spec because trying to follow the spec just by itself is maybe too difficult. [00:42:12] Hong: Yes. [00:42:14] Jeremy: Maybe that brings up the issues you were talking about before where you have specifications like JSON-LD where they're so complicated that even the biggest implementations aren't quite following it exactly. [00:42:28] Hong: Yeah. [00:42:29] Jeremy: If somebody wanted to, to get started with understanding a little bit more about ActivityPub or building something with it where would you recommend they start? [00:42:44] Hong: I recommend to dig into a lot of code from actual implementations. First, Mastodon, Misskey, Akkoma and so on. There are are some really cool tools that have been so helpful. For example, ActivityPub Academy is this awesome mastodon server for debugging ActivityPub. It makes it super easy to create a temporary account and see what activities are going back and forth. There is also BrowserPub. BrowserPub is this neat tool for looking up and browsing ActivityPub objects. It's really handy when you want to see how different ActivityPub software handles various features. I also recommend to use Fedify. I've got to mention the Fedify CLI, which comes with some really useful tools. [00:43:46] Jeremy: So if someone uses Fedify they're writing an application in TypeScript, then it sounds like they have to know the high level concepts. They have to know what are the different activities, what is inside of an actor. But the actual implementation of how do I create and parse JSON linked data, those kinds of things are taken care of by the library. [00:44:13] Hong: Yes, right. [00:44:16] Jeremy: So in some ways it seems like it might be good to, like you were saying, use the tools you mentioned to create a test Mastodon account, look at the messages being sent back and forth, and then when you're trying to implement it, starting with something like Fedify might be good because then you can really just focus on the concepts and not worry so much about the, the implementation details. [00:44:43] Hong: Yes, that's right. [00:44:45] Jeremy: Is there anything else you. Wanted to mention or thought we should have talked about? [00:44:52] Hong: Mm. I want to, talk about, a lot of stuff about ActivityPub but it's difficult to speak in English for me, so, it's a shame to talk about it very little. [00:45:15] Jeremy: We need everybody to learn Korean right? [00:45:23] Hong: Yes, please. (laughs) [00:45:23] Jeremy: Yeah. Well, I wanna thank you for taking the time. I know it must have been really challenging to give an interview in, you know, a language that's not your native one. So thank you for spending the time to talk with me. [00:45:38] Hong: Thank you for having me.

Saunter is a designer and bitcoin advocate who works at Alby: one of the most popular Lightning network wallets. In this episode, he describes his experiences with onboarding new users and increasing adoption around the world. Time stamps: Introducing Saunter (00:00:51) Evolution of Alby Wallet (00:01:38) Functionalities of the Alby Wallet (00:02:26) Lightning Business Model Challenges (00:05:46) Bitcoin as a Medium of Exchange (00:07:45) Adoption in Central America (00:09:55) Degrees of Bitcoin Adoption (00:12:59) Integration with Local Payment Systems (00:18:07) Educational Initiatives in El Salvador (00:20:43) Current State of Adoption (00:22:43) Chivo Wallet (00:25:46) Top-Down Adoption Issues (00:28:10) Grassroots Initiatives (00:30:46) Alby Wallet Features (00:35:33) Nostr Integration (00:36:08) Programmability of Bitcoin Lightning (00:39:57) Self-Hosting and Lightning Network (00:43:49) Future of Alby and User Accounts (00:46:27) Exploring Alby Wallet Options (00:51:48) Popular Apps on Alby (00:52:25) Point of Sale App Development (00:53:44) Isolated Balance Feature (00:55:07) User Experience with Alby App (00:56:30) Recommendations for Implementations (00:57:00) App Store Insights (00:58:00) Connecting Alby with Accounts (00:59:51) Channel Management and Backups (01:01:29) User Data Privacy Concerns (01:02:35) Benefits of Adding Alby to Full Nodes (01:04:14) Enhancing Node Capabilities (01:08:26) Inspiration for UX Design (01:12:56) User Testing Insights (01:15:56) Evolution of Lightning Wallets (01:16:52) Branding and Design Philosophy (01:17:53) Concerns About Security Exploits (01:19:25) Adoption Challenges and Perspectives (01:22:47) Bitcoin vs. Stablecoins (01:26:41) Market Dynamics and Adoption Rates (01:29:08) Future of Bitcoin Security (01:30:39) Interconnectedness of Bitcoin Systems (01:33:43) Challenges with Stablecoins on Lightning (01:37:31) Future Changes to Bitcoin Protocol (01:39:21) Discussion on Block Size Increase (01:40:42) Data Compression in Blocks (01:41:24) Cost of Verification Concerns (01:42:04) Layer Two Experiments (01:42:25) Risks of Layer One Changes (01:44:07) Focus on Lightning Network Development (01:45:06) Introducing Alby Wallet (01:45:29) Onboarding New Users (01:45:45) Benefits of Alby Hub (01:46:32) User-Friendly Lightning Node Setup (01:47:46) Following Saunter's Work (01:48:27)

Just when you think the bankers of the world couldn't be more in love -- with AI, that is -- along come four fintech experts to lay it all out for us in 2025. It promises to be the year of "agentic AI," among other things. And if that cute chatbot leaves roses on your desk, so much the better. Thanks to our special podcast guests: Joseph Ahn, CSO and Co-Founder, Delfi Amy Orosco, Director of Customer Success & Implementations, SWIVEL Mitch Rutledge, CEO and Co-Founder, Vertice AI Ed Vincent, CEO, SRA Watchtower

Agile World is excited to be back and talking with the team from JCURV about some really interesting case studies. The first part of the show is about bringing Agile practice into strategic working in AI and still ensuring tangible value delivery. The second part of the show focuses rapid problem solving using Agile in Healthcare to ensure quick Cancer detection.GuestsEmily Merkel Manager at JCURV | Enterprise Product and Agile TransformationsMichael Connor Director at JCURVPayal Jain Managing Director at JCURV & Chair of Women in Data®Co HostsSabrina C E NotoKarl A L Smith© 2025 ⁠⁠⁠⁠⁠⁠⁠Agile World ®⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠News and Broadcast Network ⁠California, USA | Music by Debs fromDetoxen (Facebook)

Join this channel to get access to perks such as Weekly Zoom Calls & Private Discord!! https://www.youtube.com/channel/UC4Bq... Free 30 Day Trial to Go2Lister https://www.go2lister.com/mikeI help teach people how to make money selling books on Amazon, leveraging the platform's vast reach and the profitability of reselling used books. How to sell books on Amazon? Selling books on Amazon can be an excellent side hustle or a full-time endeavor, particularly if you enjoy thrifting through places like Goodwill for hidden treasures. How to start selling on Amazon is accessible, and with my guidance on how to sell books, DVDs, CDs, and other media, beginners can quickly learn the ropes. Utilizing Amazon FBA streamlines operations, allowing sellers to focus more on sourcing and less on logistics. As a reselling coach, I provide tutorials and guidance on navigating challenges like ungating and optimizing listings for maximum visibility and sales. Whether you're looking for a part-time side hustle or aiming to become a full-time reseller, I will teach you the ins and outs of thrifting books and selling books online and can pave the way to creating passive income streams and achieving business growth.

In this episode of the Risk Intel Podcast, SRA Watchtower's own Cathy Jackson, Director of Implementations and a seasoned risk management expert joined host, Ed Vincent, to explore the evolving nature of Key Risk Indicators (KRIs) and how financial institutions can ensure their KRIs remain effective and actionable. Listen to the full episode to learn more.Follow us to stay in the know!

Episode Summary: In this episode, Maribel Lopez speaks with Dell's Chief Technology Officer and Chief AI Officer John Roese about Dell's enterprise AI technologies from their development to their future. Roese explains how the initial magical thinking around artificial intelligence has shifted into a more practical approach that aims to maximize the benefits of each implementation. He also discusses the emerging trends and ideas that he is seeing in the AI space.Key Themes: Maribel and John start by delving into enterprise AI and AI markets in general. John explains the types of AI markets and how enterprise AI differs from other applications. The conversation then moves into the challenges of AI and the steps that Dell is taking to address them. Next, John and Maribel reflect on the near-universal reactive approach that companies took to AI two years ago and how parts of that approach backfired or fizzled out. While this technology could have been approached better, its widespread use has provided companies with a real world understanding of LLMs and their applications. Now, companies take a more practical approach to AI while continuing to innovate. The key innovation that Roese highlights is agentic architecture. This technology differs from previous generative AI applications because it can operate autonomously and is highly specialized. Individual “agents” can have job descriptions that they are trained for much like a human being, and they can interact with each other as a human team would. For detailed show notes, navigate the episode using the time stamps below:[1:26] Maribel introduces the guest of the episode, John Roese. Roese is the CTO and Chief AI Officer at Dell Technologies. [1:59] The AI market is not a singular market – there is a traditional market, a training market, and an enterprise market. The enterprise market is very pragmatic in its applications. [4:10] Maribel asks about the challenges businesses see in enterprise adoption. Early discussions of new AI technology treated it like magic. Now that we have real world use cases and a better understanding of the technology, Dell is able to have grounded conversations about AI applications with real impacts. [7:48] Roesch explains the challenges that Dell is facing with AI. One of the challenges was determining where to prioritize as a company. Another is the process by which you develop application ideas. Dell had this issue when bringing ideas that were not fully formed to their legal team. [11:44] No one got AI perfectly right. Almost universally, companies reacted at the technical level before looking at business priorities. Roese encourages companies to move toward a more thoughtful approach to AI technology.[13:36] Dell learned that its goal was to add in the minimum sufficient AI structure to address the maximum use cases. In Dell's case, half of their use cases were related to converting proprietary data into generative outcomes. Creating one model to handle all of these cases is the most efficient approach. [15:05] Maribel asks Roese about the trends Dell is seeing in AI. Roese points to the emergence of agentic architecture. The idea behind agentic architecture is that they are autonomously performing agents with very specialized purposes. They can be combined much like a team of human beings. Follow John Roese: https://www.linkedin.com/in/johnroese/ Learn more about Dell's AI solutions: https://www.dell.com/en-us/shop/scc/sc/artificial-intelligence Follow Maribel Lopez on X/Twitter: https://x.com/maribellopez Subscribe to Maribel Lopez on YouTube: https://www.youtube.com/c/MaribelLopezResearch Follow Maribel Lopez on LinkedIn: https://linkedin.com/in/maribellopez/ 

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   Macy's Big Accounting Scandal, Q&A (Darian Chwialkowski, Third Stage Consulting) Keys to Successful ERP Implementations (Alec Epstein, Bryant Park Consulting) Top Transformation Mistake You're Making   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

Neel Nanda, a senior research scientist at Google DeepMind, leads their mechanistic interpretability team. In this extensive interview, he discusses his work trying to understand how neural networks function internally. At just 25 years old, Nanda has quickly become a prominent voice in AI research after completing his pure mathematics degree at Cambridge in 2020. Nanda reckons that machine learning is unique because we create neural networks that can perform impressive tasks (like complex reasoning and software engineering) without understanding how they work internally. He compares this to having computer programs that can do things no human programmer knows how to write. His work focuses on "mechanistic interpretability" - attempting to uncover and understand the internal structures and algorithms that emerge within these networks. SPONSOR MESSAGES: *** CentML offers competitive pricing for GenAI model deployment, with flexible options to suit a wide range of models, from small to large-scale deployments. https://centml.ai/pricing/ Tufa AI Labs is a brand new research lab in Zurich started by Benjamin Crouzier focussed on ARC and AGI, they just acquired MindsAI - the current winners of the ARC challenge. Are you interested in working on ARC, or getting involved in their events? Goto https://tufalabs.ai/ *** SHOWNOTES, TRANSCRIPT, ALL REFERENCES (DONT MISS!): https://www.dropbox.com/scl/fi/36dvtfl3v3p56hbi30im7/NeelShow.pdf?rlkey=pq8t7lyv2z60knlifyy17jdtx&st=kiutudhc&dl=0 We riff on: * How neural networks develop meaningful internal representations beyond simple pattern matching * The effectiveness of chain-of-thought prompting and why it improves model performance * The importance of hands-on coding over extensive paper reading for new researchers * His journey from Cambridge to working with Chris Olah at Anthropic and eventually Google DeepMind * The role of mechanistic interpretability in AI safety NEEL NANDA: https://www.neelnanda.io/ https://scholar.google.com/citations?user=GLnX3MkAAAAJ&hl=en https://x.com/NeelNanda5 Interviewer - Tim Scarfe TOC: 1. Part 1: Introduction [00:00:00] 1.1 Introduction and Core Concepts Overview 2. Part 2: Outside Interview [00:06:45] 2.1 Mechanistic Interpretability Foundations 3. Part 3: Main Interview [00:32:52] 3.1 Mechanistic Interpretability 4. Neural Architecture and Circuits [01:00:31] 4.1 Biological Evolution Parallels [01:04:03] 4.2 Universal Circuit Patterns and Induction Heads [01:11:07] 4.3 Entity Detection and Knowledge Boundaries [01:14:26] 4.4 Mechanistic Interpretability and Activation Patching 5. Model Behavior Analysis [01:30:00] 5.1 Golden Gate Claude Experiment and Feature Amplification [01:33:27] 5.2 Model Personas and RLHF Behavior Modification [01:36:28] 5.3 Steering Vectors and Linear Representations [01:40:00] 5.4 Hallucinations and Model Uncertainty 6. Sparse Autoencoder Architecture [01:44:54] 6.1 Architecture and Mathematical Foundations [02:22:03] 6.2 Core Challenges and Solutions [02:32:04] 6.3 Advanced Activation Functions and Top-k Implementations [02:34:41] 6.4 Research Applications in Transformer Circuit Analysis 7. Feature Learning and Scaling [02:48:02] 7.1 Autoencoder Feature Learning and Width Parameters [03:02:46] 7.2 Scaling Laws and Training Stability [03:11:00] 7.3 Feature Identification and Bias Correction [03:19:52] 7.4 Training Dynamics Analysis Methods 8. Engineering Implementation [03:23:48] 8.1 Scale and Infrastructure Requirements [03:25:20] 8.2 Computational Requirements and Storage [03:35:22] 8.3 Chain-of-Thought Reasoning Implementation [03:37:15] 8.4 Latent Structure Inference in Language Models

The UK Humanitarian Innovation Hub (UKHIH), Elrha, and Humanitarian AI Today bring panelists together to discuss transparency and strategies for improving transparency and accountability in AI implementations. Michael Hind, Distinguished Research Staff Member at IBM Research; Shadrock Roberts, Director of Global Data Protection & Privacy at Mercy Corps; Scott Turnbull, Chief Technology Officer at Data Friendly Space; Liam Nicoll, Signpost Product Lead at Signpost AI Lab; and Sarah Spencer, a consultant who regularly speaks on humanitarian operations and applications of artificial intelligence, contribute their insights on transparency and ways of improving transparency and accountability in AI implementations. Touching on the existing landscape of AI initiatives within the humanitarian sector, key players, and what transparency means broadly and in practice, their views connect the humanitarian and technology communities and provide valuable insight into why transparency is crucial for building trust in AI systems and engaging stakeholders in developing and leveraging uses of AI for good. The panel discussion, guest hosted by Brent Phillips from Humanitarian AI Today, mixes input on AI systems, technical information disclosure, AI governance and regulation, and how humanitarian organizations are approaching developing, testing and deploying safe, responsible and trustworthy AI applications that are transparent and accountable to end users. Panelists each share their views on ways of improving transparency and offer ideas on directions to expand the transparency conversation. In closing, panelists provide a strong case for greater information sharing on AI use cases and greater inclusivity around transparency throughout the AI building and deployment process. This episode is part of a six-part panel discussion series sponsored and produced by Humanitarian AI Today in collaboration with the UK Humanitarian Innovation Hub (UKHIH) and Elrha, with funding from UK International Development from the UK government.   More information about this episode, its focus and upcoming discussions can be found by subscribing to the UK Humanitarian Innovation Hub and Elrha's new AI newsletter: http://ukhih.org/newsletter.

Hazel Weakly joins Justin and Autumn to talk about when to build abstractions and how to implement them. They also share experiences from tech conferences, and delve into the importance of building community and psychological safety in tech environments.

Learning happens when you make mistakes. In our time working on implementations, we won't hide–we've made some mistakes that we learned from. In this episode, Doug and Jess have an insightful discussion about CRM implementations and projects that have gone wrong. They share real-life examples of setbacks Lift has faced, what mistakes were made, and the key lessons learned to help you avoid similar pitfalls.For updates on new episodes follow us on:LinkedIn: Lift Enablement, Doug Davidoff, Jess CardenasSubscribe to our YouTube channel!You can access the show notes and watch the video version of the show on our page. Thanks for listening and remember to just say no to shitty RevOps!

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   Hubspot's Acquisition of Cacheflow, Q&A (Darian Chwialkowski, Third Stage Consulting) Business Intelligence in ERP Implementations (Dominique Frechette, GURUS Solutions) Keys to Oracle Fusion Cloud Implementation Success   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

Let's dive into the importance of collaboration between business and data teams, and how to navigate the complexities of AI implementations. My guest today is Andreas Welsch. He is an internationally recognized AI leader, advisor, and the best-selling author of the "AI Leadership Handbook." With over 23 years of experience, including key roles at SAP, Andreas has been instrumental in helping Fortune 500 companies turn technology hype into real business outcomes. Andreas will share insights from his book and valuable advice for organizations embarking on their AI journey.

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   How to Localize Your AI Strategy, Q&A (Darian Chwialkowski, Third Stage Consulting) ERP Implementations the Right Way (Brett Beaubouef, Digital Transformation Author & Consultant) How Agile Leads to Digital Transformation Failure   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

In today's complex financial landscape, effective risk management is critical for the stability and success of any financial institution. Governance, Risk, and Compliance (GRC) teams play a central role in this process, ensuring that organizations are well-protected against potential risks while maintaining compliance with regulatory standards. But how exactly does GRC fit into the broader picture of Enterprise Risk Management (ERM) and how does GRC differ from the Audit function? This Risk Intel episode features Cathy Jackson, Director or Implementations at SRA Watchtower, who answers four key questions to help you understand the responsibilities of the GRC and Audit teams, how they operate, and how they integrate with ERM. Give it a listen to learn more.Follow us to stay in the know!

Send me a Text Message hereFULL SHOW NOTES https://podcast.nz365guy.com/587 What if you could master the art of balancing a demanding career with a fulfilling personal life? Join us as we sit down with Kirti Prajapati, a modern workplace architect and independent M365 consultant from India, who reveals his secrets to maintaining a harmonious lifestyle. Through his dedication to homemade food, regular gym visits, and balanced nutrition, Kiriti shares how he stays healthy and energized. He also opens up about the importance of family, the joy of solitary meditation in cafes, and his commitment to quarterly vacations—all while managing a busy consulting schedule.But that's not all. Dive into game-changing Power Platform implementations with us as we spotlight groundbreaking projects across industries. Learn how a UK-based company transformed their bicycle rental system, fostering employee well-being and realizing cost savings through Model-Driven apps, React web applications, and Azure Logic Apps. Discover how a government agency enhanced their portfolio management with the Power Platform, outperforming SAP, Salesforce, and ServiceNow in terms of security and scalability. We'll also discuss strategies for maximizing productivity through seamless technology transitions and automated deployment processes, ensuring user satisfaction and management approval. Don't miss this insightful conversation on the powerful impact of thoughtful technology integration! 90 Day Mentoring Challenge 10% off code use MBAP at checkout https://ako.nz365guy.comSupport the Show.If you want to get in touch with me, you can message me here on Linkedin.Thanks for listening

This podcast is hosted by edWeb.net.The webinar recording can be accessed here.This edWeb podcast is the kickoff to edWeb's Mental Health & Wellness Week, a series to help drive awareness and support for educator and student wellness. Listen to this edWeb podcast for a discussion with Dr. Christopher Jenson and a panel of education leaders with deep experience in the field of mental health and wellness. This session focuses on where we are now in supporting staff and student mental health:Implementations currently in place: Are we happy with them? Why or why not?The current assets and limitations of schools: What are they? What roles do we feel communities are pushing us into?Do schools have the responsibility and/or capacity to help with treatment of staff and students?The role of embedded skills and preventive mental health (novel approach) with a discussion of the research data and perspectives from presentersThis edWeb podcast is of interest to PreK-12 educators, counselors, and administrators who want to learn more for their own self-care and for the mental health and wellness of their students.edWeb.netedWeb is an award-winning professional learning network that serves the global education community.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Learn more about viewing live edWeb presentations and on-demand recordings, earning CE certificates, and using accessibility features.

ORDER MY NEW BOOK: The Final Countdown: https://a.co/d/50cqrCB CONTACT MY TEAM & I: https://www.thirdstage-consulting.com... FOR SPONSORSHIP OPPORTUNITIES: contact@majortom-productions.com

Eric and I chat about AI implementations. What do you need to be successful?

The podcast interview explores the role of RISC-V in the automotive sector. It begins with a brief introduction to RISC-V, explaining it as an open standard instruction set architecture (ISA). The discussion then shifts to current automotive trends from a processing perspective, highlighting advancements and the increasing importance of robust, high-performance computing. 

July 4, 2024: Michael Restuccia, SVP and CIO of Penn Medicine, explores the complexities and triumphs of leading a major academic medical center's IT department for over 17 years. How does one maintain momentum and innovation over such a long tenure? Michael delves into the importance of building a strong, mission-driven team and fostering a collaborative culture, especially in a hybrid work environment. They discuss the challenges of balancing budgets, the evolution of electronic health records, and the cautious yet optimistic approach to integrating AI in healthcare. What qualities make a successful team member in such a demanding field, and how do you retain top talent amidst fierce competition? Michael also shares insights into how technology can reduce administrative burdens for clinicians, improve patient care, and drive operational efficiency. This conversation provides a deep dive into the strategic thinking required to navigate the ever-evolving landscape of healthcare IT.Key Points:Leadership ChallengesTeam BuildingBudget ManagementEHR EvolutionTechnology IntegrationSubscribe: This Week HealthTwitter: This Week HealthLinkedIn: Week HealthDonate: Alex's Lemonade Stand: Foundation for Childhood Cancer

In this latest episode, Carla Sarti, former VP GBS - Lear Corporation, joins Mustansir Saifuddin to share what she's learned in her decades of experience, with both business and technology, about how businesses and teams can be successful in any IT implementation. From teamwork to fundamental project management, to supplier relations, Carla dives in to highlight quick takeaways that you can implement to make an even bigger impact with your IT implementation. Carla Sarti was most recently the Vice President of Global Business Services at Lear Corporation – a position she held since April 2018.  Prior to this position she was Vice President of Non Production Purchasing and Director of Shared Services.   Prior to Lear, she served as Account Executive at ACS, a Xerox company (now Conduent) where she acted as chief strategy officer and Director of Sales for many large accounts in the Finance and Accounting Outsourcing area.  She spent five years at Delphi Corporation in numerous roles of increasing responsibility including managing the SAP environment after implementation and working as a Lean expert for the Cockpits business.  She also worked as a plant and divisional financial analyst at TRW and an operational auditor at the Budd Company. Connect with us: LinkedIn Carla Sarti Mustansir Saifuddin Innovative Solution Partners  Twitter:  @Mmsaifuddin YouTube or learn more about our sponsor Innovative Solution Partners to schedule a free consultation.    Episode Transcript: [00:00:00] Mustansir Saifuddin: Welcome to Tech Driven Business brought to you by Innovative Solution Partners. Carla Sarti, a seasoned executive, shares her insights that any team can use for leading successful IT projects. From understanding business processes to the importance of transparency, teamwork, and supplier relations, Carla reveals the key ingredients for project success. [00:00:30] Welcome to Tech-Driven Business Carla. How are you? [00:00:33] Carla Sarti: I'm great. Thanks for having me. Great to see you. [00:00:38] Mustansir Saifuddin: It's great to have you on our show. And I'm glad that , you took the time out to share some of your thoughts and leadership with us today, [00:00:46] Carla Sarti: Absolutely. [00:00:48] Mustansir Saifuddin: so our topic is going to be Secrets to successful IT projects. How does it sound to you? [00:00:55] Carla Sarti: Amazing. It's 1 of my passions. [00:00:58] Mustansir Saifuddin: I know, I know. And I think that's going to be something that it will be very helpful to our listeners, especially in this day and age where technology is changing so fast. There are so many different options available. And I. T. Is in the middle of all of this. Let me start with this. You know, I want to set the stage. [00:01:15] So let's begin with this. Can you share some background on how you How did you find yourself leading I. T. Projects you started your career in a totally different arena? [00:01:29] Carla Sarti: Absolutely. So, yes, I have a business degree of my MBA. I started in audit and very specific businesses, purchasing finance, et cetera. But technology was always something that I was very curious and passionate about. When I was a co op at TRW, the vice president of finance came to me one day and I'm going to date myself a little bit here, but we were on Lotus 1, 2, 3, and he had a disc in his hand and he said, Carla or little kid or whatever he called me. [00:02:00] Here's a disk of Excel. I would like all of our reports moved from Lotus 1, 2, 3, put on Excel and let's review them next week. And I said, okay, let's go. And so I taught myself Excel and I really started to understand the power of technology. And that's just such a basic example. Right. So while I was still a co op, I got involved in an SAP implementation and That really opened my eyes to what technology can bring, and I've been into it ever since. [00:02:32] So different functional groups I've been in, I've always brought best in class processes along with the technology side, because I think it is, it goes hand in hand, but I've done everything from SAP, Coupa, SharePoint, RPA, and now dabbling in AI. [00:02:50] Mustansir Saifuddin: Absolutely. You know, it doesn't matter matter where you start? You know, even having a business degree, like you mentioned technology is always with you and it's around you. So you got to either embrace it and you got to go with the flow or you're going to fight it, right? So I, I like the approach that you mentioned that, you know, your first inital foray into this whole technology area was just, you know, just of the iceberg, right? [00:03:14] You got into this thing and now Years later, you are much ingrained in this whole technology stack. So, let's talk about your experience. You have decades of experience. What do you see as some key factors that contribute to the success of IT projects, which is so important? [00:03:33] Carla Sarti: So I'm going to start with the assumption that before you implement any sort of technology, You've really understood your business, right? And where are your business processes? What needs to be cleaned up? You're not just bringing in technology to bring in technology because I don't think that's ever usually successful, but so you've done that and then you've really understood again, the current processes. [00:04:01] The gaps that you have and what is your success criteria? I think a lot of people, a lot of companies don't look at what success looks like at the very beginning. And they say, Oh, okay. Yeah. We're just going to implement this. We heard it's the best solution and they don't think through, what are we trying to achieve? [00:04:19] That, that really starts dictating what a successful project looks like. Then you through the whole. Project. You obviously have to have the right team members on the project, having an executive sponsor that can break down roadblocks. I've seen projects that the best ones typically have a business person leading them. [00:04:44] Because they understand what's trying to be accomplished. Not that IT can't lead projects and they are definitely very integral to the process. But typically, when a business person runs them, they're implemented quicker. The understanding is there. The right process mapping has been done, et cetera. So you've got the right people. [00:05:07] Probably have suppliers in the mix, because what company has all that skill set on hand? So you have to have the right suppliers. And then through the course of it, you have to have the right governance. So the communication process, the transparency of where the project truly is, because as you know, IT projects are not a hundred percent foolproof, right? [00:05:33] Something always happens in any kind of project, whether you're building a house, you're, you're baking a cake or whatever it is, something goes wrong and you've got to have the right transparency and communication. To understand what to do next, then obviously you could have the best tool in the world. [00:05:51] The best project. It's going great. You have to have change management methodology and processes embedded in the project because if people aren't going to use it. What does it matter? Right? And I mentioned Excel when I was a co op, a lot of people still use Excel and you could put in the best shiny new toy technology. [00:06:13] People are comfortable with Excel. So you've got to explain to people how their jobs going to change and give them the appropriate training to make it a true success. In the end. [00:06:25] Mustansir Saifuddin: For sure. And I think you touched upon a lot of it. Some very key points. You know, starting with a champion, you know, has to be a business. How do they currently do the job? How can they do it better? You know, governance, such a key piece. You need to have that in place, change management, you know, I've been in technology field for so many years. [00:06:44] That's one thing that we know. If there is no good change management in place, It doesn't matter what technology, what kind of resources or what kind of supplier you're using, it doesn't go well. The end user needs to be on board. They need to really be part of the whole implementation process in order for them to adapt and then be the voice of the new tool because they are the ones who will be actually living with it, doing it on a daily basis. [00:07:15] So great point. [00:07:15] Carla Sarti: And people get scared. I mean, they get really nervous when a new project's coming, right? And especially in the age of AI, people think they're going to lose their jobs and companies need to do a really good job explaining. No, no, no. So you do this today, but tomorrow we need you to do that. And actually you'll probably be more fulfilled doing. [00:07:36] The new, but it's just that, that way of explaining and coaching them through it and not just dumping something on their lap. [00:07:45] Mustansir Saifuddin: Absolutely. And that's the key, right? How is it helping the real users of the system that this implementation or this piece of software doesn't matter? You're doing an E. R. P. implementation. You do some kind of data analytics project or any other systems that you're putting in place. It is there to help the business move to the next level. [00:08:08] How can we be more profitable? How can we make it easier for our customers to deal with us? different scenarios, right? And this and all of these are bundled together to give you the next level of the best, right? How can you do your job a better way than what you're currently doing? So totally agree with you. Now you touched upon one key fact, right? The idea of finding the right supplier. So how do you find the right supplier to support your initiatives? Can you share examples of successful IT projects? Where your supplier collaboration was very effective. [00:08:44] Carla Sarti: Finding the right supplier is key to the equation. I've always looked for a valued, trusted business partner. And. You know, there's, there's a lot of ways to get there. And I think a lot of it is being up front in the initial RFP process. [00:09:03] And you've got to have as much information for the supplier as possible to bid on because what you don't want is. Death by change order later because they didn't understand the project. You didn't understand the project as the business. That breaks down a relationship really, really fast. So again, more of that transparency, the collaboration. Some of the best projects I've had and I can't go into a lot of detail on them, but we implemented a tool in 18 months at one of my companies and really the success of the project was a lot. [00:09:39] on the supplier side. We brought somebody in with a great skill set in the tool that we were building. They had a road map. They had this amazing design methodology and the right questions were asked. The right people were brought by us as the company and, you know, we got off to a great start when things did go wrong. [00:10:02] They were very, very transparent. They said, okay, we need to get together. Let's pull everyone together. Let's get these questions answered. And they didn't hide things. We didn't hide things. It was probably the best project I've ever implemented. And that's what it takes. Again, that collaboration, transparency, and that win win from both sides. [00:10:25] Mustansir Saifuddin: Absolutely. I think you touched upon all the things that a successful project should look like, especially from a practices point of view, the strategy point of view and the relationships standpoint. Right? All of these work together and. You know, I, I just use the example of many different projects that I've done. [00:10:44] And, you know, especially when you're working with clients, transparency up front really helps. It sets the stage and make sure that both the client and the supplier are on the same page. And when you start off with that approach, things, like I said, things can go wrong, but you have a plan in place how to mitigate those issues, how do we get on the same page and make sure that whatever things that are an obstacle to the project are taken care of working collaboratively versus, you know, us versus them. [00:11:18] Carla Sarti: Right. Exactly. That's the last thing you want to get into in a project. It's already complex enough, [00:11:24] Mustansir Saifuddin: Yeah. And, like you mentioned earlier, right, that always something that comes up. You, you have the best of the intentions, but it can be a business challenge. There can be a technology challenge. There can be integration challenges. All different factors play a role into things can go in a different direction very quickly. [00:11:46] Carla Sarti: right? Oh, we didn't know this site had this approval process in here. And oh, this one has a different one. You find things as you get the project going and you have to be agile. You have to be flexible. You can't have. You know, the last thing you want is a supplier that's like, Oh no, you know, this, this is what we were brought in for. [00:12:06] I mean, we can talk about commercials, but you know, let's just all collaborate and get it done. That's where you need that trusted relationship because you don't want the supplier thinking, Oh, okay. They're going to ask me to do this for free. And you don't want the customer to be like, okay, they're not going to be able to do it. [00:12:23] So you've got to have that open dialogue going. [00:12:26] Mustansir Saifuddin: For sure. So, on a personal note, how do you stay on top of this fast changing pace of technology? What's, what's your secret sauce? [00:12:36] Carla Sarti: I've always been a constant learner always right? I mean, and I think being a co op at 18 years old, really drove that in me. It was the time, I kind of want to date myself it was the time when computers were kind of just starting to be used and I saw people just fumbling with the mouse. I mean, think of that in today's day and age, right? [00:13:01] I mean, back then people were fumbling with mice. I was like, oh my goodness, I never want to be in a position where, I'm not kind of at the forefront of technology. And I'm just a learner anyway. So, you know, whether it be books podcasts really from a technology standpoint, I think is what keeps me up to date. [00:13:21] I love the podcast. It's called All in One it's for billionaires that. Actually have very different views on things, whether it be politics or technology or science, and they talk about everything under the sun. Nvidia actually has an AI podcast. It's called the AI podcast, and then there's AI today. [00:13:44] And then being in GBS and shared services, a lot of my career, I stay on top of those things with SSO next. And they talk about technology, tons of technology within that realm as well. I read tons of articles on LinkedIn, the Wall Street Journal, and then definitely leadership books. I know that's not necessarily technology, but. [00:14:05] When you're talking about leading people again through change, and, you know, the best way to be collaborative, I find that to be extremely helpful. Patrick Lencioni is one of my favorite authors The 5 Dysfunctions of Team, one of my favorite authors. Favorite books. And he writes very much like fiction. [00:14:23] So it's really easy to get through. I don't know if you've ever listened to or read Jocko Wilnick's books, but he has extreme ownership and a couple others, phenomenal books, right? I mean, just kind of look at yourself in the mirror and it, it goes to project management, so extreme ownership. Am I doing everything I possibly can to be successful? [00:14:44] Have my team be successful. So really good one for project management. Mustansir. [00:14:50] Mustansir Saifuddin: Nice, I think you've got a whole slew of resources available at your fingertips that's good. I think like one thing that I really liked about your approach, I mean, you've seen it all, you've played different roles, It's refreshing to see someone like you in your space that you still find yourself as a student, you know, still keep on learning and be able to keep yourself ahead of the curve. [00:15:12] And I think that's the key, right? The different roles we play depending on what you're doing your daily job, but at the same time, looking around and seeing what else is going around you. We live in the space of, and the times of Gen AI. AI being disruptive and how it will change our lives. It's already is changing, you know how do you stay ahead or at least keep up with the technology? [00:15:39] I think is the key to your success. So that's what it seems like you you've been very much in tune with it. [00:15:46] Carla Sarti: Absolutely. One of the coolest things I ever did was reverse mentoring. So I had someone younger in the organization mentoring me, right? And then it helps you get into their shoes and understand what drives the next generation. What tools and technology are they using? It's really fascinating. And of course I, I use my kids too. [00:16:08] You know, I have a 19 year old and a 17 year old and just understanding: How they think, what they're looking at, what they're using, chat, what's GPT 4 all about. You know, you got to stay on top of things. [00:16:21] Mustansir Saifuddin: Yeah, they are the best teachers. I mean you think about technology I mean this younger generation is amazing and how they are adapting and all that. Let's get into the conversation about you know, we talked about successful supplier collaborations very key, right, important but what are some of the common challenges companies face? [00:16:41] With IT suppliers during a project. Can you share some ideas on thoughts on that? [00:16:49] Carla Sarti: I think one of the ones I've seen is where someone's oversold their capabilities, right? You've got a supplier, maybe they did a really good job on one project and they're asked to bid on another. And as a company, and again, trying to find that trusted supplier, it's very easy to fall into, well, let's just use these guys that were successful before. [00:17:13] You've really got to evaluate, are they going to be successful for this project? And of course they want business. Everyone wants business, but you've really got to look and say, okay, can I deliver on this project? Because if I can't. I'm actually going to ruin my reputation within the company. So just being honest and making sure again, from the company's standpoint, you're choosing the right supplier and that the suppliers. [00:17:42] Again, understanding the project that you're trying to implement and maybe they don't understand at first and they think they can deliver on the project. So, as a supplier, I would say, make sure you ask the questions. Be curious. Why are you doing this project? What exactly are you looking for? Oh, okay. [00:18:02] It's in this space. Okay. We don't have people in that space. Well, I can maybe bring people in to do that. You know, really understanding, that side to me, can really change the dynamic there. And then again, I'm not gonna, I'm going to keep talking about the transparency. If the supplier cannot be transparent when there is an issue, it's not going to be good.. I've always told people whether they work for me or a supplier, Bad news doesn't get better with time. You've got to bring these things forward. We've got to come up with solutions together. I don't care whose fault it is. [00:18:38] Mustansir Saifuddin: Yeah, [00:18:39] Carla Sarti: Like, ultimately, I want this project to be successful. So let's work together to get that done. [00:18:45] Mustansir Saifuddin: absolutely Absolutely. I think and and that's where I my question to you is how do you mitigate those issues? Everybody wants a smooth and successful implementation. It's just Everybody thinks that's how it should go, but we all know there are challenges. [00:18:59] Carla Sarti: Mm hmm. [00:19:00] Mustansir Saifuddin: you maybe share some ideas, thoughts on how do you mitigate those issues or something that you may have seen in the past? [00:19:08] Carla Sarti: So we, a lot of times, use just basic project management. Fundamentals, right? You've got your project plan. Are you on plan or not? Then you look at what can go wrong. Okay, you list out all the things that you think could go wrong and you start putting mitigating plans together on that, right? And having meetings around those things. [00:19:31] Okay, guys, how are we doing? Are we getting the data? That's going to be a big thing here. Did we get it? Did we not? What do we need to do? And again, having the right people on the project. So do you have somebody who can go in, break down those roadblocks if things aren't getting done, building the right relationships, again, you got to have the right people who can build relationships. [00:19:53] Project management, as you know, It's almost more about being a psychologist than anything else. I mean, you've got to bring people together that maybe don't normally work together. They have very different personalities. You've got people on the IT side that have different personalities than the project side. [00:20:11] So you've got to make sure that you understand those factors and use project management methodology. It's there for a reason. I mean, I've seen people, they're like, Oh, we don't need a project plan. Yeah. Like what? What are you talking? How do you do a successful project without a project plan? You don't even know what's coming next. [00:20:31] You don't even know where you are in the cycle. Are you on track? Are you not? So I think those things, honestly, like don't overlook the fundamentals. [00:20:41] Mustansir Saifuddin: No, I think that's a great advice. I one thing I, I, I like about your approach or your thinking is a project manager being a psychologist. You know, how many times you go through these, these iterations of projects after projects, you know, being a.supplier ourselves. I mean, I, I really appreciate your thought process on that because there's so many different stakeholders in any given time and project where you may have one stakeholder on board, but you may have someone else either business, I. [00:21:11] T. Whatever else you're working with. They may be either lost. They don't agree with your approach or there's something else that in this space. And you needs someone who can actually mitigate all those different pieces of the, [00:21:25] Carla Sarti: Mm [00:21:26] Mustansir Saifuddin: puzzle and bring it all, all of them together in a way they see the value. [00:21:30] It's all about value proposition and making sure that the end product is what the customer is asking for. Can we deliver? If we can deliver, what is the game plan? How do we go about making sure that we are all on the same page? Because at the end of the day, Once it is delivered correctly, It's a win win, you know. so [00:21:48] Carla Sarti: Hmm. [00:21:49] Mustansir Saifuddin: Do appreciate that insight into it and I know we talked about a lot of different things. I like to ask this one parting question. [00:21:58] What is that one key takeaway? You want to leave with our listeners today. [00:22:05] Carla Sarti: IT projects are very complex. So again, I would say the fundamentals are key. Understand what you're trying to accomplish. That is number one, understand the processes, get the right team involved, the right supplier, and set yourself up for success. So fundamentals. Use project management. Methodology for sure. [00:22:33] I mean, it's there for a reason and have the right, the right people on the project is key. I know I'm doing like five different key takeaways here in Mustansir, but really again, it's just so complex and the fundamentals, the right people and, and the right methodology, key, [00:22:51] Mustansir Saifuddin: No, thank you. Great advice and great takeaways. And I think once we have all these different pieces of the puzzle together, it's a recipe for success. So with that I'd like to conclude our session and I'd like to thank you for coming on on our show It was a pleasure having you. [00:23:08] Carla Sarti: likewise. Thank you for having me. [00:23:10] Mustansir Saifuddin: Thanks for listening to Tech Driven Business brought to you by Innovative Solution Partners. Carla shared valuable insights that can be used immediately by your IT team her main takeaway, focus on the fundamentals that include understanding your objectives, involving the right team of staff and suppliers, and stick to solid project management methodologies. [00:23:33] We would love to hear from you. Continue the conversation by connecting with me on LinkedIn or Twitter. Learn more about Innovative Solution Partners and schedule a free consultation by visiting isolutionpartners. com. Never miss a podcast by subscribing to our YouTube channel. Information is in the show notes.

Join Car and Keyan to discuss Stacker News' top posts of the week, Car & Keyan's favorite posts of the week, and top stackers for the week of June 21st, 2024.Follow the conversation of the episode on SN.Time Stamps:02:24 - My project got hacked and user funds were stolen29:11 - PlebDevs Beginner Backend Series32:36 - Doom is not a strategy41:19 - Bitcoin Circular Economy - a hard to achieve goal for many people46:44 - Ecash on Bitcoin Educational Resources48:17 - Long-Term Support For Calle50:02 - Ramifications Of A Samourai Plea Bargain57:14 - What are your thoughts on Bitcoin losing the Darknet59:26 - DoS Disclosure: LND Onion Bomb1:02:29 - Lugano Trip Report1:03:32 - Ideas and Implementations of Bounties1:06:06 - Ego Death Capital?1:08:12 - Some Thoughts on My Failed SN Recruitment EffortShoutout @Wumbo for time stamps. Zap em!We love the Fountain app for Lightning 2.0 podcasting, Send us a Boost, and we will read it on the next SNL.Find Car on NostrFollow Car on SNRead Thriller BitcoinFollow Thriller on NostrFollow Thriller on Zap.StreamFollow Thriller on YouTubeContribute to ~buildersLearn more about PlebLabFollow Keyan on TwitterFollow Keyan on NostrFollow Keyan on SNFollow Stacker News on NostrLearn more about Stacker News

Why you should listenLearn why mapping out business processes is crucial before implementing technology solutions and how this can lead to more successful projects.Discover the importance of speaking the same language as your clients and building long-term, trust-based relationships.Get insights into integrating platforms like Rootstock with Salesforce to provide comprehensive solutions tailored to specific industries.You're handed a potential client lead but quickly realize there's a significant missing step: the right process. In this episode, I sit down with Jessie Mead, co-founder of Cloud Journey Consulting Group. Jessie shares her extensive experience in the Salesforce ecosystem and her journey from the financial sector to becoming a top Salesforce consultant with over 17 certifications. We delve into the importance of getting business processes before implementing technology solutions and how a tool can make a significant difference. Don't miss this insightful conversation on optimizing your business processes for success.About Jessie MeadJessie Mead has been at the forefront since the early years of the Salesforce platform. Previously serving years as a Marketing Executive in the finance world, Jessie designed and implemented a groundbreaking M&A platform that led to her selection for M&A Advisors 40 under 40. She chose Salesforce as a career, has 17 certifications, and has helped countless businesses succeed with Salesforce. Jessie lives in Dallas. She has a passion for photography and loves to travel at every opportunity.Resources and LinksCloudjourneygroup.comJessie's LinkedIn profilePrevious episode: 542 - 7 Profit Drivers for Tech ConsultantsCheck out more episodes of The Paul Higgins ShowTech Consultant's RoadmapJoin our newsletterJoin the Tech CollectiveSuggested resourcesFind out more about Paul and how he can help youBONUS: Jessie offers complimentary Salesforce/Certinia architecture reviews if you'd like a health check of your current org! Take advantage of this offer by sending Jessie a LinkedIn message and letting her know you heard her podcast episode.

The first thing we noticed at URBNSURF Sydney was that everyone wore a name badge. “Dude maintaining the pool” now has a name (it's Keith by the way.) This simple customer experience measure hints at the kind of changes Jennifer Vandekreeke has in mind for Australia's premier surf park business. In her previous roles, she drove growth for travel and leisure companies, notably Carnival Cruise Lines. Having taken the reins from Damon Tudor, we were curious to find out how Jenn's experience making big, giant boats profitable (hint: wave pools are also just big, expensive pieces of machinery as well) parlay into the world of surf parks.

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   Oracle's Pressure on Customers to Update License Agreements, Q&A (Darian Chwialkowski, Third Stage Consulting) Software Integration in ERP Implementations (Mark Simon, Celigo) Why Change Management is Overrated   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

ORDER MY NEW BOOK: The Final Countdown: https://a.co/d/50cqrCB CONTACT MY TEAM & I: https://www.thirdstage-consulting.com/contact-us/ FOR SPONSORSHIP OPPORTUNITIES: contact@majortom-productions.com

Michael Kannisto runs a think tank called MindemicLab, which utilizes scenario planning, wargame simulation, and predictive modeling to help organizations develop strategies that will be effective across multiple possible futures. Michael began his career as a research chemist, but quickly realized that while molecules always act predictably and consistently, people rarely do. He has spent much of his career in corporate Human Resources exploring the uncertainty that comes along with having humans in the workplace. Large, successful, well-funded organizations frequently experience failure when purchasing technology or implementing new policies. This is mainly the result of unanticipated changes that occur along the way. Michael started MindemicLab as a resource to help others “rehearse” alternative futures, and thus increase their likelihood of success. Prior/ongoing work in this area includes deep dives into The Future of Work, The Future of Early Career Recruiting and The Future of Disability. Plastic Love by Mayiya Takeuchi Virtual HR Technology Conference

Episode Notes Join us this week on TXL as we sit down with Ed Newman, industry expert and author from talentEXP, to explore the transformative concepts outlined in his latest book Phenom Do.  In this episode, he'll address the challenges HR faces when implementing new tech by advocating for a user-centric, experience-first approach. Find out how to win organizational buy-in, leverage AI to augment human capabilities, and navigate common implementation pitfalls. Get notified for all upcoming TXL episodes here: https://info.phenom.com/talent-experience-show-subscribe/

Embark on a journey of business transformation with our latest episode of Beyond the Books, where our host Kevin teams up with Nancy, our seasoned Implementation Director, to uncover the secrets behind growth by design. In this illuminating discussion, we dive deep into the dynamic world of custom-fit implementations, unveiling the strategic maneuvers that propel businesses toward unprecedented growth and success. Join us as we dissect every facet of the implementation process, from meticulous resource vetting to strategic allocation, and unwavering support. Through real-world examples and expert insights, we decode the art of seamlessly integrating new systems into your business framework. Whether you're a seasoned entrepreneur or a budding startup, this episode is your definitive guide to harnessing the power of tailored implementations and steering your business toward limitless possibilities. Tune in now and unlock the blueprint for sustainable growth in the ever-evolving landscape of modern business.