Podcasts about Seman

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'

Semanário Expresso escreve que um em cada quatro vídeos publicados pelo presidente do Chega no TikTok é sobre estas duas minorias. Público, JN e DN dão destaque à saúde.See omnystudio.com/listener for privacy information.

Semanário Expresso escreve que um em cada quatro vídeos publicados pelo presidente do Chega no TikTok é sobre estas duas minorias. Público, JN e DN dão destaque à saúde.See omnystudio.com/listener for privacy information.

Kur'ân-ı Azimüşşan'da: “Eğer gökte ve yerde Allâhü Tealâ'dan başka ilâhlar olsaydı, gök ve yer harap (viran) olurdu (bozulurdu)” (Enbiya s. 22) buyuruluyor. Cenâb-ı Allâh'ın ortağı yoktur, O'nun gayrisinde ilâhlar yoktur. Semanın ve yerin de harap olması, bozulması bahis konusu değildir. Kâinat ilâhi nizamlarla devam ederken gerçekleri (İlâhî Kitabın muhteviyatını) kendilerine uydurduklarını sananlar, fâni varlıklara “Tanrı” diyecek kadar ileri gidip egoist ve istismarcı olurlar. İşte bunlar küfre varmışlardır. Halık'ımız hiç bir şeye, hiç bir şey de O (c.c.)'a benzemez. Kur'an-ı Kerim'de: “O'nun (Allâh'ın) hiç bir benzeri yoktur” (Şura s. 11) buyuruluyor.Bir kişi “Ben Allâh (c.c.)'u rüyada yani uykuda gördüm, işte Allâh (c.c.) öyledir veya böyledir” demiş bulunsa, kâfir olur. Cenâb-ı Allâh'ın va- adini, hayr-u affını, mükâfatini ve vaidini, âsiye ikabını, cezasını inkâr eden kâfir olur. Cenâb-ı Allâh dilerse afv eder, dilerse ikab eder. Bir kimse “Allâh (c.c.) şu şeyi bilmez veya şu şeye gücü yetmez” demiş olsa, kâfir olur. Kur'an-ı Azimüşşan'da: “Şüphesiz Allâh her şeyi bilicidir ve her şeye gücü yetendir” (Nahl s. 70) buyuruluyor. Bir kimse Allâhü Tealâ Hazretlerini lâyık olmayan şeylerle vasıflandırsa, yahut Allâh (c.c.)'un isimlerinden bir ismi yahut emirlerinden bir emri veya O (c.c.)'un vadini veya vaidini istihza etse, kâfir olur. Bir kişi, “Dünyada uyanık olduğum halde, Cenabı Allâh'ı açıktan meydanda gördüm, bana ağzından konuşup söyler” demiş olsa kâfir olur. Cenâb-ı Allâh'ın beden unsurları gibi organları, eli, ayağı var diyen ve böyle bir inançta bulunan kimse kâfir olur . İnsan Cenâb-ı Allâh'ın künhünü bilmekle mükellef ve memur değildir. Biz O (c.c.)'un râhmetinin eserlerini düşünmek, güzel isimlerini ve sıfatlarını bilmek, varlığını tasdik etmekle memuruz.(Hüseyin Aşık, Elfaz-ı Küfür, s.49-50)

O vídeo de Felca instalou o tema nacionalmente: a adultização, o lucro na exposição de crianças e os algoritmos das Big Techs. O que o capitalismo patriarcal oferece às crianças? É possível falar de direito à infância em meio ao genocídio na Palestina? Como podemos nos apoiar em Vigotski e Krupskaia para pensar a luta por uma infância plena? Participação ‪@psicologiamarxista‬  Semanário teórico-político Ideias de Esquerda: https://www.esquerdadiario.com.br/IDE Campus Virtual: https://campus.esquerdadiario.com.br Contribua com o Esquerda Diário: http://www.bit.ly/2tdC5VR Acompanhe nas redes sociais! YouTube:    / esquerdadiario   Instagram:   / esquerdadiariooficial   Twitter:   / esquerdadiario   Facebook:   / ideiasdeesquerda Transcrição

Editorial de la seman - El rol de los profetas by CCRTV

Tyler Seman shares how he transitioned from the world of finance and private equity-backed consolidator to building a mission-driven senior care business. Joining Dru Carpenito, he looks back on how this path took him through Entrepreneurship through Acquisition (ETA) before ultimately launching a Hallmark Homecare franchise. Tyler also gets candid about why he chose the senior care space, what surprised him most in his first year, and how he navigates the ramp-up phase as a first-time franchise owner.

Claudio Jacquelin habló de la actualidad de la Iglesia frente al cónclave con el sociólogo y antropólogo, Pablo Seman. Escuchá la entrevista de FM Milenium...

pjuanjpaniagua

Paula Brito Medori, Porto, 1962. Licenciada em Filosofia pela Universidade Católica Portuguesa, especializou-se em comunicação cultural, tendo construído uma carreira sólida na área da imprensa e dos museus. Atualmente, é responsável pelo Gabinete de Comunicação do Atelier-Museu Júlio Pomar, no âmbito da EGEAC. Entre 2011 e 2019, exerceu a mesma função no Museu Nacional de Arte Antiga, onde coordenou campanhas de grande impacto, como “Vamos pôr o Sequeira no lugar certo”, uma das mais bem-sucedidas angariações de fundos para aquisição de património em Portugal. Antes de se dedicar à comunicação institucional, dirigiu e chefiou redações em diversas publicações culturais e científicas, incluindo as revistas L+arte, Arte Ibérica e QUO, bem como a Agenda Cultural de Lisboa. Trabalhou dez anos no jornal Semanário, tendo sido editora das secções Sociedade e Cultura entre outras funções.Links: https://www.ateliermuseujuliopomar.pt/museu/equipa/ https://www.publico.pt/2011/03/16/jornal/portugal-tem-espaco-para-as-revistas-de-arte-21561148 https://baimages.gulbenkian.pt/images/winlibimg.aspx?skey=&doc=178069&img=14522 https://www.researchgate.net/figure/Luiz-Teixeira-de-Freitas-e-Paula-Brito-Medori-MNAC-MC-2015-Fotografia-de-Paulo-Garcez_fig5_311342533 https://observador.pt/2015/10/01/ja-foi-roubado-um-dos-quadros-expostos-na-rua/ https://fundacaojuliopomar.org/wp-content/uploads/2020/05/paula_brito.pdf https://www.publico.pt/2015/12/23/p3/noticia/as-replicas-da-exposicao-comingout-vao-a-leilao-1824980 http://www.museudearteantiga.pt/exposicoes/vamos-por-o-sequeira-no-lugar-certo https://fuel.pt/2015/mnaa/sequeira/ Episódio gravado a 12.02.2025 Créditos introdução: David Maranha - Flauta e percussão Créditos música final: Here Comes The Summer · The Fiery Furnaces EP ℗ The Fiery Furnaces Records Released on 2005-01-25 http://www.appleton.pt Mecenas Appleton:HCI / Colecção Maria e Armando Cabral / A2P / MyStory Hotels Apoio:Câmara Municipal de Lisboa Financiamento:República Portuguesa – Cultura / DGArtes – Direcção Geral das Artes © Appleton, todos os direitos reservados

*Podporte podcast Dobré ráno v aplikácii Toldo na ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠sme.sk/extradobrerano⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Luxusná dovolenka, návšteva u Putina aj spor s Ukrajinou o tranzit plyn dokázali čosi nové: spojili opozíciu, a to vrátane hnutia Slovensko Igora Matoviča či Demokratov. Do toho sa objavil prieskum od NMS, ktorý naznačuje, že opozícia by dokázala poskladať koalíciu - ale tiež s Matovičom. Aké sú tam teda vzťahy a prečo? Tomáš Prokopčák sa v podcaste Dobré ráno pýta Petra Tkačenka. Zdroj zvukov: TA3, Facebook/Igor Matovič Odporúčanie: Dnes odporúčam text nášho kolegu Jána Krempaského Netúžila po pozornosti, hoci nás všetkých prevyšovala. Jedna z obetí štvrtkového útoku na gymnáziu v Spišskej Starej Vsi Mária Semančíková, zástupkyňa riaditeľky bola totiž Jankova spolužiačka. Vo veľmi úprimnom, osobnom a emotívnom texte tak spomína na to, akým bola človekom. – Všetky podcasty denníka SME nájdete na⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ sme.sk/podcasty⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ – Odoberajte aj audio verziu denného newslettra ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ SME.sk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ s najdôležitejšími správami na⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ sme.sk/brifing⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

Al presidente de Jesús, Luz y Vida le acompañarán los presidentes de la Resurrección y la Vera Cruz en esta dirección interina que cesará cuando se produzcan nuevas elecciones

Jeho práca je snom mnohých – veď kto by nechcel vedieť čarovať! My sme však zvedaví, čo vytiahne u nás z čarovného klobúka. Alebo ten sa už dnes nenosí? Čím dokáže zaujať kúzelník v 21.storočí? Aj na to sa pýtala Eva Viteková Jaroslava Semana, ktorý sa kúzleniu venuje takmer štyri desaťročia.

Rýchly technologický vývoj a digitalizácia prináša do kyberpriestoru aj mnohé riziká. V ohrození môžu byť naše najcennejšie informácie a osobné údaje. Novela zákona o kybernetickej bezpečnosti, ktorá by mala platiť od januára 2025, má zvýšiť celkovú kybernetickú bezpečnosť na národnej úrovni. Ochrana osobných údajov a kybernetická bezpečnosť spolu úzko súvisia. O novinkách v týchto dvoch vzájomne prepojených oblastiach sme sa rozprávali s našou odbornou hostkou. Na otázky odpovedala seniorná právna expertka z AK SEMANČÍN & PARTNERS a zároveň predsedníčka Spolku pre ochranu osobných údajov – JUDr. Lucia Semančínová. Aký je súčasný stav ochrany osobných údajov na Slovensku? Ako je na tom Úrad na ochranu osobných údajov, ktorému ešte donedávna hrozil kolaps? Aké najčastejšie porušenia bezpečnostných opatrení pokutoval Úrad za posledný rok? Čo nás čaká v súvislosti s novelou zákona o kybernetickej bezpečnosti? Aké povinnosti pribudnú? Po novom sa bude zákon týkať cca 6 000 subjektov – ktorých napríklad? Ako sa zmenia sankcie? Na čo sa môžeme pripraviť už teraz? Čo odporúča podnikateľom v súvislosti s kyberbezpečnosťou a ochranou osobných údajov? JUDr. Semančínová býva pravidelnou lektorkou aj na odborných konferenciách, tá najbližšia o GDPR bude 12. –13. 6. 2025 (www.profivzdelavanie.sk). Poradca podnikateľa – denne monitorujeme a vysvetľujeme legislatívu. www.pp.sk

En este episodio, Cachorro nos habla sobre: 1st. Lo que aprendimos de la Seman 8: MIN tiene una debilidad grave, Jameis Winston (también) es el mejor QB en dos equipos, Ya nada nos sorprende sobre Patrick Mahomes, Kyle Shanahan necesita a su papá (y DAL de DIOS). 2nd. Un Super Bowl Matchup del que no hemos hablado. Analizamos a BUF y PHI y su crecimiento. …

OPEN HEAVENSMATALA LE LAGI MO LE ASO SA 29 SETEMA 2024(tusia e Pastor EA Adeboye) Manatu Autu: Faaleaga Taunuuga 4 (Destiny Destroyer 4) Tauloto -Tusi Paia–Filipi 3:19“O le malaia, o lo latou i‘uga lea; o le manava, o lo latou atua lea; o le mea latou te vivi‘i ai, o le mea e māsiasi ai lea; e loto i latou i mea a le lalolagi.”Faitauga – Tusi Paia – Faataoto 23:19-21I le faaiuga o la'u a'oa'oga o le mataupu ua taua i luga, o le tasi faaleaga taunuuga autū e toatele tagata e lē iloa, o le na'oai. O le na'oai o le amio ‘a'i e ‘ai ma inu tele. O tagata ‘ai tetele e lē mafai ona taofiofi le fia aai i taimi uma, ua fai le meaai ma a latou faamuamua - pei so latou atua, ma o tagata faapea e lē soifua umi.O le faafoe lelei o lau tausami e taua tele ma o le ala lea o le fai mai o le Tusi Paia I le Fa'ataoto 23:1-2 “‘Āfai lua te nonofo ma se ali‘i e taumafa se ‘ava, se‘ia e matuā mafaufau i mea ‘ua i ou luma; ma e tu‘u atu se polo i lou ua, pe ‘āfai ‘e te se tagata ‘ai tele;”‭‭E le o fai mai le fuaiupu ua taua i luga, o tagata fanaufouina e tatau ona fetagofi e tu'u moni lavā se naifi i o latou ua, leai, fai mai afai e lē mafai ona o latou pulea le ai tetele, tusa pe latou te nonofo I le laulau ma alii sili, ua o latou faia lava e i latou lo latou faasalaga. O loo faamatala mai i le Tusi Paia ia i tatou e ui lava o Tanielu ma ana uo o nisi na filifilia e aai i lea aso ma lea aso I mea taumafa a le tupu, na pulea lo latou fiaaai ma filifili ia aua ne'i fa'aleagaina i latou i meaai. Na o latou filifili e ava i le Atua e ala i le sui o a latou meaai, ma na faamamaluina i latou e le Atua e taui ai i latou (Tanielu 1:1-21).O le tofi o Esau na fa'aleagaina e se ipu meaai; na o le tasi le ipu meaai na mafua ai ona aveesea lona igoa mai le lisi e masani ona o tatou talanoa i ai - o le Atua o Aperaamo, Isaako ma Iakopo. Semanū e lē i ai le igoa o Iakopo a'o Esau, peita'i ua lē mafai ona taofi lona na'omeaai, ma maimau ai lona tofi o le ulumatua (Kenese 25:29-34).O nisi tagata matutua e tausasami i ‘aiga uma e tolu o le asō, ti o le taeao, aiga o le aoauli ma le afiafi, va-i-‘aiga, ma toe aai a o le'i momoe. E faafefea ona maua lou malosi e ala ai i le vaeluaga o le po mo taua fa'aleagaga pe afai e tumu lou manava i meaai ua tau lē mafai ona e tu? E toatele tagata e maliliu laiti ma fa'apu'upu'u ai o latou olaga aua ua soona aai tetele. Ua aai e faaleaga ai o latou soifua maloloina, ma i'u ina maliliu ai. Aua ne'i faapea oe.Le au pele e, e tatau ona e tausami tau lava o le taimi e manaomia, ma ai tau o le tele e manaomia e lou tino e ola ai. A tele tele lau tausami, o le a e maua I le tino vaivai, ma lē lava sou malosi e fai ai feau e atia'e ai oe ma lou aiga. O i latou e atua i o latou manava - lona uiga e pulea e le ‘ai - e i'u I le faaleagaina, pule i lau tausami.Tatalo.Tamā faamolemole aua ne'i e fa'atagaina lo'u fiafia i mea tausami e fa'aleagaina a'u, i le suafa o Iesu, Amene.

Los Denver Broncos recibirán su primer juego en casa ante los Pittsburgh Steelers en un duelo que pinta para ser dominado por las defensivas. En este episodio del Broncast, Jorge Tinajero les platicará de las claves para la victoria y más detalles de este encuentro. Deja en los comentarios tu pronóstico de este partido.See omnystudio.com/listener for privacy information.

This is a free preview of a paid episode. To hear more, visit www.enrakhoger.seMan har läst och hört om den här sortens sammanslutningar tidigare, men sällan har man kommit så nära inpå som i P1-dokumentären Sista dansen på Fårö av Jannike Åhlund. Ett gäng ur kultureliten samlas varje sommar på Fårö med vilda fester till gryningen och nakenbad på öde stränder. Det är författaren Lennart Hellsing, musikern Georg Riedel, skådespeler…

OPEN HEAVENSMATALA LE LAGI MO LE ASO TOONAI 3 AOKUSO 2024(tusia e Pastor EA Adeboye) Manatu Autu:   - O a'oa'iga e fuafuaina lou lumana'i (Discipline ‘Shapes Your Future) Tauloto -Tusi Paia– Eperu 12:11 ‘O a‘oa‘iga uma fo‘i a o i ai, e lē manatu i ai o se mea e ‘oli‘oli ai, a o le mea e fa‘anoanoa ai; ‘ae mulimuli ane e fua mai ai le fua o le amiotonu ē manuia ai ē ‘ua a‘oa‘oina ai'Faitauga - Tusi Paia: Kenese 25:29-34A o o'u i aoga maualuga, na fai mai lo'u faiaoga iā i matou, o tagata soifua uma lava na omai i le lalolagi ma avega o puapuagā mo i latou e fa'aaogā a'o le'i tuua le lalolagi. E mafai ona e filifili e fa'aaogā lau ato puapuagā a o e la'ititi, ia sa'oloto ai lou olaga pe a e matua, poo le taofi mau o puapuagā ae fai le saolotoga a'o laititi. Peita'i e tatau ona e malamalama, e mautinoa e te faaaogaina le aluga o puapuaga pe a e matua.Afai e te filifili e fa'aaogā lou aluga o puapuaga a'o e la'ititi, o le a e tuua oe lava I se olaga pulea malu puipuia. O le a e su'esu'e a o taa'alo isi, auai i leoleoga tatalo i po a'o fai pātī isi, ati'ae se tagata amio lelei a'o loo fai e isi le amioleaga ma faaputuputu mo le lumanai. a'o isi o loo fa'aalu uma tupe latou te maua. Fai mai le upu tauloto o le asō, o taimi o a'oa'iga e lē manatu o se mea e olioli ai peita'i e maua ai le filemu o le mafaufau I le lumana'i. O i latou e lē tuuina atu i latou lava i a'oa'iga a'o laiti o latou olaga, e mautinoa o loo faatali mai puapuaga mo i latou i le lumana'i. O oe e faia lau filifiliga, faataga lou tagata e ui i puapuaga o a'oa'iga i le taimi nei, poo le faasaga i le taui o le a'oa'iga mulimuli ane. Fai mai le Failauga 7:8 “E sili ‘ona lelei o le i‘uga o se mea i lona amataga. E sili ‘ona lelei o lē ‘ua ‘onosa‘i i lē ‘ua loto fa‘amaualuga.”E sili ona tāua lou i'uga na i lo'o lou amataga. E lē afaina pe e te sau i se aiga mativa, o le mea taulia aua ne'i e oti mativa. E lē afaina pe afai o oe sa leaga lou olaga toeitiiti a e alu i seoli; e taulia lou i'u i le ola e faavavau. Aua ne'i maimaua lou lumana'i i fiafiaga e gata I le taimi nei. O Esau na fia'ai ma ia fa'ataua ai lona tofi o le ulumatua mo se ipu polesi; na ia tia'ia manuia tu'u fa'asolo mo se taumafa e tasi! Semanū faapenei o tatou faapea; o le Atua o Aperaamo, Isaako ma Esau, peita'i na ave e Esau lona tulaga iā Iakopo ona o lona fia taumafa polesi. Atonu e te faapea mai sa valea Esau, peita'i e toatele tagata o loo amio faatasi ma Esau i le taimi nei. E i ai tagata semanū faapenei o avea ma perofeta iloga peita'i ua lē faataunuuina manuia ona o le lima minute o le faitaaga. O nisi e mafai ona latou maua ni pisinisi tetele peita'i ua maimau ona o le paie e galulue.Le au pele e, o le pologa o le ola pulea i a'oa'iga i le taimi nei e lē faatusalia i le taui e te selesele i le lumana'i. I le suafa o Iesu Amene.

CONVIDADO: Maria Helena Costahttps://mariahcosta.com/Maria Helena Costa nascem em Aveiro em 1965. É cristã, conservadora, casada, mãe de três filhos e avó. É presidente da Associação Família Conservadora. Há cerca de 6 anos abdicou da carreira profissional para se dedicar à família e, quase exclusivamente, a pesquisar e estudar a ideologia do género/os seus efeitos nas crianças e o que está por detrás dessa tentativa de desconstrução sexual, pessoal e socialEscritora de várias obras já editadas, entre as quais: Identidade de Género – Toda a Verdade (2019), #éhoradospais – Uma defesa do superior interesse das crianças (2020) e Feminismo Tóxico (2022), escreve também artigos de opinião no Observador, no Semanário Sol e em alguns sites, blogs e jornais on-line.___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Se desejas contribuir para o canal podes fazê-lo utilizando uma das opções abaixo:Muito obrigado pela tua ajuda!-Torne-se membro do nosso canal: https://www.youtube.com/channel/UCPvHjnk3mt4jrGSvQkUSBWA/join-PIX: 11716796709-MBWAY: +351 915167672-Paypal: https://www.paypal.com/donate?hosted_button_id=H6PFSR9EE9T5L-Bitcoin Address: 15LCdXiRWBZGVFtFLU2Riig7poZKDQ35L3-Ethereum Address: 0x69f7f2732CB0111c249765ea5631fC81dFF23dB4___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ANFITRIÕES:Rodrigo - Instagram https://www.instagram.com/rodrigofrontMarco - Instagram https://www.instagram.com/marcoacpinheiro/___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ CONTATO: zugapodcast@gmail.com___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ O Zuga Podcast é uma produção original Estúdio Zuga Produções Audiovisuais.Estamos em Vila Nova de Famalicão - Braga - Portugal.Para maiores informações:E-mail: estudiozuga@gmail.comTelemóvel/Whatsapp: +351 914374850

For today's episode, we read The Energy Conspiracy by David C Seman, vanity published in 1981. This was requested by our patron beastwiththeleast, who had this to say: "Here's to another year of Terriblo's blessings and curses. I hereby submit my patron book request for you guys to read at some point next year...I haven't read the book in full, but I skim-read a few of the extremely short chapters. It looks like the sort of thing Ted Cruz would badger his wife into reading to him as a bedtime story. Please enjoy (tolerate? choke down?) this word salad tossed with right-wing dystopian elements, baffling typos, half a pound of cheese wrapped in aluminum foil, and dry-ass dialogue in place of croutons. BYOB." Thanks for the recommendation, beastwiththeleast. We applaud your efforts in finding us an out-of-print book and digitally rendering it for ease of reading - truly a gentleman and a scholar! In addition to our usual barnyard language, today's episode includes discussion or mention of: THE GUB'MINT in the vein of authoritarianism and some conservative and libertarian viewpoints around energy.

In this captivating episode of Eye on Franchising, join me as I welcome Chris Seman, President of Strategic Franchise Systems. We explore Chris's unexpected journey into franchising and his reflections on the challenges and rewards of the industry. Don't miss this engaging conversation on the A to Z's of franchising! - Unexpected journey into franchising- Vast opportunities in franchising- Benefits of scaling a business- Low-cost franchise opportunity with Caring Transitions- Specialized services in painting industry ---Ready to watch these great conversations? Come check out a few videos have have and give me a follow!https://www.youtube.com/channel/UCwoAdrkPZmveJt5AQRDk8WA---Lance GraulichFranchise Consulting Services from ION FranchisingEye On Franchising

On Argentina's historic election.   Historian of populism and anti-populism Ernesto Seman tells us what is happening in Argentina amidst severe economic crisis. The radical libertarian madman Javier Milei failed to win, and a second-round runoff will be needed, but politics has changed irreparably. The establishment right has been outflanked, while the left-populism of 'Kirchnerismo' is in crisis.   We discuss: What is 'Peronism' and how does it occupy so much political space? How does Milei appeal to informal workers using market ideology? What is distinct about Latin American populism? How is anti-populism used to denigrate the masses? What is the role of nostalgia for the golden age in Argentina? Reading: In Chile and Argentina, anti-populist politics is failing, Ernesto Seman, FT Breve historia del antipopulismo (Brief History of Antipopulism), Ernesto Seman Ambassadors of the Working Class, Ernesto Seman Javier Milei is not done yet, Alex Hochuli, Unherd Javier Milei is not a South American Trump, Alex Hochuli, Unherd Links: /367/ Don't Pay Them Back ft. Jerome Roos /189/ Pink Tide Paradoxes ft. Fabio Luis /93/ Hot Chile and Other Neoliberal Failures ft. Pablo Pryluka

Regarding lighting of the candles on Rosh Hashana night. Let's begin with our scenario this year, where the Holiday is on Friday night which coincides with Shabbat. So therefore, the ladies would light candles like they light very Friday night eighteen minutes before sunset, and they would make a Beracha, ‘Lihadlik Ner Shel Shabbat Viyom Tov.' They would add Yom Tov because of the Holiday. That would be, 18 minutes before sunset.Regarding, Saturday night, which is the second night of Yom Tov, ladies are also required to light candles. The question is, when do they light candles on the second night of Yom Tov? Halacha says, it's most proper to light them when the men come home from Shul, right before you sit down to have the meal. At that time, the ladies should go to the candles and light them. They make the Beracha on the second night, ‘Lihadlik Ner Shel Yom Tov', as it's obviously no longer Shabbat.One has to keep in mind, that on Saturday night, you can only light candles from an existing flame. So therefore, one has to prepare an existing flame, a candle that is there which was prepared in order to take the flames. But there is a problem, that many people are not aware of. After the lady lights the candles from the existing flame, sometimes just without thinking she blows it out. Or she shakes it out. According to the Halacha, it's definitely forbidden to extinguish candles on Yom Tov. While it's permissible to light from an existing flame, but to extinguish is for sure forbidden. So you have to tell them, to very carefully just place it down and to let it go out by itself. But not to shake it, and certainly not to blow it out on the holiday.There is no Shehechiynau made at the time of Hadlakat Nerot. The ladies rely on the Shehechiynau that is made on the Kiddush.Now once already we are on the subject of Nerot, we have a custom that‘s brought down in Halacha, that since this Friday night is also Yom Tov, so we shouldn't say ‘Bame Madlikin'. We shouldn't say Bame Madlikin even though normally every Friday night we say ‘Bame Madlikin', which discusses how to light candles, and what oils are kosher, and what wicks are kosher, and which ones are not kosher. It's our custom to read it every Friday night. However, we skip it when a holiday comes out on a Friday night. Different reasons were given. One reason is because, not all the laws are the same on Shabbat as Yom Tov regarding kosher wicks and oils. So therefore, since the laws vary from Shabbat to Yom Tov, so we skip it. Other reasons are also brought down in the Mishna Berura in Seman 270.Lastly, going back. regarding making the Beracha on the Nerot Shabbat. There is a Machloket (argument) as to which comes first. The lighting or the blessing? Some make the Beracha first, which would make logical sense. The logic being always to make the Beracha and then perform the Mitzvah. Others light first and then they make the Beracha. The logic there is because they hold that making the Beracha brings on acceptance of Shabbat, and how could you light the candles if it's Shabbat already? But that logic would apply for Shabbat, but on Yom Tov everybody would agree, you should make the Beracha first and then light. It's because you are allowed to light on Yom Tov. So therefore, the Beracha is not an acceptance of anything. And therefore, it's proper to make the Beracha ‘Lihadlik Shel Yom Tov' first, and then to light. This applies even to those who light first the rest of the year. That's for Shabbat. However, for Yom Tov, it's proper to make the Beracha first and then light.

In today's episode of FranchiseU!, Kathy sits down with Christopher Seman with Strategic Franchising. Seman's successful career demonstrates how staying focused on a franchisee's desires benefits everyone, regardless of brand. Before Seman's success leading Strategic Franchising he previously served in various senior executive positions, including President of Caring Transitions, and Vice President with Mr. Handyman International. Seman is a firm believer in franchising and the franchise model, having gained this belief through his experience as a franchise executive and by owning his own franchise. Seman owned and operated a successful Mr. Handyman franchise and knows firsthand the critical importance of having a world-class training, marketing, and operational support programs in place for franchise owners at all levels of the system. After five years of amazing growth and success with Caring Transitions, Seman was promoted to COO/President of Strategic Franchising Systems to help spread his ideas and proven systems across all five Strategic Franchising brands.

-Derrama económica será de 160 mmdp en Semana Santa-Fallece el músico y compositor japonés Ryuichi Sakamoto-Más información en nuestro podcast

Chris Seman is the President of Strategic Franchising Systems. #chrisseman #strategicfranchisingsystems #president #tsc #gogetit Social Media Links Youtube Channel youtube.com/c/ChipBakerTheSuccessChronicles LinkedIn http://linkedin.com/in/chipbakerthesuccesschronicles Facebook- Profile https://www.facebook.com/tscchipbaker Facebook- Page facebook.com/chipbakertsc Instagram https://www.instagram.com/chipbakertsc/ Twitter twitter.com/chipbaker19 TikTok tiktok.com/@chipbakertsc Linktree https://linktr.ee/ChipBakerTSC Online Store http://chip-baker-the-success-chronicles.square.site/ Chip Baker- The Success Chronicles Podcast https://anchor.fm/chip-baker

Christopher Seman is the president of Strategic Franchising Systems, which is a portfolio of established companies that provide cost-effective, home-based franchises with powerful marketing systems to help generate maximum income and profits. Their esteemed businesses include The Growth Coach, Caring Transitions, Fresh Coat, TruBlue, and Pet Wants (mobile and store units). About Strategic Franchising Systems: https://strategicfranchising.com Tired of your job? Thinking of starting or buying a business? Take our Biz Quiz to filter through over 10,000 business opportunities today! https://www.vettedbiz.com/quiz-test/ Need help finding the right franchise? Click here: https://www.vettedbiz.com/franchise-search/ 00:00 Introduction 01:29 About Christopher Seman 09:13 Q&A - How much money does it cost to open a Caring Transitions Franchise? 16:38 Q&A - How do you divide your brand? 20:39 Q&A - How do you track the sales of your franchisees? 28:22 Concluding Thoughts #ChristopherSeman #StrategicFranchisingSystems #FranchiseFindings If you are looking for more information, you can connect with us through our networks: https://www.vettedbiz.com/ https://www.linkedin.com/company/vettedbiz/ https://www.facebook.com/vettedbiz https://www.tiktok.com/@businessandfranchiseinus We partner with Fund My Franchise to give you the best “one-stop source” for all your funding needs. Knowing which option is best suited for you and your business is their specialty. Whether you use our Self-Directed 401(k), allowing an entrepreneur to use qualifying retirement monies to capitalize a business, and/or traditional Debt Funding, utilizing Unsecured Lines of Credit (ULOC) or Small Business Administration (SBA) Loans, they are here to help you realize your entrepreneurial dream. Don't let bad credit stand in your way. They can help with credit repair. Click the link in the show notes to apply for a no-obligation, no-charge consultation with one of their Senior Consultants: https://share.hsforms.com/1hkqew4n2S7ap6o8z1OqBIQ4e0xw

OPEN HEAVENSMATALA LE LAGI MO LE ASO TOONAI 28 IANUARI 2023 Manatu Autu:  Na o le tasi le measesē  (Just one mistake) Tauloto – Tusi Paia: 2 Korinito 2:11‘ina ne‘i ‘ole‘olegia i tatou e Satani; auā tatou te lē vālea i ana togafiti'. Faitauga - Tusi Paia: 2 Samuelu 11:1-27 Upu FolafolaE toatele Kerisiano ua manatu e mafai a ona pauū ma toe tutū pe a manana'o ai. E masani ona ou fai atu o manuia e mafai ona pepē a'o mā'ila'ila e tumau. E mafai ona e faia se agasala ma faamagalo oe e le Atua a'o le taui o lau agasala e ola pea ma oe i aso uma o lou soifua tusa fo'i pe uma lou soifua e ola pea le taui. Na o le tasi le measesē ae mafai ona mafua ai faafitauli ogaoga mo lau fanau e o'o lava ia i latou e le'i fananau mai. I le Kenese 16:2 na fa'aoso e Sarai Aperaamo e momoe ma lana auauna fafine ma e o'o mai i le aso nei o loo mafatia pea le lalolagi I le measesē lenei e tasi. I le Kenese 25:29-34 e tasi le faaiuga sese na fai e Esau na ia faatau lona tofi o le ulumatua ma e tatou te o'o atu I le Kenese 27:30-40 fai mai le Tusi Paia e ulufale atu Esau ua ulufafo ese atu lona uso ma ave lona manuia. Na fa'atauanau Esau I lona tamā mo se manuia o totoe mo ia, ma na faapea atu Isaako i lona atalii e manuia lavā ia, o lana pelu e ola ai peitai e auauna ia i lona uso. Na mafua lea ona o le measesē e tasi. I le 2 Samuelu 11 na fai e Tavita se measesē na fanau mai ai le tele o isi sese. O lona sesē na nofonofo I lona fale I le taimi e o atu ai tupu i le taua. Semanū e le vaai Tavita I le fafine aulelei a'o taele ma faaosoosoina ai ia pe ana lē nofonofo i le fale. E tatau ona e fesili “Aisea ua autilo ai Tavita i le fanua o le isi tamaloa?” A e fa'ataga I le tiapolo se inisi na te le avea na o se maila peitai e alu a le tiapolo e lē toe taofia. E le'i umi ae auina atu e Tavita ana auauna e aami le fafine i lona fale. Na to le fafine (tulou) ma ina ia nanā lilo le agasala na taupulepule Tavita e fa'ao'o le oti ia Uria lona toalua. Na auina atu e le Atua se perofeta e ta'u iā Tavita e lē mavae le pelu ai lona aiga. E o'o mai i le aso nei e le o mavae le pelu mai Isaraelu. Na amata i le measesē e tasi o le tafao ae lē faia ona tiute. O nisi kerisiano ua manatu e lē afaina le momoe ae le tatalo. A'o le'i feala i latou i le isi aso ua tu'u e le tiapolo mailei e fai ma fa'asalāvei I o latou olaga. O le tulaga faanoanoa e manatu le tagata o faigata ona nofo I luga e tatalo o se faigata masani ma fa'aauau ai pea le moe ae le nofo I luga e tatalo I taimi tatau. Le au pele e, aua e te faatamala i togafiti a le fili o loo fealuai e saili se tasi e aina e ia (1 Peteru 5:8). Pau le avanoa e manaomia e le tiapolo o sina measesē se tasi. Aua ne'i e avea se fa'atagaga I le tiapolo. I le suafa mamana o Iesu Keriso.Amene

"O práci som premýšľal tak, že na to, aby som zarobil peniaze, musím veľa robiť. Až potom si zaslúžim odmenu a odpočinok." Vlado Seman zmenil pohľad na svoje podnikanie. Jeho práca mu umožňuje pracovať diaľkovo. Precestoval niekoľko krajín a popritom rozvíjal svoje podnikanie. Aké je "podnikanie z pláže"? Čo si na svojej ceste uvedomil? Čo mu pomohlo zmeniť jeho myslenie a nemať výčitky? Vďaka čomu sa mu znížili náklady? Vypočujte si novú epizódu, ktorou vás bude sprevádzať známy hlas z reklám a voiceoverov :)  

