Podcasts about Sha

VP of Marketing & Commerce Sha Atakhanov has been driving growth and innovation at homepathic brand Boiron for almost 17 years. From booking some of the first ads on Amazon to being an inaugural brand running shoppable ads on Samsung TVs, , Sha oversees all the channels and media that touch the consumer, and he approaches new opportunities and tech, especially AI, with a simple rule - it has to generate revenue, save time, and save money. And have some fun while you're at it.

What makes a good comic book character? What makes them stand out? What comes first; the character or the story? Those are just some of the questions we answer this week as we delve into one of the most enjoyable sides of comic creation. Also there's some birthday chat, some spider-man chat and plenty of great comics and books to check out, including one by one of comics greats! Great stuff to check out: Spider-Man, Batman, The Punisher, The Fantastic Art of Ron Turner, Comics Assemble, Sha, Pat Mills, Men of the Cloth, Hellbound Media, The Gods and Monsters of Headgrave, Frank Miller: Push the Wall, Retail Park, Underg Planet Atmos: Exordium, Mad Cave Comics, Blood Force

The Root Cause of the Churban: Disgracing Torah Scholars To truly understand the events of the Churban Beis HaMikdash (destruction of the Temple), we must always look back to its root causes so we can fix them. The Gemara ( Maseches Shabbos 119b ) teaches: אמר רב יהודה לא חרבה ירושלים אלא בשביל שביזו בה תלמידי חכמים Rav Yehuda said: Jerusalem was only destroyed because they disgraced Torah scholars. Rav Yehuda brings a prooftext from Divrei HaYamim Bais (36:16) : : (טז) וַיִּהְיוּ מַלְעִיבִים בְּמַלְאֲכֵי הָאֱלֹקים וּבוֹזִים דְּבָרָיו וּמִתַּעְתְּעִים בִּנְבִאָיו עַד עֲלוֹת חֲמַת ה' בְּעַמּוֹ עַד לְאֵין מַרְפֵּא: "They constantly insulted the messengers of God and scorned His words and scoffed at His prophets until the wrath of Hashem rose up against His people beyond remedy." This refers specifically to how King Yehoyakim refused to humble himself before the prophet Yirmeyah (Jeremiah) and disgraced him instead. The Metzudos notes that the word מִתַּעְתְּעִים metateim (scoffed/stray) comes from the root to'eh (to stray). The people claimed that the prophets were the ones who had gone astray, saying: "We know what we're doing; they are the ones who are off." Halachic Severity and the Removal of Free Will The Rambam ( Hilchos Talmud Torah 6:11 ) codifies this not as mere inspiration ( mussar ), but as definitive halacha : It is a monumental sin to disgrace or hate talmidei chachamim (Torah scholars). He cites the Gemara in Shabbos that Jerusalem was destroyed for this reason. He links this to the verse in the Torah: "Im Bechukosai Timasu" ( "If you disgrace My statutes" ), explaining that this means Melamdei Chukasai Timasu —despising those who teach Torah. The Rambam warns: וכל המבזה את החכמים אין לו חלק לעולם הבא Whoever disgraces Torah scholars has no portion in the World to Come, and is included among those of whom it is said, "They disgraced the word of God." Furthermore, in Hilchos Teshuva (6:3) , the Rambam addresses the phrase ein marpei ("beyond remedy"). We know from the story of Pharaoh that a person can commit sins so severe that God removes their free will as a punishment. The Rambam explains that those who disgrace talmidei chachamim face this exact reality: God prevents them from having the ability to do teshuva (repentance). The Parable of the Traveling Doctor Why is this sin considered so severe that it leaves a person "beyond remedy"? The rabbis offer a powerful mashal (parable): A traveling doctor arrived in a town with a caravan full of specialized medical tools. A local man desperately wanted to heal his sick son but lacked the money to pay. Desperate, the man ambushed the doctor's caravan on the side of the road and stole his baggage. Sorting through the stolen goods, the man found a bag full of complex medical instruments. Seeing no material value in them, he threw them away. Later, the man brought his sick son to the doctor and begged, "Please, save my son!" The doctor replied, "I want to help you, but someone just stole all of my medical utensils. Without them, I cannot heal him." The Nimshal (The Lesson) The talmidei chachamim are the spiritual doctors of our generation. When people disgrace them, the public stops listening to them. By destroying the scholars' credibility, the people effectively "throw away the doctor's tools." When someone's soul becomes spiritually ill, the doctor no longer has the tools to heal them. The Rambam ( Hilchos Deos 2:1 ) expands on this spiritual illness. Just as a physically sick person might taste something bitter and think it is sweet, spiritually sick people desire paths that are harmful and hate the path of righteousness. As the prophet Yeshayahu warns: "Woe to those who say of good it is bad, and bad it is good... who make sweetness into bitterness." What is the cure? ילכו אצל חכמים שהן רופאי הנפשות They must go to the sages, who are the healers of the soul, and they will heal their illness by teaching them the correct path. Torah as the Only Antidote In Mesillat Yesharim (Chapter 5) , Ramchal references the famous Gemara in Kiddushin 30b : "I created the Evil Inclination (Yetzer Hara), and I created the Torah as its antidote." If God explicitly states that the Torah is the only antidote to this spiritual poison, it is impossible to overcome the yetzer hara by any other means. Ramchal compares this to a patient who ignores a specialist's prescription to try their own remedies; the patient will ultimately perish. God knows the exact molecular makeup of the poison He created, and He holds the only antidote. This aligns with the famous Midrash: "Would that they had deserted Me, but kept My Torah! For the light within it would have returned them to the proper path." The Slippery Slope of Lashon Hara How does a person decline to the point of treating scholars this way? The Rambam ( Hilchos Tum'at Tzara'at 16:10 ) outlines the psychological progression of lashon hara (evil speech): It begins with indulging in empty, frivolous nonsense ( sichah batelah ). This leads to speaking disparagingly of the righteous ( tzaddikim ). Once comfortable mocking the righteous, they begin speaking against the prophets. Ultimately, it leads to speaking against God Himself. Rabbeinu Yonah ( Sha'arei Teshuva, Sha'ar 2:11 ) quotes Mishlei (17:10-11) regarding one who refuses to humble himself before those who rebuke him. The verse states that an cruel angel ( malach achzari ) will be sent against him. The word malach simply means messenger. Rabbeinu Yonah explains that a talmid chacham is a messenger of God sent to give gentle mussar (correction). Middah k'neged middah (measure for measure), God says: "I sent you a gentle messenger to guide you, and you ignored him. Therefore, I will send you a harsh messenger (tragedy or judgment) that you will be unable to ignore." Conclusion: A Reminder for the Summer The Pele Yoetz asks why we rarely hear public sermons about the severity of disgracing scholars. He explains that rabbis often avoid the topic because they worry people will cynically think, "The rabbi just wants honor for himself, so he's delivering a speech about it." But the truth must be spoken. This issue is highly relevant, especially during the summer months when people sit around relaxing. Discussing rabbis—what they said, what they did—is often treated as light entertainment. It isn't just innocent fun; it is the yetzer hara targeting our spiritual defenses. Do rabbis make mistakes? Of course they do; everyone makes mistakes. But if you systematically disgrace a rabbi, what will happen when he isn't making a mistake, and you desperately need his guidance? Enjoy the summer, but be smart. Protect the spiritual doctors who hold the tools to heal us.

pues otra vez por petición de los oyentes la tercera parte de estos especiales. VIGILANTE AOR BALLADS 3 1. SHA.BOOM - I DON´T WANNA SAY GOODNIGHT 2. BRIDGE 2 FAR - I MUST BE BLIND 3. JOJO - LOVE IS LIKE WATER 4. KING OF HEARTS - DON´T CALL MY NAME 5. RAT BAT BLUE - LONG GONE 6. JOHN FARNHAM - WHEN THE WAR IS OVER 7. JEFF PARIS - A MATTER OF TIME 8. MIKE RENO, ANN WILSON - ALMOST PARADISE 9. SOLEIL MOON - OHIO 10. BOBBY BARTH - I DON´T WANT TO BE ALONE TONIGHT 11. TIM FEEHAN - SOMEBODY ELSE´S MOMENT 12. JIM JIDHED - TWO COLD HEARTS 13. JIMMY DAVIS AND JUNCTION - JUST HAVING TOUCHED 14. ERIKA - IN. THE ARMS OF A STRANGER 15. BILL CHAMPLIN - NOWASTED MOMENTS 16. SEPTEMBER - IF YOU BELIEVE 17. SURGIN´- NOT DONE LOVIN´ YOU 18. FEE WAYBILL - SURPRISE YOURSELF 19. HENRY LEE SUMMER - I DON´T WANT TO LIVE THIS LIE 20. CHRIS IRVINE - NEVER LISTEN TO RUMOURS 21. DAYTONA - I DON´T WANNA LIVE WHITOUT YOU 22. BEAU COUP - FIND THE WAY 23. STEPHEN BISHOP - LOVE ON THE OUTSIDE 24. JIMI JAMISON- IF YOU WALK AWAY 25. LITA FORD - BAD LOVE 26. BONNIE TYLER - LOVING YOU´S A DIRTY JOB ( SOMEBODY´S GOTTA DO IT )

Today we preview the upcoming Monaco Diamond League which goes down on Friday July 10th and will have high quality matchups including Gabby Thomas, Julien Alfred and Adaejah Hodge in the 200m as well as Oblique Seville, Marcell Jacobs and Jordan Anthony in the 100m. We also preview the upcoming Ed Murphy Classic which will have Samuel Ogazi vs Quincy Wilson in the 400m.Finally, we discuss the competition between Melissa Jefferson-Wooden and Sha'carri Richardson, two of the fastest women in the world going head to head throughout 2026.Monaco Entries: https://monaco.diamondleague.com/en/programme-results/Ed Murphy Classic entries: https://edmurpheyclassic.com/athletes ⁠ -------------------------------------------

This show has been flagged as Clean by the host. This series is dedicated to exploring little-known—and occasionally useful—trinkets lurking in the dusty corners of UNIX-like operating systems. In UNIX Curio #8 ( HPR episode 4657 ), I talked about using standard utilities to compare files. Left unmentioned, however, was a method commonly used today—the hash function. As I've stated in previous entries, while I am an engineer, I don't have a background in computer science, so my understanding of the mathematics is limited. But I can give a practical description of what a hash function does. It takes an input, performs a set of calculations on it, and produces an output. As hash functions are practically used, the input is a set of bytes, such as a file or another piece of data like a password. The output is a numerical value in a fixed range—most often, expressed as hexadecimal characters. Because this "hash value" can always be represented in a certain number of bytes, its length as printed is usually a constant number of characters, padded with leading zeros if necessary. This episode will not cover the use of hashes in programming, focusing instead on using them to validate data. A hash function, or more specifically, a cryptographic hash function, has an additional property. It should be very difficult to predict what changes to the input would be required to produce a specific change in the output. An older, related concept is called a "checksum". While these are designed to vary when the input data is damaged or digits are transposed, they do not necessarily have that last property mentioned for cryptographic hashes. You have probably already encountered a checksum, even if you didn't recognize it. On a 16-digit number assigned to a Mastercard or Visa 1 credit or debit card, the first six digits identify the card issuer (such as a bank), the next nine digits are assigned to you by the issuer, and the last digit is a check digit. The check digit is calculated using the values of the previous 15 digits, and it is a simple way to avoid typos in entering a card number. In another example, every Ethernet frame that your devices send or receive includes a checksum 2 to help ensure that the contents weren't scrambled in transit. This is 32 bits long and is called a cyclical redundancy check, commonly referred to as a CRC. A CRC is also used in many other places—for example, the .zip file format includes one for each archive member, and this allows a program extracting files from the archive to identify if any were damaged. Our UNIX Curio for today is another example, the cksum utility 3 . It generates a 32-bit CRC based on the Ethernet algorithm. It operates on either a named file or standard input and outputs the CRC value, the length of the input, and the pathname if a file was given as an argument. Unlike most modern hashing programs, the checksum is printed as a decimal integer and is not padded, so it can be anywhere from one to ten digits long. The length value is the number of bytes in the input (actually specified as the number of octets , as systems could potentially use a byte that isn't eight bits long), also expressed as a decimal integer. There are two major ways that one could use cksum to check the validity of a file. First, if you are transferring a file from one UNIX-like system to another, you could run cksum against it on both systems and check that the CRC and length are the same. The utility can also be given multiple filenames as arguments, which would generate a list that can then be compared. The second way would be for someone publishing a file or set of files to also publish the CRC values, lengths, and names so that people downloading them could verify that they match. However, I don't think the practice of publishing lists like this really started until more recent hash functions like MD5 and SHA-1 came about so it is unlikely that anyone would publish CRC values instead. The advantage of these tools should be pretty obvious in comparison to cmp , one of the utilities discussed in UNIX Curio #8. To verify a file using cmp , you need two files to compare—if you're trying to check a large file you downloaded, you would need to spend the time and bandwidth to download a second copy. And if they didn't match, you would have no idea which of the two, if either, was correct. By contrast, cksum is quicker to run, doesn't require downloading a massive amount of excess data, and if run against the original file, makes clear what the correct value is. This utility is a follow-on from a program called sum , which operated very much the same. I had a bit of trouble tracking down the exact development history, but what seems clear is that two different variants 4 were popular: a BSD version and a System V version. Both output 16-bit checksums, but used different algorithms so they didn't give the same results. Also, the BSD version printed the length of the input data as the number of 1,024-byte blocks, while the System V version instead gave a count of 512-byte blocks. (Some sources claim that System V sum generates a 32-bit checksum 5 , which could possibly be true internal to the algorithm, but I have tested several independent implementations of the utility and all of them output a 16-bit value for both the System V and BSD algorithms.) From what I can tell, the BSD version 6,7 came first; it was in 3BSD but probably appeared even earlier. An identical copy of BSD's sum was included with UNIX/32V 8,9 , which was AT&T's 1979 port of Seventh Edition UNIX to the VAX and became one of the ancestors of System III. The divergence seems to have started with System III, released in 1980; its version of the sum utility 10,11 changed to a new default algorithm, though it could be made to use the BSD algorithm via the -r option. System V looks to have kept the same behavior as System III. It's not clear to me why this algorithm is universally called the "System V algorithm" rather than the "System III algorithm"; perhaps it is because System V saw much more widespread use. Instead of trying to reconcile these differences, the POSIX committee decided to create a new utility with a unique name, use a separate algorithm entirely, and avoid the block-length dispute by printing the length in octets instead of blocks. I should point out that POSIX states that the CRC algorithm for cksum does not strictly meet the mathematical definition of a "checksum". I don't know enough to say exactly why it doesn't qualify or to say whether either of the sum algorithms do. However, in less-formal usage the term "checksum" has gathered the meaning of any value used to represent or validate a set of data, so I am fine with using it no matter the technical details of the algorithm. When two different inputs produce the same checksum or hash value, this is called a "collision". Because the output value has a limited range, there are an infinite number of possible inputs that could produce a collision. From a practical standpoint the possibilities are more limited—the majority of these inputs are larger than the number of atoms in the universe, which can't fit on any machine. Unlike a cryptographic hash algorithm, the CRC is not specifically designed to resist an attacker crafting a malicious input that would cause a collision. However, it should be sufficient to detect accidental damage. Programs implementing more modern cryptographic hash algorithms are superior to the checksum utilities in avoiding collisions (whether malicious or accidental), but there are still three advantages that the older programs have. First, a system running a historical operating system might not have the hash programs available, but is more likely to have cksum or sum already included. Second, the checksum values are much shorter than the hashes output by the newer programs, making them easier for a user to compare by looking at them. This advantage is not as great as it might appear at first, because a common way to check a hash these days is to save a list of hashes and filenames—the hash programs can use that and do the comparison themselves, sparing the user from having to validate it character by character. The third advantage is that cksum prints the input length in bytes. This greatly limits the number of inputs that could be maliciously crafted to create a collision. I did a moderate amount of research on implementations of modern cryptographic hash algorithms and found that some, such as MD5, SHA-1, and SHA-2, do use the length of the input (often termed "message length" in the literature) as part of the material fed in to the algorithm, but none of the hashing utilities present this length to the user as part of its output. There are two possible reasons for this that seem evident to me. First, if one is hashing a password, you would certainly not want to give a clear indication of its length—that would give any attacker a massive head start on guessing the password. However, that doesn't explain why one would avoid printing the input length for a file that is made publicly available. Second, it is convenient in many contexts, such as database entries or in software (such as git ), for the hash to be a fixed length. Including an extra value that can be of variable length would complicate those use cases. However, the length value could simply be dropped and they would be no worse off than they are currently. Historically on UNIX, password hashing was treated differently from checksumming files— the crypt() function 12 was used for passwords while sum and later cksum were used to confirm a file's integrity. So even rather early on, these two use cases employed algorithms with different properties, but I haven't dived into the history deeply enough to know how intentional this was. My discussion in this episode focuses on the file use case, so understand that I'm largely avoiding the topic of password hashing. Digital signatures are yet another use case, one that I'm ignoring entirely. Every few years, some security researcher declares a particular hash algorithm to be "broken" and that everyone should move over to a new one, which generally has a longer hash. While the larger hash space certainly reduces the opportunity for collisions, this disrupts workflows, such as publishing information about software releases by e-mail, which still tends to observe a 78-character limit on each line 13 , making it harder to include a list of hashes with filenames next to them. This is in addition to the work of modifying software and scripts to use the new algorithm and managing how to treat past data. It seems to me that publishing the input length along with the hash would make it far more difficult to craft a malicious input that matches both, but I haven't found discussion of that during my investigation. (See the Appendix for a possible implementation.) Perhaps someone listening can record a response episode for HPR explaining that. References: Payment card number https://en.wikipedia.org/wiki/Payment_card_number Ethernet frame: Frame check sequence https://en.wikipedia.org/wiki/Ethernet_frame#Frame_check_sequence Cksum specification https://pubs.opengroup.org/onlinepubs/009695399/utilities/cksum.html GNU coreutils manual: sum https://www.gnu.org/software/coreutils/manual/html_node/sum-invocation.html FreeBSD 15.0 sum manual page https://man.freebsd.org/cgi/man.cgi?query=sum&sektion=1&manpath=FreeBSD+15.0-RELEASE+and+Ports 3BSD sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/man/man1/sum.1 3BSD sum source https://www.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/src/cmd/sum.c UNIX/32V sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=32V/usr/man/man1/sum.1 UNIX/32V sum source https://www.tuhs.org/cgi-bin/utree.pl?file=32V/usr/src/cmd/sum.c System III sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/man/man1/sum.1 System III sum source https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/sum.c Crypt specification https://pubs.opengroup.org/onlinepubs/009695399/functions/crypt.html RFC 2822: Internet Message Format: Line Length Limits https://datatracker.ietf.org/doc/html/rfc2822#section-2.1.1 OpenSSH 10.1 released https://lwn.net/ml/all/dd12623ae86aa5eb@cvs.openbsd.org/ Appendix The MD5 hash algorithm was (and still is) widely used, but many people characterize it as being "broken" and discourage its use. Let us imagine a variant of this, called MD5.L, where the normal MD5 hash is followed by a "." character and the input length expressed as a hexadecimal number. Take, for example, the e-mail message announcing the release of OpenSSH 10.1 14 . At the bottom, it includes an SHA-1 hash and an SHA-2 256-bit hash for the available gzipped tar files. That longer hash is encoded with Base64 because if it were given as a hexadecimal number, it would make the line longer than 78 bytes. The MD5.L hash of the file would be one character shorter than the SHA-1 hash, as shown below. (The extra length of the name makes them both consume the same number of characters. The hashes shown are for the "portable" version of OpenSSH.) Some people claim SHA-1 is also broken, seeking to have people use newer and longer hash functions. For an attacker to compromise MD5.L in this example, they would not only have to create a valid tar file compressed with gzip containing a malicious payload having the right MD5 hash, that file would have to be exactly 1,972,831 bytes long (the decimal equivalent of 1e1a5f). While there are still many possible inputs that could be tried (256 1972831 , to be exact*), this is far fewer than the infinite possibilities for plain MD5, SHA-1, or SHA-2. If for some reason it is super important to have a fixed hash length, let's imagine another variation called MD5+L. In this one, instead of L being the input length, it is the input length modulo one terabyte (2 40 bytes), which can be represented by 10 hexadecimal characters, left-padded with zeros. While this approach substantially increases the number of possible inputs an attacker could try, it is likely that an intended victim would notice that the file they downloaded is larger (or smaller) than expected by that much. The MD5+L hash is longer than a SHA-1 hash, but still shorter than a 256-bit SHA-2 hash. SHA1 (openssh-10.1p1.tar.gz) = 7fd17b99d1beffb47cd380d64079e920bb0bd91f SHA256 (openssh-10.1p1.tar.gz) = ufx6K4JXlGem8vQ+SoHI4d/aYU3bT5slWq/XAgu/B1g= MD5.L (openssh-10.1p1.tar.gz) = 80dd9bb00a86519934710d05903fdf07.1e1a5f MD5+L (openssh-10.1p1.tar.gz) = 80dd9bb00a86519934710d05903fdf07+00001e1a5f Of course, if MD5 is considered to be too weak even with the inclusion of the length, one could produce a ".L" or "+L" version of any hash function. However, longer hashes will end up running into the 78-character limit. *This is a number with 4.75 million digits that the bc utility on my laptop took almost 5 minutes to calculate. Provide feedback on this episode.

