Podcasts about b014dur7l2

In today's show, Pancham interviews Henry Daas - serial entrepreneur, entrepreneurial coach, and author of FQ: Financial Intelligence. Henry has always been an entrepreneur at heart - from starting his first company in 1991 to using his experience as a platform to coach aspiring business owners and investors. He even has self-published his book to help you learn everything you need to know about money and wealth! In today's episode, he'll share his adventures that got him from where he is today. We'll explore his entrepreneurial mindset as he shares his journey, stories that you can relate to, and his passion for coaching. He'll also discuss the difference between simply being rich and having that fulfillment in your career, questions to reflect on when making decisions, and the pressure in golden handcuffs and how you can break them. Listen and enjoy the show!   Quote: “I think it's important for you to have a real interest in what it is that you're investing in.” Timestamped Shownotes: 0:43 - Pancham introduces Henry to the show 2:08 - His entrepreneurial ventures and how his book came about 6:13 - Why you should invest in what you love (and not solely for the money!) 9:15 - The psychology of money that will help in your decisions 12:11 - How HENRYs (High Earner, Not Rich Yet) can get out of golden handcuffs 19:11 - How his book will prepare you on managing your wealth 22:19 - Taking the Leap Round 22:19 - Real estate as his first investment outside of Wall Street 24:42 - On overcoming his fear of the unknown 27:23 - Lessons learned from his real estate investment gone wrong 30:37 - Why investors should explore, start small, and learn to negotiate 33:52 - Henry's contact information 3 Key Points: Invest in what you are interested in as a way to achieve fulfillment in your life. There's a high chance of you losing interest if you're simply investing for profit. Identify what your perception of money is and how it represents to you in order to know your place when investing. Having a coach or a friend to support your decisions and listening to podcasts to learn how to diversify investments can be your first steps towards financial freedom. Get in Touch: Get all the information about Henry Daas and a copy of his book “FQ: Financial Intelligence” at fq@thegoldcollarinvestor.com Henry Daas Website - https://henrydaas.com/ The Gold Collar Investor Banking - https://thegoldcollarinvestor.com/banking/ The Gold Collar Investor Club - https://thegoldcollarinvestor.com/club/ Pancham Gupta Email - p@thegoldcollarinvestor.com Book: Never Split the Difference: Negotiating As If Your Life Depended On It by Chris Voss and Tahl Raz - https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2