SEMAN 2 | Vengan Y Vean: Mira lo Santidad de la Vida | Julio Varela by

OPEN HEAVENSMATALA LE LAGI MO LE ASO TOONAI 14 IANUARI 2023 Manatu Autu:  Ua na o le Alofa tunoa (Only by the Grace)  Tauloto – Tusi Paia: Ioane 15:16‘Tou te le‘i filifilia a‘u, ‘ae na ‘ou filifilia ‘outou ma ‘ou tu‘uina atu ‘outou, ‘ia ‘outou ō ma ‘ia ‘outou fua mai ni fua, ma ‘ia tumau o ‘outou fua; ‘ina ‘ia foa‘iina atu ‘iā te ‘outou e le Tamā mea uma lava tou te ole atu ai ‘iā te ia i lo‘u igoa...'  Faitauga - Tusi Paia: Roma 9:15-26 Upu FolafolaUa manatu nisi ua faia e le Atua mea tetele ma lelei mo i latou aua o se tulaga ua alagātatau ma ua agava'a i ai. I o latou manatu auā ua tele lo latou aogā I le Atua ua tatau fo'i la ona faamanuia mai le Atua ia I latou. Talitonu mai ma le faamaoni o mea uma lava e faia e le Atua, e faia ona o lona lava suafa, e lē mo oe ae mo lona lava suafa ia faailoa atu ai lona mana. (Salamo 106:7-8) Aua e te fa'amaualuga. E mafai e le Atua ona fa'aaogā so'o se tasi. E i ai tagata o lo'o tatalo, suesue le Tusi Paia, sili atu lo latou agava'a na i lo'o oe, ae ua filifilia oe e le Atua ma e tatau la ona e loto faafetai ai. O lenei, afai tatou te maitaulia le amio leaga, o ai se o le a tula'i? (Salamo 130:3) A vaai tagata I mea o loo fai e le Atua i le Ekalesia RCCG e manatu atonu e faapitoa a'u. Pau le tulaga ese o a'u, na filifilia a'u e le Atua, aua mai lava i aso o o'u laititi na folafola e le Atua i lo'u tamā o le RCCG o le a so'o ai le lalolagi. E lē ona o a'u ae ona ua finagalo le Atua e faailoa le mamalu o lona suafa e ala i le elalesia lenei ma ua nā o lona alofa tunoa ua filifilia ai a'u e avea ma ta'ita'i o le ekalesia. Semanū na te filifilia se isi tagata auā o loo i ai e sili atu le agava'a ia te a'u peitai ua na o lona alofa tunoa ua mafua ai ona avea a'u ma tagata filifilia. Afai e te vaai I tagata o loo malelemo pea I le agasala, ‘aua e te faamasino ia i latou ona ua faaolaina lou agaga ma o loo e agai atu i le lagi a ia e tatalo I le Atua e laveaiina i latou e ala i lona alofa tunoa, e pei ona ia laveaiina oe mai lou agai atu i Seoli. Aua ne'i galo o le Atua o lo'o galue pea mo le viiga o lona lava suafa. O le alofa tunoa ua e maua ai faamanuiaga a le Atua. Atonu na manatu le fanauga a Isaraelu na vaeluaina e le Atua le sami ulaula ma malelemo ai Farao ma ana ‘au tau ona e faapitoa i latou i le finagalo o le Atua. Leai na faia e le Atua mo lona lava suafa. Ua na o i latou o ni tagata ua alofaina i le alofa tunoa o le Atua. Ua tautino mai ai Paulo I le tusi o Roma 9:17 ‘Auā ‘ua fa‘apea mai le Tusi ‘iā Farao, “O lenei lava le mea ‘ua ‘ou fa‘atū ai ‘iā te oe, ‘ina ‘ia ‘ou fa‘aalia lo‘u mana ‘iā te oe, ‘ina ‘ia ta‘ua fo‘i lo‘u igoa i le lalolagi uma lava.”' TataloTamā faafetai mo lou alofa tunoa i luga o lo'u olaga. Faamolemole aua lava ne'i faatagaina se mea e taofia ai a'u mai lo'u fiafia pea e ola fiafia i lou fesoasoani mai lou nofoalii o lou alofa tunoa. I le suafa mamana o Iesu Keriso, Amene. 