Audio Transcript Elders here and I get the privilege of preaching for you guys this morning. So quick announcement before we get too far. It is a holiday weekend, so we don't have our full kids ministry as usual. So we have, we'll get all the kids in here today. So we got snacks and activities over there kind of where you walk in and then if, if, you know, I got four boys, we only got two here today. So I get it. If they get a little antsy and we need some more room to run, you can go through this back door here, you know, kind of turn back around this way. But we have a meeting room down there where I think the service is projected and just, just some space for the kids to move and you can still follow along with the service. So, yeah, like I said, my name is Rob Fisher, one of the elders here, privileged to. Privilege to preach for you guys today. And so every summer we try to give Aaron, our main teaching pastor, the at least eight weeks off or so out of the pulpit. We think it's important for a couple reasons we want, you know, the Bible says that elders should be, should be able to teach. So we try to get all the elders in here and we also elevate. We elevate preaching, not the preacher. You know, we think it's important not to. We love Aaron. We love the faithful week. He does faithful work. He does week in, week out. But we think it's important to, to be developing other voices and not just be only receiving the word from, from one guy. Now I will say Aaron is preaching his campground this weekend. So they've done a lot of faithful ministry there and we're excited they can do that. So just an overview today we're continuing our series through the book of Exodus. So we're in Exodus chapter 6 today. So we'll start out by reading the text. We'll pray together. Then we're going to work through the text together really line by line. And Lord willing, after we're done working through it, we'll put some main points to it and some themes and we'll see how God is going to use the life and the story of Moses to inform us how we should live in the here and now. Right? So again, we're in Exodus chapter 6 today. We can go ahead and turn there. Continue, continue to the book of Exodus. We're doing this summer. We're going to follow the life of Moses. God has been calling him to be a, to be a part of delivering the Israelites out of Egypt. And we're going to we're going to pick up here in chapter six. So this is the word of the Lord. But the Lord said to Moses, now you shall see what I will do to Pharaoh. For with a strong hand, he will send them out. With a strong hand, he will drive them out of his land. God spoke to Moses and said to him, I am the Lord. I appeared to Abraham, to Isaac and to Jacob as God Almighty. But by my name, the Lord, I did not make myself known to them. I also established my covenant with them, to give them the land of Canaan, the land in which they lived as sojourners. Moreover, I have heard the groaning of the people of Israel whom the Egyptians sold as slaves. And I have remembered my covenant. Say therefore to the people of Israel, I am the Lord. And I will bring you out from under the burdens of the Egyptians. And I will deliver you from slavery to them. I will redeem you with an outstretched arm. With great acts of judgment, I will take you to be my people. And I will be your God. And you shall know that I am the Lord, your God, who has brought you out from under the burdens of the Egyptians. I will bring you into the land that I swore to give to Abraham, to Isaac and to Jacob. I will give it to you for possession. I am the Lord. Moses. Thus. Moses spoke thus to the people of Israel. They did not listen to Moses because of their broken spirit and harsh slavery. So the Lord said to Moses, go in. Tell Pharaoh, king of Egypt, to let the people of Israel go out of his land. Moses said to the Lord, behold, the people of Israel have not listened to me. How then shall Pharaoh listen to me? For I am of uncircumcised lips. The Lord spoke to Moses and Aaron and gave them a charge about the people of Israel and about Pharaoh, king of Egypt. To bring the people of Israel out of the land of Egypt. Now these are the heads of their fathers houses. The sons of Reuben, the firstborn of Israel. Hanak, Palu, Hezron and Carmi. These are the clans of Reuben. The sons of Simeon, Jamil, Jamin, Ohad, Jakin, Zohor and Sha'. Ul. The sons of the Canaanite woman. These are the clans of Simeon. These are the names of the sons of Levi according to their generation. Gershon, Kohath and Merari. The years of the life of Levi being 137 years. The sons of Gershon, Libni and Shimei. By their clans, the sons of Kohath, Amram, Ishar, Hebron and Uziel. The years of the life of Kohath being 133 years. The sons of Merari, Mahil and Mushi. These are the clans of the Levites according to their generations. Amram took as his wife Jochebed, his father's sister, and she bore him Aaron and Moses. The years of the life of Amram being 137 years. The sons of Izar, Korah, Nepheg and Zikri. Don't know about that one. Sons of Uzziel, Mishael, Elsaphan and Sitri. Aaron took as his wife El Shaba, the daughter of Amminadab and the sister of Nahshon. And she bore him Nadab, Abuhu, Eleazar and Ithamar. The sons of Korah, Asir, Elkanah and Abiasaph. These are the clans of the Korahites. Eleazar, Aaron's son, took as his wife one of the daughters of Phutiel, and she bore him Phinehas. These are the heads of the fathers, houses of the Levites by their cleans. And these are the Aaron and Moses, to whom the Lord said, bring out the people of Israel from the land of Egypt by their host. It was they who spoke to Pharaoh, king of Egypt, about bringing out the people of Israel from Egypt. This Moses and this Aaron. And on this day, when the Lord spoke to Moses in the land of Egypt, the Lord said to Moses, I am the Lord. Tell Pharaoh, king of Egypt, all that I say to you. But Moses said to the Lord, behold, I am of uncircumcised lips. How will Pharaoh listen to me? Let's pray. Lord, you're grateful for your word. Grateful that we get to learn from it and study it. We're grateful that your word, it studies and examines us as we study and examine it. Grateful for the life of Moses and the story of Moses. We pray that we would be faithful learners of it. We're grateful that you've sustained this church. And we ask that you would. I ask that you would help me speak your truth. Clearly. We don't come here just out of. Simply out of practice. We want it to be beneficial for the building up of your church, beneficial for the equipping of your saints. And. Yeah, we just pray that it's for your glory and for the. For the good of. For the good of those who know you. And it would be a means of evangelism for those who don't. So it's in Jesus name we pray. Amen. So Exodus 6 is just a. It's just one chapter in the larger Moses narrative, right? So before we can focus on the, on the details of this passage, we have to remember where it sits within the larger story. So if we come to chapter six, without considering the setting of Moses life and his calling and the recent events, we're going to miss a lot of the weight of what God says here. So the Bible, right, is first and foremost a book about God and God's work to bring redemption, restoration to a fallen and rebellious and sinful people. And in this section of Exodus, though, God is in the process of bringing his people out of slavery in Egypt, and he's using Moses as his church chosen instrument. And because of that, we get this kind of like mini biography of Moses. So chapter six should be read as a chapter within a larger story. It is an isolated scene, but we can't. We can't really understand that isolated scene without the broader context, right? So before we work through chapter six, we need to. Just briefly, I want to look back briefly at Moses life and just see what's brought him to this moment. So, so Moses was an Israelite boy. He was born into an Israelite family while the Israelite nation is enslaved in Egypt, right? And when he was born, there's an Egyptian decree that says, you know, all the Israelite boys need to be killed. The Israelite nation is becoming too strong. Moses, however, was miraculously saved by his mother. He's eventually adopted by the Egyptian royal family, and he grows up in the Egyptian royal household. He's 40 years old. He's an adult. And Moses, he's somehow knowing that he's actually an Israelite, and he's seeing the slavery and the oppression of the Israelites, his true people. He stops an Egyptian who was beating an Israelite by murdering the Egyptian, right? And the day after his murder, Moses realizes he's like, I am in trouble. So he flees, he settles in a foreign land. He lives out. And he lives out 40 years, the next 40 years, right, as a shepherd in Midian. So he has a Midian wife, he has a Midian family, he has an occupation, and he's made a life for himself in this. This foreign land. Now, while Moses is being a shepherd, he has an encounter with God. God charges him to be the means by which God takes the nation of Israel out of Egypt. And in that encounter, Moses raises a lot of objections about his own shortcomings for the tasks. We're going to get into more. We're going to get into more of those shortcomings as we continue. But just know that Moses had a lot of questions and concerns about the task that God is giving him. And in response to Moses concerns and questions, God gives Moses powerful signs and miracles to demonstrate his power. And God also gives Moses the help of his brother Aaron to act as Moses spokesman, since Moses is always expressing his concern over his inability to speak well. Right? So that initial exchange between God and Moses is like all of chapter three and half of chapter four. Then at the end of chapter four and through most of chapter five, Moses then is acting on God's command to go back to the people of Israel who are enslaved in Egypt, and then to Pharaoh and to tell them that, you know, God is going to bring them out of Egypt, right? So Moses and Aaron, initially, they go to the elders of Israel. They tell them, God is going to deliver you from Egypt. And obviously this is well received, as we can imagine. And the Bible says the people believed and bowed their heads and they worshiped. But next, in chapter five, the end of chapter five, Moses and Aaron take their message to Pharaoh. And it goes about as well as we can imagine. So we covered last week. It was. It was far from well received by Pharaoh. Pharaoh does not let the Israelites go. And instead of letting them go, he increases their workload. So the Israelite work leaders take their complaints to Pharaoh. Pharaoh receives them without a shred of sympathy. And the Israelite slaves, then they turn their frustration towards Moses and Aaron. And that's seen at the last, at the end of chapter five. Here. This is the last scene that we have before we go into where we're starting today, into chapter six. So I'm going to read you these verses that lead up to where we're going to start from today, so we can get a grasp on the setting here. So Exodus 5, 20, 23 says they met Moses and Aaron. This is the. They say the Israelite foreman who are waiting for them as they came out from Pharaoh. I just can imagine the scene. Moses and Aaron are outside the meeting room. They're just like, oh my gosh, this is not going good, right? And they say to them, the Lord look on you and judge you because you have made a stink in the sight of Pharaoh and his servants. You've put a sword in their hand to kill us. Moses turned to the Lord and said, lord, why have you done this evil to this people? Why did you ever send me? Since I came to Pharaoh to speak your name, he's done evil to this people, and you have not delivered your people at all. So again, the background matters here, because chapter six Begins with Moses discouraged. The people are downcast and Pharaoh is unmoved. So when God replies to Moses, he's replying to, you know, he's replying to his chosen instrument. Moses is still chosen, but the chosen instrument is once again, he's questioning God's plan. He's questioning God's timing, he's questioning his own calling. So we enter chapter six. Keep this God's. Chapter six is God responding to this mood in Moses. And he's answering Moses's frustrations and fears. So in response to Moses complaints, God is gonna, he's gonna reply to Moses questions, not directly, but rather he's gonna call. He's gonna call back to his previously stated purposes. So God is, there's, there's kind of a short answer in verse one, and then there's the long answer in verses two through eight. So verse one says, the Lord said to Moses, now you shall see what I will do to Pharaoh. With a strong hand, he will send them out. With a strong hand, he will drive them out of his land. So the short answer is that God is going to use his strong hand. And this verse, right, the verse is a good reminder to be a good and thorough student of the Bible, right? If we read this over too quickly in this translation of the Bible, it's like it's not clear who the strong hand belongs to, if it's God or Pharaoh. But if you look in the commentaries or the translation, it says the first and second strong hand, it's God. This is all God's work. And this is similar language to the initial conversation between God and Moses at the burning bush about this, how this interaction would go. So like Moses first encounter with God at the burning bush, it lays out how the deliverance process is going to go. And we don't see all the details of the narrative laid out in the in the burning bush conversation, but we see, we can see most of the narrative cover. So Exodus 3, verses 19 and 20. We also, God is using the similar language to convey, to lay out the extraction process of how it's going to go. He says, I know the king of Egypt will not let you go unless compelled by a mighty hand. So I will stretch out my hand, my hand again, and strike Egypt with all the wonders that I will do in it. And after that, he will let you go. So this, this repeated language matters, right? The strong hand, the mighty hand, the outstretched arm, it all points us to the same truth. Israel's deliverance is only going to come by God's power, right? Israel's deliverance is only going to come by God's power. So when we think about verse one, it's just important to see that God is clearly stating that the deliverance of his people will be by his power, his mighty, strong and active outstretched hand. It's important to note that it's not from the willpower of Moses over Pharaoh, and it's not from the generosity of Pharaoh either. Right? The Israelite people can only be on. They're only going to be delivered by the workings of a strong and all powerful God. And the people will be led by Moses, he says, but only because Moses is the man that God chose to be the messenger. So the people would be freed by Pharaoh, but only because of the more powerful and strong mighty hand of God that he showed over the stubbornness of Pharaoh. Right? So God's short answer to Moses is that my promise is not wavered. Moses says, why me? Why is this so hard? Why can't we make any progress, right? God essentially says this. He says, keep watching what I will do. So the current difficulty Moses finds himself in, it's not evidence that God's plan has failed. It's actually evidence that things are going to according to plan. Like Pharaoh will not be easily moved. This was laid out at the burning bush, right? So in God's short answer to Moses in verse one, that's, that's the short answer in verse one. But now let's look at the longer answer, verses two through eight. So as I was reading and I was meditating on this task, being prepared for this, I was just struck again at how God's lengthier reply to Moses groaning again. It's a repetition of something that's already been laid out in the Moses narrative, right? It's been laid out in God's conversation with Moses at the burning bush. So looking at verses four and five, it says, I established my covenant with them to give them the land of Canaan. And I heard people's groanings as slaves. And I remembered my covenant. I remembered my covenant. The same language that Moses uses. So Moses wrote all this when he writes the end of chapter two. At the end of chapter two, just this huge turning point in the narrative, you know, Moses has established himself in the land of Midian. Meanwhile, business as usual, we can say, continues in Egypt. And the rest of the nation of Israel is still under the oppression of Egyptian slavery, right? Chapter 2, verse 23 and 24 says, the people of Israel are crying to God for help to be freed from slavery. And God hears their Cries the key words here. God remembers his covenant with his people. God remembers his covenant with his people. After that, the narrative turns and God calls Moses at the burning bush. Right then, in the burning bush encounter between God and Moses, God twice recalls his covenant to give the land of Canaan to the offspring of Abraham. And that covenant is going to pull us way back to Genesis 12, the Abrahamic covenant in which God promises. Abraham says, your offspring will inhabit the land of canaan. So Genesis 12 is really the basis of the Exodus narrative because it's setting, it's establishing the promise that God's people will have a home where they can live and prosper and worship the true God. Now, keep working forward through verses 6, 7, and 8, God is gonna. He's gonna drive the details of this promised home even further. It's his promise to his people to remember the covenant, right? So verse six says, I, God, I'm going to free you from Egyptian slavery. And we see the imagery of God again here says, I'm reaching out and pulling his people out of slavery with an outstretched arm. In chapter four, God says, I'm going to use a mighty hand. In the beginning of chapter six, he says, I'm going to use a strong hand. And now here in chapter six, verse six, God says, it's worth an outstretched arm with great acts of judgment, right? In verse seven, it says, you will be my people, I will be your God, and you will know that I brought Israel out of slavery. And finally, verse 8 reminds us of the covenant that God made with Abraham. Says God, the promise that God would give the land of Canaan to the Israelites. Okay, so that's our first eight verses of this chapter. And this narrative is going to continue in verse nine. And Moses is going to start taking action on these commands next. But before we get into that, let me just look it back on these eight verses. I want to summarize as best I can here. So verses one through eight, they're. They're God's reply to Moses's grumblings, really, at the end of chapter five. And so if this were like. So I was thinking about this. This is a TV show. It's divided into episodes, right? Chapter 5 ends with. With Moses in the depths. He's standing outside of the meeting place if the Israelite foreman had just brought their failed appeal to Pharaoh. And so, like, right before the credits roll, Moses is just discouraged. He's frustrating. He's wondering why his obedience to God's commands have only made things worse. And I was thinking about this, the Bible doesn't tell us. We don't get any physical demonstrations from Moses in this moment. So I can only imagine it from my own experience. But I'll just say this, if you don't know me, I've worked in construction management for the last. Trying to remember now, 6, 7, 8 years now 9 out of 10 days wear work boots, jeans, a butt down shirt and a hat. When I need to look more presentable, I just don't wear the hat. Okay? Right. But when something goes wrong on a job site, which believe it or not, sometimes happens, right, the person responsible, usually me, you have to figure out what happened, we have to figure out how to fix it. You have to figure out how long it's going to take and then you have to explain it to everybody involved. Right. And then sometimes when multiple things go wrong at once, like my hat comes off, it's a good thing to throw when you're frustrated, right. And your hands go through, your hands go through my hair like this, right. And you're just going, I don't know anything, I don't know anything about anything. Right. But this is like, this is the kind of human frustration that I, that we see Moses in here. Like, we obviously don't know what he was wearing. We don't know if he wears a hat, if he throws it, we don't know if he turned around and kicked the sand or punched the wall. But, but because, but the, his words here, they're a man overwhelmed by a mission that seems to be collapsing in front of him. And we see this frustration mounting in Moses right here. So that, so Moses again, just keep this in mind before this whole conversation happens. Moses is rejected by Pharaoh, he's blamed by the Israelite foreman. And then he's just kind of like, he's like, this is all going backwards. Like nothing is going right here. So his questions at the end of chapter five, they're not like calm theological observations. They're the words of a desperate man. And he's like, he's like, I'm trying to be obedient, but all I'm doing is leading to more suffering here. So that's the first thing to remember in these first eight verses, right. God's answer is replying to a moment of great frustration. Okay, the second thing to remember here is that God never told Moses it was going to be easy. He was like, like at no point was he like, you're just going to waltz in there and it's going to, you know, it's one conversation. It's over, right? It's not how it's laid out. From the burning bush onward God. He's already told Moses that Pharaoh would resist, that the deliverance would require God's mighty hand. So God's reply isn't a change of plan. It's more of a reminder of the plan that he's already revealed. And it's a reminder that Moses, he's like, you should have expected some hardship here, right? And the third thing to remember about these first eight verses, it's God presenting himself as the covenant maker and the covenant keeper. And God is delivering Israel from slavery by delivering Israel from slavery and bringing them one step closer to the land of Canaan. It's more than Moses assignment. It's actually. It's God fulfilling the promise he made to Abraham. So Moses has to trust in this difficult obedience. He says, I have to trust that this is a part of God's larger plan. Okay, okay, we'll keep working through it here. Let's look at verses 9 through 13. I'll read these for us. Just to refresh it here. Moses spoke thus to the people of Israel, but they did not listen to Moses because their broken spirit and harsh slavery. So the Lord said to Moses, go in, tell Pharaoh, king of Egypt, to let the people of Israel go out of his land. But Moses said to the Lord, behold, the people of Israel have not listened to me. How then shall Pharaoh listen to me? For I am of uncircumcised lips. The Lord spoke to Moses and Aaron and gave them a charge about a people of Israel, about the people of Israel, and about Pharaoh, king of Egypt, to bring the people of Israel out of the land of Egypt, Egypt. So. So first of all, here, I think we got to give Moses a little bit of credit here. He has some. We have obedience without grumbling in this case, right? He does what God commands. He's delivering the covenant reminder message to the people. But he hits another setback here. The message falls on deaf ears, right? Verse nine says that they don't. They wouldn't listen because their broken spirit and the harsh slavery. So, like going back to chapter five, Pharaoh's strategy has worked, at least for the moment. And the burden on the Israelites has become so heavy that, like, the mental occupation of survival has crowded out any glimmer of hope. And it's just one of the painful realities of this passage is like, when people are. When you're just crushed by the weight of the present moment, it's hard to see any promise of the future. So the Israelites, I don't think they're rejecting God's promise because it's untrue. I think they're just too burdened to receive it right now. So then moving forward in verses 10 through 13, the focus is going to shift from, from the people's inability to hear God's promise to Moses ongoing struggle to trust God's calling. So, so God tells Moses, he says, go back to Pharaoh and command to let Israel go. But immediately, Moses immediately goes back to his familiar objections. And Moses argues that, he says, if the people of Israel won't listen to me, Pharaoh certainly won't, right? He's like, these are the people. I'm these people who are going to benefit from this, right? Why is Pharaoh gets nothing out of this? Why would he listen? He says, he says, I have uncircumcised lips. And other translations say I have faltering lips, I have poor, poor speech. So in other words, Moses is saying the people who should most want to hear this message are not listening one, and then two. So why should Pharaoh? And lastly, third, I'm still not a good communicator. So God answers, he answers both objections. He gives a charge to Moses and Aaron. And Aaron's present presence is an answer to Moses concerned about speaking, right? Like we go back to chapter to the burning bush encounter. God says, I'll give you Aaron to help you speak, right? So just having Aaron there is an answer to one of the objections. Then the charge itself to Moses and Aaron, it just keeps it mission focused, right? He says, you gotta speak to both Israel and Pharaoh because God me, I am still intending to bring the nation of Israel out of Egypt. So, so neither Pharaoh's resistance, nor Israel's discouragement, nor Moses insecurity can overturn God's command. Okay, so that's, so we're through verse 13 now. Now at this point the narrative is going to pause for a genealogy and like, rather than skipping over it, we need to, we need to, we need to look through this and see how this serves the, the flow of chapter six and how it fits within larger narrative of the Old Testament. This is by no means the, the longest or the most, the most thorough genealogy of the Old Testament. But this one, the purpose of this genealogy, it's going to anchor Moses and Aaron and the family line of Israel. And it reminds us that this rescue mission that we're on here is, is tied to God's long standing covenant promise. So we see the genealogy start with Reuben and Israel, and Israel is another Name for Jacob. And Jacob, right, is the grandson of Abraham, Abraham, Isaac, Jacob. And so we see again that Moses, he's just God's tool to fulfill the covenant between God and Abraham. Okay. And secondly the text self identifies its purpose in verse 26 to 27 says these are the Aaron and Moses to whom the Lord said bring out the people of Israel from the land of Egypt by their host. It was they who spoke to Pharaoh, king of Egypt, about bringing the people of Israel from Egypt. This Moses and this Aaron. So by including this family history, Moses connects the deliverance of Egypt back to Abraham, Isaac and Jacob. He's not just, he's not stepping into this random moment in history. He's being placed place within the covenant story of God that God has been working on for generations. So this genealogy reminds us that God's promise has a history and his faithfulness is not interrupted by Moses weakness or by Pharaoh's resistance. Okay, final section of text here, verse 28:30. It's going to return us back to the main narrative, right? God is again going to direct Moses to speak to Pharaoh. And that's going to set us up for the events in chapter seven, right? There's a slight, there's a slight difference here. It says, tell Pharaoh, King of Egypt, all that I say to you. So we're kind of setting up for what's going to be happening next here. But this genealogy has reminded us that God's covenant purposes are still moving forward. And now the narrative is going to remind us that Moses has to continue forward as God's messenger. Right? But Moses again is going to repeat his old objection. He says, I'm not a strong speaker. How will Pharaoh listen? And the chapter is going to end with this kind of unresolved, unresolved tension in Moses mind. But not, not an unresolved, but nothing unresolved in God's plan. Right? The tension is with Moses. So that's our, that's our, that's our text, that's our passage. So Lord willing, let me just try to wrap this up for us here. It's not, it's not hard to see the repeated patterns here, right? As I, when I start writing a sermon, I have the Bible and I have a blank piece of a yellow legal pad. And I just, I make notes verse by verse, verse by verse. And as I'm doing this, I'm like, Moses complains about inability. God reminds him of God reminds Moses of God's greater purpose. Moses complains again. God reminds Moses again. Moses complains. I mean I Mean, it's like, it's not, it's not a. We don't have to be scholars here to see this repeated pattern, right? But that's like the power of the narrative, though. Like God is giving Moses this clear command. It's grounded in his power, it's grounded in covenant faithfulness. But Moses just keeps going back to his own weakness. Then God keeps pointing Moses, think beyond yourself. He's like, he's pointing Moses away, away from himself. He's pointing Moses back towards God who can accomplish the deliverance, right? And as we think about applying this passage, we have to be careful that we don't turn this into like the hero's journey of Moses and needing to believe in himself, right? The main point is not that Moses finally finds enough courage within himself. And that's the risk. These well known Old Testament narratives like Joseph, Moses, David, Daniel, Jonah, to name a few, that's the risk of these passages. The main point of these is that God is faithful, God is powerful, and God is using weak messengers to carry out his saving work. And that the danger in reading these like famous biblical narratives as if their deepest lesson was merely like, follow the healer's good traits and avoid his bad traits. Like, there's just a we can learn from Moses. But the shortfalling of that is that these characters and Moses, he's not the central figure of the passage, right? The strong arm of God, the mighty hand of God the mighty. The strong hand of God is the force that keeps the story moving forward. So when Moses is just repeatedly questioning his ability to do the work that God has called him to do, in one sense he's right. He's not wrong in his assessment of his own abilities, like Moses did not. He doesn't have the power to change Pharaoh's heart. He doesn't have the power to break the Egyptian oppression. He doesn't have the power to fulfill God's covenant promise. But Moses, still, he just keeps missing the point. It's like God is never asking him to be the deliverer. He's. God is asking him to be the messenger of the deliverer, right? Exodus chapter 3, verses 19 and 20 establish this. They say, I know that the king of Egypt will not let you go unless compelled by a mighty hand. So I will stretch out my hand, this is God speaking, and strike Egypt with all the wonders that I will do in it. And after that he will let you go. So again, God is never asking Moses to be the mighty hand. He's just asking Moses to be the messenger. God is never commanding Moses to fulfill the covenant by his own strength. He's just commanding Moses to be an obedient participant in, in God's plan of keeping the covenant. So guys, if we can, this is like, if we can get this through our brains, we can save ourselves so much worry and hanry and consternation. Like, we are not the Saviors, we are not the Saviors. Moses cannot deliver Israel, deliver Israel by his own strength. And we can't deliver ourselves from the consequences of our own sin. Right? We can't save ourselves. Moses couldn't do it. We can't do it. Salvation belongs to the Lord and our calling is just faithful obedience in that. Now back to thinking about, thinking about this narrative as a whole. Like when we read narratives and especially these biographical narratives, it's easy to be the critic. So I say this next part with some hesitation because I don't, I'm confident I would not have done much better than Moses if I were in this situation. So with that trepidation, I, I, if we can glean one like kind of follow Moses lesson out of this or maybe don't follow Moses lesson. The, the lesson we need to learn is we need to be better at speaking the truth to ourselves, right? Moses has some moments of faithful obedience, but, but he's, more often than not he's, he's just plagued by his own self doubts. So when we think about this in the real world, I think about the phrase, I don't know where I heard it first. It's like you don't rise to the occasion, you drop to the level of your training, right? So I've just gotten done this summer. It's the seventh summer I've coached Demetrius, our oldest in baseball. And the past two summers I've been the first base coach. So I get a little bit of like mid at bat coaching time. And it takes me about half the season to remember that like you're not significantly moving the needle in like player development and talent in the middle of the game, in the middle of the at bat, right? Like you got a player with a bad swing at the beginning of that bat. Nothing you can say is really going to make a significant adjustment in the middle of the at bat. So like in the middle of the, in the middle of the game, in the middle of the moment. Most people, we don't rise to the occasion, we just stoop to the level of the training. Like the game moves so fast, the next moment comes so fast and the next moment is so overwhelming that like you stoop to the level of your training, right? So what we can learn from Moses Bad example here is that we have to be faithful and consistent and diligent in consuming what is right and true and what is from God. And we have to be faithful and consistent and diligent in reminding ourselves that like God is the strong and mighty hand and we are not. Right. And again, in full honesty, I don't think I would stack up much better than Moses. Again, it's easy to be the critic. Our life isn't canonized, Right. The main application is not be better than Moses. The main application is this. Like, we have to be mindful of how highly we view our own abilities and we have to be mindful of how low or not we view God's abilities. Right? We have to be mindful of how highly we view our own abilities. And we have to be mindful of how low or how high we view God's abilities. Right? One of my dear friends and mentors in construction and just life is a man named Travis. He's been doing construction management for over 30 years. He's a wonderful man of God, father of three faithful kids, grandfather, he's in construction terms. He's forgotten more work than I've ever managed and he's forgotten more lessons than I've ever learned yet. Right. If you've been to Lucille Downtown, he managed the renovation. It turned the bank vault into this wonderful event space. He's managed like a 500,000 square foot manufacturing plant. He has the experience and the credentials to be respected. And when I first met Travis, I'd been managing projects for like two years. I was like the most stressed out I had ever been. I had more responsibility than I ever had. Like deadlines in 1, 2, 3, 4 weeks. Coming up, Rachel's eight months pregnant with Chris. I'm like overwhelmed. And I meet Travis. I can remember it's like the Panera in Fitchburg. I'm like, Travis, how do you manage this? And he didn't. I can still remember this conversation. He says he didn't give me any. Do this every day. This is my project management checklist. He goes, you know, Rob, you do everything you can. Sometimes you just have to pray those projects over the finish line. Like that was it. It's like, it's, it's hopefully simple, but. But painfully simple, right? It's like you do all we can, but we have to. We have to. We have to show up, but we have to. We have to show up and do the work that God has called us to. Do diligently. But we have to realize that there are responsibilities and goals that seem impossible for man to shoulder. So we have to have to appeal to the all powerful God for help. So when we think about Moses and our narrative today, like Moses repeated objections, they just reveal we're seeing a man who felt the weight of his own weakness, but he struggled to rest in the strength of God. So church just wrapping this up. As we continue to think about Moses and we continue to think about God using Moses to carry out his work, my prayer is that we would learn to be faithful and obedient voices for God in the world. And not because we're strong enough to accomplish his purposes, but because we serve a God who is. So that's all we got for today. Let me pray for us today and then we'll do Lord supper after that. Lord, what a, What a joy and a burden it is. To be able to. Just take time to go into Moses's life in detail and take time to see, to see his shortcomings and to see, to see your strength and your promises and to see how you're using a flawed and sinful man to fulfill your promises, to fulfill your plan to redeem the world. Like. Pray for us, pray for our church that we would, we would diligently serve, we would diligently show up, we'd be faithful, obedient servants. But we would ultimately remember that it is not, it's not on our own strength. We serve an all powerful God who has a strong hand and a mighty arm. Even thinking of this sermon today, you're using a flawed and sinful man to bring, to deliver a divine and holy word here. So pray these words will not return empty and that they would be faithful for the good of your church, the evangelism of the world, and for the building up of the saints. It's in Christ's name we pray. Amen. The post God Promises Deliverance – Exodus 6: 1-30 appeared first on Red Village Church.

