Podcasts about collaboration tools

In this episode of TBCY, host Frits Bussemaker welcomes back Keith Harrison-Broninski, CEO of Collaboration Tools Ltd, author, keynote speaker, technology consultant, and magician. They explore the urgent topic of AI safety, discussing what it truly means for artificial intelligence to be “safe,” the complexities of trust in modern AI, and how international standards and regulations can be operationalized in practical ways.Keith Harrison-Broninski shares real-world examples from his career, including pioneering work in air traffic control systems and defense, and explains how trusted engineering methodologies can be applied to the rapidly evolving world of AI. Discover how adopting an engineering mindset and holistic perspective can not only mitigate risk, but also create more valuable technology for organizations and communities.Don't miss Keith Harrison-Broninski's advice for anyone using AI and his vision for enabling safe, trustworthy AI ecosystems.

We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'

Transform how you communicate with tools that make your message stick.Meetings are where collaboration happens — but too often, scheduling them feels like the biggest barrier to meaningful connection. That's why Calendly was created: to simplify scheduling and make time for what truly matters — the conversation itself.In this episode of the Think Fast, Talk Smart Tech Tools miniseries, host Matt Abrahams talks with Calendly's Vice President of Growth, Darren Chait, about how intentional scheduling leads to better communication, stronger relationships, and more productive meetings. They explore how data-driven insights can improve collaboration, reduce burnout, and help teams make every meeting count.In addition to insight-packed discussions, this miniseries explores innovative tools that enhance the way we communicate and connect. Whether you want to make your presentations more memorable, craft stories that stick, or connect with your audience on a deeper level, these episodes will help you communicate with greater clarity, confidence, and impact.Episode Reference Links:Darren ChaitE.227 Tech Tools: Move Your Audience By Moving Through Your Presentation Ep.230 Tech Tools: Use Visuals to Your Advantage Ep.233 Tech Tools: Write with Confidence and Impact Ep.236 Tech Tools: Zeroing in on Your Email Communication Connect:Premium Signup >>>> Think Fast Talk Smart PremiumEmail Questions & Feedback >>> hello@fastersmarter.ioEpisode Transcripts >>> Think Fast Talk Smart WebsiteNewsletter Signup + English Language Learning >>> FasterSmarter.ioThink Fast Talk Smart >>> LinkedIn, Instagram, YouTubeMatt Abrahams >>> LinkedInChapters:(00:00) - Introduction (01:12) - Calendly Elevator Pitch (02:47) - The Origin of Calendly (04:44) - The Art of Intentional Scheduling (06:33) - Making Meetings More Effective (07:30) - Favorite Communicator (09:31) - Communication Hack or Tool (11:36) - Conclusion  *******Thank you to our sponsors.  These partnerships support the ongoing production of the podcast, allowing us to bring it to you at no cost.Try Prezi today and get 25% off exclusively at prezi.com/thinkfast.

Transform how you communicate with tools that make your message stick.Staying on top of communication starts with staying in control of your inbox. That's why Rahul Vohra, founder and CEO of Superhuman, believes that how we manage email directly shapes how we manage our time, focus, and relationships.For years, Superhuman has helped professionals reach Inbox Zero faster — reducing email overload and reclaiming time for what truly matters. In this episode of the Think Fast, Talk Smart Tech Tools miniseries, host Matt Abrahams talks with Vohra about the philosophy behind Inbox Zero, how better systems lead to clearer communication, and why mindfulness and intentional design can make us more effective communicators.In addition to insight-packed discussions, this miniseries explores innovative tools that enhance the way we communicate and connect. Whether you want to make your presentations more memorable, craft stories that stick, or connect with your audience on a deeper level, these episodes will help you communicate with greater clarity, confidence, and impact.Episode Reference Links:Rahul VohraEp.227 Tech Tools: Move Your Audience By Moving Through Your Presentation Ep.230 Tech Tools: Use Visuals to Your Advantage Ep.233 Tech Tools: Write with Confidence and Impact Connect:Premium Signup >>>> Think Fast Talk Smart PremiumEmail Questions & Feedback >>> hello@fastersmarter.ioEpisode Transcripts >>> Think Fast Talk Smart WebsiteNewsletter Signup + English Language Learning >>> FasterSmarter.ioThink Fast Talk Smart >>> LinkedIn, Instagram, YouTubeMatt Abrahams >>> LinkedInChapters:(00:00) - Introduction (01:18) - The Philosophy Behind Inbox Zero (04:19) - The Superhuman Elevator Pitch (05:50) - The Origin of Superhuman (09:14) - Favorite Communicator (10:17) - Communication Hack or Tool (11:59) - Conclusion  *******Thank you to our sponsors.  These partnerships support the ongoing production of the podcast, allowing us to bring it to you at no cost.Try Prezi today and get 25% off exclusively at prezi.com/thinkfast.

Connect with your clients in more than one way. Check out our recommendations for video calling software!   Read the text version   Contact the Agent Survival Guide Podcast! Email us ASGPodcast@Ritterim.com or call 1-717-562-7211 and leave a voicemail.   Video Communication Resources: Google Meet Google Workspace Microsoft Meet Phone.com RingCentral Zoho Webinar Zoho Meeting Zoom Webinars Zoom Workplace   Resources: 5 Things From the 2025 Budget Reconciliation Bill Field Notes for Agents Playlist Register with Ritter Insurance Marketing Setting Up Your Insurance Business Structure ft. Frank Lavery & Justin Abodalo The Insurance Agent's Guide to Generating Referrals – FREE eBook Download   References: “AI-Powered Online Video Meetings.” RingCentral, https://www.ringcentral.com/video.html. Accessed 24 July 2025. “Collaboration Tools for Teams of All Sizes.” Zoom, https://www.zoom.com/en/products/collaboration-tools/. Accessed 24 July 2025. “Deliver Your Message, Captivate Your Audience.” Zoom, https://www.zoom.com/en/products/webinars/. Accessed 24 July 2025. “Google Meet: Online Web and Video Conferencing Calls | Google Workspace.” Google Workspace, Google, https://workspace.google.com/products/meet/. Accessed 24 July 2025. “Google Workspace: Secure Online Productivity & Collaboration Tools.” Google Workspace, Google, https://workspace.google.com/. Accessed 24 July 2025. Asurion. “How to Share Your Screen on Facetime.” Asurion, 6 Feb. 2025, https://www.asurion.com/connect/tech-tips/share-iphone-ipad-screen-facetime/. “Online Meeting Software & Platform - Zoho Meeting.” Zoho, https://www.zoho.com/meeting/. Accessed 24 July 2025. “Small Business Communication Software: Microsoft Teams.” Microsoft, https://www.microsoft.com/en-us/microsoft-teams/small-medium-business. Accessed 24 July 2025. “Video Meetings.” Phone.Com, 21 Feb. 2025, https://www.phone.com/video-meetings/. “Zoho Webinar: Video Webinar Platform & Tool.” Zoho, https://www.zoho.com/webinar/. Accessed 24 July 2025.   Follow Us on Social! Ritter on Facebook, https://www.facebook.com/RitterIM Instagram, https://www.instagram.com/ritter.insurance.marketing/ LinkedIn, https://www.linkedin.com/company/ritter-insurance-marketing TikTok, https://www.tiktok.com/@ritterim X, https://x.com/RitterIM and YouTube, https://www.youtube.com/user/RitterInsurance     Sarah on LinkedIn, https://www.linkedin.com/in/sjrueppel/ Instagram, https://www.instagram.com/thesarahjrueppel/ and Threads, https://www.threads.net/@thesarahjrueppel  Tina on LinkedIn, https://www.linkedin.com/in/tina-lamoreux-6384b7199/   Not affiliated with or endorsed by Medicare or any government agency.