OPEN HEAVENSMATALA LE LAGI MO LE ASO TOONAI 10 TESEMA 2022 Manatu Autu: E pule le Atua I le fua tele mai (God controls fruitfulness). Tauloto – Tusi Paia: Kenese 29:31 ‘Ua silafia e le ALI‘I ‘ua ‘inosia Lea, ‘ona fa‘afanafānauina lea o ia e ia, a o Rasela ‘ua pā ia.'.  Faitauga - Tusi Paia: Isaia 54:1-8 Upu FolafolaO le Atua o ia e faia le faaiuga poo ai e fanafanau. I le Kenese 29:31 ina ua silasila atu le Atua ua inosia Lea ona ia fa'a fanauina lea o ia (tulou). O le Atua e filifilia po'o ai e fanau a'o ai e pa (tulou). Ou te talitonu ua avatu e le Atua lenei vaaiga i se tasi i le asō ina ia tu'u atoa lou talitonuga ma lou faamoemoe I le Atua ona ia fa'a fanafanauina lea o oe i le suafa o Iesu. Sa mana'o Rasela ia maua sana fanau peitai sa sesē le nofoaga na saili i ai. I le Kenese 30:1-2 sa fai Rasela ia Iakopo lona toalua e tatau ona ia avatu ni tama ia te ia, a leai o le ā oti. Ona tali atu lea o Iakopo iā Rasela po'o ia ea o le Atua? Fai mai Kenese 30:22-24 ua manatua e le Atua Rasela, ua fa'a fanauina ia. O le faamaoniga na fa'a fanauina e le Atua Rasela e ta'u mai ia I tatou o le Atua fo'i na ia tapunia lona manava. Ua ta'u mai e le Faaaliga 3:7 ia I tatou o le Atua na I ai le ki a Tavita. A ia tatala e leai se tasi e faamauina, a ia faamauina fo'i e leai se isi e talaia. O manava uma ua tapunia o le a faa fanauina I le asō I le suafa o Iesu. E lē afaina pe a manatu le tiapolo ua ia tapunia lou manava (tulou). O le ki a Tavita o le ki autu lea. Afai e tatalaina e le Atua lou manava e fa'alēaogaina uma galuega a le tiapolo. Peitai o le fanafanau e lē na o le maua o se fanau. E mafai na i ai manava o pisinisi, galuega, manatu lelei ma isi. I le Luka 5:1-7 sa fagota Peteru I le po atoa ae lei maua se i'a sa tapunia le manava / punāvai o manuia ia te ia seia o'o ina asiasi atu lē e i ai le ki a Tavita ma tatala manuia mo Peteru. E o'o atu I le isi faiva o Peteru I le ogasami loloto, o lē sa leai se i'a o lona faiva ua tetele le mau o lona faiva ua lē mafai ona ia ave uma i'a a ua tufa atu I isi faifaiva. A tatala e le Atua lou punāvai o manuia e te maua suiga lelei tetele e lē mafai ona e talitalia ma fa'aaogā na o oe. O le punāvai o ou manuia e ao ona matala I le masina nei I le suafa o Iesu. E lua mea e tatau ona e faia mo le Atua ia e fua tele mai. Muamua silasila I le Atua, na o le Atua lava mo lou manuia. E a'oa'oina oe e le Atua i mea e te fai faapei ona ia a'oa'o Peteru e lafo lona upega. Lona lua aua ne'i muta lou loto talitonu. Semanū e misi e Peteru lona manuia ona ua loto vaivai. E le'i loto e lafo le upega ae sa ia faia ona o le manatu I le fetalaiga a Iesu. Atonu ua toe o se aga e taunuu i se fesuiaiga lelei o lou olaga. Ua maea talaia e le Atua punāvai o manuia mo oe amata loa lou faiva ma ao lau seleselega. TataloTamā faamolemole tatala noanoataga o ou manuia mo a'u I le asō ma ia avea le masina lenei e iloga ai se suiga lelei mo lo'u olaga I le suafa pele o Iesu Keriso, Amene.

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/latino-studies

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/history

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/latin-american-studies

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/medicine

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/anthropology

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices

