POPULARITY
6 episodes with unsuccessful
4 episodes with unsuccessful
4 episodes with unsuccessful
4 episodes with unsuccessful
4 episodes with unsuccessful
3 episodes with unsuccessful
4 episodes with unsuccessful
2 episodes with unsuccessful
2 episodes with unsuccessful
BONUS: Swimming in Tech Debt — Practical Techniques to Keep Your Team from Drowning in Its Codebase In this fascinating conversation, veteran software engineer and author Lou Franco shares hard-won lessons from decades at startups, Trello, and Atlassian. We explore his book "Swimming in Tech Debt," diving deep into the 8 Questions framework for evaluating tech debt decisions, personal practices that compound over time, team-level strategies for systematic improvement, and leadership approaches that balance velocity with sustainability. Lou reveals why tech debt is often the result of success, how to navigate the spectrum between ignoring debt and rewriting too much, and practical techniques individuals, teams, and leaders can use starting today. The Exit Interview That Changed Everything "We didn't go slower by paying tech debt. We went actually faster, because we were constantly in that code, and now we didn't have to run into problems." — Lou Franco Lou's understanding of tech debt crystallized during an exit interview at Atalasoft, a small startup where he'd spent years. An engineer leaving the company confronted him: "You guys don't care about tech debt." Lou had been focused on shipping features, believing that paying tech debt would slow them down. But this engineer told a different story — when they finally fixed their terrible build and installation system, they actually sped up. They were constantly touching that code, and removing the friction made everything easier. This moment revealed a fundamental truth: tech debt isn't just about code quality or engineering pride. It's about velocity, momentum, and the ability to move fast sustainably. Lou carried this lesson through his career at Trello (where he learned the dangers of rewriting too much) and Atlassian (where he saw enterprise-scale tech debt management). These experiences became the foundation for "Swimming in Tech Debt." Tech Debt Is the Result of Success "Tech debt is often the result of success. Unsuccessful projects don't have tech debt." — Lou Franco This reframes the entire conversation about tech debt. Failed products don't accumulate debt — they disappear before it matters. Tech debt emerges when your code survives long enough to outlive its original assumptions, when your user base grows beyond initial expectations, when your team scales faster than your architecture anticipated. At Atalasoft, they built for 10 users and got 100. At Trello, mobile usage exploded beyond their web-first assumptions. Success creates tech debt by changing the context in which code operates. This means tech debt conversations should happen at different intensities depending on where you are in the product lifecycle. Early startups pursuing product-market fit should minimize tech debt investments — move fast, learn, potentially throw away the code. Growth-stage companies need balanced approaches. Mature products benefit significantly from tech debt investments because operational efficiency compounds over years. Understanding this lifecycle perspective helps teams make appropriate decisions rather than applying one-size-fits-all rules. The 8 Questions Framework for Tech Debt Decisions "Those 8 questions guide you to what you should do. If it's risky, has regressions, and you don't even know if it's gonna work, this is when you're gonna do a project spike." — Lou Franco Lou introduces a systematic framework for evaluating whether to pay tech debt, inspired by Bob Moesta's push-pull forces from product management. The 8 questions create a complete picture: Visibility — Will people outside the team understand what we're doing? Alignment — Does this match our engineering values and target architecture? Resistance — How hard is this code to work with right now? Volatility — How often do we touch this code? Regression Risk — What's the chance we'll introduce new problems? Project Size — How big is this to fix? Estimate Risk — How uncertain are we about the effort required? Outcome Uncertainty — How confident are we the fix will actually improve things? High volatility and high resistance with low regression risk? Pay the debt now. High regression risk with no tests? Write tests first, then reassess. Uncertain outcomes on a big project? Do a spike or proof of concept. The framework prevents both extremes — ignoring costly debt and undertaking risky rewrites without proper preparation. Personal Practices That Compound Daily "When I sit down at my desk, the first thing I do is I pay a little tech debt. I'm looking at code, I'm about to change it, do I even understand it? Am I having some kind of resistance to it? Put in a little helpful comment, maybe a little refactoring." — Lou Franco Lou shares personal habits that create compounding improvements over time. Start each coding session by paying a small amount of tech debt in the area you're about to work — add a clarifying comment, extract a confusing variable, improve a function name. This warms you up, reduces friction for your actual work, and leaves the code slightly better than you found it. The clean-as-you-go philosophy means tech debt never accumulates faster than you can manage it. But Lou's most powerful practice comes at the end of each session: mutation testing by hand. Before finishing for the day, deliberately break something — change a plus to minus, a less-than to less-than-or-equal. See if tests catch it. Often they don't, revealing gaps in test coverage. The key insight: don't fix it immediately. Leave that failing test as the bridge to tomorrow's coding session. It connects today's momentum to tomorrow's work, ensuring you always start with context and purpose rather than cold-starting each day. Mutation Testing: Breaking Things on Purpose "Before I'm done working on a coding session, I break something on purpose. I'll change a plus to a minus, a less than to a less than equals, and see if tests break. A lot of times tests don't break. Now you've found a problem in your test." — Lou Franco Manual mutation testing — deliberately breaking code to verify tests catch the break — reveals a critical gap in most test suites. You can have 100% code coverage and still have untested behavior. A line of code that's executed during tests isn't necessarily tested — the test might not actually verify what that line does. By changing operators, flipping booleans, or altering constants, you discover whether your tests protect against actual logic errors or just exercise code paths. Lou recommends doing this manually as part of your daily practice, but automated tools exist for systematic discovery: Stryker (for JavaScript, C#, Scala) and MutMut (for Python) can mutate your entire codebase and report which mutations survive uncaught. This isn't just about test quality — it's about understanding what your code actually does and building confidence that changes won't introduce subtle bugs. Team-Level Practices: Budgets, Backlogs, and Target Architecture "Create a target architecture document — where would we be if we started over today? Every PR is an opportunity to move slightly toward that target." — Lou Franco At the team level, Lou advocates for three interconnected practices. First, create a target architecture document that describes where you'd be if starting fresh today — not a detailed design, but architectural patterns, technology choices, and structural principles that represent current best practices. This isn't a rewrite plan; it's a North Star. Every pull request becomes an opportunity to move incrementally toward that target when touching relevant code. Second, establish a budget split between PM-led feature work and engineering-led tech debt work — perhaps 80/20 or whatever ratio fits your product lifecycle stage. This creates predictable capacity for tech debt without requiring constant negotiation. Third, hold quarterly tech debt backlog meetings separate from sprint planning. Treat this backlog like PMs treat product discovery — explore options, estimate impacts, prioritize based on the 8 Questions framework. Some items fit in sprints; others require dedicated engineers for a quarter or two. This systematic approach prevents tech debt from being perpetually deprioritized while avoiding the opposite extreme of engineers disappearing into six-month "improvement" projects with no visible progress. The Atlassian Five-Alarm Fire "The Atlassian CTO's 'five-alarm fire' — stopping all feature development to focus on reliability. I reduced sync errors by 75% during that initiative." — Lou Franco Lou shares a powerful example of leadership-driven tech debt management at scale. The Atlassian CTO called a "five-alarm fire" — halting all feature development across the company to focus exclusively on reliability and tech debt. This wasn't panic; it was strategic recognition that accumulated debt threatened the business. Lou worked on reducing sync errors, achieving a 75% reduction during this focused period. The initiative demonstrated several leadership principles: willingness to make hard calls that stop revenue-generating feature work, clear communication of why reliability matters strategically, trust that teams will use the time wisely, and commitment to see it through despite pressure to resume features. This level of intervention is rare and shouldn't be frequent, but it shows what's possible when leadership truly prioritizes tech debt. More commonly, leaders should express product lifecycle constraints (startup urgency vs. mature product stability), give teams autonomy to find appropriate projects within those constraints, and require accountability through visible metrics and dashboards that show progress. The Rewrite Trap: Why Big Rewrites Usually Fail "A system that took 10 years to write has implicit knowledge that can't be replicated in 6 months. I'm mostly gonna advocate for piecemeal migrations along the way, reducing the size of the problem over time." — Lou Franco Lou lived through Trello's iOS navigation rewrite — a classic example of throwing away working code to start fresh, only to discover all the edge cases, implicit behaviors, and user expectations baked into the "old" system. A codebase that evolved over several years contains implicit knowledge — user workflows, edge case handling, performance optimizations, and subtle behaviors that users rely on even if they never explicitly requested them. Attempting to rewrite this in six months inevitably misses critical details. Lou strongly advocates for piecemeal migrations instead. The Trello "Decaffeinate Project" exemplifies this approach — migrating from CoffeeScript to TypeScript incrementally, with public dashboards showing the percentage remaining, interoperable technologies allowing gradual transition, and the ability to pause or reverse if needed. Keep both systems running in parallel during migrations. Use runtime observability to verify new code behaves identically to old code. Reduce the problem size steadily over months rather than attempting big-bang replacements. The only exception: sometimes keeping parallel systems requires scaffolding that creates its own complexity, so evaluate whether piecemeal migration is actually simpler or if you're better off living with the current system. Making Tech Debt Visible Through Dashboards "Put up a dashboard, showing it happen. Make invisible internal improvements visible through metrics engineering leadership understands." — Lou Franco One of tech debt's biggest challenges is invisibility — non-technical stakeholders can't see the improvement from refactoring or test coverage. Lou learned to make tech debt work visible through dashboards and metrics. The Decaffeinate Project tracked percentage of CoffeeScript files remaining, providing a clear progress indicator anyone could understand. When reducing sync errors, Lou created dashboards showing error rates declining over time. These visualizations serve multiple purposes: they demonstrate value to leadership, create accountability for engineering teams, build momentum as progress becomes visible, and help teams celebrate wins that would otherwise go unnoticed. The key is choosing metrics that matter to the business — error rates, page load times, deployment frequency, mean time to recovery — rather than pure code quality metrics like cyclomatic complexity that don't translate outside engineering. Connect tech debt work to customer experience, reliability, or developer productivity in ways leadership can see and value. Onboarding as a Tech Debt Opportunity "Unit testing is a really great way to learn a system. It's like an executable specification that's helping you prove that you understand the system." — Lou Franco Lou identifies onboarding as an underutilized opportunity for tech debt reduction. When new engineers join, they need to learn the codebase. Rather than just reading code or shadowing, Lou suggests having them write unit tests in areas they're learning. This serves dual purposes: tests are executable specifications that prove understanding of system behavior, and they create safety nets in areas that likely lack coverage (otherwise, why would new engineers be confused by the code?). The new engineer gets hands-on learning, the team gets better test coverage, and everyone wins. This practice also surfaces confusing code — if new engineers struggle to understand what to test, that's a signal the code needs clarifying comments, better naming, or refactoring. Make onboarding a systematic tech debt reduction opportunity rather than passive knowledge transfer. Leadership's Role: Constraints, Autonomy, and Accountability "Leadership needs to express the constraints. Tell the team what you're feeling about tech debt at a high level, and what you think generally is the appropriate amount of time to be spent on it. Then give them autonomy." — Lou Franco Lou distills leadership's role in tech debt management to three elements. First, express constraints — communicate where you believe the product is in its lifecycle (early startup, rapid growth, mature cash cow) and what that means for tech debt tolerance. Are we pursuing product-market fit where code might be thrown away? Are we scaling a proven product where reliability matters? Are we maintaining a stable system where operational efficiency pays dividends? These constraints help teams make appropriate trade-offs. Second, give autonomy — once constraints are clear, trust teams to identify specific tech debt projects that fit those constraints. Engineers understand the codebase's pain points better than leaders do. Third, require accountability — teams must make their work visible through dashboards, metrics, and regular updates. Autonomy without accountability becomes invisible engineering projects that might not deliver value. Accountability without autonomy becomes micromanagement that wastes engineering judgment. The balance creates space for teams to make smart decisions while keeping leadership informed and confident in the investment. AI and the Future of Tech Debt "I really do AI-assisted software engineering. And by that, I mean I 100% review every single line of that code. I write the tests, and all the code is as I would have written it, it's just a lot faster. Developers are still responsible for it. Read the code." — Lou Franco Lou has a chapter about AI in his book, addressing the elephant in the room: will AI-generated code create massive tech debt? His answer is nuanced. AI can accelerate development tremendously if used correctly — Lou uses it extensively but reviews every single line, writes all tests himself, and ensures the code matches what he would have written manually. The problem emerges with "vibe coders" — non-developers using AI to generate code they don't understand, creating unmaintainable messes that become someone else's problem. Developers remain responsible for all code, regardless of how it's generated. This means you must read and understand AI-generated code, not blindly accept it. Lou also raises supply chain security concerns — dependencies can contain malicious code, and AI might introduce vulnerabilities developers miss. His recommendation: stay six months behind on dependency updates, let others discover the problems first, and consider separate sandboxed development machines to limit security exposure. AI is a powerful tool, but it doesn't eliminate the need for engineering judgment, testing discipline, or code review practices. The Style Guide Beyond Formatting "Have a style guide that goes beyond formatting to include target architecture. This is the kind of code we want to write going forward." — Lou Franco Lou advocates for style guides that extend beyond tabs-versus-spaces formatting rules to include architectural guidance. Document patterns you want to move toward: how should components be structured, what state management approaches do we prefer, how should we handle errors, what testing patterns should we follow? This creates a shared understanding of the target architecture without requiring a massive design document. When reviewing pull requests, teams can reference the style guide to explain why certain approaches align with where the codebase is headed versus perpetuating old patterns. This makes tech debt conversations less personal and more objective — it's not about criticizing someone's code, it's about aligning with team standards and strategic direction. The style guide becomes a living document that evolves as the team learns and technology changes, capturing collective wisdom about what good code looks like in your specific context. Recommended Resources Some of the resources mentioned in this episode include: Steve Blank's Four Steps To Epiphany The podcast episode with Bernie Maloney where we discuss the critical difference between "enterprise" and "startup". And Geoffrey Moore's Crossing the Chasm, and Dealing with Darwin. About Lou Franco Lou Franco is a veteran software engineer and author of Swimming in Tech Debt. With decades of experience at startups, as well as Trello, and Atlassian, he's seen both sides of debt—as coder and leader. Today, he advises teams on engineering practices, helping them turn messy codebases into momentum. You can link with Lou Franco on LinkedIn and learn more at LouFranco.com.
LEAVE A REVIEW if you liked this episode!!Let's Connect On Social Media!youtube.com/anthonyvicinotwitter.com/anthonyvicinoinstagram.com/theanthonyvicinohttps://anthonyvicino.comJoin an exclusive community of peak performers at Beyond the Apex University learning how to build a business, invest in real estate, and develop hyperfocus.www.beyondtheapex.com
Motorists are being advised to steer clear of a rogue deer spotted in a residential part of Ennis in recent days. There have been several sightings of the animal, who it's understood originally lived in the Lee's Road area, in Hermitage and Cloughleigh in the last two weeks. Unsuccessful attempts have been made by Clare's County Dog Warden along with members of An Garda Síochána and the National Parks and Wildlife Service to capture the deer and return him to the wild. Frankie Coote says he poses a significant threat to vehicles.
PREVIEW: China's View on North Korea's Unsuccessful Military Involvement in Ukraine Guest: Anatol Lieven Anatol Lieven discusses China's perspective on North Korea and Russia regarding the Ukraine war. North Korea's participation in Ukraine is obvious and well documented, though China neither encouraged nor prevented the involvement. The direct engagement of approximately 10,000 North Korean soldiers fighting in Kursk appears to have been unsuccessful, suffering very heavy casualties before being withdrawn from active operations. 1917 PASCHENDALE
In this episode of The Cardone Zone, Grant Cardone revisits his New York Times best-selling book, The 10X Rule, breaking down one of its most powerful distinctions — the difference between those who take massive action and those who don't. Grant delves into the mindset, habits, and relentless energy that distinguish the successful from the unsuccessful — and how inaction, hesitation, and excuses consistently lead to missed opportunities and stagnation. If you've ever wondered why some people seem to win consistently while others struggle to gain traction, this episode gives you the answers straight from the 10X philosophy that started a movement. Follow us on all social media platforms and visit GrantCardone.com for more tools, training, and strategies to take massive action and multiply your success.
Message Jason on Facebook Follow Jason Cook in Instagram Follow Jason Cook on FB Email Jason Cook here jason@lwcvip.com Testimonials click here Join the Weight Loss Secrets for Women 50+ Community Supplements
No one attends a team offsite wanting it to be a failure, says Daniel. Unsuccessful offsites are perceived as “a bad waste of time.”So what makes an offsite successful–and how can an offsite have a lasting, positive impact on your team or organization?In this episode, Daniel and Peter break down the elements of a successful team offsite and give suggestions for how to make your next one the best yet.Tune in to learn:The value of including all participants in the planning processWhat an offsite is NOT good forImportant ground rules that help guide discussionPlus, some reflections on an insightful quote from Robert Frost, including what it says about delegation and manager wellbeing.Questions, comments, or topic ideas? Drop us an e-mail at podcast@stewartleadership.com.In this episode::50 – Insight of the Week5:23 – Topic: How to Have a Successful Team Offsite9:46 – The Right Preparation17:10 – The Right People20:11 – The Right Facilitator28:43 – The Great Pivot32:43 – Ground Rules37:10 – Lightning RoundResources:Robert Frost Biography, The Poetry FoundationStewart Leadership Insights and Resources:How to Hold a Great Strategic Planning Offsite Meeting6 Reasons Your Next Meeting Should Be an OffsiteWhy Your Offsite Needs an Outside FacilitatorHow Offsites Can Jumpstart Leadership Development5 Ways Leaders Can Better Manage Feeling OverwhelmedThe Manager Crisis: 3 Areas that Need AttentionHow to Delegate Like a ProIf you liked this episode, please share it with a friend or colleague, or, better yet, leave a review to help other listeners find our show, and remember to subscribe so you never miss an episode. For more great content or to learn about how Stewart Leadership can help you grow your ability to lead effectively, please visit stewartleadership.com and follow us on LinkedIn, Instagram, and YouTube.
Understanding politics via President Trump's successful and unsuccessful use of narrative
For review:1. IDF Hits Houthi Camps in Sanaa.2. Indications Point Doha Strike on Hamas Leaders Unsuccessful.3. Qatar will host an emergency Arab-Islamic summit in Doha on Sunday and Monday to discuss the Israeli attack on the Gulf state's capital city that targeted Hamas leaders.4. Prime Minister Benjamin Netanyahu declared on Thursday evening that “there will be no Palestinian state,” as he signed an agreement to push ahead with the controversial E1 settlement expansion plan that will cut across West Bank land.5. IDF expanding operations in preparation of Gaza City campaign. In total, five IDF divisions are set to participate in the Gaza City offensive.6. Iranian Foreign Minister Abbas Araghchi said Thursday that enriched nuclear material remained “under the rubble” of facilities damaged during the recent war with Israel.7. The US Department of Defense announced it would provide the Lebanese Armed Forces (LAF) a security package worth $14.2 million to help in its new mission to disarm Hezbollah.The aid package includes shaped and demolition charges, detonating cords, electric and non-electric caps, fuse igniter generators and transportation.8. NATO allies shot down three Russian drones that illegally entered Polish air space on Wednesday. A senior Army official told reporters on Wednesday that eight other Russian drones crashed after entering Poland. 9. The House passed its version of the fiscal 2026 defense policy bill today.The 231-196 vote was split mostly down party lines.
In this episode, I ask you the question, "will the actions you took today get you closer to your goal?" I then take you through the choices we make at hundreds of points during each day and how we make decisions and choose whether we head towards success or not, using examples from my own life. Find my links for social media and a couple of freebies for direct sales reps and network marketers here https://thesuccesslounge.podia.com/freebies And grab yourself a copy of my free download, 100 Ways to Grow Your Customer Base here https://annagreen.kartra.com/page/web-100ways Join the Mission 2K Bootcamp starting 15th September 2025 here https://annagreen.kartra.com/page/mission2k Find out about the RISE and IGNITE Masterminds starting 1st October 2025 here: RISE - https://annagreen.kartra.com/page/rise IGNITE - https://annagreen.kartra.com/page/ignite Find me on socials here: Facebook www.facebook.com/annagreenmentor My Facebook Community www.facebook.com/groups/directsellingsuccesscommunity Instagram www.instagram.com/directsellingsuccess TikTok www.tiktok.com/@directsellingsuccess
Amanda and her husband had tried everything but IVF on their road to try to conceive. After failed IUIs and no known diagnosis beyond unexplained infertility, they felt stuck and frustrated. Amanda had had cycle issues for years, but had always used birth control to suppress symptoms. Now, it seemed like they could be contributing to their infertility. A friend reached out with a different option and a new perspective: restorative reproductive healthcare. The rest is history. Hear Amanda's story of natural conception and a healthy pregnancy after infertility and failed assisted reproductive technology treatments!NOTE: Appropriate for all audiences but does discuss assisted reproductive technology.GUEST BIO: Amanda, a speech pathologist, has been married to her husband for 4 years and began working with Woven Natural Fertility Care in March 2025 after unsuccessfully working with an assisted reproductive technology clinic.SHOW LINKS:Ep. 163: Healthy pregnancy in 3 cycles after being told IVF was her only hope, with LorenEp. 155: "How I got pregnant when IUIs didn't work" -- Braelyn's storyEp. 147: Emotional healing after IVF, with Shiloh IVF MinistryEp. 122: IVF Alternatives for friendsEp. 96: Theological Considerations with IVFJoin us on Substack*Get started like Amanda: Register for an Intro Session today*Send us a textSupport the showOther great ways to connect with Woven Natural Fertility Care: Learn the Creighton Model System with us! Register here! Get our monthly newsletter: Get the updates! Chat about issues of fertility + faith: Substack Follow us on Instagram: @wovenfertility Watch our episodes on YouTube: @wovenfertility Love the content? The biggest gift you could give is to click a 5 star review and write why it was so meaningful! This podcast is provided for educational and informational purposes only and does not constitute providing medical advice or professional services. The information provided should not be used for diagnosing or treating a health problem or disease, and those seeking personal medical advice should consult with a licensed physician. Always seek the advice of your doctor or other qualified health provider regarding a medical condition. If you think you may have a medical emergency, call 911 or go to the nearest emergency room immediately. Neither Woven nor its staff, nor any contributor to this podcast, makes any represe...
0:00–14:25The sections on “woman” are not distinct from the rest of the book; §68 “Will and Willingness” §64 “Skeptics” superficiality of existence ; the feminine operation and the body marked by the feminine operation.14:30–36:20John's writing project ; maybe these aphorisms are more interesting now? §74 “The Unsuccessful” and §75 “The Third Sex” ; Kaufman can't handle it anymore ; §80 “Art and Nature” the fantasy of good speech and the self-controlled cogito ; are we talking about Platonic ideals when we talk about woman as a “ship at a distance”? ; the prospect of metaphysics ; coordinating these aphorisms “on woman” with the rest of the book ; §59 “We Artists,” woman, god, and property.36:20–60:00The multiplicity of misogyny ; Nietzsche is a strange pathway by which to engage feminism; Beyond surfaces and depths (or between them); why gender is impossible to think and why that's important; politics vs. metaphysics; deconstructive feminism; the political conditions for thinking; the #FigureItOut movement; exceptions and institutions; honoring Sinèad.
A popular devotional uses Joshua 1:8 and the story of Horatio Spafford to define success. But what if the Scripture is misused, the history is incomplete, and the message is deeply flawed?
A popular devotional uses Joshua 1:8 and the story of Horatio Spafford to define success. But what if the Scripture is misused, the history is incomplete, and the message is deeply flawed?
The Rebbe reassures the writer that feelings of failure are unfounded, and that success comes through trust in Hashem and commitment to Torah and mitzvot. He advises continuing in the work that feels most manageable, checking tefillin, and saying Tehillim daily after Shacharit. https://www.torahrecordings.com/rebbe/igroskodesh/015/012/5660
On this week's episode of “Victor Davis Hanson: In His Own Words,” Hanson breaks down the party's post-2024 election autopsy and explains why they're doomed to fail if they continue on their trajectory. “ After the defeat of Kamala Harris in November 2024, the Democrats decided recently to run an autopsy, a discovery, so to speak, of why they lost that election. These autopsies are not uncommon for the losing political party, but they only tend to work if you're honest and you try to analyze every considerable factor or criterion without censorship or without fear. “ They didn't have issues and policies that reflected their core values, but would also appeal to the middle class. … They don't want to talk about the middle class because their policies—open borders, The Green New Deal, Critical Race Theory, Critical Legal Theory, defund the police—all that have to be rejected because they're anathema to the middle class. They won't do it.”
This is the audio from an Instagram Live I did today (follow us on IG @healing.embodied). I'm diving deep into the real reason you overthink (it's not what you think
This show has been flagged as Explicit by the host. Overview Several years ago I wrote a Bash script to perform a task I need to perform almost every day - find the newest file in a series of files. At this point I was running a camera on a Raspberry Pi which was attached to a window and viewed my back garden. I was taking a picture every 15 minutes, giving them names containing the date and time, and storing them in a directory. It was useful to be able to display the latest picture. Since then, I have found that searching for newest files useful in many contexts: Find the image generated by my random recipe chooser, put in the clipboard and send it to the Telegram channel for my family. Generate a weather report from wttr.in and send it to Matrix. Find the screenshot I just made and put it in the clipboard. Of course, I could just use the same name when writing these various files, rather than accumulating several, but I often want to look back through such collections. If I am concerned about such files accumulating in an unwanted way I write cron scripts which run every day and delete the oldest ones. Original script The first iteration of the script was actually written as a Bash function which was loaded at login time. The function is called newest_matching_file and it takes two arguments: A file glob expression to match the file I am looking for. An optional directory to look for the file. If this is omitted, then the current directory will be used. The first version of this function was a bit awkward since it used a for loop to scan the directory, using the glob pattern to find the file. Since Bash glob pattern searches will return the search pattern when they fail, it was necessary to use the nullglob (see references) option to prevent this, turning it on before the search and off afterwards. This technique was replaced later with a pipeline using the find command. Improved Bash script The version using find is what I will explain here. function newest_matching_file { local glob_pattern=${1-} local dir=${2:-$PWD} # Argument number check if [[ $# -eq 0 || $# -gt 2 ]]; then echo 'Usage: newest_matching_file GLOB_PATTERN [DIR]' >&2 return 1 fi # Check the target directory if [[ ! -d $dir ]]; then echo "Unable to find directory $dir" >&2 return 1 fi local newest_file # shellcheck disable=SC2016 newest_file=$(find "$dir" -maxdepth 1 -name "$glob_pattern" \ -type f -printf "%T@ %p\n" | sort | sed -ne '${s/.\+ //;p}') # Use printf instead of echo in case the file name begins with '-' [[ -n $newest_file ]] && printf '%s\n' "$newest_file" return 0 } The function is in the file newest_matching_file_1.sh , and it's loaded ("sourced", or declared) like this: . newest_matching_file_1.sh The '.' is a short-hand version of the command source . I actually have two versions of this function, with the second one using a regular expression, which the find command is able to search with, but I prefer this one. Explanation The first two lines beginning with local define variables local to the function holding the arguments. The first, glob_pattern is expected to contain something like screenshot_2025-04-*.png . The second will hold the directory to be scanned, or if omitted, will be set to the current directory. Next, an if statement checks that there are the right number of arguments, aborting if not. Note that the echo command writes to STDERR (using '>&2' ), the error channel. Another if statement checks that the target directory actually exists, and aborts if not. Another local variable newest_file is defined. It's good practice not to create global variables in functions since they will "leak" into the calling environment. The variable newest_file is set to the result of a command substitution containing a pipeline: The find command searches the target directory. Using -maxdepth 1 limits the search to the chosen directory and does not descend into sub-directories. The search pattern is defined by -name "$glob_pattern" Using -type f limits the search to files The -printf "%T@ %p\n" argument returns the file's last modification time as the number of seconds since the Unix epoch '%T@' . This is a number which is larger if the file is older. This is followed, after a space, by the full path to the file ( '%p' ), and a newline. The matching file names are sorted. Because each is preceded by a numeric time value, they will be sorted in ascending order of age. Finally sed is used to return the last file in the sorted list with the program '${s/.\+ //;p}' : The use of the -n option ensures that only lines which are explicitly printed will be shown. The sed program looks for the last line (using '$' ). When found the leading numeric time is removed with ' s/.\+ //' and the result is printed (with 'p' ). The end result will either be the path to the newest file or nothing (because there was no match). The expression '[[ -n $newest_file ]]' will be true if $newest_file variable is not empty, and if that is the case, the contents of the variable will be printed on STDOUT, otherwise nothing will be printed. Note that the script returns 1 (false) if there is a failure, and 0 (true) if all is well. A null return is regarded as success. Script update While editing the audio for this show I realised that there is a flaw in the Bash function newest_matching_file . This is in the sed script used to process the output from find . The sed commands used in the script delete all characters up to a space, assuming that this is the only space in the last line. However, if the file name itself contains spaces, this will not work because regular expressions in sed are greedy . What is deleted in this case is everything up to and including the last space. I created a directory called tests and added the following files: 'File 1 with spaces.txt' 'File 2 with spaces.txt' 'File 3 with spaces.txt' I then ran the find command as follows: $ find tests -maxdepth 1 -name 'File*' -type f -printf "%T@ %p\n" | sort | sed -ne '${s/.\+ //;p}' spaces.txt I adjusted the sed call to sed -ne '${s/[^ ]\+ //;p}' . This uses the regular expression: s/[^ ]\+ // This now specifies that what it to be removed is every non-space up to and including the first space. The result is: $ find tests -maxdepth 1 -name 'File*' -type f -printf "%T@ %p\n" | sort | sed -ne '${s/[^ ]\+ //;p}' tests/File 3 with spaces.txt This change has been propagated to the copy on GitLab . Usage This function is designed to be used in commands or other scripts. For example, I have an alias defined as follows: alias copy_screenshot="xclip -selection clipboard -t image/png -i \$(newest_matching_file 'Screenshot_*.png' ~/Pictures/Screenshots/)" This uses xclip to load the latest screenshot into the clipboard, so I can paste it into a social media client for example. Perl alternative During the history of this family of scripts I wrote a Perl version. This was originally because the Bash function gave problems when run under the Bourne shell, and I was using pdmenu a lot which internally runs scripts under that shell. #!/usr/bin/env perl use v5.40; use open ':std', ':encoding(UTF-8)'; # Make all IO UTF-8 use Cwd; use File::Find::Rule; # # Script name # ( my $PROG = $0 ) =~ s|.*/||mx; # # Use a regular expression rather than a glob pattern # my $regex = shift; # # Get the directory to search, defaulting to the current one # my $dir = shift // getcwd(); # # Have to have the regular expression # die "Usage: $PROG regex [DIR]\n" unless $regex; # # Collect all the files in the target directory without recursing. Include the # path and let the caller remove it if they want. # my @files = File::Find::Rule->file() ->name(qr/$regex/) ->maxdepth(1) ->in($dir); die "Unsuccessful search\n" unless @files; # # Sort the files by ascending modification time, youngest first # @files = sort {-M($a) -M($b)} @files; # # Report the one which sorted first # say $files[0]; exit; Explanation This is fairly straightforward Perl script, run out of an executable file with a shebang line at the start indicating what is to be used to run it - perl . The preamble defines the Perl version to use, and indicates that UTF-8 (character sets like Unicode) will be acceptable for reading and writing. Two modules are required: Cwd : provides functions for determining the pathname of the current working directory. File::Find::Rule : provides tools for searching the file system (similar to the find command, but with more features). Next the variable $PROG is set to the name under which the script has been invoked. This is useful when giving a brief summary of usage. The first argument is then collected (with shift ) and placed into the variable $regex . The second argument is optional, but if omitted, is set to the current working directory. We see the use of shift again, but if this returns nothing (is undefined), the '//' operator invokes the getcwd() function to get the current working directory. If the $regex variable is not defined, then die is called to terminate the script with an error message. The search itself is invoked using File::Find::Rule and the results are added to the array @files . The multi-line call shows several methods being called in a "chain" to define the rules and invoke the search: file() : sets up a file search name(qr/$regex/) : a rule which applies a regular expression match to each file name, rejecting any that do not match maxdepth(1) : a rule which prevents the search from descending below the top level into sub-directories in($dir) : defines the directory to search (and also begins the search) If the search returns no files (the array is empty), the script ends with an error message. Otherwise the @files array is sorted. This is done by comparing modification times of the files, with the array being reordered such that the "youngest" (newest) file is sorted first. The operator checks if the value of the left operand is greater than the value of the right operand, and if yes then the condition becomes true. This operator is most useful in the Perl sort function. Finally, the newest file is reported. Usage This script can be used in almost the same way as the Bash variant. The difference is that the pattern used to match files is a Perl regular expression. I keep this script in my ~/bin directory, so it can be invoked just by typing its name. I also maintain a symlink called nmf to save typing! The above example, using the Perl version, would be: alias copy_screenshot="xclip -selection clipboard -t image/png -i \$(nmf 'Screenshot_.*\.png' ~/Pictures/Screenshots/)" In regular expressions '.*' means "any character zero or more times". The '.' in '.png' is escaped because we need an actual dot character. Conclusion The approach in both cases is fairly simple. Files matching a pattern are accumulated, in the Bash case including the modification time. The files are sorted by modification time and the one with the lowest time is the answer. The Bash version has to remove the modification time before printing. This algorithm could be written in many ways. I will probably try rewriting it in other languages in the future, to see which one I think is best. References Glob expansion: Wikipedia article on glob patterns HPR shows covering glob expansion: Finishing off the subject of expansion in Bash (part 1) Finishing off the subject of expansion in Bash (part 2) GitLab repository holding these files: hprmisc - Miscellaneous scripts, notes, etc pertaining to HPR episodes which I have contributed Provide feedback on this episode.
Learn the secrets to being unsuccessful from Hebrews 3
FEATURING: (00:10:03) New Business - Fantasy Life i: The Girl Who Steals Time.(00:16:16) Arcade Archives2 AIR COMBAT 22.(00:31:56) Mario Kart World.(00:57:25) Unsuccessful attempt to daisy-chain Switch docks. Hiding your shameful downloads.(01:05:44) Balatro.(01:21:05) Cyberpunk 2077: Phantom Liberty.(01:31:57) Mario Smash Football/Super Mario Strikers on NSO.
We are releasing this episode early, to give you more information about the One Big Beautiful Bill that passed out of the Senate yesterday (as of publishing this episode on July 2). In this update, hear from California rancher and past CCA president Kevin Kester about the positive tax provisions in this bill for ranchers and farmers. Last week, Kevin was invited to the White House for an event highlighting the tax relief the “One Big Beautiful Bill” will provide for ranching and farming families across the country for future generations. Hear about Kevin's experience and the importance of the tax relief in this bill, which includes reducing the Death Tax, as he spoke NCBA's Senior Director of Policy Communications Hunter Ihrman on the Beltway Beef podcast.On the second half of this episode, Kaitlynn Glover, the Executive Director of the Public Lands Council and NCBA Natural Resources, joins Katie to discuss failed proposals in the bill to dispose of any public lands. Finally, hear what how the bill includes reimbursing cattle producers for loss due to depredation by federally protected predators, such as gray wolves.Text us your comments, feedback and episode ideas!
We recorded incredibly late during a tough week, but this episode may have ended up being our favorite of the season. Squish on in to the fibers of The Victory Couch as we discuss how we would handle requests from our kids about getting piercings and tattoos, the crazy things we have done for love, which careers we think we'd be horrible at, and the similarities between us and our parents (The Victory Couch is hosted by Rick and Julie Rando).Shownotes: Connect with us on Instagram @thevictorycouch, Facebook, victorycouchpodcast@gmail.com, or www.thevictorycouch.comWant a new Victory Couch sticker for your water bottle, laptop, guitar case, etc.? Send us a message and we'll mail you one.SUBSCRIBE to The Victory Couch e-mail list by visiting https://www.thevictorycouch.com/ and click SUBSCRIBE at the top of your screen. If either or both of our kids ask for piercings or tattoos, how do you plan to advise them?What's the craziest or nuttiest thing you've done for love?Which careers do you think you would not be good at?How are you like your mom and how are you like your dad?Couch crumbs: delayed fishing trip, loss of beloved family memberProp your feet up: implementation of summer rhythms has begun, letters of recommendation for personal project rolling in
Quote of The Day: “Successful people are always looking for opportunities to help others. Unsuccessful people are always asking, 'What's in it for me?'.” — Brian Tracy Hosts: TOLA Omoniyi, Kanyinsola Omojola, Goodness Ezeh
A budget motion to address a severe backlog of felony cases in Brown County has bipartisan support.See omnystudio.com/listener for privacy information.
What is THE ONE THING that if you had would make all the difference to your business? Cause it to blow up! Take off! And LEAP into greatness!? Are you missing the strategy? The A to B and how to take thing to the next level? Maybe it's your character and how you're showing up day in day out? Or possibly your beliefs? If you could just change your beliefs around what is possible then that would make all the difference? When it comes to all of these, there are laws that govern them. Work with these laws and success will be your friend but work against them, even just one of them and you'll face resistance. In today's episode, I get 8 figure CEO James Wedmore back onto the poddy for the 2nd time to discuss the laws of marketing, sales and the universe that determine how successful (or unsuccessful) you'll be. You can find more about James at: Instagram @jameswedmore Podcast - The Mind Your Business Podcast Make sure you subscribe to my podcast to stay up to date with episodes I release every week. If you loved this episode, I'd be super grateful if you could leave me a review which helps me spread this podcast out to more amazing people just like you :) HERE'S WHERE YOU CAN FOLLOW ME: Instagram: @luke_page HOW TO SIGN DREAM CLIENTS EVERY WEEK - FREE 30 minute video sharing the specific strategy you can use to sign dream clients every week and build a $15k per month coaching business using Instagram, 1 offer and no cold DM's. https://www.lukepage.com.au/clients
Full Text of ReadingsThursday of the Fifth Week of Easter Lectionary: 288The Saint of the day is Saint Rita of CasciaSaint Rita of Cascia's Story Like Elizabeth Ann Seton, Rita of Cascia was a wife, mother, widow, and member of a religious community. Her holiness was reflected in each phase of her life. Born at Roccaporena in central Italy, Rita wanted to become a nun but was pressured at a young age into marrying a harsh and cruel man. During her 18-year marriage, she bore and raised two sons. After her husband was killed in a brawl and her sons had died, Rita tried to join the Augustinian nuns in Cascia. Unsuccessful at first because she was a widow, Rita eventually succeeded. Over the years, her austerity, prayerfulness, and charity became legendary. When she developed wounds on her forehead, people quickly associated them with the wounds from Christ's crown of thorns. She meditated frequently on Christ's passion. Her care for the sick nuns was especially loving. She also counseled lay people who came to her monastery. Beatified in 1626, Rita was not canonized until 1900. She has acquired the reputation, together with Saint Jude, as a saint of impossible cases. Many people visit her tomb each year. Reflection Although we can easily imagine an ideal world in which to live out our baptismal vocation, such a world does not exist. An “If only ….” approach to holiness never quite gets underway, never produces the fruit that God has a right to expect. Rita became holy because she made choices that reflected her baptism and her growth as a disciple of Jesus. Her overarching, lifelong choice was to cooperate generously with God's grace, but many small choices were needed to make that happen. Few of those choices were made in ideal circumstances—not even when Rita became an Augustinian nun. Saint Rita of Cascia is the Patron Saint of: Difficult MarriagesImpossible CausesInfertilityParenthood Learn more about Saint Rita! Saint of the Day, Copyright Franciscan Media
5.21.25 Hour 3, Kevin Sheehan and callers give their thoughts on the tush push staying after failing to get the amount of votes needed from NFL Owners.
5.21.25 Hour 2, More callers give their thoughts on the current state of the Commanders RB room and if it's good enough to compete for a Super Bowl. Kevin Sheehan reacts to the tush push ban not receiving enough votes and therefore is here to stay.
Hello, I'd really like to grow this email list. If you enjoy this newsletter, it would mean the world to Jola and I if you encouraged one friend/fellow immigrant/colleague to subscribe…Very likely, the the only thing you will get in return is warm fuzzy feelings, and if I can attribute it to you, I'd personally send you a thank you email.Join us as we explore the bitter-sweet world of the immigrant.In this episode, I'm speaking with Bukky Wonda, who moved from Nigeria to Canada about 11 years ago, and has gone on to become a successful tech founder in the immigration space.When trying to settle into a new country, finding optimistic people can make all the difference. As Bukky explains, “Immigration is so difficult that you don't want to find people who all they come and do to you is make things worse... Find people who are optimistic, who have agency, who are persistent.”I believe this mindset has been key to her success, from landing her first job at CIBC as a financial advisor rather than starting at entry-level positions to pivoting into entrepreneurship.In this conversation, Bukky and I chat about what it was like to move and settle in Canada 11 years ago. We also explore:* Her transition from accounting to immigration tech founder* Why she describes herself as a “happenstance entrepreneur”* Tips for anyone planning to immigrate to Canada in 2025/2026* Why preparation matters when you're looking to immigrateOfficial Links✅ Connect with Bukky on LinkedIn✅ Request Bukky's immigration servicesOne AskIf you found this story helpful, please forward or share it to one immigrant out there. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit thenewcomerspod.com
Discover all of the podcasts in our network, search for specific episodes, get the Optimal Living Daily workbook, and learn more at: OLDPodcast.com. Episode 3597: Dr. Benjamin Hardy challenges the belief in a "fixed" personality, explaining how trauma, lack of peak experiences, and cultural myths about identity can leave us emotionally and mentally frozen. By healing past wounds, seeking transformative experiences, and embracing change, we can continually evolve into new, more fulfilled versions of ourselves. Read along with the original article(s) here: https://medium.com/@benjaminhardy/do-you-have-a-frozen-personality-if-so-here-are-3-possible-reasons-ef949c0464c0 Quotes to ponder: "Your memory can get stuck, and then you get stuck." "You need to stop living in the past. This isn't easy. Eventually, you can get to the point where you see the past experience as the past." "Personality is DEVELOPED. And it never has to stop developing." Episode references: The Power of Moments: https://www.amazon.com/Power-Moments-Certain-Experiences-Extraordinary/dp/1501147765 The Body Keeps the Score: https://www.amazon.com/Body-Keeps-Score-Healing-Trauma/dp/0143127748 Learn more about your ad choices. Visit megaphone.fm/adchoices
Discover all of the podcasts in our network, search for specific episodes, get the Optimal Living Daily workbook, and learn more at: OLDPodcast.com. Episode 3597: Dr. Benjamin Hardy challenges the belief in a "fixed" personality, explaining how trauma, lack of peak experiences, and cultural myths about identity can leave us emotionally and mentally frozen. By healing past wounds, seeking transformative experiences, and embracing change, we can continually evolve into new, more fulfilled versions of ourselves. Read along with the original article(s) here: https://medium.com/@benjaminhardy/do-you-have-a-frozen-personality-if-so-here-are-3-possible-reasons-ef949c0464c0 Quotes to ponder: "Your memory can get stuck, and then you get stuck." "You need to stop living in the past. This isn't easy. Eventually, you can get to the point where you see the past experience as the past." "Personality is DEVELOPED. And it never has to stop developing." Episode references: The Power of Moments: https://www.amazon.com/Power-Moments-Certain-Experiences-Extraordinary/dp/1501147765 The Body Keeps the Score: https://www.amazon.com/Body-Keeps-Score-Healing-Trauma/dp/0143127748 Learn more about your ad choices. Visit megaphone.fm/adchoices
Discover all of the podcasts in our network, search for specific episodes, get the Optimal Living Daily workbook, and learn more at: OLDPodcast.com. Episode 3597: Dr. Benjamin Hardy challenges the belief in a "fixed" personality, explaining how trauma, lack of peak experiences, and cultural myths about identity can leave us emotionally and mentally frozen. By healing past wounds, seeking transformative experiences, and embracing change, we can continually evolve into new, more fulfilled versions of ourselves. Read along with the original article(s) here: https://medium.com/@benjaminhardy/do-you-have-a-frozen-personality-if-so-here-are-3-possible-reasons-ef949c0464c0 Quotes to ponder: "Your memory can get stuck, and then you get stuck." "You need to stop living in the past. This isn't easy. Eventually, you can get to the point where you see the past experience as the past." "Personality is DEVELOPED. And it never has to stop developing." Episode references: The Power of Moments: https://www.amazon.com/Power-Moments-Certain-Experiences-Extraordinary/dp/1501147765 The Body Keeps the Score: https://www.amazon.com/Body-Keeps-Score-Healing-Trauma/dp/0143127748 Learn more about your ad choices. Visit megaphone.fm/adchoices
Weston Jon Bouchér is a California-based menswear brand and the name of its founder. He launched the company in 2019 after a decade as a full-time apparel and lifestyle model.He initially sought a white-label supplier with like-minded quality standards. Unsuccessful, he opted instead for “cut-and-sew manufacturing.” The result is a network of global manufacturers, all producing apparel to Jon's designs and specifications, and sold entirely from his Shopify site.He joins host Eric Bandholz in this episode, addressing the brand's launch, production challenges, marketing tactics, and more.For an edited and condensed transcript with embedded audio, see: https://www.practicalecommerce.com/from-model-to-menswear-founderFor all condensed transcripts with audio, see: https://www.practicalecommerce.com/tag/podcasts******The mission of Practical Ecommerce is to help online merchants improve their businesses. We do this with expert articles, podcasts, and webinars. We are an independent publishing company founded in 2005 and unaffiliated with any ecommerce platform or provider. https://www.practicalecommerce.com
Today's podcast is part of a new series on success in our Christian Life. Today's message is called: 5 Habits If Unsuccessful Families Joe shares great advice on living your best life in Christ. For more information on Joe's resources visit www.joemcgeeministries.com & www.joemcgeestore.com JOIN THE FAMILY Sign-up for the Daily Devotion with Joe to get tips, clips, and more tools to help you build a strong marriage, family, and life using God's Word. Click to JOIN THE FAMILY. WAIT... (You can also join us online) Subscribe to our Youtube channel.
#UKRAINE: EASTER CEASEFIRE UNSUCCESSFUL. JOHN HARDIE, BILL ROGGIO, FDD 1905 ODESSA
Unsuccessful at the time of release, Spirit: Stallion of the Cimarron has lived on as a cult favorite among animation fans. It has enjoyed a sequel as well as a spinoff streaming series. Guests Eric Taylor and Peter Baldeo join to talk about it.___Please consider joining our Patreon: https://www.patreon.com/wwibofficialYouTube: https://www.youtube.com/@whywasntitbetterInstagram: https://www.instagram.com/wwib_officialTwitter: https://twitter.com/WWIBpodcastSubscribe! Rate! Review! Tell a friend!
Dan Corder is joined by Professor Nazir Ismail from Wits University to discuss a ground-breaking new study that could reshape how South Africa tackles tuberculosis. The study shows that offering cash incentives and counselling to TB patients can cut the risk of unsuccessful treatment outcomes by over 50%.See omnystudio.com/listener for privacy information.
On this episode of Survey Says, a special edition of GT: The Podcast, I. Paul Singh, MD, is joined by guests Manjool Shah, MD, and Ticiana De Francesco, MD, to review a real case from his practice. They discuss the patient's treatment history and how it informs which procedures to consider for the future and which ones to rule out. The guests share how they would proceed before finding out what Dr. Singh did and how their colleagues would approach the case, based on results of a social media poll of GT's audience.
The Midrash compares Haman's plot against the Jews to a foolish bird attempting to drain the sea, beakful by beakful. At first glance, this fable highlights the impossibility of eradicating the Jewish people. But upon deeper examination, it reveals the secret of Jewish survival, the core reason for antisemitism, and the unbreakable bond between the Jewish soul and Torah. Haman's mistake was in thinking that severing Jews from Torah would make them vulnerable to destruction—yet, as history has shown, even when Jews have drifted from their spiritual roots, their intrinsic connection to G-d and Torah remains. This class explores why the Jewish people have endured against all odds and what this means for our own Jewish identity today.Key Takeaways:The Midrash's Metaphor – Haman's attempt to destroy the Jews was as foolish as a bird trying to empty an ocean. But why? This metaphor reveals deeper truths about Jewish resilience.The Secret of Antisemitism – Haman, like many persecutors throughout history, saw Jewish existence as a threat. Why have so many tyrants sought to destroy the Jewish people?The Relationship Between Jews and Torah – The Torah is to Jews what water is to fish. Even when Jews drift, they cannot fully detach from their Divine essence.G-d's ‘Unsuccessful' Plan – The Midrash states that even G-d could not destroy the Jewish people. What does this mean, and what does it teach us about the Jewish soul?Haman's ‘Final Solution' – His real plan wasn't just genocide—it was to dry up the Jewish connection to Torah and assimilate them into Persian society. This strategy failed, just as all others have throughout history.The Eternal Bond – The Jews have outlived every empire that sought their destruction, proving that their essence is eternal.A Call to Jewish Unity – If a Jew was Jewish enough for Hitler to send to the gas chambers, he is Jewish enough for us to love and embrace. Jewish survival is not just a historical fact—it is a personal responsibility.#Purim #Jewish #Antisemitism #Judaism #Faith #Rabbi #chabad #Jewishsurvival #Torah #BookofEsther #MegillahSupport the showGot your own question for Rabbi Bernath? He can be reached at rabbi@jewishndg.com or http://www.theloverabbi.comSingle? You can make a profile on www.JMontreal.com and Rabbi Bernath will help you find that special someone.Donate and support Rabbi Bernath's work http://www.jewishndg.com/donateFollow Rabbi Bernath's YouTube Channel https://www.youtube.com/user/ybernathAccess Rabbi Bernath's Articles on Relationships https://medium.com/@loverabbi
PREVIEW: Author Charles Spicer, "Coffee with Hitler," relates the frustrating story of the unsuccessful Oster plot to remove Hitler from government in September 1938. More later. September1938. Chamberlain pronounces success.
Follow us on Instagram, TikTok & Twitter, and make sure to DM us your toxic confessions!@gintoxicpodcast on Instagram@gintoxicpodcast on TikTok@gintoxicpodcast on TwitterFollow Christina Harris on Instagram, YouTube, TikTok & Twitter@beautychickee on InstagramBeautyChickee on YouTube@beautychickee on TikTok@beautychickee on TwitterFollow Lily Stewart on Instagram, TikTok & Twitter@lilyystewart on Instagram@lilystewartttt on TikTok@lilystewartt on TwitterFor all inquiries please contact podcast@beautychickee.com New full episodes every Wednesday at 12PM ET. Bonus episodes every Friday at 12PM EST. Music by @MarkGenerous.Stay toxic.
Think you're doing everything right, but still not seeing the business growth you desire? Curious about the habits that might be holding you back from reaching your full potential as an entrepreneur? This episode is tailor-made for you.In today's lesson, Omar shares the detrimental behaviors and mindsets that can sabotage your progress—habits Omar knows all too well from personal experience. From letting fear call the shots to poor cash flow management, learn how to identify these harmful habits and turn things around.Remember, recognizing these habits is the first step to overcoming them. Make a commitment to work on these areas and watch your business thrive. Hit play at the top of the page and dive into this invaluable lesson.Download the FREE P&L Sheet over at http://100mba.net/templates.Watch the episodes on YouTube: https://lm.fm/GgRPPHiSUBSCRIBEYouTube | Apple Podcast | Spotify | Podcast Feed
Think you’re doing everything right, but still not seeing the business growth you desire? Curious about the habits that might be holding you back from reaching your full potential as an entrepreneur? This episode is tailor-made for you. In today’s lesson, Omar shares the detrimental behaviors and mindsets that can sabotage your progress—habits Omar knows […] The post MBA2586 The 7 Habits of Highly Unsuccessful Entrepreneurs (and How to Avoid Them) appeared first on The $100 MBA.
State Representative Bob Morgan (D-Deerfield) joins John Williams to talk about his ‘Bears Act’ legislation that would tie public funding to a sports team’s success. Rep. Morgan also comments on the breaking news that President Trump might pardon former Illinois governor Rod Blagojevich.
The Action Academy | Millionaire Mentorship for Your Life & Business
Want To Quit Your Job In The Next 6-18 Months Through Buying Commercial Real Estate & Small Businesses?
Welcome to The Game w/Alex Hormozi, hosted by entrepreneur, founder, investor, author, public speaker, and content creator Alex Hormozi. On this podcast you'll hear how to get more customers, make more profit per customer, how to keep them longer, and the many failures and lessons Alex has learned and will learn on his path from $100M to $1B in net worth.Wanna scale your business? Click here.Follow Alex Hormozi's Socials:LinkedIn | Instagram | Facebook | YouTube | Twitter | Acquisition
© 2020-2026 Ivy Podcast Discovery LLC