We explore the latest YouTube updates with Jerry Potter featuring Jessica Stansberry on the Social Media Marketing Talk Show.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Folge 72 des „Digital Pacemaker“-Podcasts beschäftigt sich mit der Frage, warum Einfachheit oft kompliziert ist. Sven Kummer, Mitgründer von Rapidmail, erzählt, wie aus einem Side-Project im Campingwagen ein Unternehmen wurde, das E-Mail-Marketing für KMU demokratisiert. Im Mittelpunkt steht der bewusste Verzicht auf Komplexität als Erfolgsrezept: Von Anfang an setzte das Team auf intuitiv bedienbare Lösungen – ein Ansatz, der sich seit 17 Jahren bewährt, obwohl jährlich das „Ende der E-Mail” prophezeit wird. Sven verrät, warum Einfachheit keine Innovationsbremse ist, sondern kreative Standardisierung erfordert – zum Beispiel durch das automatische Vorausfüllen von Webformularen auf Basis von Unternehmensdaten. Künstliche Intelligenz wird bei Rapidmail nicht als Buzzword gehandelt, sondern als präzises Werkzeug zur Problemlösung eingesetzt. „Die Frage ist nicht, was KI kann, sondern welche Kundenprobleme wir damit besser lösen können”, betont Sven und verweist auf Lehren aus hybriden KI-Experimenten, bei denen die Authentizität und das Branchenwissen menschlicher Marketingexperten unersetzlich blieben. Spannend wird die Frage, wie verteilte Teams in flexiblen Strukturen produktiv bleiben. Rapidmail setzt auf eine Mischung aus klaren Prozessen und humorvoller Kultur. Die überraschende Erkenntnis lautet: Gelassenheit und situationskomischer Humor entschärfen digitale Kommunikationsfallen effektiver als viele Collaboration-Tools. Wer mehr wissen möchte, findet hier weitere Informationen: - Website der Rapidmail GmbH: https://www.rapidmail.de - E-Books, Checklisten & Whitepaper für gute Newsletter: https://www.rapidmail.de/ebooks-und-downloads - Literaturempfehlung „Erfolgreiches E-Mail-Marketing“ von Torsten Schwarz: https://shop.haufe.de/prod/erfolgreiches-e-mail-marketing-inkl-arbeitshilfen-online Euer Feedback zur Folge und Vorschläge für Themen und Gäst:innen sind sehr willkommen! Vernetzt Euch und diskutiert mit: - Sven Kummer: https://www.linkedin.com/in/sven-kummer/ - Ulrich Irnich: https://www.linkedin.com/in/ulrichirnich/ - Markus Kuckertz: https://www.linkedin.com/in/markuskuckertz/ Mitwirkende - Hosts: Ulrich Irnich & Markus Kuckertz // Redaktion: Marcus Pawlik © Digital Pacemaker Podcast 2025

Send us a text Cross-functional chaos? We've been there. Ange MacCabe and Maria Maycock unpack how to align technical and non-technical teams — using proven tools that drive clarity, trust, and performance across biotech, healthtech, and life sciences orgs. In this episode of The Human Side of Business, host Ange MacCabe (CEO, Intuity Performance) and consultant Maria Maycock explore the real-world friction between technical and non-technical teams — and how to fix it.From biotech to medtech and SaaS, discover what causes cross-functional breakdowns and how tools like RACI matrices, team charters, and real-time feedback loops can transform collaboration. You'll hear client stories, actionable frameworks, and tips to boost trust, productivity, and alignment across disciplines.Tune in to learn:Why technical and non-technical teams often clash — and what to do about it5 proven collaboration tools for tech-driven companiesHow communication rituals and neutral facilitation unlock better outcomesReal stories from biotech, medtech, and software teams that turned chaos into cohesionIdeal for biotech leaders, healthtech innovators, product managers, HR pros, and team leads who want to turn siloed expertise into shared success.Subscribe and connect with Intuity Performance for more on unlocking people-powered performance. https://linktr.ee/intuity_performance?utm_source=linktree_profile_share<sid=1809c076-de55-431f-9640-1d8abca81c91

Send us a textIn this episode, we are joined by Amanda Gilbert, and we dive deep into collaboration in the workplace. We discuss the importance of collaboration, how to achieve it, and the common corporate pitfalls that can prevent it.  We share practical steps for setting up collaborative environments, building trust among team members, and achieving shared goals. We also highlight real-world examples of successful collaboration and provide insights on leveraging collaboration tools and techniques. Tune in to learn how to enhance your team's performance and achieve better results through effective collaboration.Plus, we discuss what treats Mrs Lawther is getting for her birthday, the plight of children leaving the nest and a great TV box set recommendation.

  Free up your work week by using a digital appointment scheduler. Spend more time with clients and less time managing your calendar.   Read the text version   Contact the Agent Survival Guide Podcast! Email us ASGPodcast@Ritterim.com or call 1-717-562-7211 and leave a voicemail.   Resources: 3 Insurance Business Tools You Absolutely Can't Live Without: https://ritterim.com/the-ultimate-agent-resource-list/ Best Practices for Video Calls: https://lnk.to/8jc7x9 Digital Marketing for Insurance Agents: Our Top Tips to Boost Business: https://ritterim.com/blog/digital-marketing-for-insurance-agents-our-top-tips-to-boost-business/ Free eBooks & Guides: https://ritterim.com/guides/ Get Your PlanEnroll Site: https://ritterim.com/planenroll/ How to Stay Compliant During All Medicare Sales: https://lnk.to/41gE4C Meet Your Sales Specialist: https://ritterim.com/meet-your-sales-team/ MedicareCENTER: https://ritterim.com/integrity-tools/#medicarecenter Register with Ritter Insurance Marketing: https://app.ritterim.com/public/registration/ What Are Agents Responsible for Under HIPAA: https://ritterim.com/blog/what-are-agents-responsible-for-under-hipaa/ Where It All Begins: Obtaining Permission to Contact for Medicare Sales: https://ritterim.com/blog/where-it-all-begins-obtaining-permission-to-contact-for-medicare-sales/ The Ultimate Agent Resource List Pt 3: Staying Organized: https://ritterim.com/blog/the-ultimate-agent-resource-list-pt-3-staying-organized/    Appointment Schedulers: Acuity: https://acuityscheduling.com/ Google Workspace: https://workspace.google.com/resources/appointment-scheduling/ Microsoft Bookings: https://www.microsoft.com/en-us/microsoft-365/business/scheduling-and-booking-app OnceHub: https://oncehub.com/ SimployBook.me: https://simplybook.me/en/   References: Lurie, Matt. “20 Integrable Scheduling Tools for Small Business Systems.” Ruby, 11 Nov. 2024, https://www.ruby.com/blog/20-of-the-best-small-business-appointment-scheduling-tools-and-apps/. “Acuity Scheduling: Online Appointment Scheduling Software.” Acuity, https://acuityscheduling.com/. Accessed 3 Mar. 2025. “Acuity Scheduling and HIPAA.” Acuity : Scheduling, https://help.acuityscheduling.com/hc/en-us/articles/16689567523597-Acuity-Scheduling-and-HIPAA. Accessed 3 Mar. 2025. “Agencybloc's AMS+ Solution for Health, Group Benefits, & Senior Insurance.” AgencyBloc Insurance Agency CRM, https://www.agencybloc.com/ams/. Accessed 3 Mar. 2025. “Appointment Scheduler.” Radius Help Center, https://help.radiusbob.com/en/articles/5448715-appointment-scheduler. Accessed 3 Mar. 2025. “Compare All Microsoft 365 Plans.” Microsoft, https://www.microsoft.com/en-us/microsoft-365/business/compare-all-microsoft-365-business-productss. Accessed 3 Mar. 2025. “Free Appointment Booking System.” SimplyBook.Me - Free Appointment Booking System, https://simplybook.me/en/. Accessed 3 Mar. 2025. “Google Workspace.” Google Workspace: Secure Online Productivity & Collaboration Tools, Google, https://workspace.google.com/. Accessed 3 Mar. 2025. “Health Insurance Portability and Accountability Act (HIPAA) & Health Information Technology for Economic and Clinical Health (HITECH) Act - Microsoft Compliance.” Microsoft Compliance | Microsoft Learn, https://learn.microsoft.com/en-us/compliance/regulatory/offering-hipaa-hitech. Accessed 3 Mar. 2025. “HIPAA Compliance with Google Workspace and Cloud Identity.” Google Workspace Admin Help, Google, https://support.google.com/a/answer/3407054. Accessed 3 Mar. 2025. “HIPAA for Professionals.” HHS.Gov, 19 July 2024, https://www.hhs.gov/hipaa/for-professionals/index.html. “Microsoft 365 - Subscription for Productivity Apps: Microsoft 365.” Microsoft 365 - Subscription for Productivity Apps | Microsoft 365, https://www.microsoft.com/en-us/microsoft-365. Accessed 3 Mar. 2025. “Online Appointment Booking Software - Unmatched Free Plan.” OnceHub, https://oncehub.com/. Accessed 3 Mar. 2025. “Online Appointment Scheduling with Google Calendar.” Google Workspace, Google, https://workspace.google.com/resources/appointment-scheduling/. Accessed 3 Mar. 2025. “Online Bookings and Appointment Scheduling: Microsoft 365.” Online Bookings and Appointment Scheduling | Microsoft 365, Microsoft, https://www.microsoft.com/en-us/microsoft-365/business/scheduling-and-booking-app. Accessed 3 Mar. 2025. “Productivity Apps for Business Owners & Entrepreneurs | Google Workspace Individual.” Google Workspace, Google, https://workspace.google.com/individual/. Accessed 3 Mar. 2025. Alder, Steven. “The Use of Technology and HIPAA Compliance.” The HIPAA Journal, https://www.hipaajournal.com/the-use-of-technology-and-hipaa-compliance/. Accessed 3 Mar. 2025. “What Is a HIPAA Business Associate Agreement (BAA)?: TechTarget.” Healthtech Security, TechTarget, 14 Feb. 2022, https://www.techtarget.com/healthtechsecurity/feature/What-Is-a-HIPAA-Business-Associate-Agreement-BAA. “What Is Our Online Scheduler Solution?” Producer Max The Agent-Centric Platform, https://www.producermax.com/Online-Scheduler.html. Accessed 3 Mar. 2025.   Follow Us on Social! Ritter on Facebook, https://www.facebook.com/RitterIM Instagram, https://www.instagram.com/ritter.insurance.marketing/ LinkedIn, https://www.linkedin.com/company/ritter-insurance-marketing TikTok, https://www.tiktok.com/@ritterim X, https://x.com/RitterIM and Youtube, https://www.youtube.com/user/RitterInsurance     Sarah on LinkedIn, https://www.linkedin.com/in/sjrueppel/ Instagram, https://www.instagram.com/thesarahjrueppel/ and Threads, https://www.threads.net/@thesarahjrueppel  Tina on LinkedIn, https://www.linkedin.com/in/tina-lamoreux-6384b7199/   Not affiliated with or endorsed by Medicare or any government agency.

