Podcasts about codethe

Do you know how to speak up for your needs, or do you let fear keep you small? On today's ep of Expanded, EMDR therapist Janelle Nelson talks with Jessica about how she overcame fear to proceed with a divorce, and then had to conquer similar fears around standing up for herself while filing a lawsuit. Janelle shares how TBM work supported her through these major life moments, how she navigates co-parenting, manifesting a trip to Peru, and the effects of growing up in a deeply conservative home. They of course also talk about all of the blocks, tests, and Expanders Janelle came across along the way! Find the Complete Show Notes Here -> https://tobemagnetic.com/expanded-podcast In This Episode We Talk About:The remarkable manifestation journey of our guest, EMDR Therapist Janelle!A deep dive into her astrological profile and authentic codeThe effect of growing up in a deeply conservative, Christian homeHow she discovered TBM and her first manifestation list!Navigating separation, divorce and co-parentingJanelle's Rock Bottom and the breakthrough that followedHow anger can lead to depressionShamans, spirit animal meditation, self-validation!The energetic power of standing up for yourselfHow she manifested a trip to Peru and the spiritual takeaways she received Self-care, the different ways it can lookBlocks, tests and expanders she encountered along her manifestation journey! Resources: The Pathway - (12-month commitment) - Looking To Start Your Membership? Use code EXPANDED for $20 off your first month of the Pathway  or $20 off any ala carteNewsletterA la Carte Workshops Text Us: +1-213-423-5226 - (texting is only for US, Canada, & Puerto Rico)Sign Up for our TBM Manifestation Journal Waitlist Find The Missing Piece Video Class In The Episode:Text “Podcast” to +1-213-423-5226 - (texting is only for US, Canada, & Puerto Rico) to be added to our Podcast text group! Pathway Member's Manifestation Story from IntroWhen The Body Says No - Gabor Maté M.D.@jncounselingJN Counseling Linktr.ee Where To Find Us!@tobemagnetic@JessicaAshleyGill  Our Offerings:Looking To Start Your Membership? - Use code EXPANDED for $20 off your first month of The Pathway or $20 off any a la carte workshop.A La Carte - Not ready for a membership? Try an individual workshop with 3 months of access.The Basics Bundle - How To Manifest, Unblocked Inner Child & Unblocked ShadowUnblocked Inner Child Unblocked Shadow The Love Bundle - Unblocked Love & Relationships Reflection Mini-WorkshopUnblocked Money The Pathway - 12-month all-access membership includes ALL of our a la cartes + more!How To Manifest, Unblocked Inner Child, Unblocked Shadow, The Love Bundle, Unblocked Money+ The Daily Practice includes our Deep Imagining Library with over 18+ DIs+ Unblocked Boundaries + Unblocked Full Moon+ Uplevel - 3 in 1 includes Rut, Rock Bottom & Next Level workshops+ Monthly Supported Class+ Community Group to connect with fellow manifestors+ Automatic access to any new offering or DI that becomes available as well! Free Offerings to Get You StartedThe MotivationFree Clarity Exercise - Journal prompt + 1 Deep Imagining Expanded Podcast - Manifestation 101  SubmitSubmit to Be a Process GuestLeave a Review 5-star review for a chance to win a 1-year membership to The Pathway 2.0. Then tune into future episodes to hear your review announced! If you win send us a message on Intercom hi@tobemagnetic.com to claim it. 