Sha & Jon are back this week and we discussed the following: What's new on streaming and theaters.Jon does a deep dive on Supergirl. A24 collaborates with Google Ai.Disclosure day makes over 200 mil.Werewulf trailer reaction and more! 

Today we preview the 2026 Prefontaine Classic which will showcase some of the most high quality fields we have seen all year. This includes Melissa Jefferson-Wooden taking on Sha'carri Richardson, Shericka Jackson and the Clayton Twins over Women's 100m, Oblique Seville vs Kenny B, Trayvon Bromell and Kanyinsola Ajayi in the Men's 100m, Collen Kebinatshipi vs the Americans in the Men's 400m, Masai Russel vs Tobi Amusan in the Women's 100H, and much much more.-------------------------------------------

The Hidden Light of the Three Weeks Welcome to Daily Bitachon. Today, we are discussing the spiritual messages embedded within the Three Weeks, and how they directly connect to our Bitachon (trust in Hashem). We mentioned previously that the three weeks of mourning between the 17th of Tammuz and Tisha B'Av—which are about to begin this Thursday—correspond to the three-week period from Rosh Hashanah until Shmini Atzeret and Hoshana Rabba. Whether you count 21 or 22 days, these two periods mirror one another. As the Sefer Maharsha explains, hidden within these three weeks of mourning is the tremendous light of the High Holidays and the joyous season of Sukkot. The Meor V'shemesh explains that this is why every year, usually right after Shivah Asar B'Tammuz (as we will this year), we read Parshat Pinchas. Parshat Pinchas contains the Torah portions detailing the Korbanot (communal offerings) for all the major holidays: Pesach, Shavuot, Rosh Hashanah, and Sukkot. By reading about these offerings now, we arouse the spiritual power of the very holidays we are destined to create during these three weeks. The Concept of Transforming Darkness What is the underlying concept here? We can understand this through a teaching from Rabbeinu Yona. A verse in Tehillim (Psalms) states: "Make us happy ( Samcheinu ) corresponding to the days You afflicted us ( k'yemot initanu ), the years we saw evil ( ra'inu ra'ah )." As an aside, I once heard a beautiful explanation of this: We pray for joy matching the days of pain where we " saw evil." It means it wasn't really evil; it only appeared that way to our human eyes. In truth, everything Hashem does is entirely good. In the second gate of Sha'arei Teshuvah (Letter 5), Rabbeinu Yona writes that a person who truly relies on Hashem should place their hope in Him even in the most dire situations, recognizing that the darkness is actually the cause of the light ( כי החושך סיבת האורה ). He brings a proof-text from the Prophet Michah: "Do not rejoice over me, my enemy, for though I have fallen, I have risen; though I sit in darkness, Hashem is my light." On a simple level, this means: I fell, but now I am up; I was in the dark, but now I have light. However, Rabbeinu Yona quotes Midrash Tehillim (on Chapter 22) which takes it deeper: If I hadn't fallen, I never would have gotten up. If I hadn't sat in the dark, I never would have experienced the light. The light coming from darkness and the rising from a fall is not an afterthought. The fall is a prerequisite for the rise. As it says, "A righteous man falls seven times and rises." He actually needs those seven falls in order to achieve those seven ascents. The Secret of Jewish Hope The Ramchal (Rabbi Moshe Chaim Luzzatto), the famous author of the Mesillat Yesharim , writes in his book Ma'amar Hageulah that this concept is the very secret of Jewish Bitachon ( סוד ביטחון ישראל )—the foundation of our enduring hope for the complete and speedy redemption. To bring about this ultimate redemption, vast spiritual preparations and cosmic effects are constantly at play. Those who study Kabbalah understand how this dynamic works: when the Jewish people feel that God is hiding Himself and has forsaken them, that is precisely the time when Hashem is constructing immense spiritual treasure houses. Metaphorically speaking, these treasure houses are limitless in size and grandeur, filled to the brim with the most magnificent jewels and diamonds. When these storehouses are filled to a capacity beyond what the mouth can express, the ear can hear, or the heart can conceive, Hashem will open them. At that time, the Jewish people will delight in unbelievable pleasures that were forged through their hard work during dark, difficult days. This is the true meaning of Simcheinu k'yemot initanu —"Make us happy corresponding to the days of pain." Throughout this long exile, whenever we experienced a lack of light, that light was never lost. Low Light Means Saved Light This is a mind-boggling concept. Hashem takes the light and stores it away in a treasure house. Imagine you were supposed to receive a daily dose of light, but instead, you experienced total darkness. That light didn't vanish; it was saved for later. Therefore, the darker the darkness, the greater the ultimate light will be, because more light is being preserved. "Low light" simply means "saved light." Following this framework, what are the moments of greatest potential light? A Holocaust, an Inquisition, a pogrom. Those were incredibly dark days, but the light was not lost; it was being stored away. Ultimately, we will merit a world of complete tranquility and serenity, where no moaning remains. To add to this point (independent of the Ramchal), the verse says: "Light is planted for the righteous ( Or zarua latzadik ), and joy for the upright in heart." We are planting light right now. And when you plant light, incredible things grow. Reflecting the Divine Light Midrash Rabbah (Shemot 15:27) notes that the moon represents the light of the Jewish people. Just as the moon has no light of its own but receives and reflects the light of the sun, the Jewish people receive and reflect the light of Hashem. The Midrash connects this to the verses, "Or zarua latzadik..." and "Arise, shine, for your light has come." This is the deeper meaning of "Hachodesh hazeh lachem" —"This month shall be to you." We are like the moon; we wax and we wane, we diminish and we grow, but we always retain the capacity to reflect the Divine light. This is exactly what is happening during these Three Weeks. We have to experience a certain level of darkness to cultivate that future light. We must mourn the destruction of the Temple and truly internalize what we are lacking. By moving through these Three Weeks in a state of spiritual darkness, we are actively creating the light of the future Geulah (redemption). It is a wonder of wonders to view the upcoming Three Weeks, starting this Thursday with Shivah Asar B'Tammuz, through this lens. B'ezrat Hashem , we will continue with these vital lessons, but this is a powerful, foundational concept to carry with us.

A number of sources teach that if a person puts on two garments at the same time, he is likely to forget the Torah he has learned. This is mentioned in the Sha'ar Ha'kavanot, based on the teachings of the Arizal. It is brought also by the Mishna Berura. An example is placing one's Kippa in his hat, and then placing the hat on his head, such that he puts on both head coverings simultaneously. Another example is somebody who is going skiing and puts on two pairs of socks – he must put one sock on the foot at a time, rather than placing one sock inside the other and putting them together on his foot. This can also be relevant to a person wearing a shirt and a sweater; he must put on the shirt and then the sweater, rather than putting the shirt inside the sweater and then putting them on together. This applies also to those who wear two jackets; each must be put on separately. The reason for this Halacha is that according to Kabbalah, a garment is surrounded by an "Or Ha'makif" – a "supernal light." In fact, when we recite each morning the blessing "Malbish Arumim," thanking Hashem for the blessing of clothing, we refer to the special "light" that surrounds the clothes that we wear. This "light" has the effect of bringing a person Kedusha (sanctity) and warding off the Kelipot – the harmful impure forces that threaten him. If a person puts on two garments simultaneously, the inner garment does not receive the "Or Ha'makif." It must first be worn alone so it can receive this "light" before the outer layer covers it.

Tom Hardys rapkarriär, Margret är problemet och havets alla monster. Lyssna på alla avsnitt i Sveriges Radios app. Hela veckans Morgonpasset i P3 hör du i Sveriges Radios app.Sommaren är officiellt över – dags att börja förbereda sig för jul. Margret Atladottir är ÄNTLIGEN tillbaka från semestern och efterlyser sin gua sha. David Druid utser henne till ansiktet utåt för psykisk hälsa. Matilda Rånge från P3 Nyheter om att Vinted anklagas för barnhandel och den nya trenden ”darecation”. Vi ringer upp influencern och Parisbon Sandra Beijer om extremhettan i Paris och det tillfälliga alkoholförbudet. David riktar skarp kritik mot Shakiras VM-öppningsnummer och en ABC-reporter har hamnat i blåsväder efter en Bosnien-kommentar. Vi snackar om alla saker som försvinner och sedan ALDRIG dyker upp igen. Dessutom blir det ett hett snack om kvantfysik, Runar Sögaard har hamnat i klammeri klammera och djurexperten Tom Arnbom gästar studion. Vi snackar om den omtalade silverkindade blåsfisken som skapar kaos i Medelhavet och om alla monster som gömmer sig i Sveriges hav. Margret slår dessutom ett slag för att alla ska ha ärter i frysen. Och ja – Tom Hardy har släppt ett överraskande hiphopalbum.Tidpunkter i avsnittet:11:47 Nyhetsfördjupning: Vinted anklagas för barnhandel21:15 Alkoholförbudet i Paris40:32 Nyhetsfördjupning: Darecation1:07:01 Havets alla monsterKapitellänkarna ovan leder till avsnittet utan musik i Sveriges Radios app.Programledare: David Druid och Margret Atladottir.

Gambling has moved from casinos to our phones. FanDuel, DraftKings, BetMGM, ESPN Bet, Kalshi, and day-trading platforms have made “action” available every minute of the day. When is risk-taking legitimate, and when does it become gambling? Is sports betting different from day trading or prediction markets? What are the dangers of addiction, wasted time, and chasing easy money? with Rabbi Chaim Jachter – Rav of Sha'arei Orah in Teaneck, Dayan on the Elizabeth Beis Din – 25:10 with Rabbi Moshe Rotberg – Rav of Zichron Yechezkel, Toms River NJ, Rov of Hatzalah of Central Jersey, Pyscotherapist - 47:11 with Mr. Yehuda Liff – Therapist at Retorno, Specializing in addiction – 1:09:38 מראי מקומות   

Welcome to Daily Bitachon Welcome to Daily Bitachon. Having completed Sha'ar Habechina , we are now going to switch to a more timely topic. We find ourselves in the month of Tammuz , which brings the fast of the 17th of Tammuz, followed by the month of Av and its respective fast. I would like to spend some time understanding the deeper dimensions of these months. Personally, seeing how perfectly planned and intricate the events of Jewish history are always provides a powerful chizuk in emunah , which naturally leads to deeper bitachon . To fully appreciate this, we need some background. We are not in a rush, so we will take our time to truly understand it. This framework is based largely on the teachings of the Ben Ish Chai (in Parashat Devarim ), where he discusses these concepts at length. The Three Dimensions of Conflict: Place, Person, and Time First, the Ben Ish Chai notes that the twelve months of the year are fundamentally broken down into four sets of three, aligned with the solar cycle—what we know as the four seasons. Secondly, we know that from the womb, there was a perpetual struggle between Yaakov and Esav . They fought over everything in existence, categorized by the classic framework of Place, Person, and Time . These are the three core dimensions of our existence: a person lives in a place and moves through time . Place: They struggled over the land of Eretz Yisrael . Person: They struggled over who would hold the status of the Bechorah (the birthright). Time: They struggled over who would control the different seasons of the year. The Summer Cycle: Grabbing the Heel Looking at the summer cycle, Yaakov claimed the spring months of Nissan, Iyar, and Sivan —the three months of Chodesh Ha'aviv . This is a beautiful, spiritually rich period: Nissan contains Pesach, Iyar holds the bulk of Sefirat Ha'omer, and Sivan brings Matan Torah. Yaakov Avinu fought for these three wonderful months and claimed them as his own. Then, the intense heat of the summer begins—a period of strict, intense judgment. This is where Esav takes over. This aligns with the fact that Esav calculates by the sun, and the sun is at its strongest during this time. Esav was originally slated to receive Tammuz, Av, and Elul . However, the Torah emphasizes that Yaakov grabbed Esav's heel at birth, earning him the name Yaakov (from Ekev , meaning heel). This teaches us that each of these three-month cycles has a "heel," or a tail end. Yaakov pulled the heel of this summer cycle—the month of Elul —back into his own domain. This converted what would have been an equal three-and-three split into an unequal four-month to two-month split in favor of Yaakov. The Winter Cycle: Venahapoch Hu We see the exact same pattern repeat during the winter months. Tishrei, Cheshvan, and Kislev belong to Yaakov. Tishrei is the month of the High Holidays. Cheshvan, though it contains no holidays, serves as the time to review and process the spiritual gains of the Chagim . Finally, Kislev brings the light of Chanukah. The next three months— Tevet, Shevat, and Adar —should have belonged to Esav. Tevet contains the fast of Asara B'Tevet . Shevat shares a root with the word Shevet , which means a whipping stick or a staff of judgment, signifying that Shevat also carries an element of strict justice. Adar was also supposed to belong to Esav, but once again, Yaakov grabbed the heel of the cycle and pulled Adar back. This is the deeper secret behind the phrase Venahapoch hu —it was completely turned around. Ultimately, this leaves Esav with only four distinct months of intense judgment throughout the year: Tammuz, Av, Tevet, and Shevat . The Spiritual Mechanics of Heat and Cold It is fascinating to see how something as everyday as the twelve months and the changing seasons trace back to the foundational conflict between Yaakov and Esav. Furthermore, the winter and summer concepts relate directly to the ideas of severe cold and severe heat. What do hot and cold have to do with our spiritual lives? It might sound intense, but our tradition teaches that while Gehenom is made of fire—which is what most people know—there is also a Gehenom of snow. There is a realm of extreme heat (like the Sahara Desert) and a realm of extreme cold (like the North Pole). Both are incredibly difficult environments for life. These two extremes correspond to the two primary ways we stumble: Intense Heat: This represents the burning pursuit of desires and lust. Intense Cold: This represents a state of freezing, spiritual paralysis, and laziness. In the winter months, our primary challenge is to overcome the "cold" of laziness and not simply stay in bed. In the summer months, our challenge is to control the "heat" and not follow our desires. The Gehenom of fire is the consequence of chasing unbridled passion, while the Gehenom of snow is for frozen apathy. Esav is constantly trying to entrap us in these two areas. As Rashi notes, when Esav walked in to receive a blessing from his father Yitzchak, Yitzchak saw Gehenom open up behind him. Esav is the one who ultimately aligns with Gehenom , while Yaakov and his children inherit Gan Eden and Olam HaBa . Historical Precision as a Source of Chizuk These spiritual dynamics repeat themselves every single year. As we overcome the specific trials of the summer and winter, we emerge clean. The calendar is not random or haphazard. Tammuz and Av are months of strict judgment because they are Esav's remaining summer months of intense, severe heat. It is no coincidence that this was the exact time of year the Beit HaMikdash was destroyed by fire. The historical convergence is remarkable. The First Beit HaMikdash , the Second Beit HaMikdash , the Spanish Inquisition, and the outbreaks of both World War I and World War II all heavily converged around this specific window of the year. Rav Eliyahu Lopian once beautifully remarked that if the enemy only realized that the Jewish people actually derive a chizuk in emunah from the fact that these tragic events repeatedly happen at the exact same calendar window, they would have intentionally chosen a different time to attack us! Recognizing that everything is so precisely designed and orchestrated by Hakadosh Baruch Hu is profoundly comforting. It serves to strengthen our emunah and bitachon , giving us the tools to navigate and elevate these challenging times of the year.

Jon & Sha are back this week and they discussed the following:NYC Knicks winning the Championship and the aftermath.The World Cup so far.Evil Dead almost gets a NC-17 rating.The Box Office this past weekend.Discolusre Day buzz, a live Q&A & more!