Steve Ruiz, founder of TLDraw, discusses the revolutionary AI applications in TLDraw, the intricacies of infinite canvas editors, and the impact of AI on design and development. Links https://www.steveruiz.me https://www.tldraw.com https://makereal.tldraw.com https://teach.tldraw.com https://computer.tldraw.com https://gitnation.com/contents/make-real-tldraws-accidental-ai-play We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr)

Summary In this conversation, Dave Prior and Jim Benson discuss the challenges of remote work, the impact of collaboration tools on productivity, and the importance of creating humane workspaces. They explore the dynamics of meetings, the toxicity of over-communication, and the need for regular maintenance in team processes. Jim shares insights from his course on cleaning toxic waste in workplaces, emphasizing the significance of visual management and effective communication to foster a healthier work environment. Takeaways • Work should be done without fear or trepidation. • Remote work requires understanding information needs within teams. • Meetings often become unproductive due to over-communication. • Context switching can lead to frustration and decreased productivity. • Creating humane workspaces is essential for team dynamics. • Regular maintenance of team processes prevents issues from escalating. • Collaboration tools need to be used intentionally and effectively. • Visual management can help reduce workplace toxicity. • Toxic systems lead to hiring toxic leaders. • Addressing workplace toxicity is a collective responsibility. Chapters 02:11 Introduction to Jim Benson and Work Dynamics 05:09 The Challenges of Remote Work and Collaboration Tools 08:07 Meeting Overload and Productivity Killers 11:14 Communication Tools and Their Inefficiencies 14:11 The Impact of Context Switching on Work 17:07 Creating Humane Workspaces 20:10 The Role of Tools in Team Collaboration 23:08 Cleaning Toxic Waste in Work Environments 26:15 Conclusion and Course Information Links from the episode Cleaning Toxic Waste Course: https://modusinstitute.com/course/toxic-waste Modus Institute: https://modusinstitute.com/ The Collaboration Equation: https://www.collaboration-equation.com/ The Agile Network December Micro Conference (Dec 16-17): https://theagilenetwork.com Contacting Jim LinkedIn: https://www.linkedin.com/in/jimbenson/ Email: jim@moduscooperandi.com

We look at the essential skills for future leadership. Zoë recounts a gripping rescue mission in Tasmania, highlighting the significance of collaboration and trust within teams. Guest Graham Wilson, dubbed 'The Leadership Wizard,' discusses the need to unlearn outdated leadership practices and emphasizes authentic, purpose-driven leadership. The conversation also covers team dynamics and practical strategies for enhancing performance. Quotes "The secret ingredient to preventing a toxic culture is transparency around decision-making." Zoë Routh "We were educated for a world that doesn't exist anymore." Graham Wilson "Collaboration and teamwork should not be seen as cheating; they are essential for effective leadership." Graham Wilson Questions Asked What are the trends that you're paying attention to in leadership and business right now? How do you see the pace of change affecting leaders today? What does it mean for leaders to unlearn outdated beliefs and practices? How can leaders foster collaboration in an environment where teamwork may be viewed as "cheating"? What strategies can leaders implement to create an empowered workforce? Take Action Reflect on your own leadership style and identify any outdated beliefs you may need to unlearn. Implement at least one collaboration tool discussed in the episode to enhance team dynamics. Read recommended leadership books to deepen your understanding of effective leadership practices. Tip of the Week Review the collaboration self-checklist - available for subscribers only. Join the community here. You'll get 40 book summaries and recommendations on Leading Strategy and Performance, along with a special secret audio from my award-winning book, People Stuff. Key Moments (timestamps) 00:00 Welcome to the Future of Leadership 00:38 A Riveting Rescue Story 02:16 Lessons from the Rescue 06:04 Upcoming Adventures and Book Releases 06:40 Exploring Organizational Culture 09:42 Introducing Graham Wilson 11:38 The Future of Leadership Trends 17:41 Unlearning Old Leadership Patterns 23:10 Building Human Connection in Teams 29:00 Creating Certainty in Uncertain Times 29:44 The Concept of Taking the Knee 30:31 Lessons from Racing and Business 31:48 The Importance of Slowing Down 34:40 Collaboration Tools and Techniques 39:50 Future of Work and Leadership 44:50 The Fast Three Questions 46:32 Final Thoughts on Leadership 52:09 Where to Find More About Graham Wilson 53:19 Book Recommendation and Closing Remarks  

This episode was sponsored by Lucid, a provider of a visual collaboration suite for developers. Learn more here: https://lucid.co/ In this episode, David Rubinstein, editor-in-chief of SD Times, interviews Jessica Guistolise, evangelist at Lucid, about how visual collaboration can improve developer experience.They discuss:Challenges with gaining visibility in software developmentThe value of visualizationsHow visual collaboration streamlines Agile developmentResources: https://sdtimes.com/softwaredev/accelerating-innovation-how-the-lucid-visual-collaboration-suite-boosts-agile-team-efficiency/ 

On this episode of the Six Five Webcast – Enterprising Insights, host Keith Kirkpatrick gives a comprehensive wrap-up of two major tech events: Smartsheet Engage and the Zendesk AI Summit. This discussion explores the latest trends, announcements, and breakthroughs presented at these leading industry conferences. Keith covers: Key takeaways from Smartsheet Engage including new product announcements and strategic directions Highlights from the Zendesk AI Summit focusing on the future of customer experience and AI integration Predictions for how the announcements and trends from these events will influence enterprise technology strategy. Insights into the evolving landscape of work management tools and customer service technologies Implications for businesses striving to enhance collaboration and customer interaction through advanced technologies  

On the latest episode of Six Five Media at Smartsheet ENGAGE, host David Nicholson sits down with Smartsheet's Jennifer Stockton, Senior Director of Solutions Marketing, and Conga's Courtney Finger, Principal of Product Marketing Operations, for an insightful conversation about how Conga has leveraged the Smartsheet platform to transform its marketing operations. Their discussion covers: The key challenges Conga faced in marketing operations and why Smartsheet was the ultimate solution. The journey from "chaos to collaboration" made possible by Smartsheet's adoption within Conga. Favorite Smartsheet features that boost marketing and creative operations. The importance of scalability for creative teams and how Smartsheet supports this growth. Unique benefits that Smartsheet offers to organizations seeking streamlined and collaborative creative processes. Don't miss out on this deep dive into how Smartsheet is driving innovation in marketing! Learn more at Smartsheet.