This is the audio version of the essay I published on Monday.I'm excited to finally share why I've joined Temporal.io as Head of Developer Experience. It's taken me months to precisely pin down why I have been obsessed with Workflows in general and Temporal in particular.It boils down to 3 core opinions: Orchestration, Event Sourcing, and Workflows-as-Code.Target audience: product-focused developers who have some understanding of system design, but limited distributed systems experience and no familiarity with workflow engines30 Second PitchThe most valuable, mission-critical workloads in any software company are long-running and tie together multiple services. Because this work relies on unreliable networks and systems: You want to standardize timeouts and retries. You want offer "reliability on rails" to every team. Because this work is so important: You must never drop any work. You must log all progress. Because this work is complex: You want to easily model dynamic asynchronous logic... ...and reuse, test, version and migrate it. Finally, you want all this to scale. The same programming model going from small usecases to millions of users without re-platforming. Temporal is the best way to do all this — by writing idiomatic code known as "workflows".Requirement 1: OrchestrationSuppose you are executing some business logic that calls System A, then System B, and then System C. Easy enough right?But: System B has rate limiting, so sometimes it fails right away and you're just expected to try again some time later. System C goes down a lot — and when it does, it doesn't actively report a failure. Your program is perfectly happy to wait an infinite amount of time and never retry C. You could deal with B by just looping until you get a successful response, but that ties up compute resources. Probably the better way is to persist the incomplete task in a database and set a cron job to periodically retry the call.Dealing with C is similar, but with a twist. You still need B's code to retry the API call, but you also need another (shorter lived, independent) scheduler to place a reasonable timeout on C's execution time since it doesn't report failures when it goes down.Do this often enough and you soon realize that writing timeouts and retries are really standard production-grade requirements when crossing any system boundary, whether you are calling an external API or just a different service owned by your own team.Instead of writing custom code for timeout and retries for every single service every time, is there a better way? Sure, we could centralize it!We have just rediscovered the need for orchestration over choreography. There are various names for the combined A-B-C system orchestration we are doing — depending who you ask, this is either called a Job Runner, Pipeline, or Workflow.Honestly, what interests me (more than the deduplication of code) is the deduplication of infrastructure. The maintainer of each system no longer has to provision the additional infrastructure needed for this stateful, potentially long-running work. This drastically simplifies maintenance — you can shrink your systems down to as small as a single serverless function — and makes it easier to spin up new ones, with the retry and timeout standards you now expect from every production-grade service. Workflow orchestrators are "reliability on rails".But there's a risk of course — you've just added a centralized dependency to every part of your distributed system. What if it ALSO goes down?Requirement 2: Event SourcingThe work that your code does is mission critical. What does that really mean? We cannot drop anything. All requests to start work must either result in error or success - no "it was supposed to be running but got lost somewhere" mismatch in expectations. During execution, we must be able to resume from any downtime. If any part of the system goes down, we must be able to pick up where we left off. We need the entire history of what happened when, for legal compliance, in case something went wrong, or if we want to analyze metadata across runs. There are two ways to track all this state. The usual way starts with a simple task queue, and then adds logging:(async function workLoop() { const nextTask = taskQueue.pop() await logEvent('starting task:', nextTask.ID) try { await doWork(nextTask) // this could fail! catch (err) { await logEvent('reverting task:', nextTask.ID, err) taskQueue.push(nextTask) } await logEvent('completed task:', nextTask.ID) setTimeout(workLoop, 0) })() But logs-as-afterthought has a bunch of problems. The logging is not tightly paired with the queue updates. If it is possible for one to succeed but the other to fail, you either have unreliable logs or dropped work — unacceptable for mission critical work. This could also happen if the central work loop itself goes down while tasks are executing. At the local level, you can fix this with batch transactions. Between systems, you can create two-phase commits. But this is a messy business and further bloats your business code with a ton of boilerplate — IF (a big if) you have the discipline to instrument every single state change in your code. The alternative to logs-as-afterthought is logs-as-truth: If it wasn't logged, it didn't happen. This is also known as Event Sourcing. We can always reconstruct current state from an ever-growing list of eventHistory:(function workLoop() { const nextTask = reconcile(eventHistory, workStateMachine) doWorkAndLogHistory(nextTask, eventHistory) // transactional setTimeout(workLoop, 0) })() The next task is strictly determined by comparing the event history to a state machine (provided by the application developer). Work is either done and committed to history, or not at all.I've handwaved away a lot of heavy lifting done by reconcile and doWorkAndLogHistory. But this solves a lot of problems: Our logs are always reliable, since that is the only way we determine what to do next. We use transactional guarantees to ensure that work is either done and tracked, or not at all. There is no "limbo" state — at the worst case, we'd rather retry already-done work with idempotency keys than drop work. Since there is no implicit state in the work loop, it can be restarted easily on any downtime (or scaled horizontally for high load). Finally, with standardized logs in our event history, we can share observability and debugging tooling between users. You can also make an analogy to the difference between "filename version control" and git — Using event histories as your source of truth is comparable to a git repo that reflects all git commits to date.But there's one last problem to deal with - how exactly should the developer specify the full state machine?Requirement 3: Workflows-as-CodeThe prototypical workflow state machine is a JSON or YAML file listing a sequence of steps. But this abuses configuration formats for expressing code. it doesn't take long before you start adding features like conditional branching, loops, and variables, until you have an underspecified Turing complete "domain specific language" hiding out in your JSON/YAML schema.[ { "first_step": { "call": "http.get", "args": { "url": "https://www.example.com/callA" }, "result": "first_result" } }, { "where_to_jump": { "switch": [ { "condition": "${first_result.body.SomeField < 10}", "next": "small" }, { "condition": "${first_result.body.SomeField < 100}", "next": "medium" } ], "next": "large" } }, { "small": { "call": "http.get", "args": { "url": "https://www.example.com/SmallFunc" }, "next": "end" } }, { "medium": { "call": "http.get", "args": { "url": "https://www.example.com/MediumFunc" }, "next": "end" } }, { "large": { "call": "http.get", "args": { "url": "https://www.example.com/LargeFunc" }, "next": "end" } } ] This example happens to be from Google, but you can compare similar config-driven syntaxes from Argo, Amazon, and Airflow. The bottom line is you ultimately find yourself hand-writing the Abstract Syntax Tree of something you can read much better in code anyway:async function dataPipeline() { const { body: SomeField } = await httpGet("https://www.example.com/callA") if (SomeField < 10) { await httpGet("https://www.example.com/SmallFunc") } else if (SomeField < 100) { await httpGet("https://www.example.com/MediumFunc") } else { await httpGet("https://www.example.com/BigFunc") } } The benefit of using general purpose programming languages to define workflows — Workflows-as-Code — is that you get to the full set of tooling that is already available to you as a developer: from IDE autocomplete to linting to syntax highlighting to version control to ecosystem libraries and test frameworks. But perhaps the biggest benefit of all is the reduced need for context switching from your application language to the workflow language. (So much so that you could copy over code and get reliability guarantees with only minor modifications.)This config-vs-code debate arises in multiple domains: You may have encountered this problem in AWS provisioning (CloudFormation vs CDK/Pulumi) or CI/CD (debugging giant YAML files for your builds). Since you can always write code to interpret any declarative JSON/YAML DSL, the code layer offers a superset of capabilities.The Challenge of DIY SolutionsSo for our mission critical, long-running work, we've identified three requirements: We want an orchestration engine between services. We want to use event sourcing to track and resume system state. We want to write all this with code rather than config languages. Respectively, these solve the pain points of reliability boilerplate, implementing observability/recovery, and modeling arbitrary business logic.If you were to build this on your own: You can find an orchestration engine off the shelf, though few have a strong open source backing. You'd likely start with a logs-as-afterthought system, and accumulating inconsistencies over time until they are critical enough to warrant a rewrite to a homegrown event sourcing framework with stronger guarantees. As you generalize your system for more use cases, you might start off using a JSON/YAML config language, because that is easy to parse. If it were entrenched and large enough, you might create an "as Code" layer just as AWS did with AWS CDK, causing an impedance mismatch until you rip out the underlying declarative layer. Finally, you'd have to make your system scale for many users (horizontal scaling + load balancing + queueing + routing) and many developers (workload isolation + authentication + authorization + testing + code reuse).Temporal as the "iPhone solution"When Steve Jobs introduced the iPhone in 2007, he introduced it as "a widescreen iPod with touch controls, a revolutionary mobile phone, and a breakthrough internet communications device", before stunning the audience: "These are not three separate devices. This is ONE device."This is the potential of Temporal. Temporal has opinions on how to make each piece best-in-class, but the tight integration creates a programming paradigm that is ultimately greater than the sum of its parts: You can build a UI that natively understands workflows as potentially infinitely long running business logic, exposing retry status, event history, and code input/outputs. You can build workflow migration tooling that verifies that old-but-still-running workflows have been fully accounted for when migrating to new code. You can add pluggable persistence so that you are agnostic to what databases or even what cloud you use, helping you be cloud-agnostic. You can run polyglot teams — each team can work in their ideal language, and only care about serializable inputs/outputs when calling each other, since event history is language-agnostic. There are more possibilities I can't talk about yet. The Business Case for TemporalA fun anecdote about how I got the job: through blogging.While exploring the serverless ecosystem at Netlify and AWS, I always had the nagging feeling that it was incomplete and that the most valuable work was always "left as an exercise to the reader". The feeling crystallized when I rewatched DHH's 2005 Ruby on Rails demo and realized that there was no way the serverless ecosystem could match up to it. We broke up the monolith to scale it, but there were just too many pieces missing.I started analyzing cloud computing from a "Jobs to Be Done" framework and wrote two throwaway blogposts called Cloud Operating Systems and Reconstituting the Monolith. My ignorant posting led to an extended comment from a total internet stranger telling me all the ways I was wrong. Lenny Pruss, who was ALSO reading my blogpost, saw this comment, and got Ryland to join Temporal as Head of Product, and he then turned around and pitched (literally pitched) me to join.One blogpost, two jobs. Learn in Public continues to amaze me by the luck it creates.Still, why would I quit a comfy, well-paying job at Amazon to work harder for less money at a startup like this? Extraordinary people. At its core, betting on any startup is betting on the people. The two cofounders of Temporal have been working on variants of this problem for over a decade each at AWS, Microsoft, and Uber. They have attracted an extremely high caliber team around them, with centuries of distributed systems experience. I report to the Head of Product, who is one of the fastest scaling executives Sequoia has ever seen. Extraordinary adoption. Because it reinvents service orchestration, Temporal (and its predecessor Cadence) is very horizontal by nature. Descript uses it for audio transcription, Snap uses it for ads reporting, Hashicorp uses it for infrastructure provisioning, Stripe uses it for the workflow engine behind Stripe Capital and Billing, Coinbase uses it for cryptocurrency transactions, Box uses it for file transfer, Datadog uses it for CI/CD, DoorDash uses it for delivery creation, Checkr uses it for background checks. Within each company, growth is viral; once one team sees successful adoption, dozens more follow suit within a year, all through word of mouth. Extraordinary results. After migrating, Temporal users report production issues falling from once-a-week to near-zero. Accidental double-spends have been discovered and fixed, saving millions in cold hard cash. Teams report being able to move faster, thanks to testing, code reuse, and standardized reliability. While the value of this is hard to quantify, it is big enough that users organically tell their friends and list Temporal in their job openings. Huge potential market growth. The main thing you bet on when it comes to Temporal is that its primary competition really is homegrown workflow systems, not other engines like Airflow, AWS Step Functions, and Camunda BPMN. In other words, even though Temporal should gain market share, the real story is market growth, driven by the growing microservices movement and developer education around best-in-class orchestration. At AWS and Netlify, I always felt like there was a missing capability in building serverless-first apps — duct-taping functions and cronjobs and databases to do async work — and it all fell into place the moment I saw Temporal. I'm betting that there are many, many people like me, and that I can help Temporal reach them. High potential value capture. Apart from market share and market growth, any open source project has the additional challenge of value capture, since users can self-host at any time. I mostly subscribe to David Ulevitch's take that open source SaaS is basically outsourcing ops. I haven't talked about Temporal's underlying architecture but it has quite a few moving parts and takes a lot of skill and system understanding to operate. For reasons I won't get into, Temporal scales best on Cassandra and that alone is enough to make most want to pay someone else to handle it. Great expansion opportunities. Temporal is by nature the most direct source of truth on the most valuable, mission critical workflows of any company that adopts it. It can therefore develop the most mission critical dashboard and control panel. Any source of truth also becomes a natural aggregation point for integrations, leaving open the possibility of an internal or third party service marketplace. With the Signals and Queries features, Temporal easily gets data in and out of running workflows, making it an ideal foundation for the sort of human-in-the-loop work for the API Economy. Imagine toggling just one line of code to A/B test vendors and APIs, or have Temporal learn while a domain expert manually executes decision processes and take over when it has seen enough. As a "high-code" specialist in reliable workflows, it could be a neutral arms dealer in the "low-code" gold rush, or choose to get into that game itself. If you want to get really wild, the secure distributed execution model of Workflow workers could be facilitated by an ERC-20 token. (to be clear... everything listed here is personal speculation and not the company roadmap) There is much work to do, though. Temporal Cloud needs a lot of automation and scaling before it becomes generally available. Temporal's UI is in the process of a full rewrite. Temporal's docs need a lot more work to fully explain such a complex system with many use cases. Temporal still doesn't have a production-ready Node.js or Python SDK. And much, much, more to do before Temporal's developer experience becomes accessible to the majority of developers.If what I've laid out excites you, take a look at our open positions (or write in your own!), and join the mailing list!Further Reading Orchestration Yan Cui's guide to Orchestration vs Choreography InfoQ: Coupling Microservices - a non-Temporal focused discussion of Orchestration A Netflix Guide to Microservices Event Sourcing Martin Fowler on Event Sourcing Kickstarter's guide to Event Sourcing Code over Config ACloudGuru's guide to Terraform, CloudFormation, and AWS CDK Serverless Workflow's comparison of Workflow specification formats Temporal Dealing with failure - when to use Workflows The macro problem with microservices - Temporal in context of microservices Designing A Workflow Engine from First Principles - Temporal Architecture Principles Writing your first workflow - 20min code video Case studies and External Resources from our users

This week we sit with Raeann.  She is working in Phoneix but for a different airline than we do.  We get to talk about the difference between working at a  hub compared to her job at a line station.  She has taken advantage of her benefits and looks forward to everyone hearing her stories. How she got into the aviation field and what jobs she has had.New delay codeThe time we knew that Covid was serious to the industryOur first Non-Rev tripsHow much would you pay for First class on a 9+ hour tripFavorite trip to ItalyPros and cons of working at a hub compared to a line stationThe time flying took as long as just drivingMissed Christmas Market because of lost passportNew YorkTipsFind more out about our show on our Instagram @NonRevLoungePodcast and Twitter @LoungeNon. You can also reach us over email at NonRevLoungePodcast@gmail.com

This marks the 150th episode of DNA Today! Our guests to celebrate this landmark episode of DNA Today are Dr. Euan Ashley, a medical geneticist and cardiologist. And Dr. Stephen Quake, a physics professor, bioengineer and pioneer in microfluidics. A Scotland native, Dr. Euan Ashley graduated with degrees in Physiology and Medicine from the University of Glasgow. He completed medical residency and a PhD in molecular physiology at the University of Oxford before moving to Stanford University where he trained in cardiology and advanced heart failure, joining the faculty in 2006. In 2010, he led the team that carried out the first clinical interpretation of a human genome. The paper published in the Lancet was the focus of over 300 news stories, and became one of the most cited articles in clinical medicine that year. The team extended the approach in 2011 to a family of four and now routinely applies genome sequencing to the diagnosis of patients at Stanford hospital where Dr. Ashley directs the Clinical Genome Service and the Center for Inherited Cardiovascular Disease. In 2014, Dr Ashley became co-chair of the steering committee of the NIH Undiagnosed Diseases Network. Stephen Quake is a professor of bioengineering and applied physics at Stanford University and is co-President of the Chan Zuckerberg Biohub. He holds a B.S. in Physics and M.S. in Mathematics from Stanford University and a doctorate in Theoretical Physics from the University of Oxford. Dr. Quake has invented many measurement tools for biology, including new DNA sequencing technologies that have enabled rapid analysis of the human genome and microfluidic automation that allows scientists to efficiently isolate individual cells and decipher their genetic code. Dr. Quake is also well known for inventing new diagnostic tools, including the first non-invasive prenatal test for Down syndrome and other aneuploidies. His test is rapidly replacing risky invasive approaches such as amniocentesis, and millions of women each year now benefit from this approach. He was also the fifth person in the world to have their genome sequences and his genome was the subject of clinical annotation by a large team at Stanford Hospital led by Dr. Ashley. On This Episode We Discuss:The first clinical interpretation of a human genomeGenome sequencing technologiesThe cost of sequencing a genome Understanding the genomic codeThe future of precision medicineDr. Ashley's book, The Genome OdysseyWant to read the Genome Odyssey? Enter to win your own copy! Head over to our Twitter, Instagram, Facebook, and LinkedIn to enter to win a free book!Be sure to follow Dr. Ashley and Dr. Quake on Twitter! How do you keep research articles organized? We have struggled with this for years, but have finally found a solution that is simple and easy. It's called Paperpile! It radically simplifies the workflow of collecting, managing and writing papers. Paperpile allows you to highlight and annotate papers, manage references, share and collaborate and even cite directly in Google Docs and Microsoft Word. Paperpile's new mobile apps allows you to sync your library to all your devices so you can read and annotate on your iPad, iPhone, or Android device. Start your free 30 day trial today at paperpile.com with promo code “DNATODAY”. Paperpile costs only $36 per year, but with code “DNATODAY” you save 20%! Want to become a genetic counselor? Looking for ways to engage with the field and boost your resume for grad school applications? Then you should check out Sarah Lawrence's “Why Genetic Counseling Wednesday Summer Series”! Every Wednesday this June Sarah Lawrence is hosting this series where you can interact through Zoom with genetic counselors from different specialties for an hour and a half. You can sign up at SLC.edu/DNAtoday to register to level up your resume for applications in the fall. Stay tuned for the next new episode of DNA Today on July 2nd, 2021! We'll be joined by Dr. Richard Michelmore and Dr. Brad Pollock who will be discussing COVID-19 variants. New episodes are released on the first and third Friday of the month. In the meantime, you can binge over 150 other episodes on Apple Podcasts, Spotify, streaming on the website, or any other podcast player by searching, “DNA Today”. All episodes in 2021 are also recorded with video which you can watch on our YouTube channel. See what else we are up to on Twitter, Instagram, Facebook, YouTube and our website, DNApodcast.com. Questions/inquiries can be sent to info@DNApodcast.com.

https://www.humblebundle.com/books/learn-to-code-the-fun-way-no-starch-press-books?partner=thetalkinggeekThink like a programmer: an introduction to creative problem solvingPerl one-liners: 130 programs that get things doneThe book of f#: break free with managed to functional programmingLearn Java the easy way: a hands-on introduction to programmingCode craft: The practice of writing excellent codeLearn you a Haskell for great good!: A beginner's guideClojure for the brave and true: learn the ultimate language and become a better programmerLand of lisp: learn to program and lisp, one game at a time!Learn you some erlang for great good!: Hey beginner's guidePractical SQL: a beginner's guide to store telling with dataThe book of r: a first course in programming and statisticsThe art of R programming: a tour of statistical software designImpractical Python projects: play full programming activities to make you smarterThe secret Life of programs: understand computers -- craft better codeThe rust programming language (covers rust 2018)C++ crash course: a fast-paced introductionThe art of Assembly language second editionEloquent JavaScript, third edition: a modern introduction to programmingIf Hemingway wrote JavaScriptPlease leave a rating/review for this podcast!Become a podcaster and get one month free! Sign up for a Spreaker pro plan with this link to save: https://www.spreaker.com/plans?coupon_code=thetalkinggeek (that is an affiliate link)I love Humble Bundle (especially the book deals), check them out: https://www.humblebundle.com/?partner=thetalkinggeek (that is also an affiliate link)If (for some reason) you want more of me, my blog is https://thetalkinggeek.com. And you can find me on social media at:Facebook: https://www.facebook.com/KyleTheTalkingGeek/Linkedin: https://www.linkedin.com/in/kylesouzaTwitter: https://twitter.com/thekylesouzaInstagram: http://instagram.com/thekylesouza

https://www.humblebundle.com/books/learn-to-code-the-fun-way-no-starch-press-books?partner=thetalkinggeekThink like a programmer: an introduction to creative problem solvingPerl one-liners: 130 programs that get things doneThe book of f#: break free with managed to functional programmingLearn Java the easy way: a hands-on introduction to programmingCode craft: The practice of writing excellent codeLearn you a Haskell for great good!: A beginner's guideClojure for the brave and true: learn the ultimate language and become a better programmerLand of lisp: learn to program and lisp, one game at a time!Learn you some erlang for great good!: Hey beginner's guidePractical SQL: a beginner's guide to store telling with dataThe book of r: a first course in programming and statisticsThe art of R programming: a tour of statistical software designImpractical Python projects: play full programming activities to make you smarterThe secret Life of programs: understand computers -- craft better codeThe rust programming language (covers rust 2018)C++ crash course: a fast-paced introductionThe art of Assembly language second editionEloquent JavaScript, third edition: a modern introduction to programmingIf Hemingway wrote JavaScriptPlease leave a rating/review for this podcast!Become a podcaster and get one month free! Sign up for a Spreaker pro plan with this link to save: https://www.spreaker.com/plans?coupon_code=thetalkinggeek (that is an affiliate link)I love Humble Bundle (especially the book deals), check them out: https://www.humblebundle.com/?partner=thetalkinggeek (that is also an affiliate link)If (for some reason) you want more of me, my blog is https://thetalkinggeek.com. And you can find me on social media at:Facebook: https://www.facebook.com/KyleTheTalkingGeek/Linkedin: https://www.linkedin.com/in/kylesouzaTwitter: https://twitter.com/thekylesouzaInstagram: http://instagram.com/thekylesouza

My reasons for choosing Buzzsprout for my podcasting.Don't waste time like I did. Check out my first "commercial" I guess you'd call it.GO HERE to sign up for BUZZSPROUT:$20 Amazon Gift Certificate Gift - Click HERE to sign up using my referral codeThe hosting on Buzzsprout is $15 a month and I think they spiff me $5 when YOU join one of their paid plans! https://www.buzzsprout.com/?referrer_id=388093 Support the show (https://www.patreon.com/sarita88)

“Well-being is an ongoing thing. It’s a way of life. It isn’t a trend.” The paradigm is outdated. You don’t need to be successful before you can focus on your well-being. According to this episode’s guest - Megan McNealy - you can DO and BE well at the same time. More than that, if you make well-being a focal point for your life, you can actually LEVERAGE it to create even more success. Nowadays, Megan is an impact-driven entrepreneur and founder of Well-Being Drives Success - a multi-faceted platform that serves people striving for exceptional wellness and extraordinary success.But she didn’t always prioritize well-being. As an award winning, 20+ year First Vice President and Wealth Management Advisor at one of the largest financial firms in the world, Megan chased the traditional model of success. As a high achiever, she worked the hours and invested in the hustle. But in 2010, her life crescendoed into the ‘perfect storm’. Megan’s health had begun to deteriorate when she was diagnosed with rheumatoid arthritis. This condition froze her hands until she was unable to hold a pen and caused pain while walking. Then she contracted chronic kidney disease followed by kidney cancer. Megan felt like she was trying to catch a falling knife. She was broken down on the side of the road with no clear way out. It was then that she turned her focus to well-being - but not the traditional model of sleep, diet, and exercise. Instead, she created a holistic lifestyle that was based on 18 different practices - all focusing a different area of wellness. Megan’s “wealth-being” wheel helped her focus on her mind, body, and spirit - and it was so effective, it literally saved her life. After discovering that plenty of other high-ranking executives are suffering behind the scenes, Megan felt called to share what she’d discovered. It’s how her new book - Reinvent the Wheel: How Top Leaders Leverage Well-Being for Success was born. “I promised when I was sick that if I ever lived that I would devote the rest of my life to helping other people. That’s how I stay grounded.” It’s not unusual for workaholics people to believe a focus on well-being will derail their life. We kid ourselves that we don’t have enough time to meditate, journal, or take up soul-lifting activities. But what if the opposite was true? Between 2010-2018, Megan quadrupled her income. This timescale correlates directly with Megan’s wellness-first philosophy. The reality is, wellness can be leveraged for elevated levels of success, and in this episode, Megan reveals why. Check it out now and discover: Megan’s holistic definition of well-beingWhy there’s a new age of wellness-first executives rising Why gratitude is the ultimate cheat-codeThe best place to start your well-being practiceWhy wellness needs a mind, body, and spirit componentHow to leverage well-being in your lifeAnd more…If you keep putting well-being on the backburner because your work takes priority, you’ll take a lot from this episode. So check it out now and discover how you can leverage wellness to achieve the things you want. “I love journaling because it feels like when my hand moves across a page, the truth of what I really feel seems to come out.” How to contact Check out Megan’s work at www.meganmcnealy.comHer book, Reinvent the Wheel: How Top Executives Leverage Well-Being for Success is available at Amazon, Barnes & Noble, Indiebound, and Porchlight. https://www.facebook.com/vibrantmegan/https://www.instagram.com/meganmcnealy/We thrive on your feedback, so if you’ve enjoyed this show, please rate us and leave us a review. And don’t forget to subscribe to ensure you never miss an episode again. See acast.com/privacy for privacy and opt-out information.

I hope this conversation with Lisa Wang motivates you to assess your own work-ethic, triggers some introspective curiosities of your own to explore, and assess your own drive for what Lisa calls “enoughness”.Lisa Wang is the founder & CEO of SheWorx, a leading global platform empowering over 20,000 female entrepreneurs to close the funding gap and build and scale successful companies. She also founded The AcadeMe, which offers actionable master classes & executive training for women on the rise. She’s a Forbes 30 Under 30 in venture capital, keynote public speaker, US hall of fame gymnast and host of the Enoughness podcast.As someone who innately has all the markings of a hard working, insatiable over-achiever, with limitless accomplishments, in my opinion it’s Lisa’s introspection that gives her an extra spark. She has allowed herself to come to terms with an important psychological concept that she speaks about on her “Enoughness” podcast.In this conversation, we discuss all the trials and tribulations along the entrepreneurial path to Lisa’s empire, how a lack of “enoughness” is the root of many people’s suffering, and how having purpose and making an impact can consume an entrepreneur. Click here to listen on iTunes - Apple Podcasts Recognitions:Founder & CEO of SheWorxFounder of The AcadeMeForbes 30 Under 30 CIO Magazine’s Top 20 Female Entrepreneurs to Watch in 2017 & 2018Red Bull’s Hero of the Year 2018Columnist at Forbes and FortuneUS Hall of Fame GymnastYale University GraduateKeynote SpeakerLeadership CoachHost of Enoughness Podcast Topics discussed in this conversation include:How Lisa began gymnastics at the age of 9The trials and tribulations of having a last name that begins with a letter at the end of the alphabetFocus, attention, and time management as a child and Lisa’s innate work ethicLoneliness as a child paying off in collegeSheWorx started in 2014Lisa’s first jobs out of college (Yale) in China, then at a hedge fundYo app raising $1 Million inspired Lisa to make a bigger impactDrive for creative ownershipStartup Institute entrepreneurship bootcampHow and why to create a point of no returnWorking next to a CEO at a development agency and how that experience shaped LisaOne-touch food order app ideaFinding a food acceleratorAttaining investment, a partner and off to the racesWhy Lisa thinks investors are hesitant to invest in single-founder companiesSteve Jobs reference – he had vision but couldn’t codeThe importance of a teamCraigslist hiringTechnical challenges and lessonsLisa’s higher purpose for the worldLisa’s coined concept of “enoughness” and the psychological differences between men and womenHow a lack of enoughness manifests in businessThe Little MermaidThe breakthrough “enoughness moment”SheWorx What inspires Lisa to do so much everydayBeing mistaken as the assistantCreating a space where women can have access to capitalTaking painful experiences and turning them into purposeLisa’s thoughts on wellness in the startup worldTime becoming more precious as an entrepreneurWellness trends vs BalanceLisa’s wellness methodsWhy entrepreneurs tend to not have hobbiesHow Lisa measures success Bio:Lisa Wang is a former US National Champion and Hall of Fame gymnast turned entrepreneur, public speaker, and executive leadership coach.· Founder & CEO of SheWorx, the leading global platform empowering 20,000+ women to build successful companies through access to top mentors and investors.· Forbes 30 Under 30 Class of 2018 in Venture Capital and CIO Magazine's Top 20 Female Entrepreneurs to Watch in 2017 and 2018, and Red Bull’s Hero of The Year in 2018. She is a columnist at Forbes and Fortune focused on driving gender parity in entrepreneurship.· Motivational Keynote Speaker headlining conferences including Mobile World Congress, World Entrepreneur Forum, Chief Innovation Officer Summit, and more.· Executive Leadership Coach and brings the tools from over a decade as an elite athlete, and entrepreneur to train leaders to own their power.· In her spare time she produces and hosts the 5-Star Enoughness podcast. Lisa is a graduate of Yale University.

Prostitution, often known as the world's oldest profession, can be traced throughout recorded history. This cliché is so often repeated it remains completely unexamined. Is prostitution really a natural by-product of human society or does it only appear in circumstances where human sexuality is limited or curtailed?In this episode we dive deep into the history of prostitution, from ancient Sumeria and its temple prostitutes to Old Testament Israeli sex workers, to Ottoman Istanbul, and finally to the red-light districts of Amsterdam. In particular we will look atHerodotus' account of the Mesopotamian ritual of sacred prostitution in which Babylonian woman had to attend the temple of Ishtar and agree to sex with any male that askedOld Testament prostitutes from Rahab—heroine of Jericho—to Gomer, a harlot whom the prophet Hosea married as an analogy of Israel's unfaithfulness to YahwehCivic brothels that existed in every medieval European cityOttoman prostitutes who used Islamic law about widows and temporary marriage to cheat the tax codeThe 19th century question over whether prostitution should be legalized and regulated to reduce syphilis or made illegal to reduce public immorality