Plus, UK Rape Gang Inquiry Shocks World, Horrific Findings Detail Over 250,000 Young White Girls Subjected To Repeated Gang Rape, Trafficking, Pregnancy, Forced Islamic Conversion

Today we recap the 2026 LA Grand Prix including Sha'carri Richardson's 100m opener, as well as Kenny Bendarek, Christian Coleman and Letsile Tebogo in the 100m. We also reflect on the NCAA Championships and the multiple all-time performances we witnessed in Eugene.LA Grand Prix Results: https://results.usatf.org/LAGrandPrix26/?mid=9043&en=18-1-------------------------------------------

durée : 00:58:28 - Avec philosophie - par : Géraldine Muhlmann - La philosophie arabe classique s'est développée autour de grandes questions métaphysiques, logiques et théologiques, en articulant raison et révélation. Parmi ses figures majeures, Avicenne et Averroès ont profondément marqué les débats sur la connaissance, l'être et l'interprétation des textes. - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Corinne Amar, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Meryem Sebti Historienne des idées, directrice de recherche au CNRS, Olga Lizzini Professeure des universités, elle enseigne la philosophie arabo-islamique et l'islamologie. Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

durée : 00:59:00 - Avec philosophie - par : Géraldine Mosna-Savoye - Dans "La Peste brune", Daniel Guérin livre un témoignage écrit à chaud sur la montée du nazisme au début des années 1930, nourri de deux voyages à travers l'Allemagne. Marquée par ce texte, l'historienne Ludivine Bantigny nous en parle. - réalisation : Nicolas Berger, Manon de La Selle, Shaïma Giboire - invités : Ludivine Bantigny Historienne, spécialiste de l'histoire des mouvements sociaux et des engagements politiques Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Peter digs into Trivolve Tech's forensic management system after it passed 100,000 on-chain transactions on Cardano mainnet. The episode looks at what the milestone actually represents, how the evidence workflow appears to use hashing and zero-knowledge proofs, and why it stands out as a live government-style deployment rather than another proof of concept.Peter also connects the project to Trivolve Tech's broader work in India, including IndianChain and land-record infrastructure tied to millions of farmers and millions of acres. The result is a grounded look at how Cardano is being used for chain-of-custody records, tamper detection, and large-scale public-sector data integrity.Key Takeaways:- Trivolve Tech's forensic management system has surpassed 100,000 on-chain transactions on Cardano mainnet.- The use case focuses on preserving chain-of-custody integrity for police forensic evidence in India.- The workflow described in Catalyst materials combines SHA-256 hashing with zero-knowledge proofs to detect tampering without exposing sensitive evidence data.- Peter links the project to earlier Cardano Foundation work with Dubai Police, suggesting a broader pattern for blockchain-based forensic records.- Trivolve Tech's IndianChain proposal extends the story beyond forensics into government land and agriculture settlement records.- The episode frames this as practical enterprise adoption on Cardano, not a speculative or purely experimental demo.Links & References:- x.com: https://link.learncardano.io/4eWNUc- https://link.learncardano.io/Fkgrh4- Securing Forensic Chain of Custody for Indian State Govt (1million+ cases per year) Using Cardano and Zero-Knowledge Proofs: https://link.learncardano.io/GM6wgh- IndianChain: Indian Government's 10M+ Settlements on Cardano: https://link.learncardano.io/gEWuXU- x.com: https://link.learncardano.io/OpHZnR- Dubai Police will use blockchain to conduct investigations: https://link.learncardano.io/iKza9NWebsite: https://link.learncardano.io/bQ68RcX/Twitter: https://link.learncardano.io/3a1QtvDisclaimer: This content is for educational purposes only. Nothing constitutes financial advice.DISCLAIMER: This content is for informational and educational purposes only and is not financial, investment, or legal advice. I am not affiliated with, nor compensated by, the project discussed—no tokens, payments, or incentives received. I do not hold a stake in the project, including private or future allocations. All views are my own, based on public information. Always do your own research and consult a licensed advisor before investing. Crypto investments carry high risk, and past performance is no guarantee of future results. I am not responsible for any decisions you make based on this content.

Exploring the lives of three Jewish doctors. Living in very different settings, yet linked by a common thread: compassion. They left a lasting mark on medicine and Jewish history and were dedicated to the strong belief that every fragile life matters. In New York, Dr Martin Couney helped save thousands of babies. His sideshow displays were controversial, but at a time when incubator technology was widely doubted, his exhibits brought life-saving technology into the public eye. Dr Mary Gordon was born in Lithuania and her trailblazing career as a pioneering female physician who was deeply connected to Jewish life, allowed her to carry her medical calling into some of the hardest moments of the twentieth century, in Palestine, in detention camps in Cyprus and through world wars. Dr Shlomo Adler's reputation in London as a beloved doctor and trusted medical confidant to Gedolim and Torah leaders as well as to thousands of patients, rested on his complete commitment to care, innovation and halacha. We also hear from his son Dr Yossi Adler - who has continued a 3 generational family legacy - about AI and other issues confronting medicine today   Timestamps: - **0:00:00 – 0:01:13** – Podcast intro, series context (Medicine Part 2), and mention of guests (Rabbi Tatz & Dr. Yossi Adler) - **0:01:13 – 0:02:16** – Introduction of Mary Gordon; granddaughter of Reb Eliezer Gordon; name changes (Miriam → Mary, Sara → Sylvia)   - **0:02:16 – 0:03:49** – Background on the Gordon family, Telshe Yeshiva, and Reb Eliezer Gordon's leadership and social conscience (matzah bakeries)   - **0:03:49 – 0:06:21** – Fire in Telshe (1908), Reb Eliezer Gordon's fundraising trip to England, his death, funeral, and Mary receiving apology from the Chief Rabbi   - **0:06:21 – 0:09:00** – Mary's struggle to enter university, re-doing exams in England, brilliance and speed of study, financial help from Rabbi Moishe Hirsh Siegel, graduation as a physician   - **0:09:00 – 0:10:27** – Status of women doctors in England; WWI, shortage of male doctors; Mary becomes first female medical student allowed to practice in the army   - **0:10:27 – 0:12:57** – Move to South Africa; reuniting with family; pioneering practice in Johannesburg General Hospital; treating rich and poor, all races; miners' strike of 1922   - **0:12:57 – 0:15:30** – Plans to move to Palestine; WWII intervenes; army medical role, rank of captain then lieutenant colonel; final move to Palestine (1946)   - **0:15:30 – 0:18:18** – Postwar DP situation; Anglo-American committee, Truman's proposal for 100,000 DPs; British refusal; Cyprus detention policy and harsh camp conditions   - **0:18:18 – 0:21:06** – Mary chosen by the Jewish Agency to serve in Cyprus; tiny medical team; overwhelming numbers, disease, births; her legendary dedication; quote about measuring temperature vs pain   - **0:21:06 – 0:22:28** – New Year's 1948 story (two big ships arrive, many pregnant women and newborns); Mary persuades nurses to stay; later work in Israel with Yemenite immigrants; return to South Africa, work in Soweto clinics, death and legacy   - **0:22:28 – 0:24:04** – Introduction of Dr. Yossi Adler; recognition that “Dr. Adler” was a global communal institution   - **0:24:04 – 0:26:24** – Growing up in a house that doubled as a practice; constant stream of patients; balancing family meals with emergencies, especially before Hatzalah   - **0:26:24 – 0:28:18** – What made Dr. Adler's practice unique: long-term relationships, personalized care, deep sense of responsibility, readiness to innovate   - **0:28:18 – 0:32:24** – Early roots of his father's connection to Gedolim (Gerrer Rebbe, Imrei Emes); later relationships with Gedolim and Rebbes (Stipler, R' Shach, Satmar, Klausenburger, etc.)   - **0:32:24 – 0:36:24** – Stories illustrating kavod from Rebbes (“Malach Refael goes with Dr. Adler”), and equal importance of all patients; how he handled treating Gedolim without intimidation   - **0:36:24 – 0:40:21** – Lessons Dr. Yossi learned: time use, achrayus (responsibility), integrating halacha and derech eretz into medicine; a few character-defining stories   - **0:40:21 – 0:44:04** – Role of a frum doctor today: giving clear medical facts for Rabbanim, especially in end-of-life, surgery, fasting, and shidduch situations; why doctor ≠ posek   - **0:44:04 – 0:49:05** – Community health issues:   - Vaccine hesitancy and mistrust of authorities     - Halachic support for following broadly accepted medical guidance     - SIDS reduction through “back to sleep” and risk of complacency   - **0:49:05 – 0:53:59** – Discussion on modern weight-loss medications (semaglutide, tirzepatide): when benefits outweigh risks (severe obesity) vs mainly cosmetic use   - **0:53:59 – 0:56:51** – Google and patient information: opportunities and dangers; importance of joint doctor–patient interpretation rather than self-treatment   - **0:56:51 – 0:57:40** – Rabbi Tatz introduction, playful comment about trying to “one up” Rabbi Hirsch with an unknown medical figure   - **0:57:40 – 0:59:37** – Background of Dr. Cooney (Mikhail Kohn): Jewish origins in Prussia, medical studies, interest in premature infants and early incubators   - **0:59:37 – 1:03:10** – Move to America; transformation into “Dr. Cooney”; sideshow incubator exhibits at fairs and Coney Island; hospitals giving up on babies, parents bringing infants in shoeboxes; high survival rates   - **1:03:10 – 1:05:00** – Framing ethical and halachic questions: doing something risky to save life; early incubators as both spectacle and lifesaving tool   - **1:05:00 – 1:08:32** – Classic halachic scenario: terminal/“Ha'ei Sha'ah” patient offered high-risk procedure with chance of cure vs certain shorter-term survival; introduction to “Lo chosheshin lechayei sha'ah” in this context   - **1:08:32 – 1:12:08** – Majority view:     - If chance of success >50%, patient *should* generally accept.     - If

durée : 00:57:30 - Avec philosophie - par : Géraldine Muhlmann - En grand analyste du roman, Roland Barthes, dans ses essais, étudie les mécanismes du récit, la construction des personnages et les effets de sens produits par l'écriture romanesque. Son approche renouvelle la lecture du roman, en s'intéressant au texte plus qu'aux intentions de l'auteur. - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Philippe Forest Romancier et essayiste, Antoine Compagnon Écrivain, enseignant et académicien français Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

The Kabbalists taught that when one recites the "Ana Be'cho'ah" prayer, he should arrange the words of the prayer in pairs. Meaning, he should say the first two words, briefly pause, say the next two words, pause, and so on. This is the instruction given by Rav Haim Vital (1543-1620), in Sha'ar Ha'kavanot, based on the teachings of the Arizal. This is brought later by the Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909) and the Kaf Ha'haim (Rav Yaakob Haim Sofer, Baghdad-Jerusalem, 1870-1939). However, Rav Meir Mazuz (1945-2025) ruled that one should not follow this custom, as the reading becomes unintelligible in this manner. By reciting the text of this prayer in pairs of words, one ends up saying, "Ana Be'cho'ah" – "Please, with the strength"; "Gedulat Yeminecha" – "the greatness of Your right"; "Tatir Serura" – "release those who are trapped"; "Kabel Rinat" – "accept the prayer of"; "Amecha Sagebenu" – "Your nation, protect us"; "Taharenu Nora" – "purify us, O Awesome One," and so on. The words are clearly not intended to be broken up in alternating pairs of two, as they have no meaning when recited this way. Rav Mazuz therefore ruled that one should recite the text of the prayer this way: "Ana Be'cho'ah Gedulat Yeminecha" ("Please with the power of the greatness of Your right"), "Tatir Serura" ("release those who are trapped"); "Kabel Rinat Amecha" ("Accept the prayer of Your nation"); "Sagebenu Taharenu Nora" ("protect us, purify us, O Awesome One"). (Incidentally, Rav Mazuz issued a similar ruling regarding the recitation of the famous verse, "Hashem Hoshi'a Ha'Melech Ya'anenu Be'yom Kor'enu." The Kabbalists instructed pausing after the word "Ha'melech," such that one should say: "Hashem Hoshi'a Ha'Melech, Ya'anenu Be'yom Kor'enu." Rav Mazuz noted that this reading sounds as though we ask Hashem to save the King ("Hoshi'a Ha'melech"). The proper way to read this verse, Rav Mazuz ruled, is with the pause after the word "Hoshi'a," such that we say, "Hashem save us; the King shall answer us on the day we call out.") Some Siddurim use a very complex system in punctuating this prayer, adding commas and periods, in an attempt to accommodate both opinions. In any event, Rav Yisrael Bitan writes that as the Arizal, the Ben Ish Hai and the Kaf Ha'haim all say that this prayer should be divided into pairs of words, it is difficult to dismiss this practice. Therefore, this is the preferred way to read Ana Be'cho'ah.

This week on Spitball Media, Jon & Sha are back to talk all things movies!Jon reviews Masters of the Universe after seeing it on the big screen, while Sha finally checks out The Backrooms and shares what the theater experience was like.We're also diving into the latest popcorn buckets, theater collectibles, and the wild world of movie merch.Plus, Disclosure Day hits theaters this weekend, and we host our first ever LIVE Q&A!Grab a drink, join the chat, and hang out with us live every Wednesday on YouTube!If you enjoy horror movies, trailer reactions, and film news, make sure to subscribe and join the Spitball Media community. Join us live every Wednesday Night at 7:30 pm, eastern

durée : 00:57:54 - Avec philosophie - par : Géraldine Muhlmann - S'inspirant de la linguistique, Roland Barthes s'intéresse à la science qui étudie les signes et la manière dont ils produisent du sens dans la société : c'est la sémiologie. Dès lors, si la société est un système de signes, pourquoi restreindre leur analyse aux seuls textes littéraires ? - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Typhaine Samoyault Enseignante universitaire, critique littéraire et romancière, Daniel Bougnoux Professeur à l'université de Grenoble, a établi l'édition critique de la Pléiade Aragon Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

After we recite in the morning the section of the Ketoret and the passage of "Abayeh Hava Mesader," we recite a very special prayer – Ana Be'cho'ah. This prayer was composed by one of the great Tanna'im – Rabbi Nehunya Ben Ha'kaneh, whom the Hida (Rav Haim Yosef David Azulai, 1724-1806) describes as one of the earliest Kabbalists, preceding even Rabbi Shimon Bar Yohai. The Ana Be'cho'ah prayer is so significant that the Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909) and many others write that if a person arrives late to Shaharit, and needs to skip the introductory portions of the prayer service, he should not skip Ana Be'cho'ah. This prayer consists of seven lines, each of which with six letters, for a total of 42 letters, and these 42 letters spell the special 42-letter Name of Hashem. This Name is the "elevator," the Name associated with rising to the upper worlds. It is critically important to recite Ana Be'cho'ah as part of our introduction to Shaharit because it elevates us to the heavens so we can present our Tefilot to G-d. By the time we recite the Amida, we want to be standing before the Heavenly Throne, so we can speak directly to the Almighty. The recitation of Ana Be'cho'ah elevates us to the higher spheres so we can speak to Hashem while standing in front of His Throne. It is proper to recite this Tefila slowly and to take note of the first letters of the words. This Name is alluded to also in the first paragraph of Shema, which consists of 42 words (from "Ve'ahabta" through "U'bi'sh'arecha"), corresponding to the 42 letters of this Name. For this reason, some Siddurim feature the letters of this divine Name alongside the words of this paragraph of Shema. Another allusion to this Name is found in Kaddish – specifically, in the phrase "Ve'yishtabah Ve'yitpa'ar Ve'yitromam Ve'yitnaseh Ve'yit'hadar Ve'yit'aleh Ve'yit'halal," which consists of seven words that each contains six letters, for a total of 42. Some have the custom to recite Ana Be'cho'ah each night before going to sleep. The soul departs and rises to the heavens when one sleeps, and so it is appropriate to recite this prayer which, as mentioned, is associated with elevation and ascent. Likewise, it is customary to recite Ana Be'cho'ah at funerals, Heaven forbid, as the coffin is being taken for burial, and the soul is ready to rise to the heavens. In some communities, Ana Be'cho'ah is recited before Lecha Dodi on Friday night, as we elevate ourselves to the higher plane of Shabbat. Likewise, many recite this prayer after counting the Omer, as the Omer counting is intended to elevate us in preparation for Matan Torah on Shabuot. The custom to read Ana Be'cho'ah following the recitation of "Abayeh Hava Mesader" was taught by the Arizal, as brought in Sha'ar Ha'kavanot. This is cited by the Kaf Ha'haim (Rav Yaakob Haim Sofer, Baghdad-Jerusalem, 1870-1939). The Seder Ha'yom (Rav Moshe Ben Machir, Safed, 16 th century), by contrast, writes that it is better to recite Ana Be'cho'ah later, just before Baruch She'amar. He explains that the world was created with the power of this 42-letter Name, and so it is appropriate to allude to this Name just before reciting "Baruch She'amar Ve'haya Ha'olam," when we give praise to Hashem who created the world. However, we follow the Arizal's teaching, that Ana Be'cho'ah should be recited after the section of "Abayeh Hava Mesader." One possible explanation for the Arizal's custom is that the section of "Abayeh Hava Mesader," which lists the various Abodot (services) performed daily in the Bet Ha'mikdash, omits Birkat Kohaim (the priestly blessing), which was recited each day in the Bet Ha'mikdash. In the Bet Ha'mikdash, the Kohanim reciting Birkat Kohanim would use the Shem Ha'meforash – the divine Name that is normally forbidden to utter, and according to some, this was the 42-letter Name. Perhaps, then, we add Ana Be'cho'ah – which is associated with this Name – after the section of "Abayeh Hava Mesader" to allude to the daily recitation of Birkat Kohanim in the Bet Ha'mikdash. The Ana Be'cho'ah prayer concludes with the pronouncement of "Baruch Shem Kebod Malchuto Le'olam Va'ed," giving praise to the exalted Name of G-d, which this prayer expresses.

Today we preview the Oslo Diamond League, including the Men's 200m which will see Letsile Tebogo take on Gout Gout, in what will be his first major meet on the circuit against a truly high quality field. Julien Alfred will also race the 100m, and Karsten Warholm will take on Alison Dos Santos in the 400HThis Sunday, the LA Grand Prix will also go down and Sha'Carri Richardson is expected to make her 100m debut after racing a few 200m in China earlier this year. We will also see Kenny Bednarek, Christian Coleman, Rai Benjamin and Masai Russell competing in LAFinally, we discuss the NCAA Championships going down this weekend with a few notable athletes to keep a look out for.Oslo DL Start Lists: https://oslo.diamondleague.com/en/programme-results/LA Grand Prix meet website: https://www.usatf.org/events/2026/2026-usatf-los-angeles-grand-prix NCAA Champs Live Results: https://flashresults.com/2026_Meets/Outdoor/06-10_NCAA/index.htm ⁠-------------------------------------------

TradeComplianceRecords.com is a hash‑verified registry where brokers, 3PLs and enterprises upload trade compliance documents, which are sealed with SHA‑256 hashes and issued public URLs and QR codes so customs, regulators and AI systems can verify authenticity without accessing internal systems. LinkDaddy LLC City: Clearwater Address: 509 N Prescott Avenue Website: https://linkdaddy.com Phone: +1-727-350-8520 Email: tony@linkdaddy.com

durée : 00:57:46 - Avec philosophie - par : Géraldine Muhlmann - Dans "La Mort de l'auteur" (1967), Roland Barthes critique l'idée d'un auteur maître du sens de son œuvre. Il affirme que l'interprétation d'un texte ne dépend pas des intentions de l'écrivain, mais du fonctionnement du langage et de l'activité du lecteur. - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Eric Marty Écrivain et universitaire, Vincent Kaufmann Professeur émérite de littérature et d'histoire des médias à l'université de St. Gall en Suisse Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Knox Brew Stories is a weekly live radio show and podcast that offers an in-depth look into the beverages, businesses, artists, and inspiring humans who make Knoxville an amazing place to be!In this episode you'll find our regular weekly news about craft beer, as well as:Brew News (6:20)Live Music with Darrow (9:17)Interview with Sha & Ariana of Fleurish (18:17)Live Music with Darrow (48:28)Next Week on Tap (56:19)Live Music with Darrow (57:56)Co-Host & Producer: Ace Preston Co-Host & Producer: Kevin SummittAudio Engineer: Clyde TimbsPodcast Producer: Asher CokerLinks for our featured Guests:https://www.instagram.com/fleurishknoxville/https://www.ijams.org/event-details/special-event-fleurish-2026-a-sustainable-fashion-eventhttps://www.instagram.com/darrow_music/https://distrokid.com/hyperfollow/darrow4/youngBe sure to tune in live every Monday at 6pm EST at http://ChannelZradio.comAnd check out https://www.knoxbrewstories.com/ and https://www.instagram.com/suttreeshighgravity/

durée : 00:58:12 - Avec philosophie - par : Géraldine Muhlmann - "Le Degré zéro de l'écriture", publié en 1953, est un essai majeur de la réflexion littéraire du 20ᵉ siècle. Roland Barthes y analyse les rapports entre langue, style et écriture, montrant que l'écriture est toujours un choix historique et idéologique. Il développe la notion de "degré zéro". - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Mathieu Messager Maître de conférences en langue et littérature française à l'Université de Nantes., Justine Brisson Docteure en littérature française Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Auto-generated transcript: Alhamdulillah Rabbil ‘Aalameen, wa salatu wasalamu ala ash-Sha’ifa al-Anbiya’i wal-Mursaleen, wa hamdu lillahi Rabbil ‘Aalameen. Tasliman kathiran kathira. I am about to share with my brothers and sisters the first hadith in Al-Baqarah, narrated by Umar ibn al-Khattab (RA). He said: “The first thing is…” This is an important thing for us to… Continue reading Attitude decides benefit

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

Working women, "big dogs" who want a soft life. Are UFOs real? Go and forgive your mother, and overcome fear.