BONUS: Mastering Remote Work in Agile Teams With Antony Marcano NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!   In this BONUS episode, Antony, co-founder of RiverGlide and Head of Engineering at Ford Digital, joins us to share his experiences and insights from 30 years in software development, including 25 years in Agile practices. As a technical practitioner, leader, and consultant, Antony reflects on navigating remote work, overcoming challenges, and setting up successful remote software teams, while exploring future trends in the industry. The Shift to Fully Remote Work Antony reflects on his first fully remote software project, which took place during the pandemic when everyone was forced to work from home. While his team had been working together for 12 months, they struggled with traditional video conferencing tools that lacked the ability to support pair programming or mob programming effectively. This is when Antony and his team discovered Tuple, a tool that allows for seamless control sharing and a co-located pairing experience. "Switching to Tuple was a game-changer for us in making remote pairing feel as interactive as in-person collaboration." Overcoming Challenges in Remote Collaboration The biggest challenge Antony identifies in remote work is the loss of serendipitous moments—those random watercooler conversations that often lead to innovation. To address this, Antony encourages teams to create opportunities for these moments by structuring time for informal interactions and fostering a safe and open communication culture. "You can't recreate the watercooler, but you can create opportunities for innovation by encouraging open-door policies and setting up shared virtual spaces." Building Effective Remote Teams For Antony, real collaboration is critical to the success of remote teams. He grew up on XP (Extreme Programming) and believes in the power of pairing and mob programming. Antony emphasizes the importance of maintaining good practices from in-person work, such as prioritizing mental well-being, while adapting to the unique needs of remote teams. "Collaboration is not just about tools—it's about mental well-being, trust, and giving the team what they need to succeed." Keeping Teams on Track with Clear Goals Antony shares his approach to ensuring that teams remain aligned with clear goals and progress tracking. His teams focus on delivering small, incremental slices of work and using techniques like limiting Work In Progress (WIP). Rather than viewing user stories as a list of tasks, Antony encourages teams to focus on the user benefit and desired outcomes. "It's about the ‘why,' not just the ‘what.' User stories should focus on the goal, not just be a list of tasks." The Future of Remote Work in Software Development Looking ahead, Antony predicts that tools will continue to evolve, with AI playing a more significant role in software development. He discusses the possibility of having AI participants in pairing sessions and shares his concerns about the convergence of tools that may lose focus over time. Antony encourages developers to experiment with new technologies and remain open to change. "AI is the next frontier in software development, and we need to embrace how it can enhance our remote work experiences." Recommended Resources for Mastering Remote Work Antony notes that while many resources on remote work are often too generic, there are valuable tools and practices software teams can adopt. He recommends regularly rotating hosts during remote pairing sessions and setting aside time for retrospectives and discussions about the bigger 'why' behind the work. "When pairing, rotate roles, reflect regularly, and always focus on the bigger ‘why' to keep your team aligned and motivated." About Antony Marcano Antony is the co-founder of RiverGlide and Head of Engineering at Ford Digital. With 30 years of software development experience, including 25 years in Agile practices, he is a respected leader, coach, and consultant. Antony has contributed to books and journals and is a keynote speaker at global conferences and universities such as Oxford and McGill. He is also the co-creator of 'PairWith.Us,' and remains a hands-on technical practitioner, specializing in Agile development and leading teams to excel in agility. You can link with Antony on LinkedIn visit RiverGlide.com, or check out RiverGlide TV on YouTube.

Thanks to our Partners, AAPEX, NAPA TRACS, and Automotive Management Network Recorded at the 2024 Automotive Aftermarket Retailers of Ontario (AARO) Business Management and Lindertech Training Tradeshow, discover how simply attending meetings can significantly improve net profit, the impact of cost management, and tips on leveraging technology for business efficiency. Murray Voth, RPM Training. Listen to Murray's previous episodes HERE. murrayvoth@rpmtraining.net Show Notes Watch Full Video Episode Automotive Aftermarket Retailers of Ontario (AARO): https://www.aaro.ca/ Importance of Attendance (00:02:04) Discussion on how missing educational events can lead to lost opportunities and profits. Value of Showing Up (00:03:05) Murray emphasizes the connection between attendance and improved business performance. Networking and Community (00:04:39) The significance of in-person meetings for building relationships and sharing knowledge. Learning from Group Sessions (00:05:23) Murray shares insights on the benefits of participating in group coaching sessions. Addressing Intimidation in Coaching (00:07:50) Discussion on how some individuals feel intimidated and hesitant to participate in coaching. The Need for Continuous Learning (00:10:59) Carm stresses the importance of seeking expert guidance and accountability in business. Coaching Styles and Techniques (00:11:53) Murray contrasts different coaching approaches and their effectiveness in the industry. Utilizing Technology for Coaching (00:13:28) Murray discusses the transition to online coaching and the importance of Google Business Profile. Engagement in Virtual Meetings (00:14:17) The effectiveness of screen sharing and virtual meetings in enhancing learning experiences. Introduction to Collaboration Tools (00:15:54) Discussion on using screen sharing and collaboration tools for knowledge sharing among automotive shop owners. Resources for Business Improvement (00:18:58) Introduction to automotive management network resources such as SOPs and checklists for business advancement. Note-Taking and Organization (00:20:00) Personal experiences with note-taking and strategies for managing notes effectively in a business context. Using Google Docs for Accountability (00:23:22) How Google Docs can facilitate accountability by allowing team members to log and review action plans collaboratively. Networking and Community Support (00:27:02) Encouragement for members to utilize networking tools like Slack for better communication and support among peers. Understanding Employment Law (00:30:33) Insights into Canadian employment law regarding severance and the importance of having employment contracts to protect business owners. Understanding Severance Costs (00:32:12) Discussion on the financial impact of severance costs and the importance of understanding net income. Calculating Impact on Sales (00:33:13) Exploration of how to calculate necessary sales to cover losses in the automotive industry. Networking and Sharing Solutions (00:34:11) Importance of sharing experiences and...

Explore the challenges and innovations in cross-platform collaboration as Tom Hadfield, CEO of Mio, discusses how his company is bridging the communication gap between Google Workspace and other collaboration tools on SADA's Cloud and Clear podcast. This episode delves into the importance of chat interoperability and how Mio is enabling enterprises to overcome the hurdles of mergers, acquisitions, and diverse tech environments. Tom offers valuable insights on leveraging Mio to enhance generative AI capabilities by integrating data across platforms. This conversation is a must-listen for IT leaders focused on breaking down silos in their collaboration stacks. Don't miss this engaging discussion on the future of cloud security, AI, and strategic enterprise communication. Stay tuned for more content by liking, sharing, and subscribing!  

David Greenspan, founder of BLUECASE, has a PhD in High-Performance Psychology. He specializes in empowering leaders and fast-moving organizations to build great companies and achieve exceptional results.Welcome you to Change Ready, an original series brought to you by Behind the Human & Malosi. A series where we do everything possible to future-proof your mind and thrive in an era of unprecedented change. ___How Prepared is Your Team for the Next Big Disruption? Future-proof your team with Malosiminds.com Get your copy of Personal Socrates: Better Questions, Better Life Connect with Marc >>> Website | LinkedIn | Instagram | Twitter Drop a review and let me know what resonates with you about the show!Thanks as always for listening and have the best day yet!*A special thanks to MONOS, our official travel partner for Behind the Human! Use MONOSBTH10 at check-out for savings on your next purchase. ✈️*Special props

