Podcasts about book profit first

Download David's Free eBook 'Profit First' & Cheat Sheet: simplecfo.com/JC -- In this episode of The Science of Flipping, I sit down with David Richter, author of Profit First for Real Estate Investors and founder of Simple CFO. If you've ever felt like you're making money but still feel broke, you're not alone—I've been there too. David breaks down why traditional money management fails real estate investors and how the Profit First system ensures you actually keep more of what you earn. We talk about setting up the right bank accounts, avoiding costly tax mistakes, and structuring your finances like a true CEO. Whether you're just starting out or running a multi-million dollar business, this episode will give you the tools to take control of your cash flow and build real wealth.   -- Download the Free eBook & Cheat Sheet: simplecfo.com/JC Follow David on Social Media: @SimpleCFO Visit His Website: SimpleCFO.com Read the Book: Profit First for Real Estate Investors (Available on Amazon & other platforms) Hire Simple CFO Services: If you need hands-on financial help, visit SimpleCFO.com to work with David's team. --   The #1 training and coaching system to launch, grow, and scale your investing business! 

On this episode of Money Talk With Tiff, Tiffany Grant dives into the world of minority business certifications and government contracting with special guest, Susanne Mariga. Susanne brings her expert insights on how these certifications can benefit minority and women-owned businesses, and shares actionable advice on how to navigate the often complex certification process. Listen in to learn about the various levels of certifications, the benefits they offer, and how to leverage them for government contracts. Additionally, Susanne discusses best practices, potential pitfalls, and the importance of building relationships in the business world.Check out the full show notes: https://moneytalkwitht.com/podcast-show-notes/minority-business-certificationKey PointsIntroduction to Minority Business Enterprise (MBE) and Women Business Enterprise (WBE) certificationsDifferent levels of certifications: city, state, federal, and private sectorThe certification process and its benefits, including educational programs, funding opportunities, and networking eventsExamples of real-world benefits, such as access to grants during the COVID-19 pandemicUnderstanding government contracting terminology and the role of certifications in securing contractsSteps for finding and bidding on government contractsThe critical importance of understanding costs and realistic pricing for successful bidsImportance of leveraging unique skills and expertise to stand out in competitive environmentsCollaboration and partnership strategies for winning contractsGet Susanne's Book: Profit First for Minority Business Enterprises by Susanne MarigaA dollar from every copy sold supports the education of girls in Zimbabwe through a partnership with Hope Worldwide.Connect with SusanneLinkedIn: Susanne Mariga LinkedIn ProfileFollow Tiffany GrantWebsite: Money Talk With TiffSocial Media: @MoneyTalkWithT on all platformsFollow Tiffany Grant for more financial wisdom and join the Money Talk with Tiff community to stay informed and empowered on your financial journey.Support this PodcastCopyright 2024 Tiffany Grant

 Do you know your numbers?  In the last few weeks 3 conversations, one with a client, one with a dear friend who also owns an online business and another friend who crossed the million dollar mark in 2023 and has not paid herself a salary the whole year, had me on fire for this episode. If you don't know your numbers: 1- you are most likely making decisions in your biz from emotion and not data. You cannot grow like that…you will always be blindsided by your believes instead of what is TRULY happening in your business. 2- Your pricing as a service provider DEPENDS in the fact that you understand your cost, your hourly rate, so eventually you can start delegating. ( I know you probably hate that word right now, because you think you cannot afford it….that is because you dont know you numbers!) Reading the Book Profit First 4 years ago changed my life and the trajectory of my business it invited me to re-wire and reshape my relationship with Money and go deep in the Money trauma I was carrying. It MADE ME look at my money. Main topics in this episode : 

What if you could implement a cash management system today that guarantees profitability, automatically sets aside money for tax season, and ensures you don't overspend on expenses? In this episode, Hala is joined by Mike Michalowicz to break down Profit First, the cash management system that has helped hundreds of thousands of small business owners increase their profits, or generate a profit from day one. Mike Michalowicz is the entrepreneur behind three multimillion-dollar companies and is an author of business books for entrepreneurs and small business owners like Profit First, Clockwork, The Pumpkin Plan, Fix This Next, and Get Different. Mike is a former small business columnist for The Wall Street Journal and regularly travels the globe as an entrepreneurial advocate. He became a business author with a clear mission: eradicate entrepreneurial poverty.  In this episode, Hala and Mike will discuss: - What happens when you constrain a resource - How to think of profit as a habit - The value of practicing fund preallocation - The five bank accounts every small business owner needs - The difference between an ownership salary and profit - How much money should you put toward profit? - Why you should compress your operating expenses - How to pay off debt - How Relay can help you implement profit first with ease - And other topics… Mike Michalowicz is the creator of Profit First, which is used by hundreds of thousands of companies across the globe to drive profit. Today, Mike leads two new multimillion-dollar ventures, as he tests his latest business research for his books. He is a former small business columnist for The Wall Street Journal and a business makeover specialist on MSNBC. Mike is a popular main-stage keynote speaker on innovative entrepreneurial topics; and is the author of Get Different, Fix This Next, Clockwork, Profit First, Surge, The Pumpkin Plan, and The Toilet Paper Entrepreneur. Fabled author Simon Sinek deemed Mike Michalowicz “…the top contender for the patron saint of entrepreneurs.” Resources Mentioned: Relay: https://relayfi.com/profiting Mike's Book Profit First: https://mikemichalowicz.com/profit-first/ Profit First Instant Assessment: https://s3.amazonaws.com/ProfitFirst/PF-InstantAssessment.pdf  LinkedIn Secrets Masterclass, Have Job Security For Life: Use code ‘podcast' for 30% off at yapmedia.io/course. More About Young and Profiting Download Transcripts - youngandprofiting.com   Get Sponsorship Deals - youngandprofiting.com/sponsorships Leave a Review - ratethispodcast.com/yap Watch Videos - youtube.com/c/YoungandProfiting Follow Hala Taha LinkedIn - linkedin.com/in/htaha/ Instagram - instagram.com/yapwithhala/ TikTok - tiktok.com/@yapwithhala Twitter - twitter.com/yapwithhala Learn more about YAP Media Agency Services - yapmedia.io/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Hello listeners! This week we have real estate investor David Richter joining us, author of the book Profit First for Real Estate Investing. With over 10 years experience and 850 deals under his belt, David is an expert at helping real estate investors actually keep their profits instead of losing them to the endless deal-to-deal cycle. Many of us got into real estate to escape the rat race, but profit leakage can trap us right back in it if we aren't careful.In this episode, David will break down the fundamentals of profit & loss statements, balance sheets, and implementing financial systems that lead to true profitability. We'll also discuss actionable steps you can start taking today to get your books in order and stop leaving money on the table. Whether you're new to real estate investing or a seasoned pro, David's advice will help transform your business.Let's dive in to unlock the secrets of maximizing your real estate profits! David Richter is an active real estate investor who has been essential in closing over 850 deals over the last 10 years. He has experience with wholesale, turnkey, BRRRR, owner finance, rentals, lease options, and any other exit strategy you can think of. While growing and building a real estate business from 5 to over 25 deals a month, he realized that as much money was coming in, it was all going right out the door. With the unique opportunity of being in every seat as a real estate investor, he found a calling in the company's finance seat to help businesses see where their money really went.David has helped real estate companies completely turn around from going out of business to building cash reserves by using the Profit First cash flow system. He has been featured onBiggerpockets, Real Estate Disruptors with Steve Trang, and many other podcasts, shows, and stages.To help even more people, he wrote Profit First for Real Estate Investing - a derivative of the original Profit First by Mike Michalowicz that is tailored specifically to Real Estate Investors.His goal is to completely transform the Real Estate Investing industry by helping real estate investors make and KEEP more money in their businesses. As the founder and owner of SimpleCFO Solutions, he wants to bring investors true financial clarity and freedom and help every investor stop living deal to deal.Resources:• Website: simplecfo.com• Book: Profit First for Real Estate Investing by David Richter• LinkedIn: Simple CFO Solutions• Facebook: The Simple CFO• Exclusive Gift for TFV Listeners: simplecfo.com/gift • #STRShareSunday: @theidyllolhouseThanks for Visiting is produced by Crate Media.Mentioned in this episode:TFVCON | Join us September 24-26 in Columbus, Ohio for TFV CON 2023!Grab your spot now at tfvcon.com.Breezeway | Breezeway is our favorite all-in-one property operations and messaging app. We use Breezeway to standardize our cleaning, maintenance, and inspection processes and automate guest messaging to deliver a quality experience. Their photo checklists make it easy to verify detailed work in...

Welcome back to Brave & Well, friends! In this week's informative and helpful episode, I've invited Profit First expert Julie Herres to join me on the podcast.Julie is the founder of GreenOak Accounting and has helped hundreds of private practice owners gain financial freedom. She's an accountant, consultant, speaker, author of Profit First for Therapists and host of the Therapy for Your Money podcast.Together, we discuss Julie's experiences helping practices apply the Profit First model and why therapists should embrace it.Tune in as we explore:What Profit First is and isn'tHow weekly transfers can help ease you into the Profit First systemEmbracing making mistakes in your business as normalWhy it's important that therapists leave the “vow of poverty” narrative behindLinks:Visit the Green Oak Accounting WebsiteGet the free Profit First for Therapists CalculatorJoin the free Profit First for Therapists FB groupOrder Julie's Book Profit First for TherapistsListen to Julie's Podcast Therapy for Your MoneyFollow Brave and Well on InstagramSign up for the Brave and Well newsletter