Recent global events have unmasked inequitable healthcare systems that disproportionately affect poor Latinx populations along the U.S-Mexico border. Professor Jennifer K. Seman's recent publication offers a brief insight into these inequities by approaching borderlands modes of care from a historical perspective to reveal how two vital practitioners of curanderismo – “An earth-based healing practice that blends elements of Indigenous medicine with folk Catholicism” (1) – served their communities to heal physical and societal ills at the turn of the twentieth century. Borderlands Curanderos: The Worlds of Santa Teresa Urrea and Don Pedrito Jaramillo (University of Texas Press, 2021) follows the biographies of these two Mexican folk healers as they traverse borders during a moment of increased nation-building, as they are implicated in the world of the spiritualist movement, and stand firm in their faith as they are wedged against professional modern medicine. Seman grounds the history of curanderismo in the cross-cultural exchange between European, Native American, and African heritages and practices that depend largely on the belief that there is a connectedness between the mind, body, and spirit. By utilizing institutional and non-institutional archives, newspaper accounts, and built environments in which Santa Teresa and Don Pedrito traversed and are memorialized, Borderlands Curanderos offers a detailed look at their lives. One major thread linking the curanderos is how they negotiated the state and state power during the early 20th century in Mexico and the United States. “It was their extraordinary responses to the failure of institutions that made Santa Teresa and Don Pedro threats – and, in some cases, assets — to the states and institutional authority,” (4) writes Seman. In other words, their medicine did not come from the state, the church, or professional medicine, as argued in her book, but rather from a distinct cultural practice that revitalized the sick. These two healers took on the insurmountable task of tending to people and geographies who were experiencing the aftermath unleashed by settler colonialism and enslavement; or, as Seman would argue, the generational susto brought on by conquerors and settlers (9). Jonathan Cortez is currently the 2021-2023 César Chávez Postdoctoral Fellow in the Department of Latin American, Latino, and Caribbean Studies at Dartmouth College. You can follow Jonathan on Twitter @joncortz Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/christian-studies