In this episode of YourTechReport on SiriusXM, host Marc Aflalo delves into the world of business communication with Sandeep Panesar, the strategic alliances and channel partnerships lead at Selectcom Telecom. Together, they explore the remarkable journey from the reliance on copper lines to the innovative era of Voice over IP (VoIP). Sandeep provides a comprehensive overview of how Selectcom Telecom is at the forefront of this evolution, offering a fully managed business voice solution that leverages the power of WebEx Calling. This solution not only integrates seamlessly with popular collaboration tools like Zoom and Microsoft Teams but also ensures secure and professional communication for businesses of all sizes. The conversation highlights the cost-saving benefits of moving away from traditional phone systems, the importance of uninterrupted communication, and the potential pitfalls of over-reliance on cellular networks. Sandeep emphasizes the reliability and uptime guarantees that Selectcom's solution provides, backed by a Tier 1 provider's infrastructure. Marc and Sandeep also discuss the critical questions businesses should consider when evaluating their communication needs, underscoring the value of a robust and flexible communication system in today's fast-paced business environment. You can learn more about Selectcom Telecom at www.selectcomtelecom.ca Follow Sandeep Panesar on all social platforms @intosandeep. Chapters 00:00 The Evolution of Business Phone Systems 01:25 The Benefits of Voice over IP 03:49 Why Choose a Premium Business Solutions Provider Keywords: Business Communication, Selectcom Telecom, Copper Lines, VoIP, WebEx Calling, Collaboration Tools, Security, Professional Communication, Cost Savings, Uptime Guarantee, Sandeep Panesar, Marc Aflalo, Your Tech Report. Learn more about your ad choices. Visit megaphone.fm/adchoices

Clarity, Calendar Management, Consistency, Creative Organization, Communication, Collaboration Tools, Constraints, Cleanliness, Course Correction, Categorization, Cycles, Capture, Colour, Colour coding, Coding, Customizing, Custom-made solution, Chunking, Calendars, Collecting (info), Close things, Creativity, Coherence, Challenge, Calm, Cool & Collected... Continue reading →

The show features a comprehensive discussion on the state of the marketing industry with Brooke MacClean from MarketWake. The conversation covered the emergence of intermediaries in agency-CEO relationships, the need for a balance between creativity and data analytics, and the challenges of short-term contracts and industry fragmentation. The importance of building strong client relationships and the benefits of in-person meetings were also emphasized. Brooke advocated for selective client partnerships and strategic growth, highlighting the limitations of AI and the value of human insight in marketing. The acquisition of Punch List, a collaboration tool, was discussed as a strategic move to streamline project management and improve efficiency. The hosts and Brooke also speculated on the potential impact of an economic downturn on various sectors, with concerns about the restaurant and banking industries. They stressed the need for agencies to be transparent about their capabilities and to avoid roles like “fractional CMO,” which may lack commitment. Overall, the show called for leadership, collaboration, and a forward-thinking approach to navigate the complexities of the marketing landscape. Key Takeaways: The importance of balancing creativity with data analytics in marketing. Strategies for navigating potential economic downturns and their impact on different sectors. The role of strong client relationships and the benefits of in-person meetings. Insights into the acquisition of Punch List and its benefits for project management. The concept of “fractional CMO” and the challenges it presents. Keywords: Marketing Strategy, Client Relationships, Economic Downturn, Creativity, Data Analytics, Project Management, Collaboration Tools, Agency Fragmentation, Marketing Industry, Punch List, MarketWake, Fractional CMO https://www.nick-constantino.com/unveiling-the-marketing-matrix/  patreon.com/TheMarketingMadMen: https://www.nick-constantino.com/See omnystudio.com/listener for privacy information.

Send Katie a Text Message!! Your design business will grow faster, go further, and be more successful when you embrace 2 things: collaborations and technology. You may not want to admit it, but AI is here to stay! It can even have a positive impact on your firm—if you let it. And that's just one collaboration you can engage in! There's also the opportunity to join professional organizations which can keep you inspired, get you out of creative burnout, or provide educational resources. If you're curious about how collaboration and technology can benefit your business, you will not want to miss this episode with Jenny Cano! Stick around for the Coaching Corner where I'm sharing my own insecurities around collaboration and competition. Enjoy the conversation!In this episode, you will be able to:Discover how a collaborative mindset is propelling designers to become 7-figure business owners.Uncover the best way to move past the fear of technology for the sake of your firm.Learn how to strategically use collaboration and technology tools to grow your business. Full Show Notes Here!

Managing technology has never been more challenging. HBR IdeaCast's new special series, Tech at Work, offers research, stories, and advice to make technology work for you and your team. This week: how your team can get the most out of digital collaboration tools.

In this episode, Russ Summers, who heads marketing for Quantified, shares insights into leveraging generative AI to boost productivity and creativity within sales and marketing roles. Having built a 'GP team' of custom GPTs, Russ has tripled his output, illustrating how AI can serve as virtual team members for tasks ranging from webinar content creation to specialized knowledge acquisition. Through personal anecdotes and exploratory conversations, the episode delves into the process of building AI team members, the importance of play in learning and innovation, and strategies for incorporating AI into personal and professional growth. Highlights include building AI with specific skills sets like 'Wendy Webinar' and 'Roger RevOps,' and the philosophical implications of personifying AI for better engagement and output. Moreover, Russ's personal journey from a layoff to pioneering AI productivity tools opens a discussion on the transformative power of AI in the modern workplace. 00:00 Meet Russ Summers: The One-Man Marketing Powerhouse01:42 Introducing Wendy Webinar: A GPT Team Member Revolutionizing Content Creation03:42 Leveling Up with GPT: Beyond Basic Task Automation05:18 Roger RevOps: A Custom GPT for Niche Expertise08:07 Exploring the Next Frontier: Collaborative and Mentorship GPTs14:25 The Art of Building and Utilizing GPT Staff: Tips and Tricks22:27 Expanding the Team: Integrating GPTs into Human Workflows23:42 Exploring Organizational Progress and Tool Adoption25:25 The Importance of Measuring Effort and Encouraging Experimentation26:50 Fostering Creativity and Psychological Safety in the Workplace29:06 Personifying Bots for Better Engagement and Output31:42 Reimagining Brand Communication in a Conversational World34:58 The Transformative Power of Play and Exploration38:43 Strategies for Personal and Professional Growth with GPT47:54 Concluding Thoughts on Innovation and the Future of Work For more prompts, tips, and AI tools. Check out our website: https://www.beyondtheprompt.ai/ or follow Jeremy or Henrik on Linkedin:Henrik: https://www.linkedin.com/in/werdelinJeremy: https://www.linkedin.com/in/jeremyutley Show producer: Natja Rosner (nat@dreamingincolors.com)

Successful entrepreneurs, like our guest Jon Matzner, realize the power of stepping outside their local bounds to find and leverage global talent. Today, Jon sits down with A.J. to discuss how venturing beyond local boundaries can give your business a massive advantage at home. They also talk about Jon's experiences living and working abroad, his transition from government to Main Street business, and his approach to creating leverage in his businesses.About Jon MatznerJon Matzner is an accomplished business leader and former national security professional who divides his time between Dubai, UAE, and San Diego, California. With a rich background in government service—specifically in counter-terrorism and non-proliferation strategies—Jon brings a global perspective to his business pursuits. Since transitioning from the public sector, he has launched, acquired, and sold several businesses, demonstrating his passion for entrepreneurship through acquisition. Jon focuses on improving businesses by hiring top talent from abroad. He aims to modernize traditional industries using AI and help from workers from around the world. He also Jon shares his insights and experiences through his free newsletter, 'Lazy Leverage,' and his X profile.Strategies for tapping into global talent for business efficiencyThe internet boom and rise of remote work have erased geographical barriers and made it easier than ever to hire worldwide, tap into foreign markets, and source products and services from all around the globe. Here are some ways you can maximize your efficiency with global talent:Delegate Non-essential Tasks: Global talent can manage operational activities efficiently, freeing your time for strategic development.Conduct a Time Audit: Know where your time goes. A time audit can reveal tasks better suited for remote talent, thereby refining your focus on high-impact responsibilities.Choose the Right Tools for Collaboration: Tools like Notion are very useful, but it's all about finding what works for your team.Invest in Training and Development: There is so much more to global teams than just virtual assistant tasks or data entry. They can be much more than that if you take the right steps to unlock their potential. Providing resources and training them will be a good return on investment because they'll improve your company's efficiency and competitive edge.Set Clear Expectations and Goals: Ensure every team member understands their role, the quality of work expected, and the deadlines. This clarity helps in managing projects more smoothly across different time zones.Remote work allows businesses to tap into global opportunities like never before. With effective collaboration tools, good resources, and clear expectations, you can greatly improve your business efficiency. The above strategies help optimize your operations and equip your business to stay ahead in a globally competitive environment.Key Insights:Keep reinventing yourself. Whether it's learning a new skill or just finding a different approach to everyday tasks, self-improvement is key for every individual. But this also has a positive impact on your business. When you're learning and growing, you bring new perspectives and solutions to your work. This ultimately leads to innovative products, better services, and more efficient processes.Choose high-return business opportunities. Jon suggests prioritizing high-leverage activities like creating scalable systems or automating processes if you want to multiply your returns over time. This will ultimately give you more time to focus on your other ventures or priorities in life but still keep your business running smoothly.Always start with the problem. Instead of obsessing over groundbreaking ideas, focus on identifying a problem that your customers have. Do this through customer surveys, market research, social media, or competitor analysis to get to the core problems of your audience. Otherwise, you run the risk of creating a product or service without a clear audience or purpose. Build a global team. People from different backgrounds tend to approach problems and challenges uniquely. They can bring diverse and creative solutions to the table, which helps your business stay innovative. This diversity also makes your business more agile and gives you a substantial competitive advantage in your local market.Build your media leverage. Grow your brand by being active on social media, running a value-packed blog, sending out interesting newsletters, and creating other types of content. These tools can help increase your visibility, position you as an industry expert, and ultimately ensure you're never out of work.Jon's best advice for entrepreneurs:“I don't think of this as outsourcing. Outsourcing implies that you're throwing it over the fence, and it's no longer a part of your company. [...] No, this isn't outsourcing; this is building a global team.”Connect with Jon:XLinkedInResources Mentioned:Lazy Leverage NewsletterBuy Back Your Time by Dan MartellFollow Beyond 8 Figures:LinkedinTwitterWebsiteAffiliate Disclaimer: Some links in this episode are affiliate links. If you make a purchase through these links, we may earn a commission at no extra cost to you. Rest assured, we only promote products/services we believe will benefit your entrepreneurial journey.