Almost 9 years since the big split of the Bitcoin community, it's time to learn more about how the Bitcoin Cash chain developed. Calin Culianu is the creator of Fulcrum, an efficient privacy-preserving SPV client. Steve Thurmond is the most ardent advocate for Cash Stamps: a convenient paper wallet system that's used for gifting. Throughout the episode, more BCH community members will join to have the conversation that you will never hear on any other Bitcoin podcast. Time stamps: 00:01:09 Introducing Calin Culianu & Steve Thurmond 00:02:37 The Evolution of Bitcoin Cash 00:03:59 Who is Behind Bitcoin Cash Now? 00:06:34 Narratives and Misconceptions 00:07:53 Vlad's Perspective on the Fork 00:09:44 Bitcoin's Capture and Speculative Nature 00:11:48 Vlad's Journey with Lightning Network 00:16:07 Blockstream and the "Banker" Conspiracy 00:18:33 The Security Budget Debate 00:22:12 The Problem with IOU Systems like Lightning 00:24:02 Vlad's Disappointment with Onboarding 00:24:58 Ethereum's Rise Amidst Bitcoin's Infighting 00:27:52 The Bankers Won, But Crypto Still Exists 00:32:16 The Future of Bitcoin and Firing Core Devs 00:33:08 The Wall of Consensus in BTC 00:39:19 The Multi-Coin Future 00:42:48 Bitcoin Cash's Development Philosophy 00:49:08 Craig Wright's Controversial Involvement 00:55:16 The Impact of Contentious Forks 00:58:55 The Resilience of Bitcoin Cash 01:02:32 The Value of Open Source Competition 01:08:51 Greg Maxwell's Influence 01:12:00 The Ecash fork 01:25:02 Introducing New BCH Community Members 01:26:38 Building Smart Contracts on Bitcoin Cash 01:34:06 Why UTXO is Better than EVM 01:40:07 Can You Run a BCH Node? 01:41:07 The Flawed "Run a Node" Narrative 01:53:27 The Dangers of RBF and the Importance of 0-Conf 02:05:07 One-Minute Blocks Proposal 02:08:02 Finality and User Experience in Wallets 02:12:13 The "It's Just Money, Bro" Philosophy 02:41:39 What Can You Buy with BCH? 02:48:28 The Permissionless Nature of BCH 02:52:12 The Paradox of Layer Twos 02:57:18 The Stigma of Building on BCH 02:58:21 The Changing Culture of Bitcoin Cash 03:11:35 Ordinals and the "Spam" Debate 03:17:07 Would BCH Still Have a Nice Dev Culture If Michael Saylor Started Buying? 03:28:14 Quantum Computing and Satoshi's Coins 03:42:59 The Tail Emission Debate 03:50:11 The Culture is the Ultimate Defense 03:53:16 The Politicization of Bitcoin Development 03:59:26 Privacy and Fungibility 04:02:21 The Future of Privacy on BCH 04:36:12 Fulcrum: An Electrum Server Implementation 04:38:54 The Litecoin Question 04:49:13 The Difficulty of Recreating Bitcoin's Genesis 04:51:38 The Long-Term Bet on SHA-256 04:54:12 A Break and Introduction to Rosco 05:48:33 CashScript and Smart Contracts on BCH 05:55:22 BCH vs. Ethereum Smart Contracts 06:03:05 The UTXO Stack and Abstraction Layers 06:43:30 The Avalanche Pre-Consensus Question 06:45:51 The "Tax" Fork 07:04:06 The Failed Attack on Bitcoin Cash 07:08:58 The 2018 Inflation Bug Disclosure 07:22:46 The Michael Saylor Phenomenon 07:28:41 The Arrest of Roger Ver 07:39:28 Spending Crypto in the Real World 07:44:22 The End of Crypto-Friendly Spaces in Europe 07:52:05 Prediction Markets and Community Sponsorship 08:08:17 Robin Linus is Jealous of BCH Opcodes 08:09:50 Final Thoughts and Conclusion

durée : 00:59:11 - Avec philosophie - par : Géraldine Muhlmann - Le “Discours de la servitude volontaire” a été écrit autour de 1548 par Étienne La Boétie. Pour Miguel Abensour, cette thèse de La Boétie était une “hypothèse scandaleuse”. Pourquoi s'agit-il d'une hypothèse transgressive en philosophie politique ? - réalisation : Frédéric Worms, Anna Pheulpin, Carla Michel, Riyad Cairat, Antoine Ravon, Shaïma Giboire, Marine Boudalier - invités : Anne Kupiec Professeure de sociologie à l'Université Paris Diderot (Paris 7). Elle a été bibliothécaire à la bibliothèque Cujas et à la Bibliothèque publique d'information (la BPI) à Paris., Michèle Cohen-Halimi Philosophe, professeure de philosophie à l'université Paris 8, David Munnich Spécialiste de philosophie politique Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

There is a time-honored tradition to remain awake throughout the night of Shabuot and read the special "Tikkun Lel Shabuot" text that is printed in the Mahzorim. Hacham Ben Sion Abba Shaul (Israel, 1924-1998), in his work Or Le'siyon (vol. 3, 18:11), discusses the importance of this custom and presents numerous laws and guidelines relevant to the proper observance of this special occasion (listen to audio clip for precise citation). First, he mentions that even learned men who prefer studying Gemara must set aside their Talmudic studies in order to read the text of the Tikkun Lel Shabuot. If time remains after they complete the Tikkun, they may then study other material that they find more enjoyable. In Yeshivot, Hacham Ben Sion writes, students should follow the instructions of their Rosh Yeshiva in this regard. He also emphasizes that one should read the Tikkun even if he does not understand some sections of the service. Even if one plans to remain awake throughout the night, he should nevertheless recite the Keri'at Shema Al Ha'mita before Hassot (midnight as defined by Halacha). Already after Hassot, one may recite all the morning Berachot, with the exception of "Al Netilat Yadayim" and Birkot Ha'Torah. One should make a point to use the bathroom at some point before morning in order to be able to recite "Asher Yasar." At the point in the pre-dawn hours when it is uncertain whether Alot Ha'shahar (daybreak, the first appearance of light in the eastern sky) has occurred, one should discontinue his Torah learning. He should instead either immerse in a Mikveh or sing songs of praise until Alot Ha'shahar. After Alot Ha'shahar, one should wash his hands in preparation for prayer, but without reciting a Beracha. He then must recite Birkat HaTorah. Hacham Ben Sion cites in this context a passage in the work Sha'ar Ha'kavanot, which comments that whoever remains awake and diligently involves himself in Torah study throughout this night is guaranteed to survive the entire next year and to avoid all harm. Nevertheless, one should make a point of studying "Li'shmah" – with the proper motivation, out of sincere love for and commitment to Torah learning, and not to receive reward. Hacham Ben Sion also warns that sitting idly or engaging in meaningless chatter is no better than sleeping. It is therefore imperative to ensure to spend the entire night engrossed in Torah learning, and not in any other activities. In particular, one must avoid idle conversation inside the synagogue. Hacham Ben Sion also cites a comment from the Zohar that emphasizes the importance of studying with joy and fervor, in reward for which one is blessed with seventy blessings. The Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909) similarly stressed the importance of studying on this night with great enthusiasm and what he termed "purity of heart." Furthermore, on the festival of Shabuot God decrees how many "Hiddushim" (new insights) each individual will be privileged to develop during the coming year, which is determined based on the level of one's intensive study on Shabuot. Hacham Ben Sion writes that when we speak of Shabuot as "the day of the giving of the Torah," we refer not merely to the historical event of Matan Torah, but rather of the process that is renewed each year on this day. God grants a person on Shabuot the ability to think of new Torah insights, and one must therefore pray on Shabuot for Torah knowledge and the wisdom to understand to the best of his soul's capability, and also try to think of "Hiddushim" during his study on Shabuot. During the day of Shabuot, too, one should try to minimize his sleeping in order to spend as much time as possible involved in Torah learning. Every moment spent learning on Shabuot earns a person reward, and one must not squander this opportunity. In fact, there were great Rabbis who would not sleep at all on Shabuot; after remaining awake throughout the night, they would simply continue learning through the day of Shabuot. The Hid"a (Rav Haim Yosef David Azulai, 1724-1806) likewise advises against indulging in sleep on the day of Shabuot. He also emphasizes that one must ensure not to fall asleep during the prayer service. Finally, one should also devote himself to Torah study with extra vigor and diligence during the "Sheloshet Yemeh Hagbala" – the three days of preparation prior to Shabuot. Just as in the wilderness Beneh Yisrael were instructed to abstain from relations and prepare themselves for three days prior to Matan Torah, so must we increase our efforts to learn Torah and minimize our physical indulgence during these three days. Hacham Ben Sion writes that the level of inspiration one receives from the experience of Shabuot depends on the amount of effort he exerted during the three previous days to prepare for this great experience.

Cómo el ayatolá Jomeini aprovechó la revolución para instaurar un régimen islámico en Irán. Hace 50 años, Teherán era completamente diferente: las mujeres caminaban sin hiyab, las minorías prosperaban y el país era una de las naciones más modernas de Oriente Medio. En 1979 millones de iraníes salieron a las calles para exigir democracia y libertad. Lograron derrocar al Sha, pero fueron engañados.

Rabbi Moshe Lichtman joins us for a deep and sensitive conversation on the religious meaning of Zionism, the founding of the State of Israel, and the theological debates that continue to divide the Jewish world. We explore the widespread misconception that Zionism began with Theodor Herzl, tracing the ideological roots of the movement decades earlier and examining which rabbinic figures supported a return to the Land of Israel and why others fiercely opposed it. The discussion tackles some of the most difficult questions surrounding Religious Zionism: Can redemption begin through secular Jews who are not fully observant? What value is there in building the Land without Torah? Did Zionism unintentionally contribute to religious decline among Jews, and if so, how are we to understand the recitation of Hallel on Yom Ha'atzmaut? We also address the claim that Rav Kook stood virtually alone against the majority of rabbinic opinion and whether “following the majority” applies to these historical and theological questions. Finally, we turn to the words of the prophets themselves. Is the modern State of Israel a fulfillment of biblical prophecy? How can one identify the beginning of the messianic process, and who ultimately has the authority to define redemption? This episode confronts some of the most emotionally charged and intellectually challenging issues in contemporary Jewish thought with nuance, sources, and honesty.(We apologize that this episode is available in audio-only format due to unexpected Zoom connection issues during the recording.)___*This episode is dedicated to the refua shelema of Sarah Miriam bat Tamar, Binyamin ben Zilpa, and our dear friend Yaakov ben Haya Sarah Malakh, and l'ilui nishmat Zehara Yehudit bat Yaakov Ezra v'Ilana Shira___• Bio: Born and raised in Elizabeth, New Jersey, Rabbi Moshe D. Lichtman studied in several yeshivot in Israel, including Beit Midrash LeTorah, the Gruss Kollel, Sha'alvim, and the Meretz Kollel in Mevaseret Tzion. He received semichah from both the Chief Rabbinate of Israel and the Rabbi Isaac Elchanan Theological Seminary of Yeshiva University, and also holds an MS in Jewish Education from Yeshiva University's Azrieli Institute. Rabbi Lichtman made aliyah in 1991 and has since taught in numerous post-high school programs in Israel, including the Mevaseret Institutions, Be'er Miriam, and Yeshivat Yesodei HaTorah, while lecturing regularly throughout the yeshiva and seminary world. He currently lives in Beit Shemesh with his wife and eight children. Rabbi Lichtman is perhaps best known for making major Religious Zionist works accessible to the English-speaking world, including Eim HaBanim Semeichah, An Angel Among Men, A Question of Redemption, and Rise from the Dust, as well as for authoring the widely popular original work Eretz Yisrael in the Parashah, which highlights the centrality of the Land of Israel throughout the Torah.___• Get his book here: https://a.co/d/0jfsgGED___• Welcome to JUDAISM DEMYSTIFIED: A PODCAST FOR THE PERPLEXED | Co-hosted by Benjy & Benzi | Thank you to...Super Patron: Jordan Karmily, Platinum Patron: Craig Gordon, Rod Ilian, Gold Patrons: Dovidchai Abramchayev, Lazer Cohen, Travis Krueger, Vasili Volkoff, Vasya, Silver Patrons: Ellen Fleischer, Daniel M., Rabbi Pinny Rosenthal, Fred & Antonio, Jeffrey Wasserman, Jacob Winston, Ariel Klainerman, and Michael Herskovitz! Please SUBSCRIBE to this YouTube Channel and hit the BELL to get alerted whenever new clips get posted, thank you for your support!

【プロモーション：コインチェック株式会社】2026/5/31までの期間限定！対象者全員に最大で2500円分のビットコインをプレゼントキャンペーン参加はこちらから：https://coincheck.com/ja/cp_lp/yurupc202605?utm_source=podcast暗号技術が破られるとはどういうことか？ ハッシュ関数を例にして、直観的に説明しました。【目次】0:00 暗号技術は死んでいく5:54 ハッシュ関数って何？10:30 ハッシュ値を計算してみよう15:12 ハッシュ関数をハックしよう19:37 ハッシュはどこで使われている？23:41 業界を震撼させた無名の女性25:06 Web全部を揺るがす脆弱性29:52 日々進化し続ける暗号技術34:44 コインチェックとタイアップキャンペーン【参考文献】◯CRYPTO 2004 ( https://www.iacr.org/conferences/crypto2004/ )→国際学会 CRYPTOの詳細はこちらから。◯CITP Blog「Report from Crypto 2004」( https://blog.citp.princeton.edu/2004/08/18/report-crypto-2004/ )→ スタンディングオベーションが起きた話はここから。◯Collisions for Hash Functions MD4, MD5, HAVAL-128 and RIPEMD ( https://eprint.iacr.org/2004/199.pdf )→ 王小雲が2004年のCRYPTOで発表したもの。◯Flame malware collision attack explained ( https://www.microsoft.com/en-us/msrc/blog/2012/06/flame-malware-collision-attack-explained/ )→ Flameについての詳細情報◯RFC 1321「The MD5 Message-Digest Algorithm」( https://www.ietf.org/rfc/rfc1321.txt )→ MD5の仕様、MD4の後継であること◯Online Etymology Dictionary「hash」 https://www.etymonline.com/word/hash→ hashの語源◯ Washington Post「U.S., Israel developed Flame computer virus」( https://www.washingtonpost.com/world/national-security/us-israel-developed-computer-virus-to-slow-iranian-nuclear-efforts-officials-say/2012/06/19/gJQA6xBPoV_story.html )→ Flameが米国・イスラエルの合同でイラン攻撃用に開発された◯NIST「NIST Selects Winner of Secure Hash Algorithm (SHA-3) Competition」( https://www.nist.gov/news-events/news/2012/10/nist-selects-winner-secure-hash-algorithm-sha-3-competition )→ SHA-3について◯現代経済学の直観的方法（バリューブックス）→ https://www.valuebooks.jp/bp/VS0057255792（Amazon）→ https://amzn.to/42toyqQ【サポーターコミュニティへの加入はこちらから！】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://yurugengo.com/support⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【親チャンネル：ゆる言語学ラジオ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugengo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【実店舗プロジェクト：ゆる学徒カフェ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugakuto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【お仕事依頼はこちら！】info@pedantic.jp【堀元見プロフィール】慶應義塾大学理工学部卒。専攻は情報工学。理屈っぽいコンテンツを作り散らかすことで生計を立てている。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/kenhori2⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠noteマガジン→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://note.com/kenhori2/m/m125fc4524aca⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠個人YouTube→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@kenHorimoto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【水野太貴プロフィール】1995年生まれ。愛知県出身。名古屋大学文学部卒。専攻は言語学。本業は雑誌編集者。著書に『会話の0.2秒を言語学する 』（新潮社）などがある。Podcast「神保町で会いましょう」のパーソナリティも務める。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/yuru_mizuno⁠⁠⁠⁠⁠⁠⁠⁠⁠神保町で会いましょう→⁠⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/6cYkvDO0HnJKLPgDBGUjjS

Skipmode walks us through the valley of jeep beats with golden era sureshots, sublime sample reconstructions and a strong salute to Philly with Freeway, 3 Times Dope, Sha'dasious and more. Plus a rare groove jewel from James Mason, fresh soul breaks by Tiwayo and a deep funk salvage op by Edan & Insight. View the full playlist for this show at https://www.wefunkradio.com/show/1294 Enjoying WEFUNK? Listen to all of our mixes at https://www.wefunkradio.com/shows/

In this After Hours bonus episode, Sam is joined by Sha, Ciara and Cole for a chaotic, hilarious, and surprisingly thoughtful conversation you didn't know you needed. From bold personal hot takes to debating what actually counts as a “sheltered life,” nothing is off limits. The crew imagines future YGC guests, guesses what people would assume Sam went to jail for (it gets wild), and settles the ultimate nostalgia battle: Club Penguin vs. Webkinz. They also share their favorite piece of fan mail, drop their number one tip for starting a youth group, confess their weirdest favorite food combos, and dive into their honest thoughts on gentle parenting. It's unfiltered, unpredictable, and packed with laughs from start to finish.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this meeting of The Late Diagnosis Club, Dr Angela Kingdon welcomes Sha'mya Jones, a graphic designer and entrepreneur who was diagnosed as Autistic in early childhood — but didn't learn about it until she was a teenager.Sha'mya shares what it was like to grow up knowing she was different but not understanding why, navigating school, relationships, and identity without the language to describe her experience. From early academic success to social challenges and bullying, her story reflects the complexity of being both supported and left in the dark.Together, Angela and Sha'mya explore masking, college burnout, creative identity, and what it means to build a life and business that reflects who you truly are.