Slap Heard Around The Worldhttps://www.youtube.com/shorts/D5f-iYI_8Qs Seman Sellerhttps://www.ladbible.com/community/man-facing-divorce-after-donating-sperm-and-not-telling-his-wife-20220328 Youtuber Alien Love Affairhttps://allthatsinteresting.com/abbie-BelaHER CHANNELhttps://www.youtube.com/c/AbbieBelaDiary

Jennifer Koshatka Seman is a lecturer in history at Metropolitan State University in Denver. Her work has appeared in Studies in Religion/Sciences Religieuses and the Journal of the West. Visit "Borderlands Curanderos" at University of Texas Press: https://utpress.utexas.edu/books/seman-borderlands-curanderos Follow Dr. Jennifer Koshatka Seman on Twitter: https://twitter.com/jenniferseman Follow Dr. Arlene Sánchez-Walsh on Twitter: https://twitter.com/AmichelSW

In this episode, Nathan McAllister, 2010 Kansas and National History Teacher of the Year talks about "Why not"?  When a student has an idea, help them be brilliant even if it wasn't in the plan.  This philosophy led to Nate's students working to successfully enact legislation, to building on the football field, to discovering that Seman school district was named after an active and proud KKK member and fighting to change the name of the school and district.  AP News coverage of Seman High Name ChangeGet in touch with Nathan:Twitter: http://www.twitter.com/NHTOYmcEmail: natemc@hotmail.comLet's be Friends!Instagram: @teachinghistoryherwayTwitter: http://www.twitter.com/historyherwayFacebook: http://www.facebook.com/teachinghistoryherwayOn the Web/Blog: http://www.teachinghistoryherway.com