Dave and Andy discussed the following topics. Swatting! Police Arrest Teen Said to Be Linked to Hundreds of Swatting Attacks CISA's Easterly the target of ‘harrowing' swatting incident Nikki Haley targeted in 'swatting' incident at her home Physical Security.  Cleveland Clinic confiscated 30K weapons last year Security guard accused in Edmonton city hall shooting makes court appearance   DOJ: Justice Department and the FTC Update Guidance that Reinforces Parties' Preservation Obligations for Collaboration Tools and Ephemeral Messaging FTC: FTC and DOJ Update Guidance That Reinforces Parties' Preservation Obligations for Collaboration Tools and Ephemeral Messaging Risky Biz News: DOJ and FTC tell companies to stop deleting chats   Artificial Intelligence (AI) and Investment Fraud: Investor Alert UK NCSC: Global ransomware threat expected to rise with AI, NCSC warns UK NCSC: The near-term impact of AI on the cyber threat. British intelligence warns AI will cause surge in ransomware volume and impact CISA Joins ACSC-led Guidance on How to Use AI Systems Securely UK NCSC: The near-term impact of AI on the cyber threat NZ NCSC: Joint Guidance: Engaging with Artificial Intelligence OpenAI and Other Tech Giants Will Have to Warn the US Government When They Start New AI Projects Fact Sheet: Biden-⁠Harris Administration Announces Key AI Actions Following President Biden's Landmark Executive Order OpenAI Quietly Scrapped a Promise to Disclose Key Documents to the Public   23andMe admits it didn't detect cyberattacks for months Ransomware-palooza! Symantec - The 2024 Ransomware Threat Landscape Annual GRIT Ransomware Report – 2023 Dragos Industrial Ransomware Analysis: Q4 2023 Who pays, and why: A researcher examines the ransomware victim's mindset The Conjoined Triangle of Ransomware Ransomware Attacks Spotlight Need for FIs to Gauge Third-Party Risk Water Sector ransomware and other updates: Veolia Responds to Cyber Incident – company statement Water services giant Veolia North America hit by ransomware attack Water facility operator says ransomware attack affected North America division Chairs Rodgers and Carter Announce Subcommittee Hearing on Ensuring Cybersecurity of America's Drinking Water Systems CISA's Water Sector Guide Puts Incident Response Front & Center WaterISAC: 15 Security Fundamentals You Need to Know West Virginia Department of Health Takes Steps to Prevent Cyberattacks Against Water Systems   Quick Hits: In major gaffe, hacked Microsoft test account was assigned admin privileges Florida Bill Seeks Safe Harbor for Organizations with Robust Cybersecurity Programs HHS Releases New Voluntary Performance Goals to Enhance Cybersecurity Across the Health Sector and Gateway for Cybersecurity Resources NCTC First Responder's Toolbox: Responses to Overseas Conflicts May Impact Public Safety Agencies in the Homeland Mother of all breaches - a historic data leak reveals 26 billion records: check what's exposed UK tells business leaders to ‘toughen up' against cyberattacks CISA Blog: We Must Consider Software Developers a Key Part of the Cybersecurity Workforce Guidance: Assembling a Group of Products for SBOM

Real-time, synchronized collaboration across your favorite app experiences and devices with Microsoft Loop, our Microsoft 365 co-creation app. Use Loop components to work fluidly with others, while staying in your favorite collaboration app for a connected and interactive experience. Content is always live and up-to-date. View and organize all your loop activity, and provide a collaborative shared workspace for everyone to work together across projects using the Loop app. Generative AI with Microsoft 365 Copilot is integrated throughout the experience to help generate content without starting from scratch.    Derek Liddell, Principal PM Manager for Microsoft Loop shares the latest user updates, and configuration, data security, and compliance controls for Microsoft 365 admins.   ► QUICK LINKS: 00:00 - New co-creation app, Microsoft Loop 01:10 - Loop app experience 02:43 - Sharing experience in Loop 04:13 - Loop-powered collaborative notes in Teams 04:53 - Project management experience 05:52 - Admin experience07:06 - Controls and policies, and Conditional Access 08:56 - Wrap up   ► Link References Try it out at https://loop.microsoft.com  Stay up to date on admin capabilities at https://aka.ms/LoopCompliance   ► Unfamiliar with Microsoft Mechanics? As Microsoft's official video series for IT, you can watch and share valuable content and demos of current and upcoming tech from the people who build it at Microsoft. • Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries • Talk with other IT Pros, join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog • Watch or listen from anywhere, subscribe to our podcast: https://microsoftmechanics.libsyn.com/podcast   ► Keep getting this insider knowledge, join us on social: • Follow us on Twitter: https://twitter.com/MSFTMechanics  • Share knowledge on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/ • Enjoy us on Instagram: https://www.instagram.com/msftmechanics/ • Loosen up with us on TikTok: https://www.tiktok.com/@msftmechanics  

Theta Lake's Co-founder and CEO, Devin Redmond, joins UC Today's Rob Scott in this exclusive interview.Devin shares insights from his daily interactions with customers who are blazing the trail on modern collaboration leveraging Microsoft Teams - to deliver happier end-users, and ultimately greater competitive advantage for their organization.

Kate & Ryan discuss the various remote collaboration tools such as Mural, Miro, Klaxon and MS Whiteboard and how they can enhance your meeting or presentation!

In today's digital age, remote team collaboration has become more prevalent and crucial than ever. For clients and virtual assistants (VAs) working together from different locations, effective collaboration is essential for productivity and achieving shared goals. In this blog post, we'll explore recommended tools and strategies that facilitate seamless collaboration between clients and virtual assistants. See below for my list of tools (and listen to hear what I have to say about them!).1. Communication Tools:SlackMicrosoft TeamsZoomSkype2. Project Management Tools:TrelloAsanaMonday.comClickUp3. File Sharing and Collaboration:Google Workspace (formerly G Suite)Microsoft 365DropboxNotion4. Video Conferencing and Screen Sharing:ZoomMicrosoft TeamsGoogle Meet5. Task Management and Delegation:TodoistClickUpTeamwork6. Time Tracking and Productivity Monitoring:TogglClockifyHubstaff7. Document Version Control:GitHubBitbucketGoogle Workspace8. Knowledge Sharing and Documentation:NotionConfluenceGoogle Workspace9. Regular Check-Ins10. Clear Guidelines and Expectations11. Feedback and Recognition______________________________You can find me here:Instagram: @gingerbizWebsite: https://www.katymurrayphotography.com/Facebook: https://www.facebook.com/groups/TipsandTricksforyourbusinessTwitter: https://twitter.com/GingerBizKM

