POPULARITY
269 episodes with Combine
218 episodes with Combine
86 episodes with Combine
43 episodes with Combine
40 episodes with Combine
31 episodes with Combine
28 episodes with Combine
32 episodes with Combine
17 episodes with Combine
23 episodes with Combine
21 episodes with Combine
17 episodes with Combine
16 episodes with Combine
18 episodes with Combine
15 episodes with Combine
22 episodes with Combine
31 episodes with Combine
20 episodes with Combine
45 episodes with Combine
14 episodes with Combine
19 episodes with Combine
16 episodes with Combine
7 episodes with Combine
10 episodes with Combine
10 episodes with Combine
18 episodes with Combine
18 episodes with Combine
35 episodes with Combine
14 episodes with Combine
18 episodes with Combine
18 episodes with Combine
20 episodes with Combine
7 episodes with Combine
9 episodes with Combine
10 episodes with Combine
14 episodes with Combine
10 episodes with Combine
11 episodes with Combine
13 episodes with Combine
12 episodes with Combine
12 episodes with Combine
11 episodes with Combine
14 episodes with Combine
11 episodes with Combine
14 episodes with Combine
8 episodes with Combine
10 episodes with Combine
12 episodes with Combine
13 episodes with Combine
8 episodes with Combine
7 episodes with Combine
11 episodes with Combine
11 episodes with Combine
8 episodes with Combine
8 episodes with Combine
10 episodes with Combine
10 episodes with Combine
11 episodes with Combine
8 episodes with Combine
7 episodes with Combine
7 episodes with Combine
11 episodes with Combine
9 episodes with Combine
8 episodes with Combine
8 episodes with Combine
8 episodes with Combine
7 episodes with Combine
6 episodes with Combine
8 episodes with Combine
8 episodes with Combine
9 episodes with Combine
12 episodes with Combine
6 episodes with Combine
9 episodes with Combine
7 episodes with Combine
7 episodes with Combine
7 episodes with Combine
6 episodes with Combine
8 episodes with Combine
7 episodes with Combine
4 episodes with Combine
8 episodes with Combine
8 episodes with Combine
6 episodes with Combine
8 episodes with Combine
5 episodes with Combine
7 episodes with Combine
8 episodes with Combine
7 episodes with Combine
5 episodes with Combine
6 episodes with Combine
10 episodes with Combine
7 episodes with Combine
6 episodes with Combine
7 episodes with Combine
4 episodes with Combine
8 episodes with Combine
7 episodes with Combine
5 episodes with Combine
8 episodes with Combine
9 episodes with Combine
5 episodes with Combine
4 episodes with Combine
7 episodes with Combine
7 episodes with Combine
7 episodes with Combine
8 episodes with Combine
9 episodes with Combine
6 episodes with Combine
5 episodes with Combine
9 episodes with Combine
8 episodes with Combine
13 episodes with Combine
6 episodes with Combine
8 episodes with Combine
8 episodes with Combine
6 episodes with Combine
6 episodes with Combine
4 episodes with Combine
8 episodes with Combine
7 episodes with Combine
8 episodes with Combine
4 episodes with Combine
4 episodes with Combine
3 episodes with Combine
5 episodes with Combine
6 episodes with Combine
4 episodes with Combine
6 episodes with Combine
5 episodes with Combine
6 episodes with Combine
6 episodes with Combine
6 episodes with Combine
5 episodes with Combine
6 episodes with Combine
7 episodes with Combine
14 episodes with Combine
4 episodes with Combine
4 episodes with Combine
7 episodes with Combine
4 episodes with Combine
5 episodes with Combine
3 episodes with Combine
6 episodes with Combine
10 episodes with Combine
10 episodes with Combine
4 episodes with Combine
5 episodes with Combine
4 episodes with Combine
2 episodes with Combine
4 episodes with Combine
5 episodes with Combine
3 episodes with Combine
3 episodes with Combine
6 episodes with Combine
5 episodes with Combine
4 episodes with Combine
3 episodes with Combine
5 episodes with Combine
4 episodes with Combine
6 episodes with Combine
6 episodes with Combine
3 episodes with Combine
5 episodes with Combine
4 episodes with Combine
5 episodes with Combine
4 episodes with Combine
4 episodes with Combine
4 episodes with Combine
5 episodes with Combine
4 episodes with Combine
4 episodes with Combine
6 episodes with Combine
4 episodes with Combine
5 episodes with Combine
5 episodes with Combine
5 episodes with Combine
4 episodes with Combine
5 episodes with Combine
3 episodes with Combine
4 episodes with Combine
3 episodes with Combine
8 episodes with Combine
3 episodes with Combine
5 episodes with Combine
6 episodes with Combine
4 episodes with Combine
5 episodes with Combine
4 episodes with Combine
On this episode of Make It Cute we're talking the one, the only Emily Mariko and how she has a chokehold on all of our TikTok for you pages. We talk about personal branding, transparency, and her rise to her blue checkmark. Salmon (for Salmon Rice, duh) .5 lb salmon Kosher salt Pepper Garlic powder Remove salmon from the skin and season with salt, pepper, and garlic powder. Put the salmon in the airfryer for 6-8 minutes at 375F for a perfect medium cook on the salmon. Combine salmon with other ingredients from the viral salmon rice recipe and you have lunch :) Learn more about your ad choices. Visit megaphone.fm/adchoices
MIP Ag News With Jaclyn KrymowskiAg News By @theherdbookPresented By @AxonTire @ArrowCRM_Music By: @TalbottBrothers #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-agnews-10-21-21
One of the things I hear most often from women who had a transcendent, empowering, largely independent, birth experience, is that it wipes out the residue of former births they may have had, where they were more entrenched in the allopathic system. Women who had C-sections have gone on to have triumphant free-births at home, which we'll hear about in today's episode. All of the education I put out around this topic is to reassure and REMIND you that YOU can do this. Yourself. In order to have this kind of orgasmic, ecstatic birth experience means taking the reins early on in your journey. Even during conception. As you work out the kinks and blocks in yourselves and the collective of your relationship, you free up the flow for a smoother conception, pregnancy and birth.Anything significant that is NOT resolved between you, will show up in your birth.And even before that in your pregnancy and even before THAT in your conception journey.Combine all of that with the programming and imprinting you receive around birth, you've got a lot of work to do to clear the space.The most important “preparation” you can do is on your mindset, your fears, your internalized beliefs and then setting to work on reframing and recreating all of that to fit the vision YOU want to have. In today's episode, we are talking with our Well-F**ked All Star couple of the year, Mark and Amanda. Their story is amazing, and encapsulates ALL of the concepts I've just described. Amanda's first child was breech, and she was told that she'd have to have a C-section. Her fourth child was born at home, in her bed, with just her husband present. This was a free birth, with no one attending her pregnancy either. In between all of that was FIVE miscarriages. Their story is amazing, inspirational and super entertaining, as they share what happened and how they evolved along the way. Anyone can take their power back, and recreate their lives. Including you. The Sexy Mama Salon begins today! This 8-week online class is ALL about how to educate yourself, deprogram and reprogram yourself as the powerful portal you truly are. We cover everything from conscious conception, blissful pregnancy, birth orgasms, breastfeeding and early childhood education. This is the ultimate condensed and enlightened guide on how to use pregnancy and birth as an ascension experience and raise independent, free thinkers in the process. It all starts with birth. Check out Sexy Mama now.
If you drive around the countryside the number of green fields may be a surprise. As Todd Gleason reports, the quick dry-down has caused a crop loss problem farmers can't really fix.
Mr. Asato Philip Tanaka is a father of Kanga, a 12-year boy who has cerebral palsy and intellectual disability. - 田中かんがくん（12）の父親である田中フィリップあさとさんに、参加中のファンドレイジング「Roll On October」そして日豪の障害者福祉について体験談を聞きました。
Josh discusses harvest progress, trends, and the big ?
MIP Markets with Chip Nellinger – 2023 Wheat is $7.00! 1-309-550-7213 bluereefinc.com @bluereefAGWheat is giving a daily supply and demand clinic for anyone interested in attending. Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-markets-with-chip-nellinger-2023-whe
Rebecca Corry is not afraid to speak her mind and put her heart on the line. In this week's episode, she joins us to do both as she talks about her beloved Angel, a most noble, gentle soul wrapped in a Pittie body, who brought Rebecca to her purpose. Now this funny lady is the founder and president of her incredible nonprofit and a fierce advocate for the inherently good Pitbull type dogs she works tirelessly to provide spay and neuter for, to help save, and to love. Rebecca and Katya discuss broken systems, the need to get in the fight for what's right, and the importance of accepting a little inconvenience so you can experience the magic of being changed by an animal. Follow Stand Up For Pits Foundation and stay connected to what you can do to help Pitbulls. Join The Animal That Changed You community on Instagram, Twitter, and Facebook -- we're waiting to welcome you. Feel free to check out our website while you're at it. And please leave a rating or review of the show. Your support matters so much! Woof, meow, oink, moo, cheep (of course you know that means thanks for listening.)
The crew are joined by Dr. Tom Challman, Mary's dear father, and take a long look at the 1976 Dan Curtis movie, "Burnt Offerings".Dave's cocktail is a Fall version of the Old Fashioned; he found the recipe on Facebook but is unable to find the name of the person who posted it."Burnt Offerings" cocktail:Note - this is offered as a double. 4 oz. Whiskey6 ounces Rosemary Cinnamon syrup ( see below)3 - 4 dashes of Bitters. Cinnamon stick and rosemary sprig for garnish.Combine Whiskey, Syrup and Bitters in (what else?) an Old Fashioned glass, with ice.Burn the tip of a cinnamon stick, add that (burnt end UP) and a sprig of Rosemary for garnish, and try not to poke out your eye while sipping."Rosemary Cinnamon Syrup"Combine 1 cup of sugar and 1 cup of water in a saucepan with 2 or 3 sticks of cinnamon and 2 or 3 sprigs of Rosemary. Simmer for 15 minutes, strain and store in the refrigerator.Visit our website:http://www.monstermoviehappyhour.com/Chat with us on Facebook:https://www.facebook.com/monstersndri...Our Twitter:https://twitter.com/monstersndrinksMusic created by Kevin MacLeod.You can hear more of his work at:https://incompetech.filmmusic.io/
You've got an offer ready and have emailed your subscribers. Once. Maybe twice. Sure, you'd like to email them a bit more. That would help with your sales, right? But you just don't know what to email about! So here are 7 sales elements that will give you more reasons to email during your launch and help you create spikes in your sales. Ready to have your mind absolutely blown by these strategies? Let's go! SOME EPISODE HIGHLIGHTS: (2:31) Why you should email your audience more than once or twice during a launch. (4:04) Give your audience a guided tour of your sales page through your emails (and learn about the pretend electoral campaign between Paddington Bear and Rupert The Bear). (11:48) Introduce a countdown timer to create urgency (but not right at the start). (14:08) Add a bonus (or more). (16:34) Combine the bonus and the countdown timer. (17:47) Use your testimonials in your emails. (20:20) Don't introduce payment plans or down sell options at the start of your launch. (22:38) Help your customers remove overwhelm and make informed decisions. (25:03) Handle objections. (28:05) Subject line of the week. Why you should email your audience more than once or twice during a launchFirst thing first, how many times do your normally email your list when you launch a new product or service? The day you open the cart and then the day you close it? What happens in between? Can we just agree that two emails aren't really gonna cut it? When you're promoting a new offer, you need to email your list more than once or twice. But how exactly can you keep talking about this thing you're launching? Use your emails to give your audience a guided tour of your sales pageYou see, the key is to have a plan. And your plan should be all about NOT putting everything you have to say about your launch on your sales page. Hold some things back from your sales page so you have a list of valid reasons to email your list. Because during your launch, you want to use your emails to drip out pieces of your offer – email by email. This doesn't mean you're going to strip down your offer and turn it into something weak and mediocre that no one wants. Your offer needs to be amazing from day one! You're just holding off on announcing some of the stuff that most people announce at the start and breaking down the information that lives on your sales page and giving your subscribers a guided tour of it. Your emails are the place where you pick one element of your sales page and talk about it. Why? So that you can walk people through stuff they might have missed and make them pay attention to it. By announcing new things throughout your launch, you create extra surges and spikes in your sales. Because we all know how it goes - launches are made of peaks and troughs. The peaks are the beginning and at the end. You make sales on your first day and then again on the last day before the cart closes. But in between? That's when you have your troughs. So you want to create some momentum - have an excuse to email your subscribers, give them more reasons to buy, and generate more peaks during your launch. Here are 7 things (in no particular order) that will help you do just that. Hold off introducing a countdown timerA lot of people add a countdown timer to their sales page right at the start of their promotion. We suggest you don't do that. Why? First of all, because if you don't put the timer on the sales page right away, it gives you a great reason to email your list later on and let them know when your cart closes. But also, a countdown timer is a mechanism to create urgency - and a very effective one at that. So don't waste it! Because you won't create any urgency if you set your timer waaaay in the future. If you tell everyone that your offer expires in 2 weeks, they have no reason to take notice now. It's only when the hours, minutes and seconds are literally ticking...
Dental podcast: Welcome to DentalTalk. I'm Dr. Phil Klein. Compression of treatment time in oral implantology is a concept that is gaining popularity. Management of the dento-gingival complex, and development of adequate biologic width, are critical components in achieving ideal functional and aesthetic outcomes. Today we'll be discussing surgical and prosthetic strategies to enhance clinical outcomes in extraction/immediate implant placement, including the use of a final definitive titanium abutment. Our guest is Dr. Robert J. Miller, a Board Certified Diplomate of the American Board of Oral Implantology.
The KOT Crew talk about Quickley, McBride, Toppin and the Knicks Summer League performance vs the Cavs
MIP Markets with Shawn Hackett – Brazilian Coffee Tour Shawn Preps for the Coffee in Brazil. Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-markets-with-shawn-hackett-brazilian
Our heroes regroup after a dangerous combat in the sauna. What mysteries lie in the rest of Floor 8? Will our heroes triumph? Or will they end up beyond the scope of the adventure? Grab a drink and join us at the bar! Drink of the Week: The Hobo King Ingredients 1.5 oz. Dry Gin .5 oz. Sweet Vermouth 2 dashes Orange Bitters 1 oz. Lemon Juice .5 oz. Honey Syrup .25 oz. Campari floater Garnish (optional): Orange Peel Steps: 1: Combine all ingredients (but campari and orange) into a mixing tin. 2: Shake and strain into a chilled glass. 3: Add the campari as a floater. 4: Garnish with orange peel. 5: Enjoy!
Arthur Schwartz was the restaurant critic and executive food editor of the New York Daily News for 18 years. Perhaps what he's best known for is as a chameleon—he's successfully worked in radio, print media, cookbook publishing, TV, and teaching. Today Arthur talks about: Pork, Fat, Salt And here is Arthur's recipe this week! MARINADE SECHE A dry rub for pork, adapted from Julia Child's Mastering the Art of French Cooking, Vol. 1 Enough for 8 pounds of pork – chops, tenderloin, ribs 2 teaspoons dried thyme or sage 3 tablespoons salt 1 teaspoon freshly ground pepper 1 teaspoon ground allspice 1 teaspoon ground bay leaf (see note) (optional) Rub the thyme or sage between the palm and heel of your hands, to make it powdery. Combine with the other ingredients and mix well. Use a rounded teaspoon of mixture for every pound of pork. Rub it in and let stand at room temperature – no more than 2 hours -- until you are ready to cook the meat. Or, wrap in plastic and refrigerate up to 48 hours. Note: I use a small Krups coffee grinder (very inexpensive and mine is now 30 years old) to grind spices – put bay leaves in and pulse then let run until leaves are powdered.
MIP #230 – Down the Rabbit HoleWe start down the road of support equipment and quick switch to conspiracy theories. Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-230-down-the-rabbit-hole
MIP Markets with Shawn Hackett 10-15-21 – Coffee Checkup561-573-3766, HackettAdvisors.comShawn looks at expectations for his upcoming trip to Brazil. Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-markets-with-shawn-hackett-coffer-ch
This is Part I of Household Finance Merger: To Combine, or not to Combine. We have been asked quite frequently whether people should combine their finances if they get married, or commit to a long-term relationship. You can go either way really, there's no wrong answer. But what really matters is to truly understand what it means and what it takes to combine (or not) finances. Dan and Tim talked about the rights and responsibilities from an estate planning perspective. What FDIC insurance can do for you, and how Community property (aka Marital property) states and Common law property states affect your decisions. In the second part of the episode, we will talk about the importance of communication and the emotional impact of your decisions.For more information, visit us at WWW.LBW-WEALTH.COM
Combine ambiguity with anxiety and you have a preview of retail 2022 and beyond. The supply chain collapse is just the tip of the iceberg. Steve Sadove, former CEO of Saks and sought-after retail advisor, joins Robin Lewis and Shelley E. Kohan, TRR's chief strategist, as they dig into the collateral damage from the current supply chain meltdown. Learn about how holiday 2021 may not predict the long-term optimism retailers are hoping for.For more strategic insights and compelling content, visit TheRobinReport.com where you can read, watch, and listen to content from Robin Lewis and other industry experts.Be sure to follow us on LinkedIn and Twitter for the latest from Robin Lewis and The Robin Report.
Nathan Myhrvold, former chief technology officer at Microsoft and chef and author of Modernist Cuisine, joins us to discuss the new entry to the "Modernist" book collection, Modernist Pizza. The book is a three-volume exploration of pizza, its history, the techniques behind it, and where to eat it. Plus, there are over a thousand recipes to explore. Direct Artisan Pizza Dough Makes three 14-inch pizzas | Total Time: Active 15–20 minutes / Inactive 6 hours 2 cups water, 70°F 1 tsp instant dry yeast 4 2/3 cups high-gluten bread flour, 13%–14% protein 1 Tbsp + 1/4 tsp diastatic malt powder 2 1/4 tsp fine salt 1 Tbsp + 1 1/4 tsp extra-virgin olive oil 1. Combine the water and yeast in the mixer's bowl, and whisk to dissolve the yeast. 2. Add the flour and malt powder, and mix on low speed to a shaggy mass, about 1 minute. 3. Mix on medium speed to low gluten development, about 5 minutes. 4. Add the salt, and mix on medium speed until it is fully incorporated, about 1 minute. 5. Add the oil with the machine running on medium speed, and mix the dough until it reaches full gluten development, about 11 minutes. 6. Perform the windowpane test to assess gluten development. Take a portion of dough in your hands and stretch it: the more the dough can stretch without tearing, the more the gluten has developed. The dough will hold the window for at least 8–10 seconds and it can be stretched to the point that it is nearly see-through when it has reached full gluten development. 7. Transfer the dough to a lightly floured worktable. Cover well with plastic wrap. 8. Bench rest for 20 minutes. 9. Divide the dough into three even-sized pieces. 10. To preshape, place each cut square of dough smooth side down. Fold the top one-third of the dough toward the middle, and then fold the bottom one-third toward the middle, overlapping the ends slightly to form an envelope. 11. Rotate the dough 90° and roll the dough up lengthwise. 12. Gently round the dough with both hands, leaving the seam side down, to create a tight, round package. 13. If necessary, pinch the seam shut. This is important to prevent it from ripping when you shape it. 14. Repeat steps 10–13 with the two remaining pieces of dough. 15. Place on a sheet pan. Spray a very light mist of water over the dough. 16. Cover the dough well with plastic wrap. 17. Proof the dough, covered, for 4 1/2–5 1/2 hours at 70°F. 18. Test for proof using the fingertip test. Gently press the exposed surface of the dough for 2 seconds; the pressure should leave a small dent in the dough; it will slowly spring back, but the indentation should remain clearly visible after 1–2 seconds. 19. Shape, assemble, and bake the pizza according to the instructions in the recipe. Notes We recommend Giusto's High Performer High Protein Unbleached Flour. When you are adding the oil to the mixer, try to pour the oil toward the center of the dough rather than to the outside of the dough. This helps keep it from sloshing around the bowl and makes it easier for the mixer to fully incorporate it into the dough. We typically use a dough hook to mix all our medium-crust pizza doughs. If the ingredient quantities aren't large enough for the dough hook to mix them well in a stand mixer, use a paddle attachment initially to mix the ingredients uniformly. Once you have a homogeneous mass (the dough is sticky and wet, and there are no visible clumps or unincorporated water), switch to a hook attachment. Final mix time at higher speeds may vary from machine to machine. Whatever the model and yield, the goal is to achieve a good mix and full gluten development. Consider our suggested times as guidelines only. Use the windowpane test to help determine the dough's stage of gluten development. After preshaping, you can also cold-proof this dough at 39°F for 1–2 days for even better baking and texture results. If you cold-proof the dough, remove the dough from refrigeration 1 1/2–2 hours before shaping so it warms up and is easier to stretch out.
Ein NFL-Spiel in Deutschland ist in naher Zukunft! Die NFL hat drei Finalisten als Austragungsort für ein Spiel in Deutschland bekannt geben. Unsere Jungs freuen sich wie der Sport weiter wächst und sprechen über alle Initiativen der Liga. Sebastian meldet sich vom International Combine aus London und zeigt sich von der Größe mancher Spieler beeindruckt. Außerdem, Gruden raus aus Las Vegas, Russell Wilson's Verletzung und Lamar Jackson dreht komplett auf. Das und vieles mehr gibt es diese Woche in der Vollmer + Kuhn NFL Show. See omnystudio.com/listener for privacy information.
MIP Markets with Chip Nellinger - Ahead of Today's October Report309-550-7213, bluereefinc.com @bluereefAG BlueReefInc.comChip's thoughts on today's USDA October ReportAg News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-amrkets-with-chip-nellinger-10-12-21
MIP Markets with Shawn Hackett 10-12-21561-573-3766, HackettAdvisors.comWe discuss Shawn's Latest Climate Podcast. Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-markets-with-shawn-hackett-10-12-21
Who else has felt complete brain fog when lesson planning? If this sounds familiar, it's no surprise! Teachers make tons of decisions throughout the day, so when you sit down to make even more decisions with your lesson plans, it can feel like a challenge. The goal of this episode is to create some space for you to freely brainstorm your lesson plans for this fall, and I've got a quick trick to help you do that! Step 1. Pick a theme Step 2. Name the skills Step 3. Combine the theme and skills for engaging, meaningful learning activities. Make sure to listen to the episode for pumpkin themed examples for your lower elementary classroom! Did you find this helpful or are you planning on using some of these ideas? Screenshot this episode and share to your Instagram stories! Make sure to tag me so I can see! @teachinglittleleaders Fall Activities: October Counting Mats November Counting Mats
I read from combine to comdt. The word of the episode is "combining form". https://en.wikipedia.org/wiki/Classical_compound Featured in a Top 10 Dictionary Podcasts list! https://blog.feedspot.com/dictionary_podcasts/ Backwards Talking on YouTube: https://www.youtube.com/playlist?list=PLmIujMwEDbgZUexyR90jaTEEVmAYcCzuq dictionarypod@gmail.com https://www.facebook.com/thedictionarypod/ https://twitter.com/dictionarypod https://www.instagram.com/dictionarypod/ https://www.patreon.com/spejampar 917-727-5757
MIP #229 – October Economy Report with @Rich_PossonReal Estate and Farmland Values are Screaming Higher Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-229-october-economy-report-with-rich
MIP Ag News With Jaclyn KrymowskiAg News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction
In this episode host Casey Seymour of Moving Iron LLC talks with regular guest Aaron Fintel, wholesale salesperson with 21st Century Equipment. As we head into the last quarter of 2021, the two discuss the used combine market and what they expect to see happen with inventory and pricing at the end of the year and the first quarter of 2022.
With the help of AI, you'll be able to take a picture of a shirt, then ask Google to find socks with the same pattern.
Kokkie Kooyman, executive director at Denker Capital explains Absa's decision to exchange its investment business for a 17.5% stake in Sanlam Investment Holdings. Rob Stoke, non-executive chair at The Knowledge Trust on how they are working to tackle youth unemployment. In investment school, Mduduzi Luthuli co-Founder and Executive Director at Luthuli Capital, decodes investment edges. See omnystudio.com/listener for privacy information.
MIP #228 Markets with Shawn Hackett 10-5-21 561-573-3766, HackettAdvisors.comHow are the Wheat and Rice Markets going to play out?Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-markets-with-shawn-hackett-10-5-21
Longtime listener and friend of the show, Gio Lodi, released a book y'all should check out and Chris and Steph ruminate on a listener question about tension around marketing in open-source. Say No To More Process, Say Yes To Trust by German Velasco (https://thoughtbot.com/blog/say-no-to-more-process-say-yes-to-trust) Test-Driven Development in Swift with SwiftUI and Combine by Gio Lodi (https://tddinswift.com/) Transcript: CHRIS: Our golden roads. STEPH: All right. I am also golden. CHRIS: [vocalization] STEPH: Oh, I haven't listened to that episode where I just broke out in song in the middle. Oh, you're about to add the [vocalization] [chuckles]. CHRIS: I don't know why, though. Oh, golden roads, Golden Arches. STEPH: Golden Arches, yeah. CHRIS: Man, I did not know that my brain was doing that, but my brain definitely connected those without telling me about it. STEPH: [laughs] CHRIS: It's weird. People talk often about the theory that phones are listening, and then you get targeted ads based on what you said. But I'm almost certain it's actually the algorithms have figured out how to do the same intuitive leaps that your brain does. And so you'll smell something and not make the nine steps in between, but your brain will start singing a song from your childhood. And you're like, what is going on? Oh, right, because when I was watching Jurassic Park that one time, we were eating this type of chicken, and therefore when I smell paprika, Jurassic Park theme song. I got it, of course. STEPH: [laughs] CHRIS: And I think that's actually what's happening with the phones. That's my guess is that you went to a site, and the phones are like, cool, I got it, adjacent to that is this other thing, totally. Because I don't think the phones are listening. Occasionally, I think the phones are listening, but mostly, I don't think the phones are listening. STEPH: I definitely think the phones are listening. CHRIS: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Chris Toomey. STEPH: And I'm Steph Viccari. CHRIS: And together, we're here to share a bit of what we've learned along the way. So, Steph, what's new in your world? STEPH: Hey. So we have a bit of exciting news where we received an email from Gio Lodi, who is a listener of The Bike Shed. And Gio sent an email sharing with us some really exciting news that they have published a book on Test-Driven Development in Swift. And they acknowledge us in the acknowledgments of the book. Specifically, the acknowledgment says, "I also want to thank Chris Toomey and Steph Viccari, who keep sharing ideas on testing week after week on The Bike Shed Podcast." And that's just incredible. I'm so blown away, and I feel officially very famous. CHRIS: This is how you know you're famous when you're in the acknowledgments of a book. But yeah, Gio is a longtime listener and friend of the show. He's written in many times and given us great tips, and pointers, and questions, and things. And I've so appreciated Gio's voice in the community. And it's so wonderful, frankly, to hear that he has gotten value out of the show and us talking about testing. Because I always feel like I'm just regurgitating things that I've heard other people saying about testing and maybe one or two hard-learned truths that I've found. But it's really wonderful. And thank you so much, Gio. And best of luck for anyone out there who is doing Swift development and cares about testing or test-driven development, which I really think everybody should. Go check out that book. STEPH: I must admit my Swift skills are incredibly rusty, really non-existent at this point. It's been so long since I've been in that world. But I went ahead and purchased a copy just because I think it's really cool. And I suspect there are a lot of testing conversations that, regardless of the specific code examples, still translate. At least, that's the goal that you and I have when we're having these testing conversations. Even if they're not specific to a language, we can still talk about testing paradigms and strategies. So I purchased a copy. I'm really looking forward to reading it. And just to change things up a bit, we're going to start off with a listener question today. So this listener question comes from someone very close to the show. It comes from Thom Obarski. Hi, Thom. And Thom wrote in, "So I heard on a recent podcast I was editing some tension around marketing and open source. Specifically, a little perturbed at ReactJS that not only were people still dependent on a handful of big companies for their frameworks, but they also seem to be implying that the cachet of Facebook and having developer mindshare was not allowing smaller but potentially better solutions to shine through. In your opinion, how much does marketing play in the success of an open-source project framework rather than actually being the best tool for the job?" So a really thoughtful question. Thanks, Thom. Chris, I'm going to kick it over to you. What are your thoughts about this question? CHRIS: Yeah, this is a super interesting one. And thank you so much, Thom, although I'm not sure that you're listening at this point. But we'll send you a note that we are replying to your question. And when I saw this one come through, it was interesting. I really love the kernel of the discussion here, but it is, again, very difficult to tease apart the bits. I think that the way the question was framed is like, oh, there's this bad thing that it's this big company that has this big name, and they're getting by on that. But really, there are these other great frameworks that exist, and they should get more of the mindshare. And honestly, I'm not sure. I think marketing is a critically important aspect of the work that we do both in open source and, frankly, everywhere. And I'm going to clarify what I mean by that because I think it can take different shapes. But in terms of open-source, Facebook has poured a ton of energy and effort and, frankly, work into React as a framework. And they're also battle testing it on facebook.com, a giant website that gets tons of traffic, that sees various use cases, that has all permissions in there. They're really putting it through the wringer in that way. And so there is a ton of value just in terms of this large organization working on and using this framework in the same way that GitHub and using Rails is a thing that is deeply valuable to us as a community. So I think having a large organization associated with something can actually be deeply valuable in terms of what it produces as an outcome for us as consumers of that open-source framework. I think the other idea of sort of the meritocracy of the better framework should win out is, I don't know, it's like a Field of Dreams. Like, if you build it, they will come. It turns out I don't believe that that's actually true. And I think selling is a critical part of everything. And so if I think back to DHH's original video from so many years ago of like, I'm going to make a blog in 15 minutes; look at how much I'm not doing. That was a fantastic sales pitch for this new framework. And he was able to gain a ton of attention by virtue of making this really great sales pitch that sold on the merits of it. But that was marketing. He did the work of marketing there. And I actually think about it in terms of a pull request. So I'm in a small organization. We're in a private repo. There's still marketing. There's still sales to be done there. I have to communicate to someone else the changes that I'm making, why it's valuable to the system, why they should support this change, this code coming into the codebase. And so I think that sort of communication is as critical to the whole conversation. And so the same thing happens at the level of open source. I would love for the best framework to always win, but we also need large communities with Stack Overflow answers and community-supported plugins and things like that. And so it's a really difficult thing to treat marketing as just other, this different, separate thing when, in fact, I think they're all intertwined. And marketing is critically important, and having a giant organization behind something can actually have negative aspects. But I think overall; it really is useful in a lot of cases. Those are some initial thoughts. What do you think, Steph? STEPH: Yeah, those are some great initial thoughts. I really agree with what you said. And I also like how you brought in the comparison of pull requests and how sales is still part of our job as developers, maybe not in the more traditional sense but in the way that we are marketing and communicating with the team. And circling back to what you were saying earlier about a bit how this is phrased, I think I typically agree that there's nothing nefarious that's afoot in regards to just because a larger company is sponsoring an open-source project or they are the ones responsible for it, I don't think there's anything necessarily bad about that. And I agree with the other points that you made where it is helpful that these teams have essentially cultivated a framework or a project that is working for their team, that is helping their company, and then they have decided to open source it. And then, they have the time and energy that they can continue to invest in that project. And it is battle-tested because they are using it for their own projects as well. So it seems pretty natural that a lot of us then would gravitate towards these larger, more heavily supported projects and frameworks. Because then that's going to make our job easier and also give us more trust that we can turn to them when we do need help or have issues. Or, like you mentioned, when we need to look up documentation, we know that that's going to be there versus some of the other smaller projects. They may also be wonderful projects. But if they are someone that's doing this in their spare time just on the weekends and yet I'm looking for something that I need to be incredibly reliable, then it probably makes sense for me to go with something that is supported by a team that's getting essentially paid to work on that project, at least that they're backed by a larger company. Versus if I'm going with a smaller project where someone is doing some wonderful work, but realistically, they're also doing it more on the weekends or in their spare time. So boiling it down, it's similar to what you just said where marketing plays a very big part in open source, and the projects and frameworks that we adopt, and the things that we use. And I don't think that's necessarily a bad thing. CHRIS: Yeah. I think, if anything, it's possibly a double-edged sword. Part of the question was around does React get to benefit just by the cachet of Facebook? But Facebook, as a larger organization sometimes that's a positive thing. Sometimes there's ire that is directed at Facebook as an organization. And as a similar example, my experience with Google and Microsoft as large organizations, particularly backing open-source efforts, has almost sort of swapped over time, where originally, Microsoft there was almost nothing of Microsoft's open-source efforts that I was using. And I saw them as this very different shape of a company that I probably wouldn't be that interested in. And then they have deeply invested in things like GitHub, and VS Code, and TypeScript, and tons of projects that suddenly I'm like, oh, actually, a lot of what I use in the world is coming from Microsoft. That's really interesting. And at the same time, Google has kind of gone in the opposite direction for me. And I've seen some of their movements switch from like, oh Google the underdog to now they're such a large company. And so the idea that the cachet, as the question phrase, of a company is just this uniformly positive thing and that it's perhaps an unfair benefit I don't see that as actually true. But actually, as a more pointed example of this, I recently chose Svelte over React, and that was a conscious choice. And I went back and forth on it a few times, if we're being honest, because Svelte is a much smaller community. It does not have the large organizational backing that React or other frameworks do. And there was a certain marketing effort that was necessary to raise it into my visibility and then for me to be convinced that there is enough there, that there is a team that will maintain it, and that there are reasons to choose that and continue with it. And I've been very happy with it as a choice. But I was very conscious in that choice that I'm choosing something that doesn't have that large organizational backing. Because there's a nicety there of like, I trust that Facebook will probably keep investing in React because it is the fundamental technology of the front end of their platform. So yeah, it's not going to go anywhere. But I made the choice of going with Svelte. So it's an example of where the large organization didn't win out in my particular case. So I think marketing is a part of the work, a part of the conversation. It's part of communication. And so I am less negative on it, I think, than the question perhaps was framed, but as always, it depends. STEPH: Yeah, I'm trying to think of a scenario where I would be concerned about the fact that I'm using open source that's backed by a specific large company or corporation. And the main scenario I can think of is what happens when you conflict or if you have values that conflict with a company that is sponsoring that project? So if you are using an open-source project, but then the main community or the company that then works on that project does something that you really disagree with, then what do you do? How do you feel about that situation? Do you continue to use that open-source project? Do you try to use a different open-source project? And I had that conversation frankly with myself recently, thinking through what to do in that situation and how to view it. And I realize this may not be how everybody views it, and it's not appropriate for all situations. But I do typically look at open-source projects as more than who they are backed by, but the community that's actively working on that project and who it benefits. So even if there is one particular group that is doing something that I don't agree with, that doesn't necessarily mean that wholesale I no longer want to be a part of this community. It just means that I still want to be a part, but I still want to share my concerns that I think a part of our community is going in a direction that I don't agree with or I don't think is a good direction. That's, I guess, how I reason with myself; even if an open-source project is backed by someone that I don't agree with, either one, you can walk away. That seems very complicated, depending on your dependencies. Or two, you find ways to then push back on those values if you feel that the community is headed in a direction that you don't agree with. And that all depends on how comfortable you are and how much power you feel like you have in that situation to express your opinion. So it's a complicated space. CHRIS: Yeah, that is a super subtle edge case of all of this. And I think I aligned with what you said of trying to view an open-source project as more generally the community that's behind it as opposed to even if there's a strong, singular organization behind it. But that said, that's definitely a part of it. And again, it's a double-edged sword. It's not just, oh, giant company; this is great. That giant company now has to consider this. And I think in the case of Facebook and React, that is a wonderful hiring channel for them. Now all the people that use React anywhere are like, "Oh man, I could go work at Facebook on React? That's exciting." That's a thing that's a marketing tool from a hiring perspective for them. But it cuts both ways because suddenly, if the mindshare moves in a different direction, or if Facebook as an organization does something complicated, then React as a community can start to shift away. Maybe you don't move the current project off of it, but perhaps you don't start the next one with it. And so, there are trade-offs and considerations in all directions. And again, it depends. STEPH: Yeah. I think overall, the thing that doesn't depend is marketing matters. It is a real part of the ecosystem, and it will influence our decisions. And so, just circling back to Thom's question, I think it does play a vital role in the choices that we make. CHRIS: Way to stick the landing. STEPH: Thanks. Mid-roll Ad And now a quick break to hear from today's sponsor, Scout APM. Scout APM is leading-edge application performance monitoring that's designed to help Rails developers quickly find and fix performance issues without having to deal with the headache or overhead of enterprise platform feature bloat. With a developer-centric UI and tracing logic that ties bottlenecks to source code, you can quickly pinpoint and resolve those performance abnormalities like N+1 queries, slow database queries, memory bloat, and much more. Scout's real-time alerting and weekly digest emails let you rest easy knowing Scout's on watch and resolving performance issues before your customers ever see them. Scout has also launched its new error monitoring feature add-on for Python applications. Now you can connect your error reporting and application monitoring data on one platform. See for yourself why developers call Scout their best friend and try our error monitoring and APM free for 14 days; no credit card needed. And as an added-on bonus for Bike Shed listeners, Scout will donate $5 to the open-source project of your choice when you deploy. Learn more at scoutapm.com/bikeshed. That's scoutapm.com/bikeshed. STEPH: Changing topics just a bit, what's new in your world? CHRIS: Well, we had what I would call a mini perfect storm this week. We broke the build but in a pretty solid way. And it was a little bit difficult to get it back under control. And it has pushed me ever so slightly forward in my desire to have a fully optimized CI and deploy pipeline. Mostly, I mean that in terms of ratcheting. I'm not actually going to do anything beyond a very small set of configurations. But to describe the context, we use pull requests because that's the way that we communicate. We do code reviews, all that fun stuff. And so there was a particular branch that had a good amount of changes, and then something got merged. And this other pull request was approved. And that person then clicked the rebase and merge button, which I have configured the repository, so that merge commits are not allowed because I'm not interested in that malarkey in our history. But merge commits or rebase and merge. I like that that makes sense. In this particular case, we ran into the very small, subtle edge case of if you click the rebase and merge button, GitHub is now producing a new commit that did not exist before, a new version of the code. So they're taking your changes, and they are rebasing them onto the current main branch. And then they're attempting to merge that in. And A, that was allowed. B, the CI configuration did not require that to be in a passing state. And so basically, in doing that rebase and merge, it produced an artifact in the build that made it fail. And then attempting to unwind that was very complicated. So basically, the rebase produced...there were duplicate changes within a given file. So Git didn't see it as a conflict because the change was made in two different parts of the file, but those were conflicting changes. So Git was like, this seems like it's fine. I can merge this, no problem. But it turns out from a functional perspective; it did not work. The build failed. And so now our main branch was failing and then trying to unwind that it just was surprisingly difficult to unwind that. And it really highlighted the importance of keeping the main branch green, keeping the build always passing. And so, I configured a few things in response to this. There is a branch protection rule that you can enable. And let me actually pull up the specific configuration that I set up. So I now have enabled require status checks to pass before merging, which, if we're being honest, I thought that was the default. It turns out it was not the default. So we are now requiring status checks to pass before merging. I'm fully aware of the awkward, painful like, oh no, the build is failing but also, we have a bug. We need to deploy this. We must get something merged in. So hopefully, if and when that situation presents itself, I will turn this off or somehow otherwise work around it. But for now, I would prefer to have this as a yeah; this is definitely a configuration we want. So require status checks to pass before merging and then require branches to be up to date before merging. So the button that does the rebase and merge, I don't want that to actually do a rebase on GitHub. I want the branch to already be up to date. Basically, I only ever want fast-forward merges on our main branch. So all code should be ahead of main, and we are simply updating what main points at. We are not creating new code. That code has run on CI, that version of the code specifically. We are fully rebased and up to date on top of main, and that's how we're going. STEPH: All of that is super interesting. I have a question about the workflow. I want to make sure I'm understanding it correctly. So let's say that I have issued a PR, and then someone else has merged into the main branch. So now my PR is behind me, and I don't have that latest commit. With the new configuration, can I still use the rebase and merge, or will I need to rebase locally and then push up my branch before I can merge into main but at least using the GitHub UI? CHRIS: I believe that you would be forced to rebase locally, force push, and then CI would rebuild, and that's what it is. So I think that's what require branches to be up to date before merging means. So that's my hope. That is the intention here. I do realize that's complicated. So this requirement, which I like, because again, I really want the idea that no, no, no, we, the developers, are in charge of that final state. That final state should always run as part of a build of CI on our pull request/branch before going into main. So no code should be new. There should be no new commits that have never been tested before going into main. That's my strong belief. I want that world. I realize that's...I don't know. Maybe I'm getting pedantic, or I'm a micromanager of the Git history or whatever. I'm fine with any of those insults that people want to lob at me. That's fine. But that's what I feel. That said, this is a nuisance. I'm fully aware of that. And so imagine the situation where we got a couple of different things that have been in flight. People have been working on different...say there are three pull requests that are all coming to completion at the same time. Then you start to go to merge something, and you realize, oh no, somebody else just merged. So you rebase, and then you wait for CI to build. And just as the CI is completing, somebody else merges something, and you're like, ah, come on. And so then you have to one more time rebase, push, wait for the build to be green. So I get that that is not an ideal situation. Right now, our team is three developers. So there are a few enough of us that I feel like this is okay. We can manage this via human intervention and just deal with the occasional weight. But in the back of my mind, of course, I want to find a better solution to this. So what I've been exploring…there's a handful of different utilities that I'm looking at, but they are basically merged queues as an idea. So there are three that I'm looking at, or maybe just two, but there's mergify.io, which is a hosted solution that does this sort of thing. And then Shopify has a merge queue implementation that they're running. So the idea with this is when you as a developer are ready to merge something, you add a label to it. And when you add that label, there's some GitHub Action or otherwise some workflow in the background that sees that this has happened and now adds it to a merge queue. So it knows all of the different things that might want to be merged. And this is especially important as the team grows so that you don't get that contention. You can just say, "Yes, I would like my changes to go out into production." And so, when you label it, it then goes into this merge queue. And the background system is now going to take care of any necessary rebases. It's going to sequence them, so it's not just constantly churning all of the branches. It's waiting because it knows the order that they're ideally going to go out in. If CI fails for any of them because rebasing suddenly, you're in an inconsistent state; if your build fails, then it will kick you out of the merge queue. It will let you know. So it will send you a notification in some manner and say, "Hey, hey, hey, you got to come look at this again. You've been kicked out of the merge queue. You're not going to production." But ideally, it adds that layer of automation to, frankly, this nuisance of having to keep things up to date and always wanting code to be run on CI and on a pull request before it gets into main. Then the ideal version is when it does actually merge your code, it pings you in Slack or something like that to say, "Hey, your changes just went out to production." Because the other thing I'm hoping for is a continuous deployment. STEPH: The idea of a merge queue sounds really interesting. I've never worked with a process like that. And one of the benefits I can see is if I know I'm ready for something to go like if I'm waiting on a green build and I'm like, hey, as soon as this is green, I'd really like for it to get merged. Then currently, I'm checking in on it, so I will restart the build. And then, every so often, I'm going back to say, "Okay, are you green? Are you green? Can I emerge?" But if I have a merge queue, I can say, "Hey, merge queue, when this is green, please go and merge it for me." If I'm understanding the behavior correctly, that sounds really nifty. CHRIS: I think that's a distinct but useful aspect of this is the idea that when you as a developer decide this PR is ready to go, you don't need to wait for either the current build or any subsequent builds. If there are rebases that need to happen, you basically say, "I think this code's good to go. We've gotten the necessary approvals. We've got the buy-in and the teams into this code." So cool, I now market as good. And you can walk away from it, and you will be notified either if it fails to get merged or if it successfully gets merged and deployed. So yes, that dream of like, you don't have to sit there watching the pot boil anymore. STEPH: Yeah, that sounds nice. I do have to ask you a question. And this is related to one of the blog posts that you and I love deeply and reference fairly frequently. And it's the one that's written by German Velasco about Say No to More Process, and Say Yes to Trust. And I'm wondering, based on the pain that you felt from this new commit, going into main and breaking the main build, how do you feel about that balance of we spent time investigating this issue, and it may or may not happen again, and we're also looking into these new processes to avoid this from happening? I'm curious what your thought process is there because it seems like it's a fair amount of work to invest in the new process, but maybe that's justified based on the pain that you felt from having to fix the build previously. CHRIS: Oh, I love the question. I love the subtle pushback here. I love this frame of mind. I really love that blog post. German writes incredible blog posts. And this is one that I just keep coming back to. In this particular case, when this situation occurred, we had a very brief...well, it wasn't even that brief because actually unwinding the situation was surprisingly painful, and we had some changes that we really wanted to get out, but now the build was broken. And so that churn and slowdown of our build pipeline and of our ability to actually get changes out to production was enough pain that we're like, okay, cool. And then the other thing is we actually all were in agreement that this is the way we want things to work anyway, that idea that things should be rebased and tested on CI as part of a pull request. And then we're essentially only doing fast-forward merges on the main branch, or we're fast forward merging main into this new change. That's the workflow that we wanted. So this configuration was really just adding a little bit of software control to the thing that we wanted. So it was an existing process in our minds. This is the thing we were trying to do. It's just kind of hard to keep up with, frankly. But it turns out GitHub can manage it for us and enforce the process that we wanted. So it wasn't a new process per se. It was new automation to help us hold ourselves to the process that we had chosen. And again, it's minimally painful for the team given the size that we're at now, but I am looking out to the future. And to be clear, this is one of the many things that fall on the list of; man, I would love to have some time to do this, but this is obviously not a priority right now. So I'm not allowed to do this. This is explicitly on the not allowed to touch list, but someday. I'm very excited about this because this does fundamentally introduce some additional work in the pipeline, and I don't want that. Like you said, is this process worth it for the very small set of times that it's going to have a bad outcome? But in my mind, the better version, that down the road version where we have a merge queue, is actually a better version overall, even with just a tiny team of three developers that are maybe never even conflicting in our merges, except for this one standout time that happens once every three months or whatever. This is still nicer. I want to just be able to label a pull request and walk away and have it do the thing that we have decided as a team that we want. So that's the dream. STEPH: Oh, I love that phrasing, to label a pull request and be able to walk away. Going back to our marketing, that really sells that merge queue to me. [laughs] Mid-roll Ad And now we're going to take a quick break to tell you about today's sponsor, Orbit. Orbit is mission control for community builders. Orbit offers data analytics, reporting, and insights across all the places your community exists in a single location. Orbit's origins are in the open-source and developer relations communities. And that continues today with an active open-source culture in an accessible and documented API. With thousands of communities currently relying on Orbit, they are rapidly growing their engineering team. The company is entirely remote-first with team members around the world. You can work from home, from an Orbit outpost in San Francisco or Paris, or find yourself a coworking spot in your city. The tech stack of the main orbit app is Ruby on Rails with JavaScript on the front end. If you're looking for your next role with an empathetic product-driven team that prides itself on work-life balance, professional development, and giving back to the larger community, then consider checking out the Orbit careers page for more information. Bonus points if working in a Ruby codebase with a Ruby-oriented team gives you a lot of joy. Find out more at orbit.love/weloveruby. CHRIS: To be clear, and this is to borrow on some of Charity Majors' comments around continuous deployment and whatnot, is a developer should stay very close to the code if they are merging it. Because if we're doing continuous deployment, that's going to go out to production. If anything's going to happen, I want that individual to be aware. So ideally, there's another set of optimizations that I need to make on top of this. So we've got the merge queue, and that'll be great. Really excited about that. But if we're going to lean into this, I want to optimize our CI pipeline and our deployment pipeline as much as possible such that even in the worst case where there's three different builds that are fighting for contention and trying to get out, the longest any developer might go between labeling a pull request and saying, "This is good to go," and it getting out to production, again, even if they're contending with other PRs, is say 10, 15 minutes, something like that. I want Slack to notify them and them to then re-engage and keep an eye on things, see if any errors pop up, anything like that that they might need to respond to. Because they're the one that's got the context on the code at that point, and that context is decaying. The minute you've just merged a pull request and you're walking away from that code, the next day, you're like, what did I work on? I don't remember that at all. That code doesn't exist anymore in my brain. And so,,, staying close to that context is incredibly important. So there's a handful of optimizations that I've looked at in terms of the CircleCI build. I've talked about my not rebuilding when it actually gets fast-forward merged because we've already done that build on the pull request. I'm being somewhat pointed in saying this has to build on a pull request. So if it did just build on a pull request, let's not rebuild it on main because it's identically the same commit. CircleCI, I'm looking at you. Give me a config button for that, please. I would really love that config button. But there are a couple of other things that I've looked at. There's RSpec::Retry from NoRedInk, which will allow for some retry semantics. Because it will be really frustrating if your build breaks and you fall out of the merge queue. So let's try a little bit of retry logic on there, particularly around feature specs, because that's where this might happen. There's Knapsack Pro which is a really interesting thing that I've looked at, which does parallelization of your RSpec test suite. But it does it in a different way than say Circle does. It actually runs a build queue, and each test gets sent over, and they have build agents on their side. And it's an interesting approach. I'm intrigued. I think it could use some nice speed-ups. There's esbuild on the Heroku side so that our assets build so much more quickly. There are lots of things. I want to make it very fast. But again, this is on the not allowed to do it list. [laughs] STEPH: I love how most of the world has a to-do list, and you have this not-allowed to-do list that you're adding items to. And I'm really curious what all is on the not allowed to touch lists or not allowed to-do list. [laughs] CHRIS: I think this might be inherent to being a developer is like when I see a problem, I want to fix it. I want to optimize it. I want to tweak it. I want to make it so that that never happens again. But plenty of things...coming back to German's post of Say No to More Process, some things shouldn't be fixed, or the cost of fixing is so much higher than the cost of just letting it happen again and dealing with it manually at that moment. And so I think my inherent nature as a developer there's a voice in my head that is like, fix everything that's broken. And I'm like, sorry. Sorry, brain, I do not have that kind of time. And so I have to be really choosy about where the time goes. And this extends to the team as well. We need to be intentional around what we're building. Actually, there's a feeling that I've been feeling more acutely than ever, but it's the idea of this trade-off or optimization between speed and getting features out into the world and laying the right fundamentals. We're still very early on in this project, and I want to make sure we're thinking about things intentionally. I've been on so many projects where it's many years after it started and when I ask someone, "Hey, why do your background jobs work that way? That's a little weird." And they're like, "Yeah, that was just a thing that happened, and then it never changed. And then, we copied it and duplicated, and that pattern just got reinforced deeply within the app. And at this point, it would cost too much to change." I've seen that thing play out so many times at so many different organizations that I'm overwhelmed with that knowledge in the back of my head. And I'm like, okay, I got to get it just right. But I can't take the time that is necessary to get it, quote, unquote, "Just right." I do not have that kind of time. I got to ship some features. And this tension is sort of the name of the game. It's the thing I've been doing for my entire career. But now, given the role that I have with a very early-stage startup, I've never felt it more acutely. I've never had to be equally as concerned with both sides of that. Both matter all the more now than they ever have before, and so I'm kind of existing in that space. STEPH: I really like that phrasing of that space because that deeply resonates with me as well. And that not allowed to-do list I have a similar list. For me, it's just called a wishlist. And so it's a wishlist that I will revisit every so often, but honestly, most things on there don't get done. And then I'll clear it out every so often when I feel it's not likely that I'm going to get to it. And then I'll just start fresh. So I also have a similar this is what I would like to do if I had the time. And I agree that there's this inclination to automate as well. As soon as we have to do something that felt painful once, then we feel like, oh, we should automate it. And that's a conversation that I often have with myself is at what point is the cost of automation worthwhile versus should we just do this manually until we get to that point? So I love those nuanced conversations around when is the right time to invest further in this, and what is the impact? And what is the cost of it? And what are the trade-offs? And making that decision isn't always clear. And so I think that's why I really enjoy these conversations because it's not a clear rubric as to like, this is when you invest, and this is when you don't. But I do feel like being a consultant has helped me hone those skills because I am jumping around to different teams, and I'm recognizing they didn't do this thing. Maybe they didn't address this or invest in it, and it's working for them. There are some oddities. Like you said, maybe I'll ask, "Why is this? It seems a little funky. What's the history?" And they'll be like, "Yeah, it was built in a hurry, but it works. And so there hasn't been any churn. We don't have any issues with it, so we have just left it." And that has helped reinforce the idea that just because something could be improved doesn't mean it's worthwhile to improve it. Circling back to your original quest where you are looking to improve the process for merging and ensuring that CI stays green, I do like that you highlighted the fact that we do need to just be able to override settings. So that's something that has happened recently this week for me and my client work where we have had PRs that didn't have a green build because we have some flaky tests that we are actively working on. But we recognize that they're flaky, and we don't want that to block us. I'm still shipping work. So I really appreciate the consideration where we want to optimize so that everyone has an easy merging experience. We know things are green. It's trustworthy. But then we also have the ability to still say, "No, I am confident that I know what I'm doing here, and I want to merge it anyways, but thank you for the warning." CHRIS: And the constant pendulum swing of over-correcting in various directions I've experienced that. And as you said, in the back of my mind, I'm like, oh, I know that this setting I'm going to need a way to turn this setting off. So I want to make sure that, most importantly, I'm not the only one on the team who can turn that off because the day that I am away on vacation and the build is broken, and we have a critical bug that we need to fix, somebody else needs to be able to do that. So that's sort of the story in my head. At the same time, though, I've worked on so many teams where they're like, oh yeah, the build has been broken for seven weeks. We have a ticket in the backlog to fix that. And it's like, no, the build has to not be broken for that long. And so I agree with what you were saying of consulting has so usefully helped me hone where I fall on these various spectrums. But I do worry that I'm just constantly over-correcting in one direction or the other. I'm never actually at an optimum. I am just constantly whatever the most recent thing was, which is really impacting my thinking on this. And I try to not do that, but it's hard. STEPH: Oh yeah. I'm totally biased towards my most recent experiences, and whatever has caused me the most pain or success recently. I'm definitely skewed in that direction. CHRIS: Yeah, I definitely have the recency bias, and I try to have a holistic view of all of the things I've seen. There's actually a particular one that I don't want to pat myself on the back for because it's not a good thing. But currently, our test suite, when it runs, there's just a bunch of noise. There's a bunch of other stuff that gets printed out, like a bunch of it. And I'm reminded of a tweet from Kevin Newton, a friend of the show, and I just pulled it up here. "Oh, the lengths I will go to avoid warnings in my terminal, especially in the middle of my green dots. Don't touch my dots." It's a beautiful beauty. He actually has a handful about the green dots. And I feel this feel. When I run my test suite, I just want a sea of green dots. That's all I want to see. But right now, our test suite is just noise. It's so much noise. And I am very proud of...I feel like this is a growth moment for me where I've been like, you know what? That is not the thing to fix today. We can deal with some noise amongst the green dots for now. Someday, I'm just going to lose it, and I'm going to fix it, and it's going to come back to green dots. [chuckles] STEPH: That sounds like such a wonderful children's book or Dr. Seuss. Oh, the importance of green dots or, oh, the places green dots will take you. CHRIS: Don't touch my dots. [laughter] STEPH: Okay. Maybe a slightly aggressive Dr. Seuss, but I still really like it. CHRIS: A little more, yeah. STEPH: On that note of our love of green dots, shall we wrap up? CHRIS: Let's wrap up. The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. All: Byeeeeeee!!! Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.
Mara and Elysia talk about the popular trend HIIT. Everyone is doing it, but should everyone be participating? LISTEN AND SEE! But for those who love to read...here's a little written preview: What is HIIT Training: High-intensity interval training is a form of interval training, a cardiovascular exercise strategy alternating short periods of intense anaerobic exercise with less intense recovery periods, until too exhausted to continue. It's great for those who are short on time as a way of maximizing your time spent in the gym. A typical HIT session, not including your warm up, SHOULD last a maximum of 20 minutes. Many of the benefits of HIIT training have been vastly overstated by the media and marketers but there are definitely some advantages to it. PROS: HIIT training SUPPOSEDLY leads to greater EPOC (excess post-exercise oxygen consumption) when compared to continuous exercise. This means that after you have finished exercising, your body will continue to burn calories at a higher rate than normal. The evidence base is small, but at least one study has shown that you can match the training effect of continuous training in less time using a proper HIIT protocol. You get maximum benefit for decreased time investment. Since we are all super busy and stressed for time, and can't find the time in the day to exercise, this can be very valuable. It has been shown to also increase muscle growth, however, that is not the gold standard of muscle building. Strength training always wins. Even though there has been shown some benefit, it's not the most valuable way to build muscle. CONS: Increased Injury HIIT workouts often call for complicated exercise moves, like burpees and box jumps. Trainers warn that doing these moves with the wrong form can lead to pulled muscles and other injuries. Combine that with the rapid-fire pace of HIIT, and you've got a recipe for fitness injuries. Plus, intense routines often put heavy stress on your body, which can cause overuse injuries and joint strains. Work ‘till hurts, like “fitspo” Instagrammers encourage, and you'll find yourself with strained knees and shoulders. HIIT workouts should usually be done no more than 3 times a week. Also, you should start under the guidance of a professional trainer who can ensure your form is stable and correct. This will help prevent injuries from HIIT. Advanced Preparation Despite articles everywhere promise five fat-shredding minutes to a beach body, HIIT workouts aren't for fitness newbies. The complicated moves and intense demands mean this style of training works best for experienced gym-goers. If you want to start a HIIT workout with little prior experience, you need to prepare yourself with weeks of lower-intensity training. There's also plenty of workout prep to do before and after. Dynamic stretching or warm-up exercises before HIIT will minimize the odds of soreness and injuries. Post-workout static stretches are also a good idea to avoid injury and soothe strained muscles. This prep work might take as long or longer than your five minutes of training. Make sure to check out the instagram @muscle.spasms as well as our hosts @Elysian.form and @maramarek
Our heroes face off in the most dangerous of circumstances - Underwater, single file, and assailed by a swarm! Who will survive? Grab a drink and join us at the bar! Drink of the Week: Sex on the Beach Ingredients: 1.5 oz. Vodka 1 oz. Peach Schnapps 2 oz. Orange Juice 2 oz. Cranberry Juice Orange Wedge (garnish, optional) Steps: 1: Combine all ingredients in a glass over ice. 2: Garnish with orange wedge. 3: Enjoy!
MIP #228 – Heading Into the Last Quarter @AaronFintel and I talk about the Used Equipment Market heading into the last quarter of the year. We also take a hard look at the Combine Market's rapid decline. Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-228-heading-to-the-last-quarter
MIP Markets with Shawn Hackett 9-30-21561-573-3766, HackettAdvisors.comWhat is going to be in today's report and the Soft Markets?Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction https://www.spreaker.com/user/9810017/mip-market-with-shawn-hackett
In this episode, I share one atomic habit that I applied to lose 70 pounds, skipping breakfast. Yep, mom, and Judy, that dietician gives you sugary juice, cornflakes, and a muffin at the hospital are wrong. You don't need breakfast, at least just 6 hours after you gorged yourself while watching your latest Netflix binge series. Move it back 16 hours after your 6:00 dinner the night before. In this episode, I discuss my experience with the 16/8 intermittent fasting protocol and explain why it works using the work of Dr. Jason Fung and his book the Obesity Code. I am going to be doing a separate cast on his work, but you really need to read that book along with Atomic Habits by James Clear. Combine the two, and you will change your life. In Clear's book, he discusses identify and tiny steps reinforcing that identity. I am an intermittent faster and I'll share with you the tiny wins that reinforced that identity. 70 pounds later. I now have a lot of proof to reinforce that identity. And I'm no longer dadbod guy. Bye-bye Dadbod!! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app
MIP Markets with Shawn Hackett 9-28-21561-573-3766, HackettAdvisors.comAre we going to run out of natural this Winter? Ag News By @theherdbookPresented By @AxonTire, @TractorZoom, @ArrowCRM_Music By: @TalbottBrothers @casey9673 @traderbrent @Aaronfintel #AgEquipmentBusinessTalk#LetsGoMoveSomeIronContact me @: MovingIronLLC.comMovingIronPodcast@MovingIronPodcast.com#AgEquipmentBusinessTalk #LetsGoMoveSomeIron #agmarkets #combine #combinetires #corn #idlechatterpodcast #AgTires #Harvest21 #Tillage #plant21 #till21 #tractor #BushelandCents #tractorzoom #worldeconomy #IronComps #PrecisionDonor #BornThatWay #Soybeans #TaxMoves #TheHerdBook #AuctionMarket #EquipmentAuction #FarmEquipmentAuction
Being a parent is TOUGH. Having a chronic illness is TOUGH. Combine the two... and man. It's so easy to feel like you're failing EVERYWHERE. Tune in to this episode for some love... I get it. I see you. I've been there too.
This week on Episode 524 of Priority One: New York Comic Con is ready to Trek Out; the community rallies behind Wilson Cruz; Star Trek Online updates its minimum system requirements; mobile games cross to desktop; and we review Lower Decks' “Where Pleasant Fountains Lie”–but not before we chat with Cryptic Studios's Content Creator Ryon and Environment Artist Gianna! TREK IT OUT Edited by Thomas Reynolds Trekking Out the Big Apple By Elio Lleo Convention season is in full swing and New York Comic Con is next. Starting October 7th and ending October 10th, this four day event usually has stuff for everyone! Unique to this year's presentation is hybrid participation: not only are organizers reducing the total number of attendees, you can also purchase a virtual ticket that will give you access to some of the panels right from the comfort of your own home. But what's so special about NYCC? As of right now, Paramount+ is slated to present at least two panels: on Saturday, October 9th at 12:45pm the cast and producers of Star Trek: Discovery take the Empire Stage. Then on Sunday, October 10, Star Trek: Prodigy will premiere its first episode along with a panel. Image: ViacomCBS/Nickelodeon, via TrekCore. But that's not all–join the Roddenberry Podcast Network as we present a panel titled “Star Trek's Guide to Community.” I'll be there along with Kennedy and Sue from Women at Warp! That's happening Saturday, Oct 9th at 2:15pm. There's also a Hallmark presentation with new Trek ornaments, a virtual only panel with the folks behind the new Star Trek Magazine, and even Bill Shatner will be there on Thurs, October 7th. Wilson Cruz Harassed During Star Trek Day By Elio Lleo When it comes to communities, even Star Trek's can be incredibly divisive. The majority of the time, it's about NuTrek vs older Trek, who the better first officer is, or which ship is cooler. However, there are times when things can get dark and people start to show their true colors–like one fan who was offered the privilege of attending the Star Trek Day celebrations in person. Long story short, at one point during the event, while Wilson Cruz was on stage, someone in the audience yield out a homophobic slur. According to reports, no one did anything about it. The guest was not removed nor have they been identified (yet). With incredible grace and patience, Wilson continued on and later took to Twitter to address the matter. https://twitter.com/wcruz73/status/1436333680880934927 Although he may not have wanted to draw so much attention to the matter, we want to take a moment to remind you–our listeners–that tolerance for the bigoted has its limits. When you see something, say something. Learn ways on how to be the best ally you can be for people who are marginalized on a daily basis. If you're on social media and someone goes on a hate-filled rant, step up. It's the inaction of those with the means to stand up to injustices that empower those who want to watch the world burn. [If you don't think this belongs in Trek, then there's the airlock. Help yourself.–Ed.] Image: ViacomCBS, via StarTrek.com IP Theft, the Sincerest Form of Flattery By Cat Hough On Monday, we were treated to the big uniform reveal by General Jay Raymond, Chief of Space Operations for Space Force who tweeted, "Every winning team needs a uniform!.I'm excited to share the new look with you today." And to no one's surprise, the Twitterverse immediately noticed some striking similarities to some other uniforms that we are quite familiar with. They were described by one person as "a blend of the Star Trek Enterprise dress uniform, but with the Mirror Universe diagonal." https://twitter.com/SpaceForceCSO/status/1440323962697752590 [I am voluntarily putting this into my own shownotes for your edification, dear listener. You owe me.–Ed.] Josh Weinstein, a veteran writer for The Simpsons and Futurama, said the uniform reminded him of the ridiculously tight outfits worn by Zapp Brannigan; Movies in Focus hopped on the satirical bandwagon with the image of an Imperial Star Destroyer officer from the original Star Wars trilogy. "These new Space Force uniforms are looking great," jokes the caption. Quick News Roundup Here are a few headlines that we didn't discuss but might interest you. Reuben Klamer, the designer of the original Starfleet phaser rifle for the original series of Star Trek, passed away at the age of 99, according to the Toy Association. Klamer also designed props for other shows, including a gun for the hit 1960s series The Man From U.N.C.L.E. https://youtu.be/oWGNDoXG9R8 STAR TREK GAMING NEWS Edited by Thomas Reynolds PSA: She Canna Take Any More, Cap'ns! By Thomas Reynolds To every thing there is a season–and in Cryptic's opinion, the season for Windows 7 is long past. Starting February 15, 2022, anyone still using the 10-year-old OS (seriously, not even Microsoft supports it anymore) won't be able to patch or log into STO and Neverwinter. Only Windows 8 and 10 (with the superior 64-bit intellect) will have a home on the final frontier. DirectX 10 support is also getting ejected like a spent warp core on February 15th, with both games requiring Feature Level 11 or higher. That means your computer needs to have one of the following video card chipsets to play: NVidia GeForce GTX 400 or better ATI/AMD Radeon HD 5000 or better Intel HD Graphics 4000 or better Given all the fun and excitement of buying graphics cards these days, if your current card isn't up to the task...well, godspeed. [Pictured: my rig next February.–Ed.] Image: ViacomCBS, via KVNF Public Radio. Aux2Bat Gets Boimed Out By Thomas Reynolds The aqueduct, the magnetic compass, the Aux2Bat. All of these simple technologies have withstood the test of time, but the last may be the most miraculous. Needing only three Technician doffs and one boff ability at minimum, the Aux2Bat ship build is easy to assemble, trivial to fly, and still keeps your bridge officers ready for whatever space wizardry you demand of them. Sure, it hasn't been the meta in a sehlat's age, but you know what? Aux2Bat does the job, it does it pretty well, and that's pretty much all we ask...until now. Ever drop a Gravity Well, and notice your Tyken's Rift is now off-limits for 15 seconds? That's the Shared Category Cooldown kicking in, forcing you to pace yourself rather than let everything rip at once. When Cryptic first released the Boimler Effect trait, it provided a 2.5% percent chance of resetting every bridge officer ability to its Shared Category Cooldown, whenever you used a non-specialist boff ability. Great in theory, but one-in-forty odds just aren't worth a 200 Lobi investment. Yeah, that's was also our reaction. Image: ViacomCBS, via TrekZone.de So Cryptic did a little tweaking, like you do, and made it a 17.5% percent proc chance instead. As STO streamer @AugmentedDG declared on Twitter, “Boimler Effect is now as good as Aux2Bat...for cooldown reduction.” Bold words, to be sure, but there's also a fairly convincing clip of him keeping eight of his escort's twelve boff abilities concurrently running like an overambitious plate spinner. Trek out the tweet, scrape together that Lobi, and give your boffs more buffer time than they can handle. https://twitter.com/AugmentedDG/status/1438707179268284425 Is there in Screen Accuracy No Beauty? By Thomas Reynolds One of Trek cosplay's hallmarks is its hair-splitting fidelity to what's seen on screen, even when the creators themselves don't quite pull it off. Combine that tendency with STO's promise of personal immersion, and it's no surprise that some players want their captain's threads to look “correct.” To help make that a little easier, Cryptic released official in-game color guides for both the newly-available Lower Decks Starfleet jacket, and their original Khitomer uniform creation. However, rapturous Space Barbie enthusiasts should make sure they're using the second released Khitomer guide, as the first one had incorrect pant color codes. https://twitter.com/trekonlinegame/status/1439020385572245509 The Sally Ride, the Ross, and You By Shane Hoover If you were a fan of the Star Trek Adventures web series “Shield of Tomorrow” or “Clear Skies”, you're already familiar with the dangers and wonders of the Shackleton Expanse. If you weren't, then be prepared for deadly spatial phenomena, ancient alien technologies, first contact with new species and lots of boldly going. It's all there in Modiphius Entertainment's newest STA sourcebook, the Shackleton Expanse Campaign Guide. The new sourcebook is available for preorder at $60 now and is expected to ship in December 2021. This is your tabletop gaming crew's chance to follow in the warp trails of the U.S.S. Sally Ride and the U.S.S. Ross. Adventure into a nearly uncharted region of space beyond Federation, Klingon and Romulan borders. Image: Modiphius Entertainment. The new material includes five new playable alien species for STA including Orions. It also includes NPCs from Starbase 364 and around the Expanse, as well as stats for “hero” and NPC vessels. This sourcebook does require a copy of the Star Trek Adventures core rulebook, which is provided in PDF form with your order. The Ar-mod-a Returns By Thomas Reynolds Maybe 2000 feels like a long time ago to you, maybe it doesn't. Either way, the Star Trek: Armada and Armada II RTS games that came out then still hold a place in certain PC players' hearts. So much, in fact, that the Stellar Parallax modding group has finally released what Activision would not: Star Trek: Armada III. Starting as a one-person passion project back in 2012, Armada III is a full-conversion mod for 2012's Sins of a Solar Empire: Rebellion. Stellar Parallax's devoted faithful can now command the Federation, Klingons, Romulans, Borg, or Cardassian Union at the beginning of the Dominion War. See, Kurtzman? You can have more than one kind of ship in a fleet. Image: Stellar Parallax. But really, how much demand is there for a nine-year-old game mod, following up on a twenty-year-old series? After its September 10th release, Armada III is the 51st most-popular mod on the ModDB site, out of over 46,000 entries across hundreds of games–so we'd say “a lot.” [Update: #21 as of publication. Damn.–Ed.] Quick Star Trek Gaming News Roundup A few weeks back we mentioned that the mobile game Star Trek Fleet Command was beta testing a desktop client for Windows. Well, they're out of beta and it's now available for download, with special perks being offered when you log in via desktop! Game maker WizKids announced a new combo-building game titled “Star Trek Missions” –according to their announcement, “your goal is to assemble the highest-scoring combos possible by drawing cards from the Galaxy deck, the Mission deck, or the discard area.” It'll be available February 2022, but you can pre-order now.
This week on Episode 524 of Priority One: New York Comic Con is ready to Trek Out; the community rallies behind Wilson Cruz; Star Trek Online updates its minimum system requirements; mobile games cross to desktop; and we review Lower Decks' “Where Pleasant Fountains Lie”–but not before we chat with Cryptic Studios's Content Creator Ryon and Environment Artist Gianna! TREK IT OUT Edited by Thomas Reynolds Trekking Out the Big Apple By Elio Lleo Convention season is in full swing and New York Comic Con is next. Starting October 7th and ending October 10th, this four day event usually has stuff for everyone! Unique to this year's presentation is hybrid participation: not only are organizers reducing the total number of attendees, you can also purchase a virtual ticket that will give you access to some of the panels right from the comfort of your own home. But what's so special about NYCC? As of right now, Paramount+ is slated to present at least two panels: on Saturday, October 9th at 12:45pm the cast and producers of Star Trek: Discovery take the Empire Stage. Then on Sunday, October 10, Star Trek: Prodigy will premiere its first episode along with a panel. Image: ViacomCBS/Nickelodeon, via TrekCore. But that's not all–join the Roddenberry Podcast Network as we present a panel titled “Star Trek's Guide to Community.” I'll be there along with Kennedy and Sue from Women at Warp! That's happening Saturday, Oct 9th at 2:15pm. There's also a Hallmark presentation with new Trek ornaments, a virtual only panel with the folks behind the new Star Trek Magazine, and even Bill Shatner will be there on Thurs, October 7th. Wilson Cruz Harassed During Star Trek Day By Elio Lleo When it comes to communities, even Star Trek's can be incredibly divisive. The majority of the time, it's about NuTrek vs older Trek, who the better first officer is, or which ship is cooler. However, there are times when things can get dark and people start to show their true colors–like one fan who was offered the privilege of attending the Star Trek Day celebrations in person. Long story short, at one point during the event, while Wilson Cruz was on stage, someone in the audience yield out a homophobic slur. According to reports, no one did anything about it. The guest was not removed nor have they been identified (yet). With incredible grace and patience, Wilson continued on and later took to Twitter to address the matter. https://twitter.com/wcruz73/status/1436333680880934927 Although he may not have wanted to draw so much attention to the matter, we want to take a moment to remind you–our listeners–that tolerance for the bigoted has its limits. When you see something, say something. Learn ways on how to be the best ally you can be for people who are marginalized on a daily basis. If you're on social media and someone goes on a hate-filled rant, step up. It's the inaction of those with the means to stand up to injustices that empower those who want to watch the world burn. [If you don't think this belongs in Trek, then there's the airlock. Help yourself.–Ed.] Image: ViacomCBS, via StarTrek.com IP Theft, the Sincerest Form of Flattery By Cat Hough On Monday, we were treated to the big uniform reveal by General Jay Raymond, Chief of Space Operations for Space Force who tweeted, "Every winning team needs a uniform!.I'm excited to share the new look with you today." And to no one's surprise, the Twitterverse immediately noticed some striking similarities to some other uniforms that we are quite familiar with. They were described by one person as "a blend of the Star Trek Enterprise dress uniform, but with the Mirror Universe diagonal." https://twitter.com/SpaceForceCSO/status/1440323962697752590 [I am voluntarily putting this into my own shownotes for your edification, dear listener. You owe me.–Ed.] Josh Weinstein, a veteran writer for The Simpsons and Futurama, said the uniform reminded him of the ridiculously tight outfits worn by Zapp Brannigan; Movies in Focus hopped on the satirical bandwagon with the image of an Imperial Star Destroyer officer from the original Star Wars trilogy. "These new Space Force uniforms are looking great," jokes the caption. Quick News Roundup Here are a few headlines that we didn't discuss but might interest you. Reuben Klamer, the designer of the original Starfleet phaser rifle for the original series of Star Trek, passed away at the age of 99, according to the Toy Association. Klamer also designed props for other shows, including a gun for the hit 1960s series The Man From U.N.C.L.E. https://youtu.be/oWGNDoXG9R8 STAR TREK GAMING NEWS Edited by Thomas Reynolds PSA: She Canna Take Any More, Cap'ns! By Thomas Reynolds To every thing there is a season–and in Cryptic's opinion, the season for Windows 7 is long past. Starting February 15, 2022, anyone still using the 10-year-old OS (seriously, not even Microsoft supports it anymore) won't be able to patch or log into STO and Neverwinter. Only Windows 8 and 10 (with the superior 64-bit intellect) will have a home on the final frontier. DirectX 10 support is also getting ejected like a spent warp core on February 15th, with both games requiring Feature Level 11 or higher. That means your computer needs to have one of the following video card chipsets to play: NVidia GeForce GTX 400 or better ATI/AMD Radeon HD 5000 or better Intel HD Graphics 4000 or better Given all the fun and excitement of buying graphics cards these days, if your current card isn't up to the task...well, godspeed. [Pictured: my rig next February.–Ed.] Image: ViacomCBS, via KVNF Public Radio. Aux2Bat Gets Boimed Out By Thomas Reynolds The aqueduct, the magnetic compass, the Aux2Bat. All of these simple technologies have withstood the test of time, but the last may be the most miraculous. Needing only three Technician doffs and one boff ability at minimum, the Aux2Bat ship build is easy to assemble, trivial to fly, and still keeps your bridge officers ready for whatever space wizardry you demand of them. Sure, it hasn't been the meta in a sehlat's age, but you know what? Aux2Bat does the job, it does it pretty well, and that's pretty much all we ask...until now. Ever drop a Gravity Well, and notice your Tyken's Rift is now off-limits for 15 seconds? That's the Shared Category Cooldown kicking in, forcing you to pace yourself rather than let everything rip at once. When Cryptic first released the Boimler Effect trait, it provided a 2.5% percent chance of resetting every bridge officer ability to its Shared Category Cooldown, whenever you used a non-specialist boff ability. Great in theory, but one-in-forty odds just aren't worth a 200 Lobi investment. Yeah, that's was also our reaction. Image: ViacomCBS, via TrekZone.de So Cryptic did a little tweaking, like you do, and made it a 17.5% percent proc chance instead. As STO streamer @AugmentedDG declared on Twitter, “Boimler Effect is now as good as Aux2Bat...for cooldown reduction.” Bold words, to be sure, but there's also a fairly convincing clip of him keeping eight of his escort's twelve boff abilities concurrently running like an overambitious plate spinner. Trek out the tweet, scrape together that Lobi, and give your boffs more buffer time than they can handle. https://twitter.com/AugmentedDG/status/1438707179268284425 Is there in Screen Accuracy No Beauty? By Thomas Reynolds One of Trek cosplay's hallmarks is its hair-splitting fidelity to what's seen on screen, even when the creators themselves don't quite pull it off. Combine that tendency with STO's promise of personal immersion, and it's no surprise that some players want their captain's threads to look “correct.” To help make that a little easier, Cryptic released official in-game color guides for both the newly-available Lower Decks Starfleet jacket, and their original Khitomer uniform creation. However, rapturous Space Barbie enthusiasts should make sure they're using the second released Khitomer guide, as the first one had incorrect pant color codes. https://twitter.com/trekonlinegame/status/1439020385572245509 The Sally Ride, the Ross, and You By Shane Hoover If you were a fan of the Star Trek Adventures web series “Shield of Tomorrow” or “Clear Skies”, you're already familiar with the dangers and wonders of the Shackleton Expanse. If you weren't, then be prepared for deadly spatial phenomena, ancient alien technologies, first contact with new species and lots of boldly going. It's all there in Modiphius Entertainment's newest STA sourcebook, the Shackleton Expanse Campaign Guide. The new sourcebook is available for preorder at $60 now and is expected to ship in December 2021. This is your tabletop gaming crew's chance to follow in the warp trails of the U.S.S. Sally Ride and the U.S.S. Ross. Adventure into a nearly uncharted region of space beyond Federation, Klingon and Romulan borders. Image: Modiphius Entertainment. The new material includes five new playable alien species for STA including Orions. It also includes NPCs from Starbase 364 and around the Expanse, as well as stats for “hero” and NPC vessels. This sourcebook does require a copy of the Star Trek Adventures core rulebook, which is provided in PDF form with your order. The Ar-mod-a Returns By Thomas Reynolds Maybe 2000 feels like a long time ago to you, maybe it doesn't. Either way, the Star Trek: Armada and Armada II RTS games that came out then still hold a place in certain PC players' hearts. So much, in fact, that the Stellar Parallax modding group has finally released what Activision would not: Star Trek: Armada III. Starting as a one-person passion project back in 2012, Armada III is a full-conversion mod for 2012's Sins of a Solar Empire: Rebellion. Stellar Parallax's devoted faithful can now command the Federation, Klingons, Romulans, Borg, or Cardassian Union at the beginning of the Dominion War. See, Kurtzman? You can have more than one kind of ship in a fleet. Image: Stellar Parallax. But really, how much demand is there for a nine-year-old game mod, following up on a twenty-year-old series? After its September 10th release, Armada III is the 51st most-popular mod on the ModDB site, out of over 46,000 entries across hundreds of games–so we'd say “a lot.” [Update: #21 as of publication. Damn.–Ed.] Quick Star Trek Gaming News Roundup A few weeks back we mentioned that the mobile game Star Trek Fleet Command was beta testing a desktop client for Windows. Well, they're out of beta and it's now available for download, with special perks being offered when you log in via desktop! Game maker WizKids announced a new combo-building game titled “Star Trek Missions” –according to their announcement, “your goal is to assemble the highest-scoring combos possible by drawing cards from the Galaxy deck, the Mission deck, or the discard area.” It'll be available February 2022, but you can pre-order now.
Combine yield monitors appear to be across the board as harvest pressure and Russian rumors of rationing quotas on exports influenced the trade. For the week, December wheat added 15 cents while the nearby corn contract lost a penny. Harvest weather looked good as combines gobbled up acres while still looking for a fully reopened gulf to ship their product. The November soybean contract weakened 1 cent. December meal shed $3.20 per ton. December cotton strengthened $3.66 per hundredweight. Over in the dairy parlor, October Class III milk futures improved 16 cents.
Analizamos con un detalle absoluto y al más bajo nivel todos los productos presentados por Apple en septiembre de 2021. Llegaron los iPhone 13 mini, 13, 13 Pro y 13 Pro Max. Llegó (o casi) el Apple Watch series 7 como una pequeña puesta a punto y no carente de polémica y confusión. Y llegaron sin esperarlos un nuevo iPad de educación, novena generación ya, y un nuevo y rediseñado iPad mini de sexta generación, sin duda lo más destacado del evento. Con ello: ProMotion en los iPhone implementado de una forma muy inteligente, modo cinemático para grabar con profundidad de campo apoyado por la IA del dispositivo, un nuevo chip A15 Bionic y mucho más. Como siempre, mucha información y análisis necesario para entender y comprender todo en su contexto… preparados para un nuevo mega análisis. Descubre nuestro canal de Twitch en: twitch.tv/applecoding. Descubre nuestras ofertas para oyentes: "Programación asíncrona con Combine" https://www.udemy.com/course/combineswift/?couponCode=LANZAMIENTO en Udemy por $26,24/26,24€. "Concurrencia en iOS con Swift" https://www.udemy.com/course/concurrencia-swift/?couponCode=APPLECODING0621 en Udemy por $20,99/20,99€. "Swift de lado servidor con Vapor" https://www.udemy.com/course/swift-vapor/?couponCode=APPLECODING0621 en Udemy por $69,99/69,99€. "Desarrollo Seguro en iOS con Swift" https://www.udemy.com/course/desarrollo-seguro-ios-swift/?couponCode=APPLECODING0621 en Udemy por $124,99/124,99€. "Aprendiendo Swift 5.4" https://www.udemy.com/course/comenzando-con-swift/?couponCode=APPLECODING0621 en Udemy por $74,99/74,99€. Apple Coding Academy https://acoding.academy Suscríbete a Apple Coding en nuestro Patreon https://patreon.com/applecoding. Canal de Telegram de Swift. Acceso al canal t.me/desarrollandoconswift. --------------- Consigue las camisetas oficiales de Apple Coding con los logos de Swift y Apple Coding. Logo Apple Coding (negra, logo blanco) https://teespring.com/applecoding-logo-w Logo Swift (negra, logo blanco) https://teespring.com/apple-coding Logo Swift (blanco, logo color original Swift) https://teespring.com/applecoding-swift-logo-o Logo Apple Coding (blanco, logo negro) https://teespring.com/applecoding-logo-b --------------- Tema musical: "Final Frontier", compuesto por Thomas Bergensen. Usado con permisos de fair use. Escúchalo en Apple Music https://itunes.apple.com/es/album/final-frontier/914202953?i=914203055 o Spotify https://open.spotify.com/track/1On5yF6WvujqjSTGUMpQjy.
Beneath the Surface, We Rise for Episode 79!Finally back at it. Awaiting a new computer for the BTS compound. In the meantime KNOXZ was able to cook up this epic set from his latest show in St. Petersburg. A curated mix specially crafted for the true dnb head. Old to new, and raw to anthem; make no mistake this is the skill of a veteran. Combine all the segments and be sure to get your mood off in the right direction. Bless up #allkru !Fighting Fire Charity LP (Donate for the Free LP including Transforma – Blood Red Sky):https://www.playitforward.com/projects/154Donation for Optiv (Edwards Legacy for his boys):https://www.facebook.com/donate/821769254914181/Listen to Best Drum and Bass Podcast – Beneath the Surface Ep. 79 on these platforms: Subscribe to the podcast on iTunes: http://bit.ly/bestdnbGoogle Play – http://bit.ly/bdnb-gplay iHeartRadio – http://bit.ly/bdnb-ihrTunein – http://bit.ly/bdnb-tunein Stitcher – http://bit.ly/bdnb-stitcherEp. 79 Tracklist:*Spor / Beam Cannon [Anachronic]*Bullet Proof / Deadman [Perspective PR007 2001]*Dropset X KNOXZ / Listen [Abducted LTD]*Music separate from mix.Follow KNOXZ: www.facebook.com/KNOXZMUSICwww.soundcloud.com/KNOXZ See acast.com/privacy for privacy and opt-out information.
Hi Friend! In today's Quick Tip Tuesday episode, I answer Evelyn's question, "How do I combine 2 unrelated passions into one cohesive brand?!" Like many of us, Evelyn is multi-passionate and truly has two business focuses. Her two ideas don't have much in common... which poses a problem. If we are to build a micro-niche business, how can we blend our many ideas and loves into just 'one thing'? Is it possible for Evelyn? Find out. If you want to be featured on a Quick Tip Tuesday episode, head to stefaniegass.com, scroll all the way down on the homepage and leave Stef a quick Speakpipe message! Grab a notebook and pen, this one is gold. Xo, Stef P.S. 48-HOUR FLASH SALE IS HAPPENING RIGHT NOW! SAVE 20% OFF ANY STEFANIE GASS COURSE! THE STEFANIE GASS SCHOOL HAS BEEN REVAMPED AND IS READY FOR YOU! Dig into Clarify your Calling 2.0, Podcast Pro University 2.0, or Course Crafter 2.0! Use the code: UPGRADE at checkout. Hurry, this offer ends 9/22/21 at 11AM MST.
Our topic on this episode of the Ready for Retirement podcast is about combining retirement planning with legacy planning.Questions answered: How do I combine retirement planning goals with my legacy planning goals? What are the best strategies when it comes to exploring retirement planning and legacy planning together? What is the best approach for my individual situation? Are you ready to start focusing on the things that truly matter when it comes to your financial future?We're on YouTube! Check us out here for more content to help you create a secure retirement: YouTube - Root Financial PartnersLET'S CONNECT!FacebookLinkedInWebsiteENJOY THE SHOW?Don't miss an episode, subscribe via Apple Podcasts, Stitcher, Spotify, or Google PlayHave a question you want answered on a future episode? Submit it here
Interviews With The Hunting Masters - Big game Hunting podcast
Lessons Learned – Confidence and Optimism Equal Patience with Jeremy Houston Show Notes: Ever since I started this series on Lessons Learned, one topic has come up again and again: patience. My guest today, though, connects some dots in a new way. Jeremy says that you have to have confidence in order to be patient. He and I have both learned the hard way that when you lose faith in your abilities as a hunter, you give up early. And when you give up early, you miss out on great opportunities. I like to call these “mental give-ups,” and it's important to ignore that little voice in your head that tells you to just call it quits. That, Jeremy believes, is where optimism comes in. If you know the area and the animals in it, and you have a little optimism that something good will come your way, you're much more likely to ignore the mental give-ups and stick it out. Jeremy and I also talk about ways to keep on hunting and improving our skills, even outside of the season. For me, that means bowhunting coyotes. For Jeremy, that means wildlife photography. He explains how “hunting with a camera” allows him to be out in the field year-round. Plus, since you have to get in close to the animals to get a good picture, Jeremy gets to practice his stalking skills while also studying the animals in the wild. What's Inside: You have to have confidence in order to be patient. Ignore the “mental give-up”. How to build confidence in your equipment. Be in “hunting mode” from the moment you leave the truck. How to “hunt with a camera” year round. Mentioned in this episode: Phoenix Shooting Bags save 20% with code johnstallone Days In The Wild Muley photos on Instagram Short Description: You've heard me talk with my guests before about how important patience is when it comes to big game hunting. My guest today, Jeremy Houston, explains how patience is tied directly to confidence, both in yourself and your equipment. Combine that with a little optimism, and you'll be set up for success. Tags: mule deer hunting, big game hunting, hunting tips, hunting guide, big buck hunting, hunting stories, archery, bow hunting, wildlife photography
"Can I combine fasting with other weight loss plans?" asks Margueritte from Facebook. Here with our answer is Shawn Wells, biochemist, dietitian, sports nutritionist, and formulation scientist. According to Shawn, fasting works great with other weight loss plans. Listen to the full episode to learn how fasting can be utilized with other great tools to maximize your weight loss. Take Shawn's free Fasting Quiz to learn your personal fasting type. fastingquiz.com
Complete our Listener Survey to Win a $100 Amazon Gift Card: https://bit.ly/3DjoM6b Debt, Investing, Relationships, Career As heard on this episode: Churchill Mortgage: https://bit.ly/2JcfkGy Sign up for a FREE trial of Ramsey+ TODAY: https://bit.ly/3rZTUAx Tools to get you started: Debt Calculator: https://bit.ly/2Q64HME Insurance Coverage Checkup: https://bit.ly/3sXwUn5 Complete Guide to Budgeting: https://bit.ly/3utmVXi Check out more Ramsey Network podcasts: https://bit.ly/3fHhbVE
© 2020-2021 Ivy Podcast Discovery LLC