Please send us all of your blood and seman. In this episode Trevor gets pimped and performs terribly, Ken gets his first interview for residency, we talk about squid game and how STUPID pakistani people are. And as is tradition, we make light of suicide! Yay!

X TRIES TO GET COMMERCIAL! Michael and Jenny from Shiny Around the Edges join us to discuss X's frustrating attempt to cash in. How obscure can an artist be and still have documentaries made about them? Is X the best or the worst name for a band? What did Ray Manzarek bring to the table? Did X just put out an album that none of us listened to? Is not being rich or famous enough a good reason to quit a band? What kind of rockabilly is this? Who else was in that movie “Road House”? Does John Doe want his fans to get home safely? Does everyone have their own X story? And how did Professor Xavier train all these mutants? We'll dig into it all this week on Detours and Outliers.

  Dr. Michael Seman is an assistant professor in the LEAP Institute for the Arts' arts management program at Colorado State University. He received his doctorate in urban planning and public policy from the University of Texas at Arlington in 2014 and his work primarily examines the intersection of music, entrepreneurship, and economic development on the urban landscape. Before joining Colorado State University, Michael was Director of Creative Industries Research and Policy at the University of Colorado Denver College of Arts and Media.   Michael teaches both undergraduate and graduate students and is currently writing a book about music scenes and how they can transform cities for the University of Texas Press. His co-edited volume concerning the production and consumption of music in the digital age was published by Routledge in 2016 as part of their Contemporary Human Geography Series and Michael recently helped author music strategies for both the City of Denver and the State of Colorado. Michael's work can also be found in many academic journals including Cities, Regional Science Policy and Practice, Applied Research in Economic Development, City, Culture and Society, Industrial Geographer, Artivate: A Journal of Entrepreneurship in the Arts, and most recently in Growth and Change.   National Public Radio, Vice, Wired, The Washington Post, and many regional media outlets seek Michael's insight and he is often invited to speak at professional and civic events across the country. Prior to completing his graduate work, Michael spent several years as an executive at Creative Artists Agency in Beverly Hills, California where he focused on internal marketing and project development. Michael also managed daytime programming for the “35 Denton” and “Oaktopia” music festivals in Denton, Texas while earning his doctorate. He is represented by the Creative Class Group for speaking engagements.