Viirtue and TeamMate partnership deliver best of both worlds, UCaaS functionality and Teams collaboration tools, MSPs encouraged to take hybrid approach to Teams and UCaaS “We turn Microsoft Teams into a softphone that has all the features of UCaaS of Viirtue piped through, through our integration with Viirtue, so really get the best of both worlds,” says Eric Hernaez of TeamMate Technology. “Although Teams is a phenomenal collaboration tool, Microsoft phone system might not fill all the needs and compare, on an apples-to-apples basis with a true UCaaS system that has been built for that purpose as Viirtue has. So, with a tool like TeamMate, a Viirtue reseller can say… you don't have to give up the great features you are using in UCaaS just to use Teams as your interface to make phone calls.” “There's a myth out there that folks have to buy Teams in its native form and that works best,” adds Dan Rosenrauch of Viirtue. The way Teams works best, if you're going to use it as your call control platform, is when you're able to pull in all those complex features, whether it's things like contact centers, spoken IVR, more complex call routing that Microsoft can't (natively) support, or if you're just going to provide the telephony.” Rosenrauch argues that a hybrid approach to selling these solutions, combining both, is what Viirtue's most successful resellers take. The TeamMate PBX Connector is a unique add-on to Microsoft Office 365 which allows you to natively integrate any existing PBX Phone System into Microsoft Teams. It activates the Calls dial-pad in Microsoft Teams as a softphone on an external PBX, effectively turning Teams into a softphone. As a leading UCaaS provider, Viirtue offers innovative solutions with both wholesale and retail through agent partner and white label partner programs. “This is a long-time brewing,” says Rosenrauch about the partnership and the deepening integration of the two company's offerings. In this podcast we learn about the partnership's go to market strategy, which entered on making things easier for partners, and seamless for the end customer. Visit Viirtue Visit TeamMate Technology  

This episode of This Week in Enterprise Tech discusses the latest issues around AI, including legal implications, security concerns, and practical applications. Lucid Software Chief Product Officer Dan Lawyer joins hosts Curt Franklin, Brian Chee, and Oliver Rist to explain how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities. Recent phishing campaign targeting Zimbra customers in over a dozen countries AI requiring changes to data center heat dissipation strategies Verizon expanding 5G coverage using newly available C-band 5G spectrum White House again telling executive branch to take cybersecurity seriously Potential NY Times lawsuit against OpenAI over ChatGPT training on copyrighted content Lucid Software's Chief Product Officer Dan Lawyer explains how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities, and streamlining the HR onboarding process. Hosts: Brian Chee and Curtis Franklin Co-Host: Oliver Rist Guest: Dan Lawyer Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT panoptica.app

This episode of This Week in Enterprise Tech discusses the latest issues around AI, including legal implications, security concerns, and practical applications. Lucid Software Chief Product Officer Dan Lawyer joins hosts Curt Franklin, Brian Chee, and Oliver Rist to explain how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities. Recent phishing campaign targeting Zimbra customers in over a dozen countries AI requiring changes to data center heat dissipation strategies Verizon expanding 5G coverage using newly available C-band 5G spectrum White House again telling executive branch to take cybersecurity seriously Potential NY Times lawsuit against OpenAI over ChatGPT training on copyrighted content Lucid Software's Chief Product Officer Dan Lawyer explains how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities, and streamlining the HR onboarding process. Hosts: Brian Chee and Curtis Franklin Co-Host: Oliver Rist Guest: Dan Lawyer Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT panoptica.app

This episode of This Week in Enterprise Tech discusses the latest issues around AI, including legal implications, security concerns, and practical applications. Lucid Software Chief Product Officer Dan Lawyer joins hosts Curt Franklin, Brian Chee, and Oliver Rist to explain how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities. Recent phishing campaign targeting Zimbra customers in over a dozen countries AI requiring changes to data center heat dissipation strategies Verizon expanding 5G coverage using newly available C-band 5G spectrum White House again telling executive branch to take cybersecurity seriously Potential NY Times lawsuit against OpenAI over ChatGPT training on copyrighted content Lucid Software's Chief Product Officer Dan Lawyer explains how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities, and streamlining the HR onboarding process. Hosts: Brian Chee and Curtis Franklin Co-Host: Oliver Rist Guest: Dan Lawyer Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT panoptica.app

This episode of This Week in Enterprise Tech discusses the latest issues around AI, including legal implications, security concerns, and practical applications. Lucid Software Chief Product Officer Dan Lawyer joins hosts Curt Franklin, Brian Chee, and Oliver Rist to explain how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities. Recent phishing campaign targeting Zimbra customers in over a dozen countries AI requiring changes to data center heat dissipation strategies Verizon expanding 5G coverage using newly available C-band 5G spectrum White House again telling executive branch to take cybersecurity seriously Potential NY Times lawsuit against OpenAI over ChatGPT training on copyrighted content Lucid Software's Chief Product Officer Dan Lawyer explains how Lucid's visual collaboration tools aim to improve teamwork through integrating AI capabilities, and streamlining the HR onboarding process. Hosts: Brian Chee and Curtis Franklin Co-Host: Oliver Rist Guest: Dan Lawyer Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT panoptica.app

Are you drowning in endless emails, constantly interrupted by Slack notifications, and suffering from Zoom fatigue? In this episode, Jennifer Smith, CEO of Scribe, will help you break free from collaboration overload and reclaim your work-life balance. Discover the hidden dangers of remote collaboration, the surprising reasons why productivity tools may be working against you, […]

In this show, Derek Liddell, an engineering leader from the Loop team at Microsoft presents the end-to-end experiences with the new Microsoft Loop app, available both on the web and in mobile. The Loop app is a transformative co-creation experience that brings together teams, content, and tasks across your tools and devices. It gives you a central place to bring people together to create real-time content in a simple, collaborative and structured way, from using intelligent search to build your first shared workspaces, where you can enjoy super-fast synchronized collaboration to leveraging AI with Copilot in Loop, to generate ideas with others on your team to get in your flow. Copilot capabilities in Loop will begin rolling out in the next few months.  If you're using Loop components today, you might familiar with how you can embed live, auto-updating content seamlessly across apps like Microsoft Teams, Outlook email, Word and even the Whiteboard - all from the same source, freeing you up to work in your preferred collaboration modality. The Loop app builds on this and gives you a new hub to create and find all of your shared Loop components, workspaces, and pages. ►QUICK LINKS: 00:00 - What is Microsoft Loop? 00:30 - Loop components in Microsoft Teams, Outlook, and Word 01:28 - The new Microsoft Loop app 01:39 - Getting started with Loop  04:47 - Working with others in their preferred apps 06:45 - Using AI with Copilot to generate and refine content 09:28 - Notifications, getting back to your Loop components, and ideas 10:09 - Wrap up ► Link References: Start using Loop at https://loop.microsoft.com Get the mobile app at https://aka.ms/getLoopmobile Admin steps to enable at https://aka.ms/enableLoop ► Unfamiliar with Microsoft Mechanics? As Microsoft's official video series for IT, you can watch and share valuable content and demos of current and upcoming tech from the people who build it at Microsoft. • Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries • Talk with other IT Pros, join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog • Watch or listen from anywhere, subscribe to our podcast: https://microsoftmechanics.libsyn.com/podcast ► Keep getting this insider knowledge, join us on social: • Follow us on Twitter: https://twitter.com/MSFTMechanics • Share knowledge on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/ • Enjoy us on Instagram: https://www.instagram.com/msftmechanics/ • Loosen up with us on TikTok: https://www.tiktok.com/@msftmechanics 

Information governance, or IG, is the new term (and then some) for records management—now encompassing the entire life cycle of information from creation to disposition. Dennis and Tom talk lawyers through the basics of an effective IG framework and the need for us to understand up-to-date best practices and legal obligations for data privacy, security, litigation readiness, and, eventually, disposal of information. The guys also discuss AI developments in IG and its potential within future systems. Later, how would you like to have Dennis and Tom's answer to any and every collaboration question you could think of? The guys discuss the possibility of developing a GPT3 chatbot fluent in The Lawyer's Guide to Collaboration Tools and Technologies: Smart Ways to Work Together. As always, stay tuned for the parting shots, that one tip, website, or observation you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for answers to your most burning tech questions. Mentioned in This Episode: A Segment: Contoural Webinars MER Sapient ACEDs B Segment: Creating a ChatGPT Chatbot out of our book Pick a Book to Talk to Parting Shots: Vacay