In the last 90 days, Ian Tuttle purchased a trailer for $18,000 and then flipped it for about $45,000, netting a tidy $27,000 profit — and this was his very first real estate purchase! So, in this episode, we’re performing a case study of the purchase, breaking down everything Ian did to achieve this incredible sale from the moment he signed up for my group mastermind to the moment he deposited that check into his bank account. I think it’s really important to share stories from not just real estate veterans but also new players who are finding success. This industry isn’t just for giant corporations and old money. There are a lot of opportunities here, opportunities that just about anyone can take advantage of if they know how. We tell stories about: [03:25] Taco-flavored meat products [04:00] Ian’s biggest takeaway from the mastermind [06:45] How Ian found this property for such a good deal [08:30] Putting up the capital and cleaning up the property [10:20] Going from contract to close [15:25] Ian’s ongoing purchase of a second property [16:50] How fear stopped Ian from jumping into real estate sooner [20:30] Working in real estate during the pandemic [26:55] Live and flips [30:20] Preparing for future opportunities To learn more, and for the complete show notes, visit: reisociety.com (https://www.reisociety.com/) Resources: Red River Properties: www.facebook.com/RedRiverFL (https://www.facebook.com/RedRiverFL) If you aren’t using Propstream yet, you should be. Get your 7-Day Free Trial at trial.propstreampro.com/reisociety (http://trial.propstreampro.com/reisociety) Join the 30-Day Virtual Bootcamp Mastermind: www.reisociety.com/mastermind (https://www.reisociety.com/mastermind/) Never Split the Difference: Negotiating As If Your Life Depended On It (https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2) by Christopher Voss and Tahl Raz The REI Society Podcast is a production of (http://crate.media)

Can you find a "career peer" - a partner for deep work - at work? Emily Kurze and Nate Kartchner met at work and began to collaborate on projects, on personal and professional growth, and eventually came together with a business collaboration. They combine personal and business growth in their own podcast, Good. Working. Order. This week Emily Kurze and Nate Kartchner talk with Kat. Emily and Nate are colleagues and friends who met at work and now collaborate as business partners. Nate: Has been working for 15 years in marketing, mostly in digital. Emily: A recovering field biologist who has been in marketing for 9 years in program, campaign and content marketing. Nate and Emily started working together about 5 years ago. At first, their different styles caused friction: Nate had been getting results by doing his own thing, and Emily was there to instill process. They began to work more closely and effectively together over time at that workplace, and after leaving, they now collaborate on consulting and other side projects. One aspect of Nate and Emily’s effectiveness at collaboration is that difference in styles. They complement each other, which helps them with decision-making by seeing other angles. Although Nate and Emily both have full time jobs, they started a “think tank for ideas,” OSA Ventures, to work on projects that are interesting to them. Their first projects are a podcast, Good Working Order, that is growing into a podcast network, Megamouth Radio, alongside a marketing consultancy, Megamouth Marketing. Because they have “day jobs”, Nate and Emily only take consulting jobs that bring them joy and challenge. Their business has a fluid roadmap based on their availability, their interest and their passions. Nate and Emily’s podcast, Good Working Order, focuses on self-improvement and growth without sacrificing yourself. They always want to be better -- emotionally, psychologically, professionally -- and the podcast helps them make each other better. Another key to Emily and Nate’s success is that they stay in very close contact, so when they do meet, they don’t have to catch each other up. They have achieved greater depth in their relationship and in their problem solving because they don’t have to deal with minutia. Nate and Emily often do a “walk and talk,” where they talk on the phone and think while in motion. They also have a book club together, where they read the same books and then discuss them. These books now provide a common language and frame of reference for them to use when working together. This is especially true around uncomfortable conversations and negotiations; it helps formalize the space to be safe and discuss tough things. They try to end every conversation, even the tough ones, feeling better about things. Two book recommendations: * Never Split the Difference (https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2) by Chris Voss * Dare to Lead (https://daretolead.brenebrown.com) by Brene Brown Nate shares that his friendship and relationship with Emily has definitely helped him to be better, especially the way Emily pushes him and helps him think through problems. Her insights and their differences help him see things from a different side of marketing, and that creates a lot of value. Emily fashions herself a work clairvoyant -- she sees patterns in the workplace, and Nate helped her see how she could be decisive based on that gift. Like any relationship, Nate and Emily’s is built on trust, and that trust is built every day. They found that trust while working on a huge project. They didn’t want the other to be alone without resources in that project, and they came together to collaborate and support each other. “Here’s someone pulling for me as much as I’m pulling for them.” They say to look for a mirror who pushes you, stands up for you, and listens. Knowing each other’s worlds well enough to be able to cheer each other on from a knowledgeable place is what makes a career peer relationship work. When your peer knows your job, they can give you better, deeper feedback. A peer also needs to respect your work and respect and like you as a person. Nate always found Emily to be smart and respected her feedback. Howegver, someone who is just a cheerleader, and who doesn’t challenge you and hold you accountable, isn’t going to push you to make you stronger and better. As Nate and Emily have supported each other in stretching, they have really realized that they had something special together that they need to help others discover. How did they figure out how to go into business together? They had to talk about a lot of things -- money, expectations, thoughts and hopes, and vision -- and then had to keep having those conversations with each other. They had to change their vision and ideas to find product-market fit -- with themselves. Emily and Nate's projects: * Good. Working. Order. (https://www.megamouthradio.com/shows/good-working-order/) Being your best self takes work. * OSA Ventures. (OSA-Ventures.com) A digital lab exploring new concepts in marketing and growth.

Zack Friedman, author of "The Lemonade Life", Chris Voss, author of "Never Split the Difference", and Ryan Levesque, author of the best-selling book "Ask" and new book "Choose",  share with your host, Travis Chappell, their thoughts on "who you know" and "what you know."   Episode Highlights:    Zack Friedman "Who you know" has the ability to offer something to the "what you know" down the road. Be Authentic: Remember that we are all humans and connect with them in that way. Never be afraid to talk to someone, no matter how "big" they are.   Chris Voss Both!  Who you know may not matter if you don't know anything. What you know must fit the situation. Why preparation and research are so important to your presentation. Why it's critical to speak to small groups in the same way you address large groups. Building another person's vision.   Ryan Levesque Who you know: It's impossible to amass all the knowledge you need in business. Successful people have "one move."  An Example of finding a mentor: the connection with Dr. Glenn Livingston.   3 Key Points:   Authenticity is the key to building meaningful relationships. Who you know doesn't matter unless what you know brings value to the conversation. Become your mentor's #1 student.     Tweetable Quotes: “What value can I offer to someone else, how can I create impact, how can I make their life better?” - Zack Friedman “Who you know is useless without understanding the value of the introduction.” - Chris Voss “My one move is to find a mentor in the space that I want to be in, and I become my mentors #1 student.” - Ryan Levesque Resources Mentioned: Visit Travis’ website at Buildyournetwork.co (http://www.buildyournetwork.co/) Learn more about mentorships and masterminds for FREE at freemmcourse.com/enroll (http://www.freemmcourse.com/join) Get your tickets for Travis new live event in Vegas at www.bynlive.com (http://www.bynlive.com) “The Lemonade Life” (https://www.amazon.com/Lemonade-Life-Success-Happiness-Anything/dp/140021159X) by Zack Friedman “Never Split the Difference” (https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2) by Chris Voss “Choose” (https://www.amazon.com/Choose-Important-Decision-Starting-Business/dp/1401957471) by Ryan Levesque Download the Himalaya App in the Google Play (https://play.google.com/store/apps/details?id=com.ximalaya.ting.himalaya&hl=en_US) Get more free content from Travis at threenetworkingsecrets.com (http://threenetworkingsecrets.com) For information regarding your data privacy, visit acast.com/privacy (https://www.acast.com/privacy)

Recorded at Øredev 2018, Fredrik talks to Judy Rees. We start from Judy’s presentation Getting them to get it and discuss the challenges of really listening, communication, and the how the clean language technique can help you both understand others better, and get your own ideas across better as well. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Øredev 2018 Judy Rees Judy’s presentations at Øredev 2018 - Getting them to get it, and Overcoming the difficulties of remote meetings Clean language Woody Zuill Judy on Youtube Olaf Lewitz Chris Voss Never split the difference - Chris' book David Grove - discoverer(?) of clean language Teletext Arrival Caitlin Walker Penny Tompkins and James Lawley cleanlanguage.co.uk learncleanlanguage.com Titles I would present you as a Jedi master Jedi mistress A master listener As a result of paying attention Listening has such a low status in the world Don’t talk and don’t think about talking It’s against our programming to pay complete attention Paying attention is an active pursuit A question is a much more precise tool The nearest thing the FBI have to a Jedi mind trick The tools to reason about conversation See through the leaves Enabling them to heal themselves It’s designed for use with humans People are really rubbish at saying what they want in all kinds of domains of their lives Humanity is currently the limit The modeling brain Their model of David’s model

Discipline is an essential element to obtain freedom. On this new podcast, Ken Greene explains how discipline brings you more freedom in all aspects of life. Ken and Tammi revisit personal experiences where this concept was put to the test, so stay tuned to learn more about this topic! Ken Greene transitioned from being a Professional Engineer (P.E.) to the “Engineer of Finance.” His goal is to help people become financially independent and help them earn better yields with less risk by investing Off Wall Street.   Links and Resources from this Episode For resources and additional information of this episode go to http://engineeroffinance.com Connect with Ken Greene http://engineeroffinance.com Office 775-624-8839 https://www.linkedin.com/in/ken-greene https://business.facebook.com/GreeneFinance https://www.amazon.es/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2   Show Notes Talking about the financial symposium: Summit for advisors - 2:04 Struggling with the creation of a savings strategy - 2:36 With discipline comes the word "freedom" - 6:08 Talking about discipline at home - 6:50 Talking about the book: Never Split The Difference - 14:38 The independence and freedom of an individual - 16:06 You don't know your parents' love until you have a child - 17:00 With a little bit of discipline, you'll have freedom - 19:00 A technique to help people create discipline - 20:24 Pay yourself first! - 22:08 Ken tells us the next podcast topics - 28:13   Review, Subscribe and Share If you like what you hear please leave a review by clicking here Make sure you are subscribed to the podcast so you get the latest episodes. Subscribe with Apple Podcasts Follow on Spotify Subscribe with Stitcher Subscribe with RSS

For Justin Colby, a wildly successful real estate investor from California who's flipped well over $100 million in real estate, success didn't come easy. In fact, when Colby first decided to enter into the real estate industry in 2007, he had just lost his home to a foreclosure, his car was repossessed and he was living on a friend's couch in San Francisco. He was a victim to the market frenzy and bubbling valuations that had him in way above his head and he simply let it all go.   Contact Justin Info@thescienceofflipping.com   Content Mentioned: Never split the difference https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2   Power of Now   The Secret   Tony Robbins   Connect with Ola www.instagram.com/oladantis Find me using @OlaDantis for all social media Send me a DM when you follow so I can say hi!

Panel: Aimee Knight AJ O’Neal Charles Max Wood Special Guest: Gil Tayar In this episode, the panel talks with Gil Tayar who is currently residing in Tel Aviv and is a software engineer. He is currently the Senior Architect at Applitools in Israel. The panel and the guest talk about the different types of tests and when/how one is to use a certain test in a particular situation. They also mention Node, React, Selenium, Puppeteer, and much more! Show Topics: 0:00 – Advertisement: KENDO UI 0:35 – Chuck: Our panel is AJ, Aimee, myself – and our special guest is Gil Tayar. Tell us why you are famous! 1:13 – Gil talks about where he resides and his background.  2:27 – Chuck: What is the landscape like now with testing and testing tools now? 2:39 – Guest: There is a huge renaissance with the JavaScript community. Testing has moved forward in the frontend and backend. Today we have lots of testing tools.  We can do frontend testing that wasn’t possible 5 years ago. The major change was React. The guest talks about Node, React, tools, and more! 4:17 – Aimee: I advocate for tests and testing. There is a grey area though...how do you treat that? If you have to get something into production, but it’s not THE thing to get into production, does that fall into product or...what? 5:02 – Guest: We decided to test everything in the beginning. We actually cam through and did that and since then I don’t think I can use the right code without testing. There are a lot of different situations, though, to consider. The guest gives hypothetical situations that people could face. 6:27 – Aimee. 6:32 – Guest: The horror to changing code without tests, I don’t know, I haven’t done that for a while. You write with fear in your heart. Your design is driven by fear, and not what you think is right. In the beginning don’t write those tests, but... 7:22 – Aimee: I totally agree and I could go on and on and on. 7:42 – Panel: I want to do tests when I know they will create value. I don’t want to do it b/c it’s a mundane thing. Secondly, I find that some times I am in a situation where I cannot write the test b/c I would have to know the business logic is correct. I am in this discovery mode of what is the business logic? I am not just building your app. I guess I just need advice in this area, I guess. 8:55 – Guest gives advice to panelist’s question. He mentions how there are two schools of thought. 10:20 – Guest: Don’t mock too much. 10:54 – Panel: Are unit tests the easiest? I just reach for unit testing b/c it helps me code faster. But 90% of my code is NOT that. 11:18 – Guest: Exactly! Most of our test is glue – gluing together a bunch of different stuff! Those are best tested as a medium-sized integration suite. 12:39 – Panel: That seems like a lot of work, though! I loathe the database stuff b/c they don’t map cleanly. I hate this database stuff. 13:06 – Guest: I agree, but don’t knock the database, but knock the level above the database. 13:49 – Guest: Yes, it takes time! Building the script and the testing tools, but when you have it then adding to it is zero time. Once you are in the air it’s smooth sailing. 14:17 – Panel: I guess I can see that. I like to do the dumb-way the first time. I am not clear on the transition. 14:47 – Guest: Write the code, and then write the tests. The guest gives a hypothetical situation on how/when to test in a certain situation. 16:25 – Panel: Can you talk about that more, please? 16:50 – Guest: Don’t have the same unit – do browser and business logic stuff separated. The real business logic stuff needs to be above that level. First principle is separation of concerns. 18:04 – Panel talks about dependency interjection and asks a question. 18:27 – Guest: What I am talking about very, very light inter-dependency interjection. 19:19 – Panel: You have a main function and you are doing requires in the main function. You are passing the pieces of that into the components that need it. 19:44 – Guest: I only do it when it’s necessary; it’s not a religion for me. I do it only for those layers that I know will need to be mocked; like database layers, etc. 20:09 – Panel. 20:19 – Guest: It’s taken me 80 years to figure out, but I have made plenty of mistakes a long the way. A test should run for 2-5 minutes max for package. 20:53 – Panel: What if you have a really messy legacy system? How do you recommend going into that? Do you write tests for things that you think needs to get tested? 21:39 – Guest answers the question and mentions Selenium! 24:27 – Panel: I like that approach. 24:35 – Chuck: When you say integration test what do you mean? 24:44 – Guest: Integration tests aren’t usually talked about. For most people it’s tests that test the database level against the database. For me, the integration tests are taking a set of classes as they are in the application and testing them together w/o the...so they can run in millisecond time. 26:54 – Advertisement – Sentry.io 27:52 – Chuck: How much do the tools matter? 28:01 – Guest: The revolutions matter. Whether you use Jasmine or Mocha or whatever I don’t think it matters. The tests matter not the tools. 28:39 – Aimee: Yes and no. I think some tools are outdated. 28:50 – Guest: I got a lot of flack about my blog where I talk about Cypress versus Selenium. I will never use Jasmine. In the end it’s the 29:29 – Aimee: I am curious would you be willing to expand on what the Selenium folks were saying about Puppeteer and others may not provide? 29:54 – Guest: Cypress was built for frontend developers. They don’t care about cross browser, and they tested in Chrome. Most browsers are typically the same. Selenium was built with the QA mindset – end to end tests that we need to do cross browser. The guest continues with this topic. 30:54 – Aimee mentions Cypress. 31:08 – Guest: My guessing is that their priority is not there. I kind of agree with them. 31:21 – Aimee: I think they are focusing on mobile more. 31:24 – Guest: I think cross browser testing is less of an issue now. There is one area that is important it’s the visual area! It’s important to test visually across these different browsers. 32:32 – Guest: Selenium is a Swiss knife – it can do everything. 33:32 – Chuck: I am thinking about different topics to talk about. I haven’t used Puppeteer. What’s that about? 33:49 – Guest: Puppeteer is much more like Selenium. The reason why it’s great is b/c Puppeteer will always be Google Chrome. 35:42 – Chuck: When should you be running your tests? I like to use some unit tests when I am doing my development but how do you break that down? 36:06 – Guest. 38:30 – Chuck: You run tests against production? 38:45 – Guest: Don’t run tests against production...let me clarify! 39:14 – Chuck. 39:21 – Guest: When I am talking about integration testing in the backend... 40:37 – Chuck asks a question. 40:47 – Guest: I am constantly running between frontend and backend. I didn’t know how to run tests for frontend. I had to invent a new thing and I “invented” the package JS DONG. It’s an implementation of Dong in Node. I found out that I wasn’t the only one and that there were others out there, too. 43:14 – Chuck: Nice! You talked in the prep docs that you urged a new frontend developer to not run the app in the browser for 2 months? 43:25 – Guest: Yeah, I found out that she was running the application...she said she knew how to write tests. I wanted her to see it my way and it probably was a radical train-of-thought, and that was this... 44:40 – Guest: Frontend is so visual. 45:12 – Chuck: What are you working on now? 45:16 – Guest: I am working with Applitools and I was impressed with what they were doing. The guest goes into further detail. 46:08 – Guest: Those screenshots are never the same. 48:36 – Panel: It’s...comparing the output to the static site to the... 48:50 – Guest: Yes, that static site – if you have 30 pages in your app – most of those are the same. We have this trick where we don’t upload it again and again. Uploading the whole static site is usually very quick. The second thing is we don’t wait for the results. We don’t wait for the whole rendering and we continue with the tests. 50:28 – Guest: I am working mostly (right now) in backend. 50:40 – Chuck: Anything else? Picks! 50:57 – Advertisement: Get A Coder Job! END – Advertisement: CacheFly! Links: JavaScript React Elixir Node.js Puppeteer Cypress SeleniumHQ Article – Ideas.Ted.Com Book: Never Split the Difference Applitools Guest’s Blog Article about Cypress vs. Selenium Gil’s Twitter Gil’s Medium Gil’s LinkedIn Sponsors: Kendo UI Sentry CacheFly Picks: Aimee How Showing Vulnerability Helps Build a Stronger Team AJ Never Split the Difference Project - TeleBit Charles Monster Hunter International Metabase Gil Cat Zero The Origin of Consciousness in the Breakdown of the Bicameral Mind

Panel: Aimee Knight AJ O’Neal Charles Max Wood Special Guest: Gil Tayar In this episode, the panel talks with Gil Tayar who is currently residing in Tel Aviv and is a software engineer. He is currently the Senior Architect at Applitools in Israel. The panel and the guest talk about the different types of tests and when/how one is to use a certain test in a particular situation. They also mention Node, React, Selenium, Puppeteer, and much more! Show Topics: 0:00 – Advertisement: KENDO UI 0:35 – Chuck: Our panel is AJ, Aimee, myself – and our special guest is Gil Tayar. Tell us why you are famous! 1:13 – Gil talks about where he resides and his background.  2:27 – Chuck: What is the landscape like now with testing and testing tools now? 2:39 – Guest: There is a huge renaissance with the JavaScript community. Testing has moved forward in the frontend and backend. Today we have lots of testing tools.  We can do frontend testing that wasn’t possible 5 years ago. The major change was React. The guest talks about Node, React, tools, and more! 4:17 – Aimee: I advocate for tests and testing. There is a grey area though...how do you treat that? If you have to get something into production, but it’s not THE thing to get into production, does that fall into product or...what? 5:02 – Guest: We decided to test everything in the beginning. We actually cam through and did that and since then I don’t think I can use the right code without testing. There are a lot of different situations, though, to consider. The guest gives hypothetical situations that people could face. 6:27 – Aimee. 6:32 – Guest: The horror to changing code without tests, I don’t know, I haven’t done that for a while. You write with fear in your heart. Your design is driven by fear, and not what you think is right. In the beginning don’t write those tests, but... 7:22 – Aimee: I totally agree and I could go on and on and on. 7:42 – Panel: I want to do tests when I know they will create value. I don’t want to do it b/c it’s a mundane thing. Secondly, I find that some times I am in a situation where I cannot write the test b/c I would have to know the business logic is correct. I am in this discovery mode of what is the business logic? I am not just building your app. I guess I just need advice in this area, I guess. 8:55 – Guest gives advice to panelist’s question. He mentions how there are two schools of thought. 10:20 – Guest: Don’t mock too much. 10:54 – Panel: Are unit tests the easiest? I just reach for unit testing b/c it helps me code faster. But 90% of my code is NOT that. 11:18 – Guest: Exactly! Most of our test is glue – gluing together a bunch of different stuff! Those are best tested as a medium-sized integration suite. 12:39 – Panel: That seems like a lot of work, though! I loathe the database stuff b/c they don’t map cleanly. I hate this database stuff. 13:06 – Guest: I agree, but don’t knock the database, but knock the level above the database. 13:49 – Guest: Yes, it takes time! Building the script and the testing tools, but when you have it then adding to it is zero time. Once you are in the air it’s smooth sailing. 14:17 – Panel: I guess I can see that. I like to do the dumb-way the first time. I am not clear on the transition. 14:47 – Guest: Write the code, and then write the tests. The guest gives a hypothetical situation on how/when to test in a certain situation. 16:25 – Panel: Can you talk about that more, please? 16:50 – Guest: Don’t have the same unit – do browser and business logic stuff separated. The real business logic stuff needs to be above that level. First principle is separation of concerns. 18:04 – Panel talks about dependency interjection and asks a question. 18:27 – Guest: What I am talking about very, very light inter-dependency interjection. 19:19 – Panel: You have a main function and you are doing requires in the main function. You are passing the pieces of that into the components that need it. 19:44 – Guest: I only do it when it’s necessary; it’s not a religion for me. I do it only for those layers that I know will need to be mocked; like database layers, etc. 20:09 – Panel. 20:19 – Guest: It’s taken me 80 years to figure out, but I have made plenty of mistakes a long the way. A test should run for 2-5 minutes max for package. 20:53 – Panel: What if you have a really messy legacy system? How do you recommend going into that? Do you write tests for things that you think needs to get tested? 21:39 – Guest answers the question and mentions Selenium! 24:27 – Panel: I like that approach. 24:35 – Chuck: When you say integration test what do you mean? 24:44 – Guest: Integration tests aren’t usually talked about. For most people it’s tests that test the database level against the database. For me, the integration tests are taking a set of classes as they are in the application and testing them together w/o the...so they can run in millisecond time. 26:54 – Advertisement – Sentry.io 27:52 – Chuck: How much do the tools matter? 28:01 – Guest: The revolutions matter. Whether you use Jasmine or Mocha or whatever I don’t think it matters. The tests matter not the tools. 28:39 – Aimee: Yes and no. I think some tools are outdated. 28:50 – Guest: I got a lot of flack about my blog where I talk about Cypress versus Selenium. I will never use Jasmine. In the end it’s the 29:29 – Aimee: I am curious would you be willing to expand on what the Selenium folks were saying about Puppeteer and others may not provide? 29:54 – Guest: Cypress was built for frontend developers. They don’t care about cross browser, and they tested in Chrome. Most browsers are typically the same. Selenium was built with the QA mindset – end to end tests that we need to do cross browser. The guest continues with this topic. 30:54 – Aimee mentions Cypress. 31:08 – Guest: My guessing is that their priority is not there. I kind of agree with them. 31:21 – Aimee: I think they are focusing on mobile more. 31:24 – Guest: I think cross browser testing is less of an issue now. There is one area that is important it’s the visual area! It’s important to test visually across these different browsers. 32:32 – Guest: Selenium is a Swiss knife – it can do everything. 33:32 – Chuck: I am thinking about different topics to talk about. I haven’t used Puppeteer. What’s that about? 33:49 – Guest: Puppeteer is much more like Selenium. The reason why it’s great is b/c Puppeteer will always be Google Chrome. 35:42 – Chuck: When should you be running your tests? I like to use some unit tests when I am doing my development but how do you break that down? 36:06 – Guest. 38:30 – Chuck: You run tests against production? 38:45 – Guest: Don’t run tests against production...let me clarify! 39:14 – Chuck. 39:21 – Guest: When I am talking about integration testing in the backend... 40:37 – Chuck asks a question. 40:47 – Guest: I am constantly running between frontend and backend. I didn’t know how to run tests for frontend. I had to invent a new thing and I “invented” the package JS DONG. It’s an implementation of Dong in Node. I found out that I wasn’t the only one and that there were others out there, too. 43:14 – Chuck: Nice! You talked in the prep docs that you urged a new frontend developer to not run the app in the browser for 2 months? 43:25 – Guest: Yeah, I found out that she was running the application...she said she knew how to write tests. I wanted her to see it my way and it probably was a radical train-of-thought, and that was this... 44:40 – Guest: Frontend is so visual. 45:12 – Chuck: What are you working on now? 45:16 – Guest: I am working with Applitools and I was impressed with what they were doing. The guest goes into further detail. 46:08 – Guest: Those screenshots are never the same. 48:36 – Panel: It’s...comparing the output to the static site to the... 48:50 – Guest: Yes, that static site – if you have 30 pages in your app – most of those are the same. We have this trick where we don’t upload it again and again. Uploading the whole static site is usually very quick. The second thing is we don’t wait for the results. We don’t wait for the whole rendering and we continue with the tests. 50:28 – Guest: I am working mostly (right now) in backend. 50:40 – Chuck: Anything else? Picks! 50:57 – Advertisement: Get A Coder Job! END – Advertisement: CacheFly! Links: JavaScript React Elixir Node.js Puppeteer Cypress SeleniumHQ Article – Ideas.Ted.Com Book: Never Split the Difference Applitools Guest’s Blog Article about Cypress vs. Selenium Gil’s Twitter Gil’s Medium Gil’s LinkedIn Sponsors: Kendo UI Sentry CacheFly Picks: Aimee How Showing Vulnerability Helps Build a Stronger Team AJ Never Split the Difference Project - TeleBit Charles Monster Hunter International Metabase Gil Cat Zero The Origin of Consciousness in the Breakdown of the Bicameral Mind

Panel: Aimee Knight AJ O’Neal Charles Max Wood Special Guest: Gil Tayar In this episode, the panel talks with Gil Tayar who is currently residing in Tel Aviv and is a software engineer. He is currently the Senior Architect at Applitools in Israel. The panel and the guest talk about the different types of tests and when/how one is to use a certain test in a particular situation. They also mention Node, React, Selenium, Puppeteer, and much more! Show Topics: 0:00 – Advertisement: KENDO UI 0:35 – Chuck: Our panel is AJ, Aimee, myself – and our special guest is Gil Tayar. Tell us why you are famous! 1:13 – Gil talks about where he resides and his background.  2:27 – Chuck: What is the landscape like now with testing and testing tools now? 2:39 – Guest: There is a huge renaissance with the JavaScript community. Testing has moved forward in the frontend and backend. Today we have lots of testing tools.  We can do frontend testing that wasn’t possible 5 years ago. The major change was React. The guest talks about Node, React, tools, and more! 4:17 – Aimee: I advocate for tests and testing. There is a grey area though...how do you treat that? If you have to get something into production, but it’s not THE thing to get into production, does that fall into product or...what? 5:02 – Guest: We decided to test everything in the beginning. We actually cam through and did that and since then I don’t think I can use the right code without testing. There are a lot of different situations, though, to consider. The guest gives hypothetical situations that people could face. 6:27 – Aimee. 6:32 – Guest: The horror to changing code without tests, I don’t know, I haven’t done that for a while. You write with fear in your heart. Your design is driven by fear, and not what you think is right. In the beginning don’t write those tests, but... 7:22 – Aimee: I totally agree and I could go on and on and on. 7:42 – Panel: I want to do tests when I know they will create value. I don’t want to do it b/c it’s a mundane thing. Secondly, I find that some times I am in a situation where I cannot write the test b/c I would have to know the business logic is correct. I am in this discovery mode of what is the business logic? I am not just building your app. I guess I just need advice in this area, I guess. 8:55 – Guest gives advice to panelist’s question. He mentions how there are two schools of thought. 10:20 – Guest: Don’t mock too much. 10:54 – Panel: Are unit tests the easiest? I just reach for unit testing b/c it helps me code faster. But 90% of my code is NOT that. 11:18 – Guest: Exactly! Most of our test is glue – gluing together a bunch of different stuff! Those are best tested as a medium-sized integration suite. 12:39 – Panel: That seems like a lot of work, though! I loathe the database stuff b/c they don’t map cleanly. I hate this database stuff. 13:06 – Guest: I agree, but don’t knock the database, but knock the level above the database. 13:49 – Guest: Yes, it takes time! Building the script and the testing tools, but when you have it then adding to it is zero time. Once you are in the air it’s smooth sailing. 14:17 – Panel: I guess I can see that. I like to do the dumb-way the first time. I am not clear on the transition. 14:47 – Guest: Write the code, and then write the tests. The guest gives a hypothetical situation on how/when to test in a certain situation. 16:25 – Panel: Can you talk about that more, please? 16:50 – Guest: Don’t have the same unit – do browser and business logic stuff separated. The real business logic stuff needs to be above that level. First principle is separation of concerns. 18:04 – Panel talks about dependency interjection and asks a question. 18:27 – Guest: What I am talking about very, very light inter-dependency interjection. 19:19 – Panel: You have a main function and you are doing requires in the main function. You are passing the pieces of that into the components that need it. 19:44 – Guest: I only do it when it’s necessary; it’s not a religion for me. I do it only for those layers that I know will need to be mocked; like database layers, etc. 20:09 – Panel. 20:19 – Guest: It’s taken me 80 years to figure out, but I have made plenty of mistakes a long the way. A test should run for 2-5 minutes max for package. 20:53 – Panel: What if you have a really messy legacy system? How do you recommend going into that? Do you write tests for things that you think needs to get tested? 21:39 – Guest answers the question and mentions Selenium! 24:27 – Panel: I like that approach. 24:35 – Chuck: When you say integration test what do you mean? 24:44 – Guest: Integration tests aren’t usually talked about. For most people it’s tests that test the database level against the database. For me, the integration tests are taking a set of classes as they are in the application and testing them together w/o the...so they can run in millisecond time. 26:54 – Advertisement – Sentry.io 27:52 – Chuck: How much do the tools matter? 28:01 – Guest: The revolutions matter. Whether you use Jasmine or Mocha or whatever I don’t think it matters. The tests matter not the tools. 28:39 – Aimee: Yes and no. I think some tools are outdated. 28:50 – Guest: I got a lot of flack about my blog where I talk about Cypress versus Selenium. I will never use Jasmine. In the end it’s the 29:29 – Aimee: I am curious would you be willing to expand on what the Selenium folks were saying about Puppeteer and others may not provide? 29:54 – Guest: Cypress was built for frontend developers. They don’t care about cross browser, and they tested in Chrome. Most browsers are typically the same. Selenium was built with the QA mindset – end to end tests that we need to do cross browser. The guest continues with this topic. 30:54 – Aimee mentions Cypress. 31:08 – Guest: My guessing is that their priority is not there. I kind of agree with them. 31:21 – Aimee: I think they are focusing on mobile more. 31:24 – Guest: I think cross browser testing is less of an issue now. There is one area that is important it’s the visual area! It’s important to test visually across these different browsers. 32:32 – Guest: Selenium is a Swiss knife – it can do everything. 33:32 – Chuck: I am thinking about different topics to talk about. I haven’t used Puppeteer. What’s that about? 33:49 – Guest: Puppeteer is much more like Selenium. The reason why it’s great is b/c Puppeteer will always be Google Chrome. 35:42 – Chuck: When should you be running your tests? I like to use some unit tests when I am doing my development but how do you break that down? 36:06 – Guest. 38:30 – Chuck: You run tests against production? 38:45 – Guest: Don’t run tests against production...let me clarify! 39:14 – Chuck. 39:21 – Guest: When I am talking about integration testing in the backend... 40:37 – Chuck asks a question. 40:47 – Guest: I am constantly running between frontend and backend. I didn’t know how to run tests for frontend. I had to invent a new thing and I “invented” the package JS DONG. It’s an implementation of Dong in Node. I found out that I wasn’t the only one and that there were others out there, too. 43:14 – Chuck: Nice! You talked in the prep docs that you urged a new frontend developer to not run the app in the browser for 2 months? 43:25 – Guest: Yeah, I found out that she was running the application...she said she knew how to write tests. I wanted her to see it my way and it probably was a radical train-of-thought, and that was this... 44:40 – Guest: Frontend is so visual. 45:12 – Chuck: What are you working on now? 45:16 – Guest: I am working with Applitools and I was impressed with what they were doing. The guest goes into further detail. 46:08 – Guest: Those screenshots are never the same. 48:36 – Panel: It’s...comparing the output to the static site to the... 48:50 – Guest: Yes, that static site – if you have 30 pages in your app – most of those are the same. We have this trick where we don’t upload it again and again. Uploading the whole static site is usually very quick. The second thing is we don’t wait for the results. We don’t wait for the whole rendering and we continue with the tests. 50:28 – Guest: I am working mostly (right now) in backend. 50:40 – Chuck: Anything else? Picks! 50:57 – Advertisement: Get A Coder Job! END – Advertisement: CacheFly! Links: JavaScript React Elixir Node.js Puppeteer Cypress SeleniumHQ Article – Ideas.Ted.Com Book: Never Split the Difference Applitools Guest’s Blog Article about Cypress vs. Selenium Gil’s Twitter Gil’s Medium Gil’s LinkedIn Sponsors: Kendo UI Sentry CacheFly Picks: Aimee How Showing Vulnerability Helps Build a Stronger Team AJ Never Split the Difference Project - TeleBit Charles Monster Hunter International Metabase Gil Cat Zero The Origin of Consciousness in the Breakdown of the Bicameral Mind

Cedric went from no deals to closing on his first ever real estate wholesaling deal. He realised that his first foray into entrepreneurship wasn't going as he had imagined, so he quickly pivoted into Real Estate and he seeing some momentum and traction.   Learn more at: dwellynn.com/invest   Contact Cedric: https://www.instagram.com/cedric.andrew16/     Content mentioned: Never split the difference https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2   Follow Ola www.instagram.com/oladantis @OlaDantis for all social media Send me a DM when you follow so I can say hi!

On this episode, Julien Meyer & Alfredo Castro discuss..... Topics discussed: MBA's...are they worth it?!? What do mattress startups and Blue Apron have in common? Riots at G-20 summit Links mentioned in this episode: https://www.dmagazine.com/business-economy/2017/07/att-targets-iot-startups-with-new-200m-venture-fund/ https://www.usatoday.com/story/money/2017/07/07/sears-holdings-kmart-store-closures/459277001/ https://techcrunch.com/2017/07/07/waymo-drops-patent-claims/ Never Split the Difference by Christopher Voss : https://www.amazon.com/Never-Split-Difference-Negotiating-Depended-ebook/dp/B014DUR7L2/ref=sr_1_1?s=books&ie=UTF8&qid=1499482368&sr=1-1&refinements=p_27%3AChris+Voss This podcast is powered by ZenCast.fm