Making Every Therapy Practice Profitable: An Interview with Julie Herres Curt and Katie interview Julie Herres of GreenOak Accounting about her new book, Profit First for Therapists. We explore what profit first is, the unique challenges that therapist face in implementing profit first, the core principles of profit first, mistakes therapists make in implementation, and the benefits of using this bookkeeping model. Transcripts for this episode will be available at mtsgpodcast.com! In this podcast episode, we talk about the profit first method specific to therapy practices Therapists often struggle with their money, oftentimes forgetting to pull out profit or paying themselves. One accounting system that helps therapists to better manage their money is Profit First. Our friend, Julie Herres, has written a book about this system with specific information for how this accounting system applies to therapists. What is Profit First? ·      Focusing on profit as a given number in your accounting ·      You identify the profit you need FIRST to determine what you can spend on your expenses ·      An accounting system created by Mike Michalowicz What are the unique challenges that therapists face in implementing profit first? ·      Therapist guilt and emotional processes that get in the way of therapists mastering the money in their businesses ·      The stages of change that go into realigning your budget to stabilize your finances in your business and personal life The core principles of Profit First ·      “Use a smaller plate” so you spend less money. You add bank accounts, so each is smaller to divide out your profit, expenses, pay, and taxes. ·      “Serve sequentially” – to the different bank accounts ·      “Remove temptation” – the idea is that you won't use money that is in a labeled account for something else. ·      “Enforce a rhythm” – moving money consistently, to help see the ebb and flow of money in the business. Mistakes therapists often make in implementing Profit First ·      Not changing spending habits ·      Changing too much too quickly ·      Not creating separate bank accounts (this is a key to success) The benefits of using Profit First in your therapy practice ·      Understanding where your money is going ·      Planning for scaling into a group practice ·      Looking at finances in a structured and consistent way ·      Understanding the percentages for all the money in the business ·      Making sure that you are paying yourself and taking profit in your business Thoughts about group practices ·      The different phases of growth ·      The benefits of using a more structured system to weather the emotional challenges of growth in your business ·      Reverse engineering your practice to support your life Resources for Modern Therapists mentioned in this Podcast Episode: We've pulled together resources mentioned in this episode and put together some handy-dandy links. Please note that some of the links below may be affiliate links, so if you purchase after clicking below, we may get a little bit of cash in our pockets. We thank you in advance! The Book: Profit First for Therapists by Julie Herres https://www.profitfirstfortherapists.com/mtsg @Julie.Herres on Instagram GreenOak Accounting Facebook Group: Profit First for Therapists Relevant Episodes of MTSG Podcast: Don't Take Tax Advice From Therapists: An interview with Julie Herres Financial Therapy: An interview with Lindsay Bryan-Podvin Asking for Money Stay in Touch with Curt, Katie, and the whole Therapy Reimagined #TherapyMovement: Patreon Buy Me A Coffee Modern Therapist's Survival Guide Creative Credits: Voice Over by DW McCann https://www.facebook.com/McCannDW/ Music by Crystal Grooms Mangano https://groomsymusic.com/

Mike Michalowicz had founded and sold two multi-million dollar companies by his 35th birthday and was confident that he had it made. After he became a small business angel investor, he lost his entire fortune due to a series of bad business decisions. Mike decided to start over, find a way to grow healthy and strong businesses, and eliminate entrepreneurial poverty. In this episode, Mike will break down his Profit First framework. He will also give the rundown on how to create and manage a profitable business.  Mike Michalowicz is the entrepreneur behind three multimillion-dollar companies and is an author of business books for entrepreneurs and small business owners like Profit First, Clockwork, The Pumpkin Plan, Fix This Next, and Get Different. Mike is a former small business columnist for The Wall Street Journal and regularly travels the globe as an entrepreneurial advocate. He became a business author with a clear mission: Eradicate entrepreneurial poverty.  In this episode, Hala and Mike will discuss:  - Why profits should come first  - The Profit First Formula - How Parkinson's Law applies to profiting - Why you should split your money into small chunks - Target Allocation Percentages (TAP) - The way to handle business debt - Why constrained spending brings natural innovation  - Why all revenue is not the same - The most effective marketing strategy for small businesses - And other topics… Mike Michalowicz is the creator of Profit First, which is used by hundreds of thousands of companies across the globe to drive profit. Today, Mike leads two new multi-million-dollar ventures, as he tests his latest business research for his books. He is a former small business columnist for The Wall Street Journal and business makeover specialist on MSNBC. Mike is a popular main-stage keynote speaker on innovative entrepreneurial topics; and is the author of Get Different, Fix This Next, Clockwork, Profit First, Surge, The Pumpkin Plan, and The Toilet Paper Entrepreneur. Fabled author Simon Sinek deemed Mike Michalowicz “…the top contender for the patron saint of entrepreneurs.” Resources Mentioned: Mike's Website: https://mikemichalowicz.com/ Mike's LinkedIn: https://www.linkedin.com/in/mikemichalowicz/ Mike's Twitter: https://twitter.com/MikeMichalowicz?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor Mike's Instagram: https://www.instagram.com/mikemichalowicz/?hl=en Mike's Facebook: https://www.facebook.com/MikeMichalowiczFanPage Mike's Podcast The Entrepreneurship Elevated Podcast: https://mikemichalowicz.com/podcast/ Mike's Blog: https://mikemichalowicz.com/blog/ Mike's Book Profit First: https://mikemichalowicz.com/profit-first/ Profit First Instant Assessment: https://s3.amazonaws.com/ProfitFirst/PF-InstantAssessment.pdf  LinkedIn Secrets Masterclass, Have Job Security For Life: Use code ‘masterclass' for 25% off at yapmedia.io/course. Sponsored By:  Shopify - Sign up for a $1 per month trial period at shopify.com/profiting More About Young and Profiting Download Transcripts - youngandprofiting.com   Get Sponsorship Deals - youngandprofiting.com/sponsorships Leave a Review - ratethispodcast.com/yap Watch Videos - youtube.com/c/YoungandProfiting Follow Hala Taha LinkedIn - linkedin.com/in/htaha/ Instagram - instagram.com/yapwithhala/ TikTok - tiktok.com/@yapwithhala Twitter - twitter.com/yapwithhala Learn more about YAP Media Agency Services - yapmedia.io/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Welcoming Debra Angilletta to the HVAC Financial Freedom podcast! Debra is the CEO & Founder of Angilletta & Associates, a former Wall Street Trader, and is certified in the advanced level implementation of the Amazon Best Seller - "Profit First" from NY Times best-selling author Mike Michalowicz. In this podcast, Debra taught us how the Profit First methodology can help you retain more profits in your HVAC business, and you'll also learn... 0:19 Introducing Debra Angilletta 2:11 Debra's Background And How She Got Into the Finance Industry 4:18 Debra's Working Experience on Wall Street 6:38 What Inspired Debra to Take a Leap to Entrepreneurship 8:16 What is the "Profit First" Method and How It Can Boost Your Business's Profits 10:07 "Profit First" is Better For Entrepreneurs Than Traditional Profit Formula 12:07 Profit First Concept Made Easy: Set Small Plates For Your Business 17:05 Implementing the "Profit First" Formula Creates Steady and Sustainable Income in Your Business 20:37 Bridging The Gap: Profit First & GAAP Accounting Principles 23:33 How to Start Using the Profit First System - Follow These 3 Easy Steps! 24:23 About the Book: "Profit First" by Mike Michalowicz (A Must-Read!) 25:02 What Does Financial Freedom Mean to Debra and Ways to Achieve It 28:00 Don't Be Afraid To Take The Leap For Financial Freedom 32:15 How to Network and Invest Your Way to Financial Freedom 35:33 FREEBIE! Get Your Copy of "5 Secrets to Success Hiding Inside Your Financials" E-Book 37:26 Connect with Debra So sit back, listen in, and enjoy this conversation!

Welcome to the Real Estate Ballers Show. Performing a property inspection is typically a part of the buyer's due diligence. The cost of one is nominal in comparison to what an investor could lose if he or she misses an item or several items in need of repairs. In this episode, Vee and Adam discuss how they handle the inspection and the inspection report when they are buying and when they are selling. Listen to learn how this episode could keep you out of trouble. Adam Schneider is the owner of Homewood Realty and CEO of Oakwood Lending. In 2012, Adam left corporate America to start his own real estate venture. Today, he is one of the thought leaders in HomeVestors - America's #1 House Buyer and in his own local real estate community in Raleigh, NC. Vee, the founder of REBallers, is a franchise owner and a Developmental Agent of HomeVestors “We Buy Ugly Houses”.  Today, Vee is actively buying and selling properties in Houston, Austin, San Antonio, and Corpus Christi, TX while growing her rental portfolio of long-term and short-term rentals. Book: Profit First by Mike Michalowicz Follow us on Social Media:Instagram @reballersFacebook: https://www.facebook.com/REBallersLinkedIn: https://www.linkedin.com/company/reballers/Join our community:https://www.facebook.com/groups/1764098016997548Wanna be on our show? Email info@reballers.comPlease visit our sponsor, which made this episode possible: Buzz Vacation Rentals, a premier short-term and vacation rental manager in Houston and Galveston, helps investors to maximize earnings on their investment properties.  https://buzzvacationrentals.com/If you enjoy the show, would you please leave us a short review on Apple Podcast? It takes less than a minute, and it really makes a difference in helping to spread the words. I also love to read them and share them with our guests!Disclaimer: All information, content, and materials available in these episodes are designed for educational and inspirational purposes only. We are not financial advisers. We only express my opinion based on our experience. Your experience may be different. Investing of any kind involves risk. While it is possible to minimize risk, your investments are solely your responsibility. It is imperative that you conduct your own research. There is no guarantee of gains or losses on investments#therealestateballersshow #reballers