Early bird discounts for the San Francisco World's Fair, the biggest AIE gathering of the year, end today - prices will go up by ~$500 tonight so do please lock in ASAP!From near-universal AI tool adoption inside Shopify to internal systems for ML experimentation, auto-research, customer simulation, and ultra-low-latency search, Mikhail Parakhin joins us for a deep dive into what it actually looks like when a 20-year-old, $200B software company goes all-in on AI. We cover why Shopify has become much more vocal about its internal stack, what changed after the December model-quality inflection, and why the real bottleneck in AI coding is no longer generation, but review, CI/CD, and deployment stability.We also go inside Tangle, Tangent, SimGym, which are three major AI initiatives that Shopify is doing to make experimentation reproducible, optimization automatic, customer behavior simulatable, and search and catalog intelligence faster and cheaper at scale. Along the way, Mikhail explains UCP, Liquid AI, and why token budgets are directionally right but often measured badly, why AI-written code can still increase bugs in production, what makes Shopify's customer simulation defensible, and what he learned from the Sydney era at Bing.We discuss:* Mikhail's path from running a major Microsoft business unit spanning Windows, Edge, Bing, and ads to becoming CTO of Shopify* Why Shopify is talking more publicly about AI now, and why staying at the frontier has become necessary for the company* Shopify's internal AI adoption curve, the December inflection, and why CLI-style tools are rising faster than traditional IDE-based tools* Why Jensen Huang is directionally right on token budgets, but raw token count is still the wrong way to evaluate engineering output* Why the real unlock is not more agents in parallel, but better critique loops, stronger models, and spending more on review than generation* Why AI coding can still lead to more bugs in production even if models write cleaner code on average than humans* Why Shopify built its own PR review flow, and why Mikhail thinks most off-the-shelf review tools miss the point* How PR volume, test failures, and deployment rollback are becoming the real bottlenecks in the agent era* Why Git, pull requests, and CI/CD may need a new metaphor once code is written at machine speed* What Tangle is, and how Shopify uses it to make ML and data workflows reproducible, collaborative, and production-ready from the start* Why Tangle is different from Airflow, and why content-addressed caching creates network effects across teams* What Tangent is, and how Shopify is using auto-research loops to optimize search, themes, prompt compression, storage, and more* Why Tangent is becoming a democratizing tool for PMs and domain experts, not just ML engineers* Why AutoML finally feels real in the LLM era, and where auto-research still falls short today* Why Tangle, Tangent, and SimGym become much more powerful when combined into one system* What SimGym is, why simulated customers only work if you have real historical behavior, and why Shopify's data gives it a moat* How SimGym evolved from comparing A/B variants to telling merchants what to change on a single live storefront to raise conversions* Why customer simulation is so expensive, from multimodal models to browser farms to serving and distillation costs* How Shopify models merchant and buyer trajectories, runs counterfactuals, and thinks about interventions like discounts, campaigns, and notifications* Why category-level behavior is so different across commerce, and why ideas like Chinese Restaurant Processes are showing up again in practice* Shopify's new UCP and catalog work, including runtime product search, bulk lookups, and identity linking* Why Shopify is using Liquid AI, and why Mikhail sees it as the first genuinely competitive non-transformer architecture he has used in practice* Where Liquid already works inside Shopify today, from low-latency query understanding to large-scale catalog and Sidekick Pulse workloads* Whether Liquid could become frontier-scale with enough compute, and why Shopify remains pragmatic and merit-based about model choice* Who Shopify is hiring right now across ML, data science, and distributed databases* The Sydney story at Bing, why its personality was not an accident, and what Mikhail learned from deliberately shaping AI character early onMikhail Parakhin* LinkedIn: https://www.linkedin.com/in/mikhail-parakhin/* X: https://x.com/MParakhinTimestamps00:00:00 Introduction: Mikhail Parakhin, Microsoft, and Shopify00:01:16 Why Shopify Is Talking More About AI00:02:29 Internal AI Adoption at Shopify and the December Inflection00:06:54 Token Budgets, Jensen Huang, and Why Usage Metrics Can Mislead00:10:55 Why Shopify Built Its Own AI PR Review System00:12:38 AI Coding, More Bugs, and the Real Deployment Bottleneck00:14:11 Why Git, PRs, and CI/CD May Need to Change for Agents00:18:24 Tangle: Shopify's Reproducible ML and Data Workflow Engine00:21:19 Why Tangle Is Different from Airflow00:26:14 Tangent: Auto Research for Optimization and Experimentation00:30:07 How Tangent Democratizes Experimentation Beyond ML Engineers00:33:06 The Limits of Auto Research00:36:36 Why Tangle, Tangent, and SimGym Compound Together00:37:20 SimGym: Simulating Customers with Shopify's Historical Data00:42:47 The Infra Behind SimGym00:46:00 Why SimGym Gets Better with Real Customer History00:47:30 Counterfactuals, HSTU, and Modeling Merchant Trajectories00:51:55 CRPs, Clustering, and Category-Level Customer Behavior00:53:30 UCP, Shopify Catalog, and Identity Linking00:55:07 Liquid AI: Why Shopify Uses Non-Transformer Models00:59:13 Real Shopify Use Cases for Liquid01:03:00 Can Liquid Scale into a Frontier Model?01:09:49 Hiring at Shopify: ML, Data Science, and Databases01:10:43 Sydney at Bing: Personality Shaping and AI Character01:13:32 Closing ThoughtsTranscript[00:00:00] swyx: Okay. We're here in the studio, a remote studio, with Mikhail Parakhin, CTO of Shopify. Welcome.[00:00:08] Mikhail Parakhin: Thank you. Welcome.[00:00:10] swyx: I don't even know if I should introduce you as CTO of Shopify. I feel like you have many identities. Uh, you led sort of the, the Bing ML team, I guess, uh, uh, or ads team. I, I don't know, I don't know, uh, you know, it's, uh, people va-variously refer you as like CEO or, or, uh, I don't know what that, that, that said previous role at Microsoft was.[00:00:29] Mikhail Parakhin: Uh, that was... Yeah, my previous role w- at Microsoft was the-- I actually was the CEO of one of Microsoft's business units, which included, as I, you know, as we discussed, all the things that people like to laugh about, uh, including Windows and Edge and Bing and ads and everything.[00:00:47] swyx: Yeah, yeah. What a, what a, what a wild time.You've obviously, uh, done a lot since you landed at Shopify. Uh, one of the reasons I reached out was because you started promoting more sort of internal tooling, uh, primarily Tangle, but also a lot of people have seen and adopted Tobi's QMD, uh, and obviously, I think, uh, Shopify has always been sort of leading in terms of, uh, engineering.I think more-- it's just more recent that you guys have been more vocal about your sort of AI adoption. Is that, is that true?[00:01:16] Mikhail Parakhin: Well, I think AI tools in general are fairly recent development, uh, and we've-- Shopify, you know, at this stage of its development, we're developing AI in-in-house and other, uh, building tools that use AI and, you know, interfacing with the wider AI community, uh, you know, are on the sort of the, uh, runaway trajectory.So it just did by sort of natural byproduct. We, we talk about it more also. We just, uh, just even yesterday, Andrej Karpathy was famous in tweeting about, oh, are there some, uh, ways, uh, that, that you can organize your agents to store the data and then, uh, look up the data so that you don't have to research or, or lose context every- Yestime. And a little bit tongue in cheek, I tweeted that, “Hey, we've, we've done it much earlier, and we even have different approaches, Tobi and I.” Tobi, of course, is a big fan of QMD, and I'm more of a SQL, SQLite fan. But, uh, yeah, very similar things that we've already done here. The point is, yeah, we're very dynamic, you know, explosively growing company, and we have to be at the forefront of AI adoption, obviously.[00:02:29] swyx: Yeah. Yeah. Um, you, your team kindly prepared some slides actually that we were gonna bring up on to, uh, the screen. I think I can, I can screen share, and then we can kind of go through some of the shocking stats that maybe, maybe put some numbers to what exactly is going on. So here we have, uh- An internal AI tool adoption chart.What are we looking at here? What ?[00:02:54] Mikhail Parakhin: Yeah, this is very interesting statistics. Uh, this is number of daily active workers, you know, think of, uh, DAO, basically the active users of-[00:03:05] swyx: Yeah ...[00:03:05] Mikhail Parakhin: AI tool as a percentage of all the people in the company, right? And then- Yeah ... different AI tools. And, uh, you could see two things here is that one is the green is total.Uh, green is just total. So you could see that it approaches really % by now. It's hard not to do your job now without interacting deeply, at least with one tool. You could see another interesting thing is just as many people commented in December was the phase transition when suddenly models gotten good enough that, that everything took off and started growing.Uh, it, it was many people noticed that the thing is that small improvements accumulated into this big change in Sep- December roughly timeframe.[00:03:52] swyx: Yeah.[00:03:52] Mikhail Parakhin: The other thing I would claim you could see is that, uh, CLI-based tools and tools that don't require you to look at the code becoming more popular, and you could see, yeah, various versions of, uh, Cloud Code and Codex and Pi and internal development tools taking off.Uh, exactly, yeah, uh, and blue is our River, just internal agent for coding, where tools, uh, that require IDEs such as, uh, GitHub, Copilot or Cursor, they're not exactly shrinking, but they're not growing as fast. Like, uh, red, red line is, is the IDE kind of tools. So you could see that they're, they're not experiencing as, as fast of a growth.[00:04:37] swyx: As I understand it, basically, every employee has their choice, right? Of choose whatever tool you use, and then you're just kind of doing a, a daily sur-survey or something.[00:04:47] Mikhail Parakhin: Exactly. And, uh, we- Yeah ... the, the push is to get your job done, you can use any tool, and we effectively fund unlimited tokens for everybody.Uh, we, we do, we do try to control the models that, uh, people use, but from the bottom, not from top. Like we basically say, “Hey, please don't use anything less than Opus four point six.”[00:05:09] swyx: Oh .[00:05:10] Mikhail Parakhin: Some people, some people end up using GPT five point four extra high. Some people use Opus four point six. Um, uh, you know, uh, there are some, uh, there are plus and minuses in going for full one million context window versus not.But, uh, we try to discourage people from using anything less than that.[00:05:28] swyx: Yeah, yeah. Got it, got it. Uh, I mean, uh, that's, you know... The, the next chart here, it really kind of shows the expansion and the sort of December twenty twenty-five inflection, right? That, uh, people are using a lot of tokens. I think it's also really interesting that no one was kind of abusing it in twenty twenty-five.Like it was- Had comparatively, uh, to this year, there was almost no growth. I mean, it's still like, you know, probably, probably gave fifty percent.[00:05:56] Mikhail Parakhin: Yeah. This is just a different scale. It's still exponential- Yeah, yeah ...growth at just a different- ...rate of expansion. Uh, there was inflection point, and Sean, I would claim the, the super interesting part here is that you could see that the distribution becoming more and more skewed.Yes. The top percentiles grow faster. So that means- Yeah ...the people in the top ten percentile, they, their consumption grows faster than seventy-five and so forth. So, uh, the distribution skews more and more towards the highest users, which is... I don't know what it tells me. It's like it feels not ideal, to be honest.Or maybe it's okay. We'll see.[00:06:36] swyx: Why does it feel not ideal? Is, is it because of, um, quantity over quality, or what's the concern?[00:06:42] Mikhail Parakhin: Because take it to the limit. That means, you know, if, if this rate of separation continued- Ah, yes ...a year, there will be one person consuming all the tokens. So it's just, it's kinda strange.[00:06:54] swyx: Yeah, I mean, um, uh, I, I think internal like teaching and all that, uh, will, will help sort of distribute things more widely. But in, in the early days, of course, the people who are sort of more AI-pilled will obviously find more ways to use it than the people who are less AI-pilled. Maybe let's, let's call it that.I'll just, I'll just kinda quickly, uh, pause from the, the... You know, we will go back to the rest of the slides, but I just wanna, um, review, you know, there are a lot of CTOs of, of large companies like yourself where they're all considering some kind of token budget, right? Like I think it's something, something that Jensen Huang has been talking about, where like if your 200K engineer is not using 100K of tokens every year, like they're, they're underutilizing coding agents.Of course, Jensen Huang would say that, but like it seems a very quantity over quality approach and like some, some people are basically saying like, well, is this comparable to judging engineer quality by lines of code, right? Which we also know is like kind of flawed, but better than nothing. So I, I don't know if you have like a sort of management take here on, on how to view this kind of, uh, metrics.[00:08:02] Mikhail Parakhin: Well, I mean, you're, you're baiting me. I, I like... This is my favorite topic. Uh, if you let me, I'll probably talk for two hours on just this. I have a lot of things to say. Like I do think Jensen gotten a lot of bad press saying, “Oh, of course you're, you know, this, uh, the- ...the cake seller says you don't need enough cakes.”You know? Like, of course. Uh, but, uh, I actually, uh, think that's undeserved. I think he, he's actually right. Uh, I do think- He,[00:08:33] swyx: he's directionally correct.[00:08:35] Mikhail Parakhin: Yeah. Yeah. He's directionally correct for sure. Uh-[00:08:37] swyx: Who knows what the right number is? Yeah.[00:08:39] Mikhail Parakhin: The thing that I do Uh, want to say, and this is something that we learned through trial and error and very important is like two things.One is that it's not about just consuming tokens. Uh, you can consume tokens and, and in fact, the anti-pattern is running multiple agents, too many agents in parallel that don't communicate with each other. That's almost useless, uh, compared to just fewer agents and burns tokens very efficiently. Uh, setting up the right critique loop, especially with the high quality models, where one agent does something, the other one, ideally with a different model, critiques it, uh, suggests ways to improve it, the agent redoes it with this critique and, and so it takes much longer.So people don't like it because latency goes up. You know, they, they have to wait until this debate is happening. But, uh, the quality of the code is much higher. And another thing, just since you mentioned like, look, uh, uh, yeah, the overall budget is just like, uh, lines of codes. Lines of codes are exploding for everybody right now, or partially because AI is really mover balls, but partially just because AI can write a lot more code, you know, doesn't get tired.And so you have to have to have a very strong narrow waist during PR review. Otherwise, just the number of bugs will go through the roof. It's, uh, it's this unexpected consequence of the just volume trumping everything. I would claim by now good model writes code on average with fewer bugs than, than the average human.But since they write so much more of it, like more of it will make it into production. So you have to- You still[00:10:26] swyx: have[00:10:26] Mikhail Parakhin: more bugs. Yeah. Have to have a very rigorous PR reviews, also automated of course. But, uh, yeah, that to spend a lot budget there. Like this, this for me, for me, actually, the important metric is the ratio of budget spent during code generation versus, uh, spent, uh, expensive tokens like GPT, uh, five point four Pro or, uh, uh, Deep Think from Gemini, you know, checking on PR reviews.[00:10:55] swyx: Yeah, totally. Uh, I noticed in your chart you didn't have any review tools. Do you just use like, like let's say a Claude code to review tools? Or do you have another set of review tools like the Greptiles, the Code Rabbits, uh, Devin Reviews has a review tool. I don't know if you've had those specialist review tools.[00:11:13] Mikhail Parakhin: You are a little bit jumping on my store tool right now because the graphs I was only showing public tools. Uh, uh, the-- I haven't found a good PR review tool that, that does what I think should be done. And, uh, partially my, my thinking is because it's so... It just goes against both what people feel like emotionally they prefer and, uh, some of the, uh, you know, frankly Even business models that, that the companies run.At peer review tool, uh, time, you want to run the largest models. That means, I don't know, Codex or, or, uh, Cloud Code is not gonna cut it. You need to have pro-level models if you really want to, uh, stand the tide of bots from going into production. And you need us to spend a lot of time, the models taking turns, but you don't want, like, a big swarm of, uh, of, uh, agents.So in fact, you end up in a different dual-dualistic world where you generate not that many tokens. You, in fact, generate few tokens, but it takes f-a long time because these are expensive models taking turns rather than many, many agents trying to do many things in parallel. So that's, that's why I feel like I haven't found good tools, so we are using our own for peer review for now.[00:12:33] swyx: Yeah. Yeah. I mean, uh, I think a lot of companies are building their own, uh, especially to their needs, right?[00:12:38] Mikhail Parakhin: Mm-hmm.[00:12:38] swyx: Um, I, uh, you also have a chart here going back to the slides on, uh, PR merge growth, where we're now at thirty percent, uh, month on month rather than ten percent. Uh, and also the, the estimated complexity is going up.You know, this is productivity, right? ‘Cause y- presumably there's more stuff going into the code base and more, more features getting worked on. I'm curious about the backlog, right? Like the, the, the-- I actually don't mind a pro-level model taking an hour or two hours to review my PR, because I've dealt with humans who take a week to review my PR, right?And I keep pinging them on Slack, “Hey, hey, review my PR.” So, you know, I think there's some trade-off here where, like, it still doesn't make sense.[00:13:18] Mikhail Parakhin: Exactly. That, that's exactly m-my point. Uh, that on one hand, you can tolerate longer latencies at, uh, PR. On the other hand, like right now, the real problem is not in spending time waiting for PR.It's real problem is since there's so much more code than- Yeah ... uh, probability of at least some tests failing going up, and then you, like, keep de-failing, then you have to find the offending PR, evict it, retest it without that PR, and so deployment cycle becomes much longer. Uh, so it actually, in terms of the overall time to deploy, it's total time savings if you spend more time on a longer model, like thinking for an hour, because then, then you, you don't have to spend all that time during testing and rolling, you know, rolling back the deployment.[00:14:03] swyx: Yeah, totally. That's still worth it. You know, you don't look at the individual, look at the aggregate, and look at the, the, the change in the aggregate system.[00:14:11] Mikhail Parakhin: Exactly.[00:14:11] swyx: I'm kind of curious if, like, there's this PR mentality and, like, c-- the, the, the CICD paradigm will be changed eventually. Some people are like, obviously a lot of people want new GitHub, but I even wonder if, like, Git is the problem, right?Like, is that the bottleneck? Is the concept of a PR a bottleneck? Do you guys use stack diffs? I don't know if, uh, that's a, like, a merge queue stack diff type of thing.[00:14:34] Mikhail Parakhin: We, we use, we use Stacks, we u- we use Graphite. We worked with, uh, Graphite a lot. Uh, so we use Stack, uh, PRs. I think, uh, like that's clearly the overall CICD in general, and the interaction with the code repository right now is the, clearly the sort of the, the main issue and the bottleneck for us, uh, and highest top of mind.I would say we probably need a different metaphor or different whole design of how to process it in new agentic world. I haven't seen anything dramatically better yet. I, I think everybody right now is just trying to keep their head above the water ‘cause, ‘cause there, there's so many PRs and then everybody's CICD pipelines start creaking, the, the times are increasing, the number of bugs slipping by increasing, and you have to, have to clap on down.And so we are a little bit in this situation when we need to first stabilize that story and then start thinking, hey, what, what it could be a completely different and new world, which I haven't... I know some people working on it. I haven't seen something, like anything super compelling yet, but clearly the old thing were designed for humans will need to be morphed into something new.[00:15:53] swyx: One of the thing that I, I think about is kind of like the merge conflict is basically a global mutex on the whole system, right? And in, in hu- in human organizations, we do have something like that. It's the company standup. But like, other than that, it's like it's actually fitting for us to be somewhat decentralized, somewhat plugged into one stream of information source, but somewhat lossy.Like it's okay, you know, that, that not every delivery is like atomic consistency. Like we're not dealing with a database sometimes.[00:16:27] Mikhail Parakhin: This is a very good point, uh, because since humans don't write code too fast, you know that global mutex is not too bad. Once you-[00:16:36] swyx: Yes ...[00:16:37] Mikhail Parakhin: start writing code at the speed of machine, it becomes the, you know, the bottleneck.Then what do you do? Maybe, and I can't believe I'm saying this because I, I'm long-- lifelong opponent of, uh, microservices, and I always thought that was, like, a really bad idea. And now that you're saying it, like, maybe in new guys like microservices will make a comeback, you know, because then you, you can ship things independently in tiny things and, and the managing all that complexity automatically will be much easier.I don't know. Like, we'll s-- we'll have to see.[00:17:10] swyx: Yeah. I mean, I don't know what the Microsoft or, or Shopify thing is, but I, I read this paper from Google where they have a monorepo that deploys into microservices, right? And then, uh, the other concept that I think about a lot is the Chaos Monkey concept from, from Netflix.Being able to create, like, this robust system where, um, uh, you know, you, you have the service discovery, you have the, uh, the independent, independent microservices discovery and, and, uh, you know, probably going to be a fair amount of duplication. That's how an organic system sort of scales, uh, that, that you have that...I don't know how you call it. Slack? Robustness? Depend-- uh, d-duplication. I, I, I forget the-- I, I'm-- And this-- those-- these are not exactly the terms- Hmm ... I'm looking for, but I c-can't really think of the words. Okay. I was gonna go into Tangent and Tangle. Uh, so, uh, we, we sort of discussed the overall stats that, uh, Shopify has.Uh, but, you know, I, I think some, some pretty cool stuff that you guys are working on is your ML experimentation, uh, and your, your sort of auto tr-research training pipeline. Presumably you're much closer to this one because it's, it's a sort of personal hobby of yours. How, how would you explain them in, together?I thought we have a slide that, like, uh, has the s- the system diagram.[00:18:24] Mikhail Parakhin: Yeah. Tangle first and then Tangent as a-[00:18:27] swyx: Yeah ...[00:18:28] Mikhail Parakhin: as a thing on top of Tangle. And, uh, Tangle is the third generation, I claim, of, uh, systems of, uh, running any data processing, but a bit with a skew for ML experiments, but not necessarily. Any sort of data processing tasks where you need to iterate, share, and you have scale so that you want maximum efficiency.You know how, like, normally you would work, you would-- Imagine you're a data scientist or an ML practitioner, you would get Jupiter notebooks or, or maybe you would get, uh, you know, Pyth- your Python scripts, and you would manage the data, and you produce those TSV files, and you put them in some JFS or something.Then you would notice that, oh, it has this, uh, weird missing values. You go and write another script that, uh, goes and replaces them with, uh-[00:19:20] swyx: Ah ...[00:19:21] Mikhail Parakhin: dash S. And then, then you, then you run some, some, uh, “Oh, I need to filter bots.” And so you run some light GBM model that, uh, removes the bots. And then, then you like-- And then you, you kind of like get into shape, and then you start experimenting, and you run multiple experiments, and then you're like, “Oh my God,” like, “this experiment is worse.”You undo, and you cannot get to previous result. And like, “Ah, what did I do?” Like that. Again, then, then you finally like get everything working. Then you like start throwing it over the fence to production. You, you replicate it, those things don't work, and then sometimes you like don't notice that you forgot some feature naming and the, the features don't match.But then, like imagine you, you did everything, and then six months later you're like, have to repeat it because now there's more data, or you wanted to do another pass, and you're like, “What, what did I do?” Or like, or like, “This script crashes now,” or the, “the path has changed.” And then, then you're trying to, like you spend another month just doing ar- digital archeology on your own, you know, history, right?Now multiply that by many, many teams. Now imagine you got an intern that you wanna ramp up. Now you have to show that intern, “Oh, you know, look, here's the folder, there's the scripts, you know, ask your cloud agent to do, and then, uh, to, to figure it out.” And then cloud agent does something, and then you're, “Ah, yeah, right, right, it was the wrong folder.I forgot to tell you, I actually have this other thing I forgot myself.” And, and that's, that's the, like, the daily life we all, uh, all know it, uh, if, if you're a data scientist, machine practitioner, ma- machine learning practitioner or, uh, or even like any data managing, uh, person.[00:21:00] swyx: Yeah. So I, I used to do this, uh, f- uh, on the quant finance side, uh, in, in my hedge fund.So we did this before Airflow, and then, uh, obviously Airflow came along and, uh, then more recently Dagster, uh, I would say is like, in my mind, what I would use for that shape of problem, uh, where you had to materialize assets and create a pipeline.[00:21:19] Mikhail Parakhin: And that's, that's very good segue because... So Airflow is great, but Airflow is more about you, you have something and you wanna repeatedly run it in production on schedule.It's less about you as a team developing things and being able to share, and you grabbing the standard pipeline and saying, “Hey, I wanna change this tiny little component in the huge sea of data processing, and I don't wanna-- I wanna run ten experiments on this, and I wanna do hyperparameter optimization.”All that is very hard to do with Airflow. It's very easy to do with Tango. Tango is m- more about, it's everything about group of people Running experiments, it might be agents too nowadays. Uh, running experiments cheaply, collaborating, sharing results. Uh, you don't need to understand fully. You, you grab-- you clone somebody else's experiment or somebody else's pipeline, uh, run, uh, change small piece, run it, be, like, get it to production state, and then ship in one click.So then the... You don't have to port it into any other system to, to run in production. You can just run the same experiment. It's, it's fully production ready. And, and it's, uh, it has lots of... Again, as I said, it's third generation system. The original one was, I would claim there was Ether and then, uh, at least in my career, Ether was the first, first, uh, that pioneered this type of approach.And then there was, uh, Nirvana, which, uh, uh, at Yandex, which did kind of sec-second take on this. And now this one aggregates the, the learnings from all of those and, and Airflow as well to, to get to the state where you try it, it, it feels kind of magical. Uh, ‘cause now everything is based on content, uh, hashes.So even if the version changed, but if the output didn't change, nothing is being rerun. It's very efficient. If you... Multiple people start experiment that needs the same sort of data preprocessing, it's not repeated multiple times. It's automatically done only once. If you start ten experiments that all require, you know, some, some data preparation first as the first step, and you don't have to coordinate for that.Like, you don't have to know that other people are starting it. You now, it's very easy compos-, uh, composability, any language you can u- uh, you wanna use, and it's very visual. So you can see immediately, you can edit it easily, you can assemble small things with just even mouse clicks if you want to, and, uh, share, clone.And everybody knows also it's fully kind of static in the sense that we rerun it second time, it will exactly have the same results. Like, you will never have to do digital archeology. So full versioning and everything is also there.[00:24:06] swyx: Uh, so, so people can, uh... It's open source. Go to the GitHub repo and, and, uh, check it out.Uh, and it is also a really good, uh, blog post about it. I think all these is, like, really appealing. The, the, the, the thing that I think sells me the most about it is that, um, sort of development to production transition, right? Which I think, um, a lot of people haven't really solved that, uh, strictly, right?Like, we develop really, really well in, in Python notebooks, but then, you know, that's obviously not a sort of production ready process. I think that, like, any way in which that is solved, I think is, is very appealing. Then the other thing that you mentioned, which also raised my eyebrows, was content-based caching, which you mentioned is, is, um, you know, is ve-very much, uh, um, a sort of efficiency measure about, uh, you know, just like recalculation only on, on sort of content addressing Which I think makes sense.Uh, it surprised me that the savings could be this much, but maybe I just haven't worked at your scale where there's so much duplication, uh, that people just rerun because they change a single ID upstream.[00:25:10] Mikhail Parakhin: It does, yeah. But it's not only you rerun. The, the main savings are coming from the fact that you ran it, you got your job done, and you moved on.Then- Yeah ... somebody else in some department you don't know existed runs the same task, but on a newer version.[00:25:27] swyx: Yeah.[00:25:27] Mikhail Parakhin: Like right now, you can't, in, in most of the organizations, you can't even find out about it so that you can't even measure that you're spending that time twice, right? Here- Yeah ... if everybody's on Tango, that's detected automatically and detected that the output is the same.And then for that person, all it looks like is like experiment just suddenly moved, jumped forward, right? Uh, uh- Yeah ... so that's because, because the, there's network effect of multiple people helping each other.[00:25:51] swyx: Yeah. This is one of those things where it's designed to be a platform from the beginning rather than an individual developer's tool from the beginning, right?And, and everything's gonna streams down from there. That is the sort of Tango, uh, orchestrator, and it's, it manages jobs. We've seen a few versions of this, and this is obviously, uh, uh, the sort of, uh, unique approaches that you guys have, have, uh, figured out. And then there's Tangent.[00:26:14] Mikhail Parakhin: Yeah. And Tangent is basically an automatic auto research loop that can help and kind of do your work for you.Uh- ... you know, uh, effectively, effectively, Andrej Karpathy recently popularized it with auto research. Yes. Remember he said like he was, uh, speed running this, uh... Yeah, uh, you know the story. The, here we're basically bringing the same capability into Tango so that, uh, the, uh, Tangent can analyze it. It's just an agent that can run multiple experiments, figure out what can be changed, and keep on rerunning it, keep on modifying until, uh, maximizing some goal, some loss function, whatever you need to, to achieve.And in general, I would say if you're not using auto research-like approach in whatever you do, like literally whatever you do, then you're missing out. We saw at Shopify that taking like a wildfire, anything where you can put measurements can be done dramatically better. Our-[00:27:19] swyx: Mm-hmm ...[00:27:20] Mikhail Parakhin: uh, speed of, uh, templatization HTML, uh, completely new UX tem- uh, templatization of, uh, reducing latency for liquid themes.Uh, we-- Our, uh, search, uh, recently we moved from It's hard even, uh, quote from eight hundred QPS to forty-two hundred QPS with the same quality just by pure optimizations and not a research loop that kept running and changing code in our index serve on the same number of machines, just increasing the throughput.We, we managed to improve the quality of gisting and machine learning process. Uh, you know, gisting is the prompt compression technique that[00:27:59] swyx: allows for[00:28:00] Mikhail Parakhin: lower latency and, and lower and, uh, actually higher quality slightly. So like literally whatever different walks of life, and it doesn't have to be AI related.Uh, we, we had a reduction in, uh, storage because the agents would go and find data sets that clearly are derivative, uh, and then you don't need to store things twice. You know, we, we, we found somewhat embarrassingly that it was one of the largest tables was hashing random IDs into another random ID, and we literally- Oofput only one. So it was translating, yeah, two random IDs hashed[00:28:36] swyx: into[00:28:37] Mikhail Parakhin: each. So, so[00:28:37] swyx: it has access to the code as well, so it can, it can check the, like what, what the hell is it doing?[00:28:42] Mikhail Parakhin: So there, there cou- it could be run in two levels. You, uh, you know, at the superficial level, it could just use ex-existing components and, uh, reshuffle them.Uh, you know, like you can grab- Yeah ... uh, XGBoost, and you can grab some, some Py- PyTorch module, and then can grab some, you know, grab another tools and, and combine them. At a deeper level, since Tangle is all sort of CLI based underneath you, every, every component is a wrapped really CLI, uh, call and a YAML file, it can analyze code and create new components and, and, uh, keep on iterating as well.So, so you can, you can both have quick modifications of existing t- uh, pipelines with the, with components that are already there pre-baked, or you can create new components, uh, and-[00:29:29] swyx: Yeah ...[00:29:29] Mikhail Parakhin: keep iterating on those. So auto research is, again, this is probably the, the thing I was excited the most in the last two months happening, and we see it taking like, like totally like a wildfire.Just, uh, everybody, every day, every... well, every day, every minute, I would, uh, have somebody Slack message saying, “Oh, look how much better I made it.” And, uh, it's all throughout the research.[00:29:53] swyx: Is this democratized in some way in, in the sense that like is it your ML, uh, engineers and researchers doing this, or is it your regular PMs and software engineers also have the ability to auto-- to use Tangent?[00:30:07] Mikhail Parakhin: This is an awesome question. Like, Tango in general and Tangent in particular are extremely democratizing. Like they- Yeah ... they are the main tools for- ‘Cause I don't[00:30:15] swyx: need the details.[00:30:16] Mikhail Parakhin: Yeah. Exactly. Initially used by ML and AI engineers, but then literally, as you said, PMs are like the highest user right now is one of PMs on our org, uh, Sartak and he was, he was number one by, by usage of, of this ‘cause they're just, uh, energetic and knowledgeable, and now it, it unlocks a lot of capability where you don't have to co-change code manually.[00:30:39] swyx: I mean, I mean, because it kind of cuts out the ML, ML engineer from the process because the, the, the PMs have the domain knowledge and the ability to think about, uh, from first principles about, okay, what, what results do I want? And they can-- they even have the access to the data that, that needs to go in.So it's like in some ways, like this is the magic black box that we've always wanted for, for training and, and for, uh, I guess, uh, uh, hill climbing, whatever.[00:31:04] Mikhail Parakhin: It's basically cloud code for your AI development- ... uh, situation, right? Like now, now you don't have to know exactly how algorithms work. You can just, uh, bring your domain knowledge and expertise and product knowledge and iterate within Tangent until you've gotten the results that you need.[00:31:21] swyx: In my previous roles, every time that someone has pitched AutoML, you know, I've always been like, “Uh, this is not, this is not gonna work. It's, you know, it's, it's always gonna be a flop.” Somehow it's working now. I mean, presumably the answer is now we have LLMs and it's good enough, right? It's, it's an emergent property that we can do auto research, but like, it doesn't feel that satisfying that how come we didn't do this before, right?Like we just did like parameter search and like, I don't know. That's maybe that's it.[00:31:48] Mikhail Parakhin: Yeah. Bayesian optimization and hyperparameter optimization was, was the one that, or facet of AutoML that was used very actively, which incidentally also built into, uh, Tango. But, you know, I know Patrice Simard very well, and, uh, he was such a, uh, such a proponent of AutoML, and he put, like literally spent careers trying to democratize it.Without LLMs, it just turned out to be very hard. Like it, you, you would have flexibility within certain narrow domain, but it was hard to wider scale, and now with LLMs suddenly it's like magic wand, and so suddenly everybody- ... is an AutoML expert.[00:32:28] swyx: Yeah, I, I think it's multiple things, right? Like I'm, I'm just gonna bring up the, the, the chart again, right?Like LLMs can do the monitoring very well. That is the very potentially unbounded, super unstructured. It can do the analysis very well, it can do the... Uh, and basically it is much more intelligence poured into every single step. Uh, there's maybe nothing structurally changed about AutoML, but this is just m-more intelligent and more unstructured.[00:32:53] Mikhail Parakhin: Exactly.[00:32:54] swyx: Any flaws that you've run into? Like everyone is like drinking the Kool-Aid, oh my God, time savings, uh, you know, performance improvements. Like what, what, uh, issues have you have, uh, come up?[00:33:06] Mikhail Parakhin: This is really cool. It's not a solution to all the world's problems for sure. The limitations are usually the ones I-- And this is where we get into a bit of a subjective territory.Uh, I can only share what I've, I've seen so far, and I'm sure the situation, uh, is changing, and, you know, maybe after I say it, like many people will reach out and say, “Hey, what about this?” And you don't know that, and then, then we'll be probably right. But what I've seen is auto research is very good at doing kind of obvious things that you don't have bandwidth to do or you didn't notice or maybe you're not aware of like the-- some standard practices.It is not good at doing something completely out of distribution, something that, you know, you have to think for, for multiple days, uh, and, and do something like none of this. So, so it's, uh, I, uh, set an experiment once, uh, on, on my sort of, uh, hobby thing, and I let it run for, uh, ended up, uh, several weeks run, uh, you know, it's like full production kind of scale, so it, you know, slow runs and, and it ex-- it performed in the end, uh, over four hundred experiments, and only one was successful.I'm like, “Okay, that's, that's good.” But-[00:34:18] swyx: But it saved time.[00:34:19] Mikhail Parakhin: Yeah, I saved time. Like it, it was the, that thing. Yeah, if I, if I were doing four hundred experiments myself, my betting average, as I said, would have been much higher, I'm sure. But also, first of all, it would take me like three years to do four hundred experiments.And, uh, I didn't have to do them. Like the machines were just, uh, the price of electricity did that. So, and I got one improvement, uh, that in, uh, my, my-- Honestly, when I was starting that experiment, my thinking was to go and show that, “Hey, Andre, maybe you just don't know how to optimize.” And I was super smart because in, in my pro-problem, it was optimized for many years, and it was like fully improved.Uh, and I didn't expect it, you know, auto research to find anything at all. Yet it did. So instead of making fun of Andre, I ended up, uh, a big, big supporter. Yeah, that's exactly the tweet. Yes.[00:35:10] swyx: You and Toby really, really go back and forth on-online a lot, which is really funny. Uh, think of it as, as an eval for the optimalness of the code it's running on.Uh, it's almost like it reminds me of like a Kolmogorov complexity thing, but, uh, I guess it's-- there's some optimal thing that you're trying to sort of reduce down to, I guess. Um, and so, so you, you, you know, you should congratulate yourself that you had, uh, you know, uh, ninety-nine percent, uh, optimality.[00:35:36] Mikhail Parakhin: Exactly, yeah. I think Andre really deserves a lot of credit for popularizing this approach. This is, uh, this is incredibly, I think, powerful and cool and You know, the, uh, even him, him just mentioning it led to a lot of gains in a lot of places in the industry, so we should be thankful.[00:35:56] swyx: Yeah. I think he also has a just...I don't know what it is. Like, um, you know, it, it is a simple self-contained project that people can take and apply to other things, which is, is, is one thing, but also just the name. Just like somehow no one, no one managed to call their thing auto research. It's just naming things is very important. I think that that is mostly, uh, our coverage of Tango and, and, uh, Tangents.I think obviously, you know, there's a lot of, uh, ML infra at, at Shopify that people can, uh, dive into. We're about to go into SimGym, but before I do that, any, any other sort of broader comments around this whole effort? Like where is it, where is it leading to?[00:36:36] Mikhail Parakhin: As a segue to SimGym, like all those things start composing strongly.And, uh, you could see a huge unlock when you can look at each one of the tools and, and you see, oh, they're extremely useful. Uh, Tango is useful by itself. Auto Research is useful by itself. SimGym is useful by itself. If you combine all three, you create like synergetic effect. I think that's why we wanted to even, uh, cover them today is because this is something that if you go back even, you know, five years ago, would've been unthinkable.Uh, replicating that, uh, would, would be either incredibly costly or impossible, right? With probably thousands of people are required.[00:37:20] swyx: Well, we have serverless human, uh, serverless intelligence, right? Like, uh, so yes, you do have thousands of hu-- of, of intelligences, not just, not humans. And that's, that's close enough, right?Even if they're not AGI, they're, they're close enough to do the, the task that you need them to do. And, and, you know, that's, there's plenty for, for a lot of routine work, knowledge work. Okay, let's get into SimGym. Um, this is one of those things I, I was surprised to see actually it's apparently your, uh, one of your most popular launches, and I think something that, uh, I think Sim AI, I think Yunjun Park, who did the Smallville thing, there's a very small cottage industry of people trying to do like the simulate customer thing.I think a lot of people maybe don't super trust this yet because they're like, well, obviously they would just do what you prompt them to do, right? But maybe just think, uh, tell us about the sort of inspiration or origin story.[00:38:10] Mikhail Parakhin: That's exactly actually the thing I wanted to cover, because if you don't have the historical data, all you can do is prompt a-agents in a vacuum, and they will do exactly what you prompt them to do.In fact, when I first proposed it, and this is a bit of, um, my brainchild initially, if I, I can boast, even Toby said like, “But wouldn't they, they just repeat what, what you tell them?” And, uh, but I'm like, “Yes, except Shopify has decades of history of how people made changes and what there is, uh, there, what it resulted in terms of sales.”So now what we can do is we can-- we have this... It's not, it's a noisy data. There's a small, usually websites, uh, you know, like things, things are never in isolation. It's almost never AB experiment. It's always AA experiment when there's has two meanings, but basically, you know, in different time you run two different things.But if you aggregate in general, uh, like everything together, and you apply, uh, denoising and collaborative filtering like approach, you can extract a very clear signal. And then you can optimize your agents. And that's why it took so long. It took almost a year of that optimization of just us sitting and fiddling, and, and we had this internal goals of correlation of hitting-- internal goal was to hit zero point seven correlation with, uh, add to cart events, for example.Like that, that if we run real AB test experiment, that it should, it should go and, and rep-uh, replicate, uh, same sort of success that, that humans had or lack thereof. And it, it took forever, and I don't think that's easily replicatable because, uh, like who else would have that data? You have to have this historic, you know, decades, uh, worth of data.And now, now the, like the other thing you need is in-infrastructure and the scale, right? Because, uh, w- again, what we found, uh, stat sig results, you need to run a lot of simulations, a lot of agents, and, and it's-- Those are expensive things. Like you're, you're making actions in the browser because you want a real friction.You want to, to be able to get the image like of what humans will see because you wanna, uh, detect effects like, “Hey, if I make my images larger, will I have more sales or l- uh, fewer sales?” And like usually people's intuition here, by the way, is that I increase my images, I will have more because they look nicer.You know, designers all look sparse and big images. Like usually your sales tank, right? But, but, uh, you know, from HTML, all the characters look the same only the, the size tag looks different, right? So it's very hard. So you have to take visual information, you have to run this in simulated browser environment on the big farm and, and of course, you have to have, uh, like very, very expensive model, good model with multi-model model.So all this it's-- is what's taken so long and, uh, to share my personal fail a little bit there, Sean, is like, you know, we always had this bias to-- for like large company bias. You know, we always, uh, whenever you-- we do, we're like, “Hey, we'll run an experiment,” right? We make, make a change, and we will run an experiment and then, uh, see, uh, see which one's better or like, “No, this is worse,” and most of them are worse, so you discard it and keep iterating, hill climbing.And we're like, “Oh, like smaller merchants, they cannot get stat sig results. They cannot really run experiments simply because, you know, in a week there would be not enough data for them.” So we thought from this perspective. What we didn't realize is that most people don't have A and B, they just have one thing, and they need suggestions of What A and B should be.So, uh, we first build this, hey, we run simulation on two separate teams and, and, uh, say, “Hey, which one is better?” We then morphed it into, and very recently just released it, when you have just your site, your theme, we run over it and we say, “Hey, here's what predicted values of, of, uh, uh, conversions are, and here's how we think you should modify it to increase your conversions.”And then circling back to what you started with, the proof is in the pudding. Like, if we are not correlating with reality, like, people will not be using it. And, uh, thankfully, we see literally every day more users than the previous day. So, so right now, uh, right now- It's working. Yeah. I'm-- Right now my problem is how to pay for it all because the so our major thing is how to optimize the LLMs, do distillation, how to run the headless browsers, uh, and handful browsers, uh, uh, cheaper so that we can accommodate the increase in traffic.[00:42:47] swyx: Yeah. I, I understand that you, uh, you published a lot of technical detail at GTC, so I was just gonna bring it up a little bit. I think s- was this in, in con-conjunction with some kind of GTC presentation? Or something like that, right?[00:42:59] Mikhail Parakhin: Well, we, yeah, we, we did it in several place, but yeah, we had the engineering- Yeahblog, uh, as well. Yeah.[00:43:05] swyx: Yeah. So you're running, uh, GPT OSS. Uh,[00:43:08] Mikhail Parakhin: the, this is an older version. You know, now we run multimodal model. But yeah- Yeah ... GPT OSS, we still run GPT OSS as well for[00:43:15] swyx: And then you have the VMs, and you also have browser-based. I really like this one where it you said, “It violates almost every assumption that standard LLM serving is designed for.”And then you had like, basically orders of magnitude differences between everything.[00:43:29] Mikhail Parakhin: Exactly. Which is, which, uh, which was, you know, a bit of a challenge to implement, like when, like even simple things. Uh, be- since it violates all the assumptions, for example, multi-instance GPUs, like MIGs don't work as well.But we needed, uh, to get MIG to work because, ‘cause otherwise it's way too expensive. And so we had to deal with the, yeah, with, uh, lots of infrastructure and, and, uh, work with, uh, uh, Fireworks and CentML, uh, you know, to help with optimizations and browser-based, as you mentioned. Yeah, like, takes a village.[00:44:04] swyx: Okay. So there's a lot of like, I guess, experimentation in the infrastructure so far, and you've published more or less what you have here. I guess I'm, I'm less familiar with CentML. I, I don't do, uh, that much work in this, this part of the stack. But why was it the sort of preferred instance platform?[00:44:22] Mikhail Parakhin: There are really three probably top companies. There used to be, uh, uh- Three top companies, uh, at least I was aware of that did, uh, LM optimization. You know, together Fireworks and Santa ML, not necessarily in that order. Santa ML recently got acquired by NVIDIA. Uh, what they did is if you have a model and you want to optimize it to a specific prof-- uh, profile of usage, uh, they would go and do it.And, uh, we work with, with those companies, uh, this was work particularly in with Santa ML and NVIDIA to get them the best possible results out of it. And, and sometimes you, you have to retune depending on, like sometimes you want the maximum throughput, sometimes you want minimal latency, sometimes you want like the cheapest, right?And, yeah, or some combination. And so yeah, these are people who would come and help you.[00:45:14] swyx: I see. I see. Yeah, yeah. I'm familiar with these people for the LLM, you know, autoregressive stack. But the other interesting category of these optimizers is also the diffusion people, whereas like Fel and, you know, uh, Pruna recently has come up a lot as well, which I think is like really underappreciated, uh, at least by myself, because I, I thought, oh, all the workload would be LLMs, but actually there's a lot of diffusion as well.[00:45:38] Mikhail Parakhin: Exactly.[00:45:38] swyx: There's a lot here, so I, I, I... it's, it's, uh, it's, it's, it's hard to cover. But I, I do think like people underappreciate the importance of customer simulation, basically. I think this is something that I'm candidly still getting to terms with. Uh, you know, uh, you also-- your team also like prepared this, like, really nice diagram.Uh, I, I assume this is AI generated.[00:46:00] Mikhail Parakhin: Yeah, it looks-[00:46:01] swyx: Maybe it's not.[00:46:01] Mikhail Parakhin: Yeah, it looks, uh, Gemini-ish. Yeah, but, uh, uh, honestly, I, I don't know where, where the hell they generated. It looks, look, uh, looks like it's, uh, Google. But the interesting part, John, that, that, uh, we haven't covered, but I, I wanted to mention is if your store had previous customers, rather than it's a new store, you're like new merchant just launching things, it helps tremendously in just correlation and forecast.Yeah, we take your previous, uh, customer's behavior, and we create agents that replicate those specific distribution of, of customers that you get, and then we a- we apply those to your changes, and then that, that raised raw, you know, the re-- uh, just correlation with the add to cart events or to-- with conversion or whatever it, it, it may be, uh, quite dramatically.So, uh, replicating humans in general seems like an interesting, cool challenge.[00:46:58] swyx: As a shareholder, I think this is the-- like if people are Shopify shareholders, they should really deeply understand this because this is basically the moat. The, the more you use Shopify, the more it will just automatically improve, right?Like you're, you're doing the job for them.[00:47:13] Mikhail Parakhin: Yeah, that's what we started with. Like, uh- ... uh, otherwise, if you're just a startup, I wouldn't do it if, uh, you know, if it was my startup because Without the data, it, yeah, as, as you said, it's, it's exactly the case that, uh, whatever you say in prompt, that's, that's what the agents will be doing.[00:47:30] swyx: The statistician in me wants to like really satisfy the sort of, um, statistical intuition, I guess. Um, to me it's kind of, uh, the, the word that comes to mind is, um, ergodicity. Uh, so let's say a, a customer takes this path, customer takes this path, customer takes this path, right? Um, the... In my mind, the way I explain it is like, okay, here, here's the ninety-five percentile, here's the five percentile, and here's the median, right?Um, but to me, what SimGym is potentially doing is that it can, uh, modify... It can sort of model the sort of in-between sort of journeys as well, that, that maybe are dependent on the previous states. This may be like a very RL-type conclusion where like basically the summary statistics, if you only did naive AB testing, you only have the, the statistics at, at, at a certain point, and you only judge based on the sort of overall summary statistics.But here you can actually model trajectories. Does that make sense? Or-[00:48:31] Mikhail Parakhin: That makes total sense because like, well, that, that makes even more sense that maybe even you realize bec- because-[00:48:38] swyx: Okay. Please,[00:48:38] Mikhail Parakhin: please. Yes ... we do-- Yeah. The, so internally, uh, we have this system, we talked about it briefly once at NeurIPS.We have a huge HSTU-based system that models the whole companies, uh, and their possible paths. And like- Yeah ... what you are, what you are showing, like actually at any point of time, you can either model the user's behavior or you mo- can also think about, uh, the whole merchant as a company, as the entity that acts in the world.You can model that as well. And then you can do, can do counterfactuals. In your graph, like in your blue graph, uh, if you're... Imagine in the center there, uh, somewhere in the middle, you would have an intervention. I give that person a coupon, or I don't know, I send a personal thank you card, or give a discount in some- somewhere.And then you can, uh, then you can do forward rollouts from that counterfactual. So what would have happened with that intervention or without the intervention? And you can even ch- change where that intervention, uh, in time can happen, right? Like some- where, where in this journey. So we, we do this at the Shopify scale for our merchants, and then if we notice that something that they can be fixing, like there's a strong counterfactual, like we have Shopify policy, they basically get a notification like, “Hey, we think your...something is wrong with your-” I don't know, Canadian sales. Like, uh, it looks like it's misconfigured. Here's what you need to do. Or do you think like, uh, you have to set up this campaign with these parameters? And we do that at the buyer level to literally offer discounts or cashback or, or things to buyers.So this is-- I'm getting very excited. Like this is my sort of area of, uh, interest, I guess, and, and hobby. But being able to m-model something complex as human beings or companies and model counterfactuals on it, where you can have interventions in the future and optimize when to make intervention, what kind inter-- uh, what kind of intervention to make.It's such an unlock that previously was completely impossible. Like the-- it was, it was always dreamed of, but never... Like how would you even simulate it without LLMs or HTUs? I think very, very exciting times.[00:50:59] swyx: I just wanted to, uh, to maybe illustrate this. I, I'm not the best illustrator, but I, I am a conceptual statistics guy.And y-you know, you cannot just do this. Like this is a dimensionality AB test doesn't do, right? Like, uh, because it doesn't have the, the, the change over time, uh, stochastic nature, uh, and it doesn't have the sort of contextual like... Here's all the context to this point. Um, okay, cool. Um, that's SimGym.You're, you're gonna burn a lot of tokens on this thing. But you're, you're one of the, the only scale platforms in the world that can, uh, that can do this across a huge variety of workloads, right? I'm even curious on a sort of human, uh, research level of like, well, do, does retail behave d-differently from like clothing sales?D-does that behave differently from electronic sales? I, I don't know. I don't know what else you guys... The Kardashian shoppers, do they differ from like people who buy, uh, I don't know, cars and, uh, whatever.[00:51:55] Mikhail Parakhin: Well, very different, and different sensitivities and different modes of, uh, shopping and, and different levels of what's important.Now, to-totally, you can do aggregations at, uh, at a store level. You can do aggregations at a different, uh, category level. I don't know if, uh, you know, for our statisticians among us, I couldn't believe, but we-- recently we're looking at it, and we had to bring back, uh, CRPs, you know, Chinese restaurant process.It's a, like, way of aggregating and, like, naturally grow clustering. So across... Specifically to answer questions that, uh, like you were just posing on how, how if, if buyers behave different categories. And I'm like, “I haven't seen CRP since two thousand and one.” It's[00:52:37] swyx: so What? It's so- What is... No, I haven't, I haven't seen this.No. This is not in my training. Uh,[00:52:44] Mikhail Parakhin: but, but yeah, it, uh, uh, it actually, like the, the-- there was a very popular kind of theory, popular neurips HTML circles in early two thousands, uh, kind of nice. And now, now it has practical applications, uh- Yeah ... that we were resurrecting.[00:53:03] swyx: Yeah, amazing. Uh, I, I can see, I can see how this is like a, uh, a fun job for you where you get to apply all these things.Um, yeah, yeah, so super cool. Super cool. So, okay, so, so anyone who, who knows what CRPs are and has always wanted to use them at work, uh, they should, they should definitely join Shopify. Okay, so w-we have a lot and but I, I'm, I'm being mindful of the time. I, I do wanted to, to sort of cover some other things.Um, I-I'll give you a choice, UCP or Liquid?[00:53:30] Mikhail Parakhin: Liquid. I think, I think on UCP, you know, like UCP is very important for us and, and it just we are-- UCP, we have a structured, uh, discussions, and you can read about them, and we have, uh, blog posts, and we have a big release this week, in fact, like with our catalog.Oh,[00:53:46] swyx: okay.[00:53:46] Mikhail Parakhin: Uh, yeah,[00:53:46] swyx: but- Le-I mean, we, we can, we can discuss the, the, the release briefly because we'll release this after the-- after it's already announced so whatever. There's a catalog that you guys are doing?[00:53:55] Mikhail Parakhin: Yeah. So we are, we are- Okay ... we are bringing in capabilities of a whole, uh, Shopify catalog.Basically, you now you can search for products, you can do lookups by specific ID, you can do bulk lookups when you need to bring m-multiple products. You don't need to know in ad-in advance what you're trying to show or to sell or check out. Like, you can now, you can now have this decided at, at runtime, and this big area for investment for us for both non-personalized and personalized searches, trying to provide basically a win-window into whole universe of products that are being sold everywhere in the world.And Shopify is really not exactly, but almost like a super set of any-anything being sold. Now we are bringing it into UCP and, uh, and, uh, identity linking is another big thing for us, uh, so that you, you can use, uh, like Google or whatever, whatever identity you have, uh, they're minimizing friction.[00:54:56] swyx: Yeah. So[00:54:57] Mikhail Parakhin: yeah, big release for us.But Liquid AI of course we never talk about, and the problem might be more, more aligned with what we d-discussed previously on this chat.[00:55:07] swyx: Sure. The main thing that everyone understands about Liquid is that it is inspired by Worm, and I still don't know why. I'm curious on your explanation. I think you, you, uh, you can make things very approachable.And also I think like what is the potential of like the, the level of efficiency that you get out of Liquid?[00:55:23] Mikhail Parakhin: You- we all familiar with transformer architectures. And, uh, for the longest time, there was a competing architecture, it's called the state space models. So, so Sams, uh, you know, Chris, Chris Reyes, one of the pioneers and, and lots of startups, uh, trying to make those realities.They have, uh, significant benefits being main being, uh, being much faster and, uh, lower footprint and not quadratic in length, you know, sort of, uh, linear in, in, uh, in your context length. But with state space models- They never quite made it. Like they're used-- They have, uh, certain niches when they thrive, their hybrid architectures are useful, but they never quite made it.And liquid neural networks are, you can think of them as a next step, like, uh, sort of, uh, state-space model square. It's non-transformer architecture that's more complicated than sta-state space and really difficult to code if you-- if I'm being honest. But it's, um, very efficient. It's, uh, subline-- sub, uh, quadratic in, in length of your context.Uh, it's very compact way to represent things, and that's a liquid AI company. They... Their goal is to productize it, and very often you have this need, uh, when you need to have long context and small model, and you want to have low latency. Like in general, it's basically on par with transformers, and if you do hybrids with transformers, it's, it's even better.That's why we at Shopify, when we tried multiple and we constantly try multiple models, multiple companies, we found that for small, particularly with low latency applications, when you have low latency and/or if you need longer context lengths, liquid was the best. And so we still use the whole zoo and always like obviously test and use everything, uh, every open source model and, you know, it feels l