Information governance, or IG, is the new term (and then some) for records management—now encompassing the entire life cycle of information from creation to disposition. Dennis and Tom talk lawyers through the basics of an effective IG framework and the need for us to understand up-to-date best practices and legal obligations for data privacy, security, litigation readiness, and, eventually, disposal of information. The guys also discuss AI developments in IG and its potential within future systems. Later, how would you like to have Dennis and Tom's answer to any and every collaboration question you could think of? The guys discuss the possibility of developing a GPT3 chatbot fluent in The Lawyer's Guide to Collaboration Tools and Technologies: Smart Ways to Work Together. As always, stay tuned for the parting shots, that one tip, website, or observation you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for answers to your most burning tech questions. Mentioned in This Episode: A Segment: Contoural Webinars MER Sapient ACEDs B Segment: Creating a ChatGPT Chatbot out of our book Pick a Book to Talk to Parting Shots: Vacay

The votes are in (all two of ‘em!), and Dennis and Tom agree that Microsoft Teams wins the best collaboration software award by a landslide. It's been awhile since the guys have highlighted Teams tips and tricks, so tune in for up-to-date, magical insights that can turn you into a Teams wizard in no time. Later, in keeping with the spooky season, Dennis and Tom creep through the Google product graveyard. The Big G is well known for snuffing out its own creations, much to the dismay of users, so the guys examine the whys and wherefores of these murders and whether you should hesitate to invest your time into new Google offerings. As always, stay tuned for the parting shots, that one tip, website, or observation you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for answers to your most burning tech questions. Mentioned in This Episode: A Segment: Tips to Make You a Microsoft Teams Wizard The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition Mike Tholfson on YouTube Microsoft Teams Adoption B Segment: The Google Graveyard  Killed by Google Parting Shots: 7 Mesh Router Mistakes to Avoid 2022 LTN Tech Survey

The votes are in (all two of ‘em!), and Dennis and Tom agree that Microsoft Teams wins the best collaboration software award by a landslide. It's been awhile since the guys have highlighted Teams tips and tricks, so tune in for up-to-date, magical insights that can turn you into a Teams wizard in no time. Later, in keeping with the spooky season, Dennis and Tom creep through the Google product graveyard. The Big G is well known for snuffing out its own creations, much to the dismay of users, so the guys examine the whys and wherefores of these murders and whether you should hesitate to invest your time into new Google offerings. As always, stay tuned for the parting shots, that one tip, website, or observation you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for answers to your most burning tech questions. Mentioned in This Episode: A Segment: Tips to Make You a Microsoft Teams Wizard The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition Mike Tholfson on YouTube Microsoft Teams Adoption B Segment: The Google Graveyard  Killed by Google Parting Shots: 7 Mesh Router Mistakes to Avoid 2022 LTN Tech Survey

Dennis and Tom's new book, “The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition,” is available now! Debbie Foster hosts this episode to chat with Dennis and Tom about their writing process for this new edition and specific tools lawyers need to make the most of modern legal practice.  As always, stay tuned for the parting shots, that one tip, website, or observation that you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for the answers to your most burning tech questions. Show Notes - Kennedy-Mighell Report #323 A Segment: Debbie Foster Interviews Dennis and Tom The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition https://www.americanbar.org/products/inv/book/424883450/ B Segment: Interview, Part II  Parting Shots: Calendly - https://calendly.com/  Law Department Innovation Library - https://www.ldilibrary.com 

More likely than not, your tech stack isn't enabled to its greatest functionality. Why? Well, sometimes you just don't know what you don't know. Dennis and Tom talk about maximizing the potential your tools, platforms, apps, and software have to interact more collaboratively to improve the day-to-day operations of your law firm. Connecting your components improves not only your human interactions, but lets your technologies work together to their greatest capabilities.  Though not yet widely available, Twitter's edit function is out in the wild for a small group of users. The guys put this edit button through their “Hot or Not?” filter, considering the negative and positive possibilities enshrouded in an editable tweet.  As always, stay tuned for the parting shots, that one tip, website, or observation that you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for the answers to your most burning tech questions. Mentioned in This Episode Segment A: The Collaboration Layer of Your Technology Stack The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition https://www.americanbar.org/products/inv/book/424883450/ Segment B: Hot or Not - Twitter's New Edit Function https://www.theverge.com/2022/9/3/23335692/twitter-edit-button-platform-bluesky  Parting Shots: Movemap - https://www.movemap.io/explore/us LTRC Roundtable Discussion: Personal Knowledge Management https://www.lawtechnologytoday.org/2022/08/ltrc-roundtable-discussion-personal-knowledge-management/ 

The concept of the workplace has evolved rapidly over the past two years, and many are now opting for a hybrid work approach rather than a complete return to the office. Does this choice work? Yes–as long as your collaboration tools are on point! Collaboration connoisseurs Dennis and Tom talk through effective strategies for communication, socialization, and remote workspaces to help today's hybrid workers thrive.  Find out more in their latest book: The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition Later, on “Hot or Not?” – the guys chat about whether legal tech conference hashtags are still “a thing” or trè passé.  As always, stay tuned for the parting shots, that one tip, website, or observation that you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for the answers to your most burning tech questions. Mentioned in This Episode A Segment: Collaborating in Hybrid Environments The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition https://www.americanbar.org/products/inv/book/424883450/ B Segment: Hot or Not - Hashtags at Legal Technology Conferences Parting Shots: Google Pixel Buds Pro - https://store.google.com/product/pixel_buds_pro?hl=en-US  ThoughtTrace - https://www.thoughttrace.com/ PatternBuilder - https://www.netdocuments.com/resource/patternbuilder-document-and-workflow-automation

It's here! The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition just dropped, so your favorite authors/podcast co-hosts are giving listeners the inside scoop on how this new edition helps lawyers make smarter choices for home-based legal practice. Later on, Dennis and Tom bring back their Hot or Not? segment to analyze whether foldable devices are cool or just plain silly. As always, stay tuned for the parting shots, that one tip, website, or observation that you can use the second the podcast ends. Have a technology question for Dennis and Tom? Call their Tech Question Hotline at 720-441-6820 for the answers to your most burning tech questions. Mentioned in This Episode: A Segment: What's the Latest in Collaboration Tools & Technologies The Lawyer's Guide to Collaboration Tools & Technologies: Work From Home Edition https://www.americanbar.org/products/inv/book/424883450/ B Segment: Hot or Not - Foldable Devices? Galaxy Z Fold 4 - https://www.samsung.com/us/smartphones/galaxy-z-fold4/ Galaxy Z Flip 4 - https://www.samsung.com/us/smartphones/galaxy-z-flip4/ Parting Shots: Deepl https://www.deepl.com/translator What to do when a friend's Facebook account is hacked or duped - https://www.online-tech-tips.com/computer-tips/what-to-do-when-a-friends-facebook-account-is-hacked-or-duped/

673: In this interview, Thomas Kurian, Chief Executive Officer of Google Cloud, discusses the future ahead for cloud technology. He begins with an assessment of where we as a society are currently in the evolution of cloud computing and how Google's Cloud Platform differs from the rest of the players in the space. Thomas then describes Google's ambitious mission of training 40 million people on cloud technology, why it's important, and how Google plans on achieving it. Finally, Thomas looks ahead at the future of work and the role technology and collaboration tools will play in managing a hybrid workforce.

673: In this interview, Thomas Kurian, Chief Executive Officer of Google Cloud, discusses the future ahead for cloud technology. He begins with an assessment of where we as a society are currently in the evolution of cloud computing and how Google's Cloud Platform differs from the rest of the players in the space. Thomas then describes Google's ambitious mission of training 40 million people on cloud technology, why it's important, and how Google plans on achieving it. Finally, Thomas looks ahead at the future of work and the role technology and collaboration tools will play in managing a hybrid workforce.

Unified communication and collaboration (UCC) is central to the way people work and interact in the world today. How can partners participate more broadly in the marketplace to grow their business?  Shelby Skrhak speaks with Stephen Yochum , Director of UCC at Ingram Micro, about:  - What is UCC and how is it changing - PLANS - How Ingram Micro assists customers with challenges  Visit Ingram Micro's Unified Communications and Collaboration or email UCC for more information.  To join the discussion, follow us on Twitter @IngramTechSol #B2BTechTalk  Listen to this episode and more like it by subscribing to B2B Tech Talk on Spotify , Apple Podcasts , or Stitcher . Or, tune in on our website.