For a lot of minority business owners, building wealth is much more than just the glitters and gold of the entrepreneur title. Business profit can mean the difference between going hungry and keeping your family fed. As an advocate for financial education, I really wanted to bring someone onto the show that can showcase how a different system of cash management can improve the family business profit over time. In this episode, I'm joined by Susanne Mariga, a CPA with a passion to put an end to entrepreneurial poverty and improve minority family legacies. With over two decades of experience, Susanne has practiced and perfected the Profit First cash management system which has lifted thousands of entrepreneurs from struggle to success. So if you've been struggling and can't seem to strike a balance with your cash management, Susanne definitely has something for you to try out! Highlights >> Profitable Minority Money >> Paying for Profit First >> Strategies to Increase Business Profit >> How Accounting Helps Profitability >> What Inspires Susanne to Grow, Learn, and Lead Connect with Susanne: >> https://susannemariga.com/ (Website | susannemariga.com) >> https://susannemariga.com/book/ (Book | Profit First for Minority Business Enterprises) If you loved this episode, you have to listen to these episodes as well:  >> https://minority-money.captivate.fm/episode/all-the-colors-changing-the-complexion-of-wealth-with-diana-g-yanez (Episode 141: All The Colors: Changing the Complexion of Wealth with Diana G. Yanez) >> https://minority-money.captivate.fm/episode/diversity-in-financial-planning-with-rita-cheng (Episode 120: Diversifying the Financial Planning Landscape with Rita Cheng) >> https://minority-money.captivate.fm/episode/the-power-of-taking-control-of-your-finances-with-naseema-mcelroy (Episode 104: The Power of Taking Control of your Finances with Naseema McElroy)  I'm sure you're getting tons of value from the podcast! Don't forget to subscribe on Apple Podcasts (https://apple.co/3jN77Mv) , Spotify (https://spoti.fi/3jParH0) , Google Podcasts (https://bit.ly/3n3i8vb), or on your favorite podcast app and SHARE THIS

Last week in our goal-setting episode, we mentioned that we'd bring a guest on to talk about finances. Today, that guest is joining us. Moshe Amsel is the host of the Profit with Law Podcast, the founder of the Law Firm Growth summit, a certified Profit First Professional, and a business coach to many law firms. He's also a dad of 6, a paramedic, and a former accountant and IT professional.  We truly couldn't ask for a better guest to talk about revenues, financial numbers, and goals related to finances for law firms. Throughout our discussion, Moshe explained all about the problem with goal setting and just leaving it at that. He helped us understand the importance of having a system for making sure we're on track with our goals and course-correcting.  Today's episode is part one of this conversation. In it, we revisit goal-setting from a numbers perspective. We dive deeper into setting revenue goals based on our take-home needs. We also talk all about investing vs. spending when we are first building our business. Moshe teaches how much we should be spending, what profit we need for that, and how to shape our mindset around all of this. Next week we will share the second half of the conversation but, for now, tune in to learn all about revenue and profit.  Show Highlights: Goal-setting in regards to revenue. How to reverse engineer your revenue goal to reach your profit goal. The profit matrix for any healthy business. Why we need to set big visions. How to translate the profit matrix into a revenue goal. Where our revenue should be going in our law firms. How to shift your perspective from that of a technician to that of a business owner. How to treat investments into your business as sprints. Subscribe and Review We'd appreciate you subscribing to this podcast and leaving an Apple Podcasts review. Reviews help others discover and learn what Law Firm Next is all about. It only takes a second and helps us out a lot! Supporting Resources: https://www.profitwithlaw.com/ Book: Profit First by Mike Michalowicz  Book: Who Not How by Dan Sullivan & Dr. Benjamin Hardy  Book: The Infinite Game by Simon Sinek  *** Episode Credits If you like this podcast and are thinking of creating your own, consider talking to my producer, Danny Ozment. He helps thought leaders, influencers, executives, HR professionals, recruiters, lawyers, realtors, bloggers, coaches, and authors create, launch, and produce podcasts that grow their business and impact the world. Find out more at https://emeraldcitypro.com

One common mistake that we see many real estate investors make is not knowing the financial side of their business. They're so focused on getting as many deals as they can and they either avoid or abdicate their financials, so it gives them a lot of problems in the long run. In today's episode, we have David Richter to help us learn what we need to do to stop living from deal to deal and actually create a business that's profitable. David Richter is a published author and a Profit First expert. He wrote the book Profit First for Real Estate Investing and he's telling us why this system is something we all need. Key Talking Points of the Episode [00:00] Introduction [00:55] Who is David Richter? [01:17] How did David become a Profit First guru? [02:23] Bringing the idea to Mike Michalowicz  [03:00] How did David get involved in real estate? [04:19] Working with a company in NW Indiana [04:59] Coming to the Collective Genius as a service provider [05:56] Where the cash eating monster comes from [06:44] Your responsibility as the business owner [07:19] The biggest problem of most investors [08:10] The pay cash, close quickly mentality [09:14] The Profit First formula [10:35] Profit First as a discipline [11:30] The big difference in Profit First for Real Estate [12:45] The other accounts you should be opening [14:05] Reserves can help grow your business [15:17] Making profit a habit [16:26] Why is it so hard to make profit a habit? [17:25] How important are the right people in the right roles? [19:55] 1-800-sell-now [20:34] David's biggest mistake in real estate [21:41] 3 critical points in owning rental properties [21:57] Partnering with clients as a CFO [23:17] Who are the people who need Profit First? [25:26] Profit First for Real Estate Investing   Quotables   “95% of the time, I would say it's like that, where the number one mistake we see is just avoiding the financial side or just abdicating the responsibility of the financial side to someone else.”   “As an entrepreneur or business owner, you at least have to have that control over your cash, and know where your cash is flowing, where your cash is going.”   “As the business owner, you have to be savvy but you don't have to be an accountant or a bookkeeper, and all that.”   “No one's really taught you this side. I get it, you're not the CPA, bookkeeper, or accountant. You haven't been taught just basic money management at a high level at all.”   “With this “pay cash, close quickly” mentality, there's a tendency to use all their cash in the next deal and as you scale and grow, inventory expands, you pour more money into the assets so your balance sheet is heavy, but you can absolutely be very very cash grabbed.”   “You might be doing 100 deals a month, but you still gotta be able to live and eat and pay your people the next week.” “It's income minus profit equals expenses, so it's just switching the profit and expenses. So you make a sale, you collect income, then you take your profit first and what you left over is expenses in the business.”   “We've heard that over and over and over again, but I feel like it hasn't hit home until you see money in accounts and you're making profit a habit in your business.”   “I love the formula, I love that shift in mentality, but I love that it has teeth behind it too in the practical side.”   “Making money is a skillset, but retaining money is a discipline.”   “I teach about reserves and how it's peace of mind for you. You don't have to live from deal to deal.”   “Lenders love reserves. They love to be able to see those reserves in your account.”   “The whole point of this system is making profit a habit inside your business, not just this one time event at the end of the year, hopefully, that you have money leftover to take at the end of the year.”   “You gotta get into some kind of rhythm for you that you know you can do for your business.”   “There is this stigma that I hear the words CPA, bookkeeper, accountant, and I automatically shut down.”   “You have to have the right people and trust them to get the bookkeeping in place and to do the taxes right.”   Links   Website: Simple CFO Solutions https://simplecfosolutions.com/   Book: Profit First for Real Estate Investing https://www.amazon.com/Profit-First-Real-Estate-Investing-ebook/dp/B098865Y5B

In this episode we're joined by business process and automation consultant, Daniel Cooper. Daniel is the Managing Director of Lolly Co and author of the upcoming book, 'Upgrade: The Lightning Fast Path to Productivity and Automation in Business'.In this episode we discuss:How Daniel automated 60% of his previous job (and eventually left to launch Lolly Co!)What you should do before you try and automate anything in your businessEntry-level automation software recommendationsHow can SME's get start with AI?Daniel's favourite business automation examplesReferenced in this episode:[Book] Profit First: https://amzn.to/3zU61Uthttps://ifttt.com/https://zapier.com/https://tray.io/https://www.process.st/https://openai.com/CONNECT WITH DANIEL/LOLLY COhttps://lolly.co/https://twitter.com/imdanielcooperCONNECT WITH SCOTT:scott.colenutt@sitevisibility.comhttps://www.linkedin.com/in/scottcolenuttCONNECT WITH SITEVISIBILITY:https://www.sitevisibility.co.uk/https://www.youtube.com/user/SiteVisibilityhttps://twitter.com/sitevisibilityhttps://www.facebook.com/SiteVisibilityhttp://instagram.com/sitevisibility See acast.com/privacy for privacy and opt-out information.

Today's episode is a continuation of the key takeaways from Atomic Habits Book by James Clear including the topic on how to break bad habits. It's not enough to assume you have "bad habits". You need to know exactly which habits you want to change and get over with!    KEY TAKEAWAYS:  4 laws of breaking bad habits Examples of removing a bad habit from your environment Takeaways from the Book: Profit First by Mike Michalowicz Using a Contract Template   RESOURCES/LINKS MENTIONED: Atomic Habits Scorecard (Free download)   BOOKS MENTIONED: Atomic Habits by James Clear Profit First: Transform Your Business from a Cash‑Eating Monster   ASCEND: Don't Wait To Enjoy Your Life, Tomorrow, Live It Today! How To Grow Your Business, Expand Your Impact, and Experience Your Perfect Life:  

Today’s guest is Austin Church from Knoxville, Tennessee. Austin helps e-commerce founders stand out online with their brand strategy. He also coaches freelance creatives.   After Austin got laid off in spring 2009, during the U.S. recession, he became a freelance copywriter. Does Austin consider himself an agency? Not exactly. He likes to pull in other creatives as necessary, and he serves as the project manager. He calls it the “antique shop” model — bigger antique shops don’t own all the antiques; they provide the space for other dealers, sell their products and earn a commission.   When he first started freelancing, Austin wasn’t great at keeping tabs on his income and expenses, and he didn’t save for or pay his quarterly taxes. When his accountant sister fired him as a client, it was a wakeup call. The book “Profit First” by Mike Michalowicz helped Austin figure out a better way to handle his money, mainly by getting several checking accounts and allocating each one toward certain things, like quarterly taxes.   Austin is also a fan of the book “Atomic Habits” by James Clear. Clear says if you make habits obvious and easy, they’re more likely to stick. That resonated with Austin and helped him institute some better business and personal systems.   One system he highly recommends is to create email templates, especially when you’re asking clients for referrals. After a project goes well, at the end, when the client is happy, customize that referral template quickly and email it to your client.   Austin also recommends tracking every client and project lead imaginable and having a simple way to track them. Check in with that spreadsheet every week to see what leads you need to follow up on. It can take several “touches” or interactions with a potential client before you land a project, and without those multiple check-ins you could lose out on great projects and clients.   Austin says we have to put in a statistically significant number of activities. We often give up too soon. But, for example, if you are using Instagram to get clients, you need to have conversations with 100 people, not three.   Austin builds his business on selling strategy. He recognized that about 3 out of every 10 clients know exactly what they want, and he helps them with that. But most are unclear. For example, they might ask for a new website, but what they really need is an entire marketing strategy.   Austin started offering strategy, or strategic planning, which he now calls a “wayfinding workshop.” After talking with the client, he gets the sense of whether they’re lacking clarity and need strategic help. If they’re not willing to pay for that, it’s a red flag for him and isn’t a fit for him as a client.   He also sells “strategy retainers” where he meets with clients every two weeks to work on their strategy. With those packages, he’s not responsible for the implantation phase. He says most freelancers probably skew toward one or the other — they either like the strategy or the implementation. But going back and forth between the two with the same client can cause whiplash.   When Austin sees other freelancers struggling in their freelance business, their challenges often fall under one of the six 6 Ps: positioning, packaging, pricing, pipeline, psychology, process.   Biz Bites: Get a Text Expander App (atext) and Don’t Open Your Email Until 11 a.m.   Resources:   Austin’s website and his free freelance course: AustinLChurch.com   Austin on Twitter   Austin on LinkedIn   Episode #79 of Deliberate Freelancer: Six-Figure Freelancing: Consistently Sending LOIs and Using Upwork, with Laura Pennington Briggs   Episode #80 of Deliberate Freelancer: Six-Figure Freelancing: Writing B2B Tech Content, with Satta Sarmah Hightower   Episode #81 of Deliberate Freelancer: Six-Figure Freelancing: Focus on a Niche and Partner with Other Freelancers, with Lynne Testoni   Episode #82 of Deliberate Freelancer: Six-Figure Freelancing: Embracing an Entrepreneurial Mindset, with Gresham Harkless   Book “Profit First” by Mike Michalowicz   Book “Atomic Habits” by James Clear   Book “The Business of Expertise” by David C. Baker   Book “Give and Take” by Adam Grant   Book “Million Dollar Consulting” by Alan Weiss   Book “Essentialism: The Disciplined Pursuit of Less” by Greg McKeown   “The Chef Show” on Netflix   iKamper rooftop tent    

When you're in the season of your business where you’re ready to scale, whether you're one person or a company of 10 or 100, you've got to start thinking about doing financial projections. However, a financial projection is not just about cash flow forecasting. There’s actually more to it than that.  In this episode, we dish out the five baby steps to doing financial projections for your online business.  Every business has its own ebb and flow. That’s why it’s important to have this as part of your regular process so you’re able to predict and realize your future.  In this episode, you will hear: When to start doing financial projections The 5 baby steps to financial projections What to predict in doing financial projections The time frames of financial projections Subscribe and Review Have you subscribed to our podcast? We’d love for you to subscribe if you haven’t yet.  We’d love it even more if you could drop a review or 5-star rating over on Apple Podcasts. Simply select “Ratings and Reviews” and “Write a Review” then a quick line with your favorite part of the episode. It only takes a second and it helps spread the word about the podcast. If you really enjoyed this episode, we’ve created a PDF that has all of the key information for you from the episode. Just go to the episode page at www.profithero365.com/payplayprofit​ to download it. Supporting Resources: ProfitHERO™ The IRS Is NOT Your Boss, So Stop Acting Like It!  Book: Profit First by Mike Michalowicz Episode Credits If you like this podcast and are thinking of creating your own, consider talking to my producer, Danny Ozment. He helps thought leaders, influencers, executives, HR professionals, recruiters, lawyers, realtors, bloggers, coaches, and authors create, launch, and produce podcasts that grow their business and impact the world. Find out more at https://emeraldcitypro.com

How do you know when to burn your ships, quit your full time job, and make Amazon full time? We speak to Todd Welch, host of the Entrepreneur Adventure podcast and Amazon Seller. Todd left his job too early in the process and ended up going back to his 9-5 job. He's still working in fact. He shares his mistakes and advice to know your numbers before you make the leap yourself.Now hire a bookkeeper. After all expenses.Can’t just look at top line sales.Got $60,000 into debt.Now that I know the numbers, back at topline 130k per month. Snowball it ongoing.Took Amazon to purchase more product.How did the business model change after you had the bookkeeping in place?Now all wholesale. 15% profit margin good number in wholesale world.2 week budgetIn the beginning too much money not enough products. Later too much products and not enough money.ROI 60%. 26% margin. Listings collect dustSo how do you know when you should quit your job?Book: Profit First, for ecommerce sellers. https://www.amazon.com/Profit-First-Ecommerce-Sellers-Money-Making/dp/0960028315Take salary out 3 months before you quit, take money out, see if business can run. Debate of debtScale. Risk vs reward.Product failuresDidn’t differentiateToo low price - $15 Seek unique stuffHow did it feel to fail, how did it feel when you went back to work?Plan to go back to full time soon?You may also like “So you married an Amazon Seller” https://www.youtube.com/watch?v=8jmeKKY9r7oFind Todd at https://entrepreneuradventure.com/https://www.youtube.com/channel/UCeNVgygMlCnOYRf_799fLqgSupport the show (https://www.paypal.com/paypalme/myamazonguy)

Strong retail sales skills are more important than ever, as stay-at-home orders have proven. What is really holding you back from having amazing retail sales skills? Maxine Drake, well-known beauty business coach and contributing author of The Esthetician’s Guide To Outstanding Esthetics, asks all the questions you need to ask yourself. Poor retail sales numbers aren’t a result of clients’ lack of interest or income. Listen as we discuss how to improve your retail skills and in turn improve your retail sales.   To connect with Tracy Donley, ASCP Executive Director, click here    To join Associated Skin Care Professionals (ASCP) click here    Questions about Associated Skin Care Professionals (ASCP) membership or professional liability insurance for estheticians call 800-789-0411   If you are interested in adding Business Personal Property (BPP) insurance to your membership click here    Follow Associated Skin Care Professionals (ASCP) on Instagram    To access ASCP’s extensive Back to Practice guide, click here    Book: The Big Leap by Gay Hendricks    Book: Start with Why by Simon Sinek   Book: Profit First by Mike Michalowicz   Free resources, ebooks, blogs, and videos from Maxine Drake   Esthetician Inner Circle Membership—Your complete digital marketing & business-building training center. Let’s build, grow, and scale your business!   Do you need more clarity, accountability, step-by-step action plans, and an incredible group of esty-besties to help build your confidence? Register for the Beauty Business Summit—The premier event for licensed industry professionals. Social:   Maxine Drake on Instagram and Facebook   Beauty Business Summit on Instagram and Facebook    

Do you know what you should be focusing on to make your business more profitable? We’ve had conversations with many clients during these challenging times. While some businesses are booming, others are taking a hit in sales. But the one thing that seems to be on everyone’s mind is profitability.   In this episode, we set the framework for our entire Profit Series. Whether or not your business is thriving during this time, we share the five-step process of creating the roadmap you can use for profitable growth.  Episode Highlights:  4:52 The decision you have to make about the metrics you keep in focus 6:19 How do you define profit? 9:12 What it means to set a profitability goal and how it differs in different industries 14:53 How to set a capitalization goal 17:55 What is a salary cap? 21:25 How to manage salary caps 25:03 The three levers to drive profitable growth Links and Resources:  Book: Profit First by Mike Michalowicz Boredwalk Tshirts @a_brawn on Twitter @andrewfoxwell on Twitter Brand Growth Experts Foxwell Digital Review or subscribe on iTunes

Never stop learning. Level Up! Why is this so important? • Do what you already do, but better. • Don't fall behind your competitors. • Offer more to your clients. • Raise your rates. Hosts Present: Cory Jenkins – Aspen Grove Studios / FB / @aspengrovellc David Blackmon – Aspen Grove Studios / FB / @aspengrovellc Tim Strifler - Divi Life / FB / @timstrifler Stephanie Hudson - FocusWP / FB Josh Hall – JoshHall.co / FB Resources Mentioned: LinkedIn Learning - https://www.lynda.com/ Book: Built To Sell - https://builttosell.com/ Book: Profit First - https://profitfirstbook.com/ Book: Build a Story Brand - https://buildingastorybrand.com Book: This is Marketing - https://seths.blog/tim/ Courses: Troy Dean - https://troydean.com.au Courses: Divi Life - https://divilife.com/online-divi-courses/ Courses: Divi Space - https://divi.space/product/category/courses/ Courses: Josh Hall - https://joshhall.co/web-design-courses/ Join us Live on Youtube or Facebook every Tuesday @

Never stop learning. Level Up! Why is this so important? • Do what you already do, but better. • Don't fall behind your competitors. • Offer more to your clients. • Raise your rates. Hosts Present: Cory Jenkins – Aspen Grove Studios / FB / @aspengrovellc David Blackmon – Aspen Grove Studios / FB / @aspengrovellc Tim Strifler - Divi Life / FB / @timstrifler Stephanie Hudson - FocusWP / FB Josh Hall – JoshHall.co / FB Resources Mentioned: LinkedIn Learning - https://www.lynda.com/ Book: Built To Sell - https://builttosell.com/ Book: Profit First - https://profitfirstbook.com/ Book: Build a Story Brand - https://buildingastorybrand.com Book: This is Marketing - https://seths.blog/tim/ Courses: Troy Dean - https://troydean.com.au Courses: Divi Life - https://divilife.com/online-divi-courses/ Courses: Divi Space - https://divi.space/product/category/courses/ Courses: Josh Hall - https://joshhall.co/web-design-courses/ Join us Live on Youtube or Facebook every Tuesday @

I am continuing my special series of discussions during the COVID19 pandemic, this time we are talking with Dan Holden from Holden Capital about all things finance and capital in times of uncertainty. During dynamic, volatile periods it is common for fear to take hold and cloud our vision of the future. It is often made more challenging when people and organizations around you are withdrawing capital or pausing to take stock. However, it is important to work through the fear, tackle the issue and get yourself set for future success. In this conversation we cover: 1. What property developers should they be doing to get their finance sorted. Use the down time to making themselves ready/bankable by having a business plan that:  - sets out their historical credentials, skills and ability to deliver - financial capacity through their assets and liabilities, and cashflow - how they intend to manage their business over the coming months and years Don’t do it alone. Talk to your advisors, accountant can help if they are a good one, or us as finance broker can add lots of value beyond just getting a good price on debt pieces. 2. Can you still get money to finance your property development project? Definitely but it’s a very different landscape with less players, lenders are holding their capital back and new ones filling the gap. 3. How have the finance/lending markets reacted? We have 160 lenders on our panel, I would put them into 2 categories; 1. many have temporarily closed, preferring to see how bad the economy is going to be hurt before lending more. 2. some have decided to keep lending but at lower gearing and risk, and some have put in place higher pricing 4. Should you delay applying for property development project funding? Not if you have a sound deal, understand your capabilities and accept that the cost of funding has shifted for now. Expand on risk return and impact of waiting or going ahead. 5. Should you be buying development sites? Same as above, need to understand your market, likely timing of events, have the ability to sit and wait but then be ready to deliver on the financiers requirements per 1. 6. What is something you have learnt in the past few weeks in response to what has been happening? - Not always the lenders that you expect to stand up when it gets tough - A lot of time waster financial offers emerging requiring careful due diligence to avoid disappointment - Developers are remaining positive and generally looking to be ready when the market re-opens 7. Any books, movies, shows you are recommending to people - Holden Capital's Constructive Finance podcast - we recently did a series on different loan products and how to best use them in your business to repatriate an recycle capital - Book: Profit First by Mike Michalewiscz – getting your business cash flow, being the way your money flows in an out of your business. Cash is king, cash is oxygen, few people finding that out the hard way in tough economic times - Book: Barefoot Investor by Scott Pape. Links - Holden Capital - www.holdencapital.com.au

ALRIGHT! So with all this craziness going on, as business owners we could use some clarification on how to manuerver these new programs. Today we are talking with Wade Carpenter president of Carpenter & Company CPA's PC. He will be walking us through what is going on, what the loan options are, and how we can best use them. EIDL: 4% Interest 30 years 10k forgiveness (Only if 10k is pulled out.) PPP: 1% interest, forgiven as long as it's used as guidelines suggest. If you have any questions about this or want to get in contact you can find that info below: Book: Profit First : https://smile.amazon.com/Profit-First-Transform-Cash-Eating-Money-Making/dp/073521414X/ref=tmm_hrd_swatch_0?_encoding=UTF8&qid=&sr= Wade Carpenter Facebook: https://www.facebook.com/Carpenter.and.Co.CPAs/?eid=ARBJM6itYqbbKuMGJunr_aTYFX9lYzO1gCbY5OGq-OMLxZZMY4_46q07SuFC4wBXJKZkUPDRM9Z1zd-7&timeline_context_item_type=intro_card_work&timeline_context_item_source=100000052532909&fref=tag Email: wcarpenter@carpentercpas.com Addison Corbin Email: Addison@addisoncorbin.com Insta: @addisoncorbin James Chapman email: jamesc@insuredbycig.com Insta: @jdchapman84 Facebook:https://www.facebook.com/Theeverydaygrinders/

Mike Michalowicz is the entrepreneur behind three multimillion-dollar companies and is the author of Profit First, The Pumpkin Plan and what BusinessWeek deemed the entrepreneur’s cult classic, The Toilet Paper Entrepreneur. Mike is a former small business columnist for The Wall Street Journal and the former business makeover specialist on MSNBC. Today Mike travels the world as an entrepreneurial advocate speaking to groups just like aftermarket professionals. He is globally recognized as the guy who “challenges outdated business beliefs” and teaches us what to do about it. (https://www.amazon.com/gp/product/073521414X/ref=as_li_ss_il?ie=UTF8&linkCode=li3&tag=remarkableres-20&linkId=14aa6c38ef90e54a7035822caf1ff868&language=en_US) Carm Note: I loved this book and believe it should be required reading for all aftermarket professionals if you own a shop or not. The principles in this book will help set you free from the ‘I’ve run out of cash and I can’t pay myself’ syndrome. Mike’s father-in-law is a shop owner so he does understand the challenges of our profession. I’ve heard from your industry peers who have implemented ‘Profit First’ and they are well on their way of making the kind of profits indicative of the investment they make in their business. Make Profit First a way of doing business. You deserve to be incredibly successful but you must implement this system or something similar to control your spending. You’ll soon find where your weak area is, yet still profit from your hard work.   Key Talking Points: Actions of owners trigger profitability or lack thereof Cash flow management system The money will flow into the shop Then allocated to the profitability of the company Pay owner/operator, taxes, parts, operations of a business Now can see what money is available for what purpose before spend it Revenue Profitability trap- if profitability down then will revert to sell more, if you want to be profitable then you need to reallocate money to profit. Every transaction has a piece allocated to profit. Money taken out stored away, business runs off of the remainder. 5 core fundamental accounts Income- the inflow of cash Profit- reward shareholders (owning stock in your own company) Owner compensation- owner salary Taxes- business pays for taxes The account that manages operations of the business “Profitability isn’t an event, it’s a habit.” – not bottom line not year end Sales-profit= expenses  (new formula) Support networkFind support with another shop, accountability partner Profit First Professionals- trainer Efficiency- the secret sauce Always Improve Piggy bank Had nonprofitable computer technology businesses. Sold first company and made money Started a second company- sold to Fortune 500 Started third company- went into debt in 2008. Had to tell the family they were going to lose house and possessions. Told 9-year-old daughter he wouldn’t be able to pay for horseback riding lessons. Daughter ran to the bedroom and brought the piggy bank back to Mike to help support the family. Awakening and turning point- learned how to create a successful business and make profit a habit    Healthy business Can run with the complete absence of owner- 4 full weeks physical and digital disconnect Resources: Thanks to Mike Michalowicz for their contribution to the aftermarket’s premier podcast. Mike Michalowicz web site (https://www.mikemichalowicz.com/) . Link to the ‘BOOKS‘ page highlighting all books discussed in the podcast library  (https://remarkableresults.biz/books/) . Leaders are readers. Leave me an honest review on iTunes (https://airtable.com/tblOgQmbnkHekpl0L/viwSbPkieMNhLOmtK/recQNomCKr1D5I9x4) . Your ratings and reviews really help and I read each one of them.

This episode is all about finance, numbers, and revenue. It may not be everyone's favorite topic but a lot of coaches are seeing most of their money going out and are receiving very little profit. This week, Karen and Kathleen sit down with Amber Dugger to talk about planning finances to build a profitable business right from the start. Amber is the found of Budget Alchemy, a holistic system combing personal finance and business cash flow strategies that was developed for health coaches to end the stress and anxiety around numbers. If you want to keep more of your money at the end of the month and have your coaching business become your main source of income then you're going to want to stick around! In this episode we talk about… What it looks like to have a profitable health coaching business What profit first is and how it can help health coaches starting out Cash flow management and how is it different from bookkeeping What a purposeful revenue goal is and how it can help you become more profitable How to set up a strong financial foundation for your business and transition it to full time Links to Resources: Ambers Website - AmberDugger.com Amber's Facebook group - https://www.facebook.com/groups/sweetlifepurposefulmoney/ Book: Profit First by Mike Michalowicz - https://www.amazon.com/Profit-First-Transform-Cash-Eating-Money-Making/dp/073521414X/ Acuity Scheduling [Affiliate link]:  http://bit.ly/2MSgaIM YBAB (You Need a Budget) software – Get two months free - http://bit.ly/2KYSvWc The Wellness Business Podcast Facebook Page - https://www.facebook.com/thewellnessbusinesspodcast/ Karen's  Facebook Group  - https://www.facebook.com/groups/emaillistbuildingforcoaches/ Kathleen's  Facebook Group  - https://www.facebook.com/groups/healthcoachpeers/ Kathleen's Instagram - https://www.instagram.com/kathleenlegrys/ Karen's Instagram - https://www.instagram.com/karenpattock/

AiA 152: Multirepo vs Monorepo with Jeff Whelpley and Kushal Dave On today's episode of Adventures in Angular, we have panelists Ward Bell, Joe Eames and Charles Max Wood. We have special guests, Jeff Whelpley and Kushal Dave. The discussion ranges from the organization of code bases to the benefits of using Monorepo vs Multirepo. Tune in! [00:01:45] – Introduction to Jeff Whelpley and Kushal Dave Kushal is CTO at Scroll, a start-up. Before that, he was at Foursquare, Chartbeat, Google, and IBM. He has worked in a lot of monorepo code base. Although he actually has experience working on a lot of Multirepo situations. Jeff is the CTO of a small startup in Boston called GetHuman that helps people with customer service problems. He has been on Adventures in Angular a couple of times before. He has also been in a couple of other podcasts before, as well as in the open-source community. [00:03:20] – Introduction to the issue Typically, when you’re working in just one or two people team, you don’t really have that many issues centered on dev process, coordinating changes between each other, and trying to figure out the best optimal way to organize your code. Most of the time, you understand the entire code base because you’re working with everything. It gets to be a much different problem once you get to have a larger team. In essence, everything is starting slow down because of different overhead related to the process that was needed in order to make sure got quality changes. You basically have to spend a lot of time and thought around your developer process, how you structure your code, how you physically setup, and organize your entire code base. [00:06:20] – How to organize your code bases? When Kushal worked at Google, everything is in a single giant repository. There are one or two exceptions for client code and some infrastructure things. It allowed people to feel that they could change any of the code and it made it easy to keep everybody in sync with the state of the code. There is some sort of workflow and process things that you have to change in order to get that right. Probably, the biggest one is trying to keep the repo from working in long running branches because things start to diverge. That was the model of Foursquare too. [00:08:15] – How do you run all of the CI across everything? The answer changes to different sizes. At Scroll and for most of the time that Kushal was at Foursquare, it was efficient to run all the builds on every commit. If you just have one mega build that just runs continuously, that’s good enough up until 30 or 40 developers. Once you hit that size, there’s a variety of build tools out there that you can use and understand the structure of your code base. Once you’ve used one of these build tools, declaratively indicate which artifacts depends on which libraries, and what the full dependency thing is, you can build only the relevant CI’s. You can decide whether this change only touches this binary or this test. Chuck also like the approach of having everything in master. If it was experimental, it would still go into master and their CI would effectively run the different builds with the different feature flags. If what you did broke something that somebody else was working on in a process, you could just adjust it midstream. [00:16:00] – Gatekeeper process The gatekeeper process protects the whole code base but at the same time, it’s in the layer of bureaucracy. We’ve been reviewing every piece of code before it’s allowed to land in master. Everybody on our team commits multiple times a day to master. All the changes, as much as possible are really small, especially the feature flag check. In that world, there is this bureaucracy. Hopefully, it’s not holding you up too much. The flipside of that is when you’ll feel really confident that you didn’t break anybody who depends on you and you’re going to have to revisit this change a month from now. For the past 9 months or so, Jeff tried a bunch of different configurations. He tried monorepo and other configurations from the other end of the spectrum - many small packages. As he was interviewing people with their different setups, they’ve all encountered the same types of problems. Regardless if you’re using monorepo or not, as long as you’re trying to keep your changes small and specific, and implemented quickly, it can alleviate any other pains. [00:22:10] – Guard rails The guard rails are just the reviewers. For us, every change that’s getting reviewed means that in some extent, there’s a human check on that. I’m not sure if you can but I certainly know that Reviewable and Fabricate both offer sort of wide range of configuration options. I can imagine the world in which you can programmatically keep people from landing changes that didn’t have that level. In Github, there are guard rails. That actually helps the reviewers. It’s reassuring to have some technology that this person is associated with this set of boundaries. If you want to step outside of the boundaries, they’re going to have to get some other person who understands the code that’s outside of the line to join in approving that. If their organization is big, this is something that they might have to think about. Jeff advises to really be careful about what you’re doing. Is this a change where you are just bumping version numbers or is this something that you have to change a business logic? [00:28:15] – Allowing different people to upgrade dependencies The only way Kushal has ever seen it done is a brutal all-nighter by somebody who has to sit there and get everything working. But one of the things that Google does is they develop a lot of patterns about how to refactor code to make things easier. One solution that Jeff sees is the complete opposite of the spectrum from monorepo. Dr. Gleb Bahmutov is a huge fan of open-source smaller repos - a lot of the mentality of keeping things small, separate and distinct. He’s decided that he’s going to stick in the many repo universe and just create tooling to solve some of these problems. For versioning, he runs this server that detects that a new version has been published. It will automatically try to update it and run all the tests. But according to Kushal, if you have different repos, you can move differently in terms of dependencies but if you’re now out of sync, you may suddenly have incompatible dependencies across what you’re doing. It’s a question of when you want to deal with the problem. Chuck talks about the ways you can get out of sync. With the multirepo, you can get out of sync not just on the dependencies and the build process, but also on the API’s. If you have a module that you’re working on over here and whatever are consuming it on the other side as a driver may not be updated yet so it doesn’t talk properly. Jeff also noticed that with Angular DI, if you aren’t actually using the same version, you run into issues because it has to be the exact same thing at every level or else the injection token is different. [00:36:50] – Develop within Monorepo or develop in a separate repo Chuck thinks that it depends. If there are a lot of dependencies and shortcuts that he can take by relying on the monorepo, he will do it on the monorepo like if it auto loads the correct libraries automatically. And then, they don’t have to do a whole lot of setup. If it’s small, independent, and it’s going to move quickly, then, a separate repo may be the right answer. Kushal adds that there are a lot of benefits in doing it in the monorepo. With feature flags, you have the benefit of reviewing it. It also allows you and others to keep up with everyone in terms of breaking API changes, other than having some brutal merge. Jeff will do it in a separate repo. If this an experimental thing, it disturbs people less. It alleviates the notifications that go on. That is why Kushal’s team also built a lot of custom Slack cooks in order to get some notifications tailored to the parts that they only care about. [00:44:50] – How do you work it out so that things aren’t so tightly coupled? There are no circular dependencies between your packages even transitively. As your monorepo grows you may eventually have some tooling that requires that for your build system. Can this layer have this type of functionality? Or does it need to be moved into a new package? It also means it improves your architecture. Kushal’s team is working on Java. This object that users and organizations create can know about each other’s’ objects but the users can never depend back into organizations or vice versa. You can think of the layered model of networking. We have the pure data model objects are not allowed to know anything about the service layer that interacts with the database. The database can know about those model objects. The web tier can obviously know about both the model objects and the service tier because it utilizes both of those. [00:47:30] – How are those relationships defined? They are defined in build files. If you look at Pants or Blaze or Buck, all those build systems have explicit dependency configurations so you can sort of keeping any of those invariants from being broken.  But Kushal’s team just have a Wiki page that lists out the rules. They also have a test that looks for any cycles in any package dependencies. Jeff’s team created a CLI tool that walks down all subdirectories from where they’re running it. It finds all the package JSON in all your subdirectories and it creates the dependency graphs. They haven’t fully moved to a monorepo but they did start to consolidate. They have a couple of larger repos. This tool will see the dependency graph for all the NPM modules and also see the dependencies between the repos based off of the NPM module dependencies. [00:50:20] – Multimonorepo It’s not perfect to have one larger repo that has basically all of the none-deployable codes. Jeff and his team have a separate set of repos for the actual deployable code. They haven’t made the jump to where Kushal is advocating – using build tools. [00:50:20] – To open-source When you want an open-source portion of what you’re doing but not the entire company’s code base, Jeff thinks that there’s really no way out of having a separate repo for that. Google has this giant internal repo because not everything in it is open-source. Angular is open-source. That’s at least one driver that Angular is in the public Github repo and Google use so much of Angular. And some companies want the sort of open collaboration and free support and upgrades from the community. Other companies see that they’re giving away some kind of competitive advantage that they’re not willing to give up. [00:55:40] – Monorepo is better in all cases Jeff recognizes that there’s a number of organizations that have successfully implemented it but there isn’t an easy way for someone to do it. It’s not common knowledge and does not have a well-known set of tooling and best practices. There’s still a lot to go to get to the point where it’s a no-brainer and everybody knows how to do this the right way. Ward doesn’t know how to do a monorepo but according to him, if he is in an organization or starting an organization, he would go figure out how to do it and would want his organization to have a monorepo. Chuck tends to lean to monorepo but doesn't always do it either. Another caveat is even if he starts with the monorepo, that doesn’t mean that’s where he’s going to end. The answer is if you put them all in separate repos and it turns out that you need benefits of having them all in the same place, you can move them all in one repo. It may not be easy depending on how big and complicated you make your mono or the way you tie together your disparate repos. Kushal is all in. The only time that he wouldn’t do it is if he’s building disparate open-source projects and wanted them to play the open-source ecosystem. The net benefit is that everyone is moving together rapidly because monorepo is optimized for speed. But Kushal wishes that the tooling is better and that many people move to this model. Joe is also open to monorepo in a larger organization. He thinks that the separate repos keep things but monorepo can solve a lot of problems. [01:01:55] – Places to go Jeff has a bunch of articles for people who are pro-monorepo and are advocating for that. He has yet to find one that sets forth like a good mental model or decision framework. This is what Jeff hopes to create in the next couple of weeks before the conference. Picks Ward Bell Hiking Fishing Southern Sierras Chuck Max Wood Book: Profit First by Mike Michalowicz Ketogenic Diet Air-conditioning Joe Eames Book: Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are by Seth Stephens-Davidowitz Rent a scooter to ride around Rome Jeff Whelpley Survey: Monorepo vs Multirepo Twitter: @jeffwhelpley Medium: @jeffwhelpey Kushal Dave Technical Design Reviews Book: The Orphan Master’s Son Twitter: @krave Medium: Workflow

AiA 152: Multirepo vs Monorepo with Jeff Whelpley and Kushal Dave On today's episode of Adventures in Angular, we have panelists Ward Bell, Joe Eames and Charles Max Wood. We have special guests, Jeff Whelpley and Kushal Dave. The discussion ranges from the organization of code bases to the benefits of using Monorepo vs Multirepo. Tune in! [00:01:45] – Introduction to Jeff Whelpley and Kushal Dave Kushal is CTO at Scroll, a start-up. Before that, he was at Foursquare, Chartbeat, Google, and IBM. He has worked in a lot of monorepo code base. Although he actually has experience working on a lot of Multirepo situations. Jeff is the CTO of a small startup in Boston called GetHuman that helps people with customer service problems. He has been on Adventures in Angular a couple of times before. He has also been in a couple of other podcasts before, as well as in the open-source community. [00:03:20] – Introduction to the issue Typically, when you’re working in just one or two people team, you don’t really have that many issues centered on dev process, coordinating changes between each other, and trying to figure out the best optimal way to organize your code. Most of the time, you understand the entire code base because you’re working with everything. It gets to be a much different problem once you get to have a larger team. In essence, everything is starting slow down because of different overhead related to the process that was needed in order to make sure got quality changes. You basically have to spend a lot of time and thought around your developer process, how you structure your code, how you physically setup, and organize your entire code base. [00:06:20] – How to organize your code bases? When Kushal worked at Google, everything is in a single giant repository. There are one or two exceptions for client code and some infrastructure things. It allowed people to feel that they could change any of the code and it made it easy to keep everybody in sync with the state of the code. There is some sort of workflow and process things that you have to change in order to get that right. Probably, the biggest one is trying to keep the repo from working in long running branches because things start to diverge. That was the model of Foursquare too. [00:08:15] – How do you run all of the CI across everything? The answer changes to different sizes. At Scroll and for most of the time that Kushal was at Foursquare, it was efficient to run all the builds on every commit. If you just have one mega build that just runs continuously, that’s good enough up until 30 or 40 developers. Once you hit that size, there’s a variety of build tools out there that you can use and understand the structure of your code base. Once you’ve used one of these build tools, declaratively indicate which artifacts depends on which libraries, and what the full dependency thing is, you can build only the relevant CI’s. You can decide whether this change only touches this binary or this test. Chuck also like the approach of having everything in master. If it was experimental, it would still go into master and their CI would effectively run the different builds with the different feature flags. If what you did broke something that somebody else was working on in a process, you could just adjust it midstream. [00:16:00] – Gatekeeper process The gatekeeper process protects the whole code base but at the same time, it’s in the layer of bureaucracy. We’ve been reviewing every piece of code before it’s allowed to land in master. Everybody on our team commits multiple times a day to master. All the changes, as much as possible are really small, especially the feature flag check. In that world, there is this bureaucracy. Hopefully, it’s not holding you up too much. The flipside of that is when you’ll feel really confident that you didn’t break anybody who depends on you and you’re going to have to revisit this change a month from now. For the past 9 months or so, Jeff tried a bunch of different configurations. He tried monorepo and other configurations from the other end of the spectrum - many small packages. As he was interviewing people with their different setups, they’ve all encountered the same types of problems. Regardless if you’re using monorepo or not, as long as you’re trying to keep your changes small and specific, and implemented quickly, it can alleviate any other pains. [00:22:10] – Guard rails The guard rails are just the reviewers. For us, every change that’s getting reviewed means that in some extent, there’s a human check on that. I’m not sure if you can but I certainly know that Reviewable and Fabricate both offer sort of wide range of configuration options. I can imagine the world in which you can programmatically keep people from landing changes that didn’t have that level. In Github, there are guard rails. That actually helps the reviewers. It’s reassuring to have some technology that this person is associated with this set of boundaries. If you want to step outside of the boundaries, they’re going to have to get some other person who understands the code that’s outside of the line to join in approving that. If their organization is big, this is something that they might have to think about. Jeff advises to really be careful about what you’re doing. Is this a change where you are just bumping version numbers or is this something that you have to change a business logic? [00:28:15] – Allowing different people to upgrade dependencies The only way Kushal has ever seen it done is a brutal all-nighter by somebody who has to sit there and get everything working. But one of the things that Google does is they develop a lot of patterns about how to refactor code to make things easier. One solution that Jeff sees is the complete opposite of the spectrum from monorepo. Dr. Gleb Bahmutov is a huge fan of open-source smaller repos - a lot of the mentality of keeping things small, separate and distinct. He’s decided that he’s going to stick in the many repo universe and just create tooling to solve some of these problems. For versioning, he runs this server that detects that a new version has been published. It will automatically try to update it and run all the tests. But according to Kushal, if you have different repos, you can move differently in terms of dependencies but if you’re now out of sync, you may suddenly have incompatible dependencies across what you’re doing. It’s a question of when you want to deal with the problem. Chuck talks about the ways you can get out of sync. With the multirepo, you can get out of sync not just on the dependencies and the build process, but also on the API’s. If you have a module that you’re working on over here and whatever are consuming it on the other side as a driver may not be updated yet so it doesn’t talk properly. Jeff also noticed that with Angular DI, if you aren’t actually using the same version, you run into issues because it has to be the exact same thing at every level or else the injection token is different. [00:36:50] – Develop within Monorepo or develop in a separate repo Chuck thinks that it depends. If there are a lot of dependencies and shortcuts that he can take by relying on the monorepo, he will do it on the monorepo like if it auto loads the correct libraries automatically. And then, they don’t have to do a whole lot of setup. If it’s small, independent, and it’s going to move quickly, then, a separate repo may be the right answer. Kushal adds that there are a lot of benefits in doing it in the monorepo. With feature flags, you have the benefit of reviewing it. It also allows you and others to keep up with everyone in terms of breaking API changes, other than having some brutal merge. Jeff will do it in a separate repo. If this an experimental thing, it disturbs people less. It alleviates the notifications that go on. That is why Kushal’s team also built a lot of custom Slack cooks in order to get some notifications tailored to the parts that they only care about. [00:44:50] – How do you work it out so that things aren’t so tightly coupled? There are no circular dependencies between your packages even transitively. As your monorepo grows you may eventually have some tooling that requires that for your build system. Can this layer have this type of functionality? Or does it need to be moved into a new package? It also means it improves your architecture. Kushal’s team is working on Java. This object that users and organizations create can know about each other’s’ objects but the users can never depend back into organizations or vice versa. You can think of the layered model of networking. We have the pure data model objects are not allowed to know anything about the service layer that interacts with the database. The database can know about those model objects. The web tier can obviously know about both the model objects and the service tier because it utilizes both of those. [00:47:30] – How are those relationships defined? They are defined in build files. If you look at Pants or Blaze or Buck, all those build systems have explicit dependency configurations so you can sort of keeping any of those invariants from being broken.  But Kushal’s team just have a Wiki page that lists out the rules. They also have a test that looks for any cycles in any package dependencies. Jeff’s team created a CLI tool that walks down all subdirectories from where they’re running it. It finds all the package JSON in all your subdirectories and it creates the dependency graphs. They haven’t fully moved to a monorepo but they did start to consolidate. They have a couple of larger repos. This tool will see the dependency graph for all the NPM modules and also see the dependencies between the repos based off of the NPM module dependencies. [00:50:20] – Multimonorepo It’s not perfect to have one larger repo that has basically all of the none-deployable codes. Jeff and his team have a separate set of repos for the actual deployable code. They haven’t made the jump to where Kushal is advocating – using build tools. [00:50:20] – To open-source When you want an open-source portion of what you’re doing but not the entire company’s code base, Jeff thinks that there’s really no way out of having a separate repo for that. Google has this giant internal repo because not everything in it is open-source. Angular is open-source. That’s at least one driver that Angular is in the public Github repo and Google use so much of Angular. And some companies want the sort of open collaboration and free support and upgrades from the community. Other companies see that they’re giving away some kind of competitive advantage that they’re not willing to give up. [00:55:40] – Monorepo is better in all cases Jeff recognizes that there’s a number of organizations that have successfully implemented it but there isn’t an easy way for someone to do it. It’s not common knowledge and does not have a well-known set of tooling and best practices. There’s still a lot to go to get to the point where it’s a no-brainer and everybody knows how to do this the right way. Ward doesn’t know how to do a monorepo but according to him, if he is in an organization or starting an organization, he would go figure out how to do it and would want his organization to have a monorepo. Chuck tends to lean to monorepo but doesn't always do it either. Another caveat is even if he starts with the monorepo, that doesn’t mean that’s where he’s going to end. The answer is if you put them all in separate repos and it turns out that you need benefits of having them all in the same place, you can move them all in one repo. It may not be easy depending on how big and complicated you make your mono or the way you tie together your disparate repos. Kushal is all in. The only time that he wouldn’t do it is if he’s building disparate open-source projects and wanted them to play the open-source ecosystem. The net benefit is that everyone is moving together rapidly because monorepo is optimized for speed. But Kushal wishes that the tooling is better and that many people move to this model. Joe is also open to monorepo in a larger organization. He thinks that the separate repos keep things but monorepo can solve a lot of problems. [01:01:55] – Places to go Jeff has a bunch of articles for people who are pro-monorepo and are advocating for that. He has yet to find one that sets forth like a good mental model or decision framework. This is what Jeff hopes to create in the next couple of weeks before the conference. Picks Ward Bell Hiking Fishing Southern Sierras Chuck Max Wood Book: Profit First by Mike Michalowicz Ketogenic Diet Air-conditioning Joe Eames Book: Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are by Seth Stephens-Davidowitz Rent a scooter to ride around Rome Jeff Whelpley Survey: Monorepo vs Multirepo Twitter: @jeffwhelpley Medium: @jeffwhelpey Kushal Dave Technical Design Reviews Book: The Orphan Master’s Son Twitter: @krave Medium: Workflow

AiA 152: Multirepo vs Monorepo with Jeff Whelpley and Kushal Dave On today's episode of Adventures in Angular, we have panelists Ward Bell, Joe Eames and Charles Max Wood. We have special guests, Jeff Whelpley and Kushal Dave. The discussion ranges from the organization of code bases to the benefits of using Monorepo vs Multirepo. Tune in! [00:01:45] – Introduction to Jeff Whelpley and Kushal Dave Kushal is CTO at Scroll, a start-up. Before that, he was at Foursquare, Chartbeat, Google, and IBM. He has worked in a lot of monorepo code base. Although he actually has experience working on a lot of Multirepo situations. Jeff is the CTO of a small startup in Boston called GetHuman that helps people with customer service problems. He has been on Adventures in Angular a couple of times before. He has also been in a couple of other podcasts before, as well as in the open-source community. [00:03:20] – Introduction to the issue Typically, when you’re working in just one or two people team, you don’t really have that many issues centered on dev process, coordinating changes between each other, and trying to figure out the best optimal way to organize your code. Most of the time, you understand the entire code base because you’re working with everything. It gets to be a much different problem once you get to have a larger team. In essence, everything is starting slow down because of different overhead related to the process that was needed in order to make sure got quality changes. You basically have to spend a lot of time and thought around your developer process, how you structure your code, how you physically setup, and organize your entire code base. [00:06:20] – How to organize your code bases? When Kushal worked at Google, everything is in a single giant repository. There are one or two exceptions for client code and some infrastructure things. It allowed people to feel that they could change any of the code and it made it easy to keep everybody in sync with the state of the code. There is some sort of workflow and process things that you have to change in order to get that right. Probably, the biggest one is trying to keep the repo from working in long running branches because things start to diverge. That was the model of Foursquare too. [00:08:15] – How do you run all of the CI across everything? The answer changes to different sizes. At Scroll and for most of the time that Kushal was at Foursquare, it was efficient to run all the builds on every commit. If you just have one mega build that just runs continuously, that’s good enough up until 30 or 40 developers. Once you hit that size, there’s a variety of build tools out there that you can use and understand the structure of your code base. Once you’ve used one of these build tools, declaratively indicate which artifacts depends on which libraries, and what the full dependency thing is, you can build only the relevant CI’s. You can decide whether this change only touches this binary or this test. Chuck also like the approach of having everything in master. If it was experimental, it would still go into master and their CI would effectively run the different builds with the different feature flags. If what you did broke something that somebody else was working on in a process, you could just adjust it midstream. [00:16:00] – Gatekeeper process The gatekeeper process protects the whole code base but at the same time, it’s in the layer of bureaucracy. We’ve been reviewing every piece of code before it’s allowed to land in master. Everybody on our team commits multiple times a day to master. All the changes, as much as possible are really small, especially the feature flag check. In that world, there is this bureaucracy. Hopefully, it’s not holding you up too much. The flipside of that is when you’ll feel really confident that you didn’t break anybody who depends on you and you’re going to have to revisit this change a month from now. For the past 9 months or so, Jeff tried a bunch of different configurations. He tried monorepo and other configurations from the other end of the spectrum - many small packages. As he was interviewing people with their different setups, they’ve all encountered the same types of problems. Regardless if you’re using monorepo or not, as long as you’re trying to keep your changes small and specific, and implemented quickly, it can alleviate any other pains. [00:22:10] – Guard rails The guard rails are just the reviewers. For us, every change that’s getting reviewed means that in some extent, there’s a human check on that. I’m not sure if you can but I certainly know that Reviewable and Fabricate both offer sort of wide range of configuration options. I can imagine the world in which you can programmatically keep people from landing changes that didn’t have that level. In Github, there are guard rails. That actually helps the reviewers. It’s reassuring to have some technology that this person is associated with this set of boundaries. If you want to step outside of the boundaries, they’re going to have to get some other person who understands the code that’s outside of the line to join in approving that. If their organization is big, this is something that they might have to think about. Jeff advises to really be careful about what you’re doing. Is this a change where you are just bumping version numbers or is this something that you have to change a business logic? [00:28:15] – Allowing different people to upgrade dependencies The only way Kushal has ever seen it done is a brutal all-nighter by somebody who has to sit there and get everything working. But one of the things that Google does is they develop a lot of patterns about how to refactor code to make things easier. One solution that Jeff sees is the complete opposite of the spectrum from monorepo. Dr. Gleb Bahmutov is a huge fan of open-source smaller repos - a lot of the mentality of keeping things small, separate and distinct. He’s decided that he’s going to stick in the many repo universe and just create tooling to solve some of these problems. For versioning, he runs this server that detects that a new version has been published. It will automatically try to update it and run all the tests. But according to Kushal, if you have different repos, you can move differently in terms of dependencies but if you’re now out of sync, you may suddenly have incompatible dependencies across what you’re doing. It’s a question of when you want to deal with the problem. Chuck talks about the ways you can get out of sync. With the multirepo, you can get out of sync not just on the dependencies and the build process, but also on the API’s. If you have a module that you’re working on over here and whatever are consuming it on the other side as a driver may not be updated yet so it doesn’t talk properly. Jeff also noticed that with Angular DI, if you aren’t actually using the same version, you run into issues because it has to be the exact same thing at every level or else the injection token is different. [00:36:50] – Develop within Monorepo or develop in a separate repo Chuck thinks that it depends. If there are a lot of dependencies and shortcuts that he can take by relying on the monorepo, he will do it on the monorepo like if it auto loads the correct libraries automatically. And then, they don’t have to do a whole lot of setup. If it’s small, independent, and it’s going to move quickly, then, a separate repo may be the right answer. Kushal adds that there are a lot of benefits in doing it in the monorepo. With feature flags, you have the benefit of reviewing it. It also allows you and others to keep up with everyone in terms of breaking API changes, other than having some brutal merge. Jeff will do it in a separate repo. If this an experimental thing, it disturbs people less. It alleviates the notifications that go on. That is why Kushal’s team also built a lot of custom Slack cooks in order to get some notifications tailored to the parts that they only care about. [00:44:50] – How do you work it out so that things aren’t so tightly coupled? There are no circular dependencies between your packages even transitively. As your monorepo grows you may eventually have some tooling that requires that for your build system. Can this layer have this type of functionality? Or does it need to be moved into a new package? It also means it improves your architecture. Kushal’s team is working on Java. This object that users and organizations create can know about each other’s’ objects but the users can never depend back into organizations or vice versa. You can think of the layered model of networking. We have the pure data model objects are not allowed to know anything about the service layer that interacts with the database. The database can know about those model objects. The web tier can obviously know about both the model objects and the service tier because it utilizes both of those. [00:47:30] – How are those relationships defined? They are defined in build files. If you look at Pants or Blaze or Buck, all those build systems have explicit dependency configurations so you can sort of keeping any of those invariants from being broken.  But Kushal’s team just have a Wiki page that lists out the rules. They also have a test that looks for any cycles in any package dependencies. Jeff’s team created a CLI tool that walks down all subdirectories from where they’re running it. It finds all the package JSON in all your subdirectories and it creates the dependency graphs. They haven’t fully moved to a monorepo but they did start to consolidate. They have a couple of larger repos. This tool will see the dependency graph for all the NPM modules and also see the dependencies between the repos based off of the NPM module dependencies. [00:50:20] – Multimonorepo It’s not perfect to have one larger repo that has basically all of the none-deployable codes. Jeff and his team have a separate set of repos for the actual deployable code. They haven’t made the jump to where Kushal is advocating – using build tools. [00:50:20] – To open-source When you want an open-source portion of what you’re doing but not the entire company’s code base, Jeff thinks that there’s really no way out of having a separate repo for that. Google has this giant internal repo because not everything in it is open-source. Angular is open-source. That’s at least one driver that Angular is in the public Github repo and Google use so much of Angular. And some companies want the sort of open collaboration and free support and upgrades from the community. Other companies see that they’re giving away some kind of competitive advantage that they’re not willing to give up. [00:55:40] – Monorepo is better in all cases Jeff recognizes that there’s a number of organizations that have successfully implemented it but there isn’t an easy way for someone to do it. It’s not common knowledge and does not have a well-known set of tooling and best practices. There’s still a lot to go to get to the point where it’s a no-brainer and everybody knows how to do this the right way. Ward doesn’t know how to do a monorepo but according to him, if he is in an organization or starting an organization, he would go figure out how to do it and would want his organization to have a monorepo. Chuck tends to lean to monorepo but doesn't always do it either. Another caveat is even if he starts with the monorepo, that doesn’t mean that’s where he’s going to end. The answer is if you put them all in separate repos and it turns out that you need benefits of having them all in the same place, you can move them all in one repo. It may not be easy depending on how big and complicated you make your mono or the way you tie together your disparate repos. Kushal is all in. The only time that he wouldn’t do it is if he’s building disparate open-source projects and wanted them to play the open-source ecosystem. The net benefit is that everyone is moving together rapidly because monorepo is optimized for speed. But Kushal wishes that the tooling is better and that many people move to this model. Joe is also open to monorepo in a larger organization. He thinks that the separate repos keep things but monorepo can solve a lot of problems. [01:01:55] – Places to go Jeff has a bunch of articles for people who are pro-monorepo and are advocating for that. He has yet to find one that sets forth like a good mental model or decision framework. This is what Jeff hopes to create in the next couple of weeks before the conference. Picks Ward Bell Hiking Fishing Southern Sierras Chuck Max Wood Book: Profit First by Mike Michalowicz Ketogenic Diet Air-conditioning Joe Eames Book: Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are by Seth Stephens-Davidowitz Rent a scooter to ride around Rome Jeff Whelpley Survey: Monorepo vs Multirepo Twitter: @jeffwhelpley Medium: @jeffwhelpey Kushal Dave Technical Design Reviews Book: The Orphan Master’s Son Twitter: @krave Medium: Workflow

Today on Business Machine is Jenn Scalia. Jenn is an online business coach and entrepreneur, known for her tough love, no-B.S style. She helps entrepreneurs overhaul their biggest fears and empowers them to share their message. Mission To help entrepreneurs build and promote their online businesses by generating new customers, clients, and more revenue.  In 10 years, Jenn would like to make her business more training and educated based, and less one on one consulting. She would like to expand her reach to help more entrepreneurs.  Learning From Our Mistakes A mistake Jenn learned early on was trying to do everything on her own. The struggle of taking on all the work can quickly burn you out and that it is okay to look for help and support for your business. Recommendations Quote: “At any given moment we have two options: to step forward into growth or to step back into safety.” Book: Profit First by Mike Michalowicz Eat With: Tony Robbins App/ Tech: Grid Diary Eat With: Franklinville Inn Contact: JennScalia.com MichiganCreative.com/videoreport