En este episodio, nos vamos a fondo con todo lo que estuvo pasando en el primer fin de semana de acción de postemporada. Hablamos de los finalistas de a los premios, damos nuestras predicciones para el resto de la postemporada y cerramos con la autopsia a los warriors, Únete a la comunidad de Whatsapp de Los NBA Freaks:https;//chat.whatsapp.com/FmSCEFkbeLyGzwnzfpSEFJRedes sociales:Facebook, X, Instagram: @losnbafreaksEmail:losnbafreaks@gmail.com

The Shulhan Aruch, the authoritative code of Halacha, begins with the following instruction: "Yitgaber Ka'ari La'amod Ba'boker La'abodat Bor'o" – "One shall strengthen himself like a lion to arise in the morning for the service of his Creator." The fact that this Halacha opens the Shulhan Aruch shows us that waking early in the morning is a fundamental part of our religious responsibilities. In fact, this quality is what impressed Bilam when he attempted to place a curse upon Beneh Yisrael, compelling him to bless them, instead, as he exclaimed, "Hen Am Ke'labi Yakum" – "Behold, a nation that rises like a lion" (Bamidbar 23:24). Rashi explains this as a reference to the way Beneh Yisrael rise in the morning and immediately "pounce" to perform Misvot, putting on Tallit and Tefillin, and praying. Indeed, Rashi (Shemot 19:3) brings from the Midrash that each time Moshe Rabbenu climbed to the top of Mount Sinai, he did so early in the morning – "Kol Aliyotav Be'hashkama Hayu." Some explain this to mean that every spiritual "ascent" requires "Hashkama" – rising early. The path to spiritual greatness begins with waking up early in the morning. Abraham Abinu is likewise described on several occasions as rising early in the morning, because this is how he became great – by beginning his day early. Rav Eliyahu Lopian (1876-1970) was known for rising early every morning. When he was asked about this practice, he said that when he leaves this world, and will stand before the Heavenly Tribunal, he will be judged regarding his compliance with the Shulhan Aruch. He wanted to at least "pass" the first question – whether he complied with the Shulhan Aruch's very first ruling, that one should make an effort to get up early in the morning. If a businessman scheduled an early morning meeting with a prospective customer, and the potential deal was worth a million dollars, there is no question that he would be up at the crack of dawn and arrive early so he could be fully prepared with his sales pitch. The money at stake motivates the businessman to arise early. If we knew that the Misvot we perform each morning are worth many times more than any amount of money, bringing us eternal rewards, we would never think to sleep late. We would eagerly get out of bed and rush to perform the Misvot energetically and enthusiastically, as early as we could. People want to stay in bed and sleep late only if they don't have anything to wake up for. Once we acknowledge the inestimable value and worth of each and every Misva, we realize how much we have to do, and we then excitedly get out of bed early in the morning to get started. Rising early is also a crucial component of our ongoing struggle against the Yeser Ha'ra (evil inclination). The Sha'reh Tefila comments that just as when an army goes out to war, the first battle is the most important one because it sets the tempo and momentum for the rest of the war, our first battle with the Yeser Ha'ra each day similarly sets the tone for the rest of the daily "war" against it. The Yeser Ha'ra tries to convince us to remain in bed, and if we win this struggle and get up early, then we are in a better position to emerge victorious in our subsequent struggles with the Yeser Ha'ra throughout the day. Waking up early, then, helps us overcome all spiritual challenges that we encounter. The Hida (Rav Haim Yosef David Azulai, 1724-1806) cites his grandfather, the Hesed Le'Abraham (Rav Abraham Azulai, Hebron, d. 1643), as finding an allusion to this concept in the Gemara's famous teaching, "Ha'ba Le'horgecha, Hashkem Le'horgo" – "He who comes to kill you, arise to kill him." On the simple level, this means that one is allowed to kill a person who seeks to kill him. On a deeper level, however, "He who comes to kill you" refers to the Yeser Ha'ra, which seeks to spiritually kill us by leading us to sin. The Gemara teaches us, "Hashkem Le'horgo" – that we should arise early in the morning in order to defeat the Yeser Ha'ra. The way we eliminate our evil inclination is by waking early. This is alluded to also in G-d's pronouncement to the snake after it lured Adam and Hava to sin in Gan Eden: "Hu Yeshufcha Rosh, Ve'ata Teshufenu Akeb" (Bereshit 3:15). Literally, this means that human beings will kill the snake by stomping on its head, whereas the snake can strike the human being only by biting its foot. Additionally, however, "Hu Yeshufcha Rosh" means that the way we defeat the Yeser Ha'ra – which is symbolized by the snake – is through "Rosh," by waking up at the "head," or beginning, of the day. Conversely, the snake can defeat a person through "Akeb," the "heel," by convincing him to oversleep and get a late start to the day. The Torah says that when Abraham Abinu set out to fulfill the command of Akedat Yishak, he arose early in the morning and saddled his donkey ("Va'yashkem Abraham Ba'boker Va'yahavosh Et Hamoro" – Bereshit 22:3). The word "Hamor" ("donkey") is often interpreted as an allusion to "Homriyut," physicality, the animalistic tendencies within every person. Abraham succeeded in "saddling" and restraining his physical qualities by rising early in the morning. The Midrash comments that this donkey was the same donkey on which Moshe Rabbenu rode when he journeyed from Midyan to Egypt, and Mashiah will ride this same donkey when it arrives to redeem the Jewish People. The deeper meaning of the Midrash is that all great Sadikim – like Moshe Rabbenu and Mashiah – succeed in overcoming their physical tendencies by rising early in the morning, like Abraham Abinu did. The Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909), in Parashat Vayishlah, writes that the first half of the night – from nightfall to midnight – is called "Layil," whereas the period from midnight until sunrise is called "Layla" – the word "Layil" with the letter Heh added. This letter Heh signifies a higher level, indicating that this is a time of great spiritual potential. Accordingly, the Ben Ish Hai writes, the great Sadikim would go to sleep right at nightfall and then rise at Hasot to learn Torah until the early morning. The Ben Ish Hai notes that the letters of the word "Layla" (Lamed, Yod, Lamed, Heh) are the first letters of the words "Ha'ba Le'horgecha Yashkim Le'horgo" – alluding to the aforementioned teaching that the way we defeat and eliminate the Yeser Ha'ra is by rising early, and being awake during the "Layla," the second part of the night. Although nowadays we are not able to keep to this schedule, nevertheless, this demonstrates for us the importance of rising early in the morning. The Sages teach, "Kol Hat'halot Kashot" – "All beginnings are difficult," which means simply that any new undertaking is difficult at the outset, when a person gets started. However, Rav Haim Palachi (Turkey, 1788-1868) explained that this refers to the morning, the beginning of the day. Getting out of bed in the morning is difficult, but this is a challenge we must all work to overcome. Another reason to start the day early is that whenever we begin something new, it is critically important to start strong, as this builds a sturdy foundation for the rest of the undertaking. If the foundation of a structure is done improperly, the rest of the building will not be safe. Likewise, the beginning of any new project must be strong and sturdy for it to succeed. The Jewish Nation has succeeded because we are built on the strong foundation of our Abot (patriarchs) and Imahot (matriarchs), righteous men and women who laid the spiritual groundwork for Am Yisrael. This is true also of a new day – the stronger we start our day, the more likely we are to have an accomplished and successful day. We find numerous examples of this concept in our sources. Elisha Ben Abuya was an outstanding scholar, a Tanna, and the mentor of the great Rabbi Meir, but he ultimately lost his way and became a heretic, committing grievous sins such as desecrating Shabbat and even Yom Kippur. Different stories are told to explain how and why Elisha Ben Abuya abandoned the path of Torah observance. One story, told in the Talmud Yerushalmi, is that when he was a young child, his father showed him the great Sages of Israel, how their Torah study brought the fire of the Shechina into the home, and he said, "If you learn Torah, you can do amazing things like these Rabbis!" Since as a youngster Elisha was taught the message that he should learn Torah for self-serving motives, and not out of a sincere desire to serve Hashem, his educational foundations were shaky, and this allowed him to be led astray as an adult. Likewise, the Midrash comments that Noah was sharply reprimanded for planting a vineyard right after exiting the ark following the flood. As he set out to rebuild the earth, he should have begun with something more significant and meaningful than producing wine. The process was started on the wrong foot, as it were, on faulty foundations, and so Noah was criticized. This idea has also been developed in the context of the Hanukah story. As we know, the Gemara tells that the Hashmonaim, after driving the Greeks from Jerusalem, found only a small jug of pure oil with which to kindle the Menorah in the Bet Ha'mikdash, and this small quantity of oil miraculously sufficed for eight nights. The Peneh Yehoshua (Rav Yaakob Yehoshua Falk, Germany, 1680-1756) raises the question of why the Hashmonaim did not rely on the Halacha which permits performing the service in the Mikdash in a state of impurity if the entire nation is in such a state ("Tum'a Hutra Be'sibur"). After the Greeks had defiled the Bet Ha'mikdash, this leniency was certainly relevant and applicable, seemingly obviating the need to use specifically pure oil. The Peneh Yehoshua answered that the Hashmonaim did not wish to rely on Halachic leniencies as they inaugurated the Bet Ha'mikdash anew. They were now beginning a new chapter, restoring the service in the Bet Ha'mikdash after many years during which it could not be performed, and so they found it necessary to perform the service at the very highest standards, in order to set the tone for the years to come. They therefore refused to rely on the leniency of kindling the Menorah with impure oil. King Shlomo teaches in Kohelet (2:14), "He'hacham Enav Be'rosho" – "The wise man, his eyes are upon his head." The plain meaning of this verse is that a wise person looks at the potential outcome of his actions, and assesses potential risks before acting. Additionally, however, this verse has been understood to mean that a wise person focuses on the "head," on the beginning of his day, to ensure to start the day the right way, as this impacts the rest of the day. It is told that when Rav Shmuel Salant (1816-1909), the renowned Rabbi of Jerusalem, grew old, he decided to bring a Rabbi from Europe to assume his position, and the Rabbi chosen was the Aderet (Rav Eliyahu David Rabinowitz-Teomim, 1843-1905). Immediately upon the Aderet's arrival, Rav Salant brought him to officiate at a wedding to show the community their new leader. The Aderet was weary from the long, grueling trip, and so when the time came to recite the Beracha over the wine under the Huppa, he mistakenly recited "She'ha'kol" instead of "Ha'gefen." He immediately corrected himself, and recited "Ha'gefen." Afterward, people spoke about the Aderet with disdain, charging that he was ignorant of Halacha. It is well-known that although the proper blessing over wine is, of course, "Ha'gefen," one who mistakenly recited "She'ha'kol" over wine has fulfilled his obligation and does not then recite "Ha'gefen." There were those who claimed that the Aderet was unfit to serve as a Rabbinic leader, as he was unfamiliar with this simple Halacha. The Aderet explained that he certainly knew this Halacha, but he nevertheless recited "Ha'gefen" because he was reciting the blessing over the wine not only for himself, but also on behalf of the Hatan (groom), who was standing under the Huppa with his bride, prepared to begin their new life together. This new beginning, the Aderet explained, could not be built on a shaky foundation, using Halachic leniencies. It was important for the proper Beracha to be recited, even if the wrong Beracha would normally suffice after the fact, so that the marriage would begin on a strong foundation. While as a practical matter, one could question this line of reasoning, the basic concept is an important one – whenever we start something new, we must strive to begin as strongly as possible. We must therefore try hard to begin each day the right way, by waking early in the morning with energy and enthusiasm, ready to serve our Creator.

This week: Rage dropping 0-Day Claude Mythos, things are different now From UART to root, on a device made in China, where's the FCC? More CUPS vulnerabilities Russians are hacking routers, FCC ban doesn't stop them Mongoose vulnerabilities, and FCC still does nothing Renting virtual phones Iran's cyber attacks SHA-256 almost broken? Catching Axios New Rowhammer, dubbed GPUBreach, gives you root Windows 11 has sudo! (And SSH...) And Inside a Kubernetes Scanning Fleet Visit https://www.securityweekly.com/psw for all the latest episodes! Show Notes: https://securityweekly.com/psw-921

After the passing of a parent, Heaven forbid, the child observes a twelve-month period of mourning, and thus, fundamentally, Kaddish should be recited for that entire period. However, the Rama (Rav Moshe Isserles, Poland, 1530-1572) brings (Y.D. 376) Poskim who ruled that the mourner should stop reciting Kaddish after eleven months. This is due to the Mishna's teaching in Masechet Eduyot (2:10) that the wicked are punished in Gehinam for twelve months. If a mourner recites Kaddish for a parent for twelve months, this might give the impression that he considers his parent a wicked person, Heaven forbid, such that the parent requires twelve months of Kaddish to be spared the punishments of Gehinam. Therefore, some Poskim rule that the child should recite Kaddish for only eleven months. A second custom is mentioned by the Kenesset Ha'gedola (Rav Haim Benvenisti, Turkey, 1603-1673), who writes that he instructed people to stop reciting Kaddish one week before the culmination of the twelve-month mourning period. By contrast, the Sha'ar Ha'kavanot (Rav Haim Vital, 1542-1620) cites the Arizal's teaching that a mourner should recite Kaddish for a parent throughout the year of mourning. The Arizal emphasized that Kaddish is recited even on Shabbat and Yom Tob, when the wicked receive a respite from the punishments of Gehinam. This demonstrates, the Arizal explained, that reciting Kaddish does more for the deceased parent than simple extricate the soul from Gehinam; it also elevates the soul to higher levels in Gan Eden. Publicly declaring G-d's greatness fulfills the Misva of Kiddush Hashem – glorifying the Name of G-d, which is the greatest Misva a person can perform. In fact, some Kabbalists teach that the Misva of Kiddush Hashem can rectify even the most grievous sins. The merit of the Kaddish recitation, then, brings immense benefits to the deceased parent's soul, beyond protecting the soul from the punishments of Gehinam. Therefore, the Arizal maintained that reciting Kaddish for the entire year of mourning does not necessarily give the indication that one considers his parent a wicked person. Accordingly, the Hida (Rav Haim Yosef David Azulai, 1724-1806) writes that the custom in Italy, Egypt and Jerusalem was to recite Kaddish for twelve full months. Nevertheless, the Hida recommended refraining from reciting Kaddish for one week. Similarly, the Ben Ish Hai (Rav Yosef Haim Baghdad, 1833-1909), in his Rav Pe'alim, writes that the custom in Baghdad was to conduct a memorial service (Arayat) after eleven months to signify that the deceased is not considered a sinner, after which the mourners would refrain from reciting Kaddish for one week, and then resume reciting Kaddish until the end of the twelfth month. This is, indeed, the common practice in our community – to refrain from Kaddish for one week at the beginning of the twelfth month, and to then resume the Kaddish recitation until the end of the month. It should be noted that this entire discussion applies only to the Kaddish recitations in the prayer service. The Kaddish recited after Torah learning or after the reading of Tehillim is recited by a mourner throughout the twelve months, even during the week when he abstains from Kaddish during the prayer service. Additionally, Hacham David Yosef, in Halacha Berura, cites his father, Hacham Ovadia, as ruling that if a mourner serves as Hazzan, then he recites all the Kaddishim included in the prayer service, even during the first week of the twelfth month. Summary: Different customs exist as to when a mourner stops reciting Kaddish for a deceased parent. The generally accepted custom in our community is to stop reciting Kaddish during the first week of the twelfth month, and to then resume reciting Kaddish until the end of the month. Even during that week, the mourner recites Kaddish after Torah learning and Tehillim reading, and if he serves as Hazzan, then he recites all the Kaddishim that are part of the prayer service.

AWS Morning Brief for the week of April 6th, with Corey Quinn. Links: Announcing Amazon RDS for Oracle on AWS OutpostsAWS Direct Connect now supports AWS CloudFormationAWS Service Availability UpdatesAmazon S3 Vectors expands to 17 additional AWS RegionsAmazon CloudFront now supports SHA-256 for signed URLs and signed cookiesAmazon CloudWatch now supports OpenTelemetry metrics in public previewAnnouncing compute-optimized instance bundles for Amazon LightsailAnnouncing managed daemon support for Amazon ECS Managed InstancesLeverage Agentic AI for Autonomous Incident Response with AWS DevOps AgentNavigating the NGINX Ingress retirement: A practical guide to migration on AWSOptimizing data transfer costs when using AWS Network Load BalancerAWS Security Agent on-demand penetration testing now generally available

Sam jumps on a chaotic After Hours Zoom call with Micah, Zay, Buddy, Sha and a bunch of YGC fans where nothing is off limits—diving into behind-the-scenes moments from the podcast, how stories actually make the cut, ministry advice, and plenty of unfiltered fan interaction along the way. The crew swaps stories, reacts in real time, and leans into the kind of conversations that definitely wouldn't make it to a normal episode, all while keeping the energy loose, unpredictable, and exactly what you'd expect from a late-night call with the YGC community…See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.