The Freelancers' Show

In this episode of The Freelancers Show, Reuven Lerner gives some insight into recessions, how they work and how you can prepare for them. He explains that an economy will rise and fall but is always growing. A recession is when instead of growing the economy decreases, there is less business activity, layoffs, etc…  Reuven explains why some people are talking about an upcoming recession. It is impossible to predict a recession but economists can use various events as signs of possible recessions. He explains how the long expansion, trade wars, and the inverted yield curve all point to an upcoming recession. Recession doesn’t always affect every sector, Reuven shares examples of recessions and the sectors they hit.  Reuven lists ways to prepare your business for a recession and share examples of how he has been doing this for his own business. First, make sure you cast a wide net for potential clients. Next, specialize in something specific and make sure the world knows your name and what you do. He stresses the importance of starting a mailing list.  Reuven warns against remaining in one vertical sector. He also warns to be careful about employing anyone full time and shares the pain he suffered during a recession trying to pay everyone’s salaries out of pocket. He advises moving from only working business to business to business to customer and gives tips on how to start that move. Finally in encourages everyone to keep up with economic news. Panelists

• Reuven Lerner

Sponsors

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in .NET
• My Ruby Story
• CacheFly

Links

• https://www.facebook.com/freelancersshow/

Picks Reuven Lerner:

• Slate Money podcast
• Marketplace
• Double Twist
• Podcast Addict
• BlueMail

In this episode of The Freelancer’s Show the panel discusses setting boundaries on the scope of engagements. This means not taking jobs that are too big or too small for you. They begin by define projects that are too small. They explain how many may not realize that there is such a thing a project that is too small.  A too-small engagement may be too short in duration or not profitable enough.  An example Erik Dietrich shares is a two-hour job that is three hours away and they are only paying your $200, between travel, and labor that is 8 hours of work for only $200 which is not worth it. Jeremy Green shares an example from his past. He fell into the trap of taking on 2-hours per month retainer contracts. The problem with contracts like these is that clients cannot intuitively understand how long things will take or may feel that the 2-hours they paid for should roll over when a month goes by without using them.  They explain how setting boundaries defining what is too small is better than trying to use your judgment at the time of the engagement. Many developers have an any work is better than no work mindset, the panel explains how this is not true especially when you are losing money to the overhead of communicating for 5 hours, doing a 5-hour job and only getting paid for 5-hours of work, ostensibly cutting your profits in half.  Erik walks listeners through a helpful exercise of putting numbers to your costs, working your way backward through the numbers to decide how much you would actually have to make in order for a project to be worth your time. He explains that he wishes he had started doing this years ago. This exercise will also arm you with information that will help you from a negotiating perspective. It allows you to speak with authority about what you will and won’t do, giving you the power in the sales conversation and allowing your clients to see what they are really asking of you. Besides the time spent and how much money you will make, the panel shares another scoping boundary, turn around time. They explain that if a client tells you they needed this done yesterday, run. It is a red flag, this means they haven’t done enough planning and it will only lead to a bad situation. Jeremy explains the difference between those who say they want it as soon as possible and those whose hair is on fire and they need it now now now.  Some ways to set boundaries for this is to require a certain number of weeks before you can begin a project and a certain number of weeks for actually working on the project. By setting these boundaries you make sure the project is sane and workable. Erik explains that as the professional you have the experience to set a reasonable timeline for the work required, which means you should have control over the conversation of time.  Next, the panel moves on to establishing boundaries with clients. They explain the importance of setting expectations when it comes to contacting your and the hours you keep. Also, set expectations on how quickly you expect them to respond to you. Jeremy shares times when short projects were dragged out because the client failed to respond to his emails. The panel discusses strategies for getting feedback from clients and escape routes for when clients refuse to communicate.    On the opposite end of the scale are projects that are too large of an engagement. How large is too large depends on the individual. Some developers may want a year-long contract where they work full time on one project while others may be looking to build a consulting practice. However, no matter what you are looking for it is always possible to get in over your head.  The panel advises listeners to have a realistic view of what you can actually do and what you want as a freelancer. Do you want to work solo or over a team? This decision will affect the types and sizes of jobs you will take. You don’t want to take a job that should be done by a team when you want to remain solo, on a similar note you wouldn’t want to take on a job that you could do alone but still have to pay a whole team.  The panel warns against taking on projects with an undefined scope of work, something vague like building an e-commerce site could be dragged on and on as the client adds on more and more features they want. They advise that if you take a job with a project fee to make sure you charge for discovery. Jeremy shares a time where he agreed to one job and once he saw the code he realized the job was not what he agreed to. The panel shares ways to avoid this problem. One way is to agree to work for a number of weeks and revisit the scope of the work after getting your hands into the code. Now that they have explained how to set your boundaries, the panel shares advice on how to disengage from engagements that do not fit the boundaries you have set. The engagements that are too small are easier to disengage from. Using the 2-hour retainer model from earlier, explain to your clients that you have increased the minimum number of hours needed to keep you on retainer and that they do have need of that work. If they agree then great, if not it gives you a reason to move on and find work that fits your needs.  Erik explains two rules of thumb when disengaging from a client. First, a great phrase that no one can argue with is “I can’t make a business case for this”. The other is that when disengaging to err on the side of generosity, give them a generous refund or allow them to keep a sample of your product.   Extracting yourself from an over scoped project is much more difficult especially if they have paid you a large sum upfront and you have put a lot of work into the project. The advice the panel gives is to go to your client as early as possible and explain that the project is going to take a lot more time and resources that you first thought and hopefully you will be able to work something out. If possible, before engaging in any project the panel advises you to determine the worst-case scenario and to work safeguards into the agreement.   Finally, the panel lists questions to ask yourself to determine the perfect projects for yourself. Do you want to hire subcontractors? Is there a time limit you want to work on one project for? What are your costs? What and how many hours do you want to work each day? How much communication do you want to have with clients? What fo you want your business and life to look like. Once you answer these questions and set your boundaries the perfect scope of engagements will be easier to define.   Panelists

• Erik Dietrich
• Jeremy Green 

Sponsors

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in DevOps
• My JavaScript Story
• CacheFly

Links

• https://twitter.com/daedtech
• https://www.facebook.com/freelancersshow/

Picks Erik Dietrich:

• American Express Travel Insiders
• HitSubscribe Mailing list

Jeremy Green:

• The Raconteurs

In this episode of The Freelancers Show, Erik Dietrich explains the term economic buyer and how it can affect freelancers and business owners. An economic buyer is the person within an organization who has the authority to purchase something. Knowing who your economic buyer is will affect how you market your product, for freelancers, this includes labor or services.  Starting with the most desirable, Erik lists the main types of buyers’ situations. The first is the autonomous buyer situation. A lone buyer makes the decision about purchasing a product. Erik shares the example of a manager taking the team out for lunch. They didn’t have to consult anyone and decided to do that on their own. The next situation and the second most desirable after the autonomous buyer situation is the buyer and research assistant/influencer. For this situation, Erik uses the example of the CIO or director of engineering choosing the new IDE for a new project. They may not care about the finer details or don’t have the technical know-how or time to do the research, so the pick someone to do the leg work and allow them to advise them on the purchase. The next situation is the buyer committee. In this situation, the committee debates the purchase and will eventually make the purchasing decision. Erik shares an example of an organization overhauling its website and wanting to get a CMS and starting a blog for marketing purposes. This involves IT and Marketing and has multiple paths to choose from. The last and least desirable situation is the system/algorithm. The example Erik shares is the hiring process for a large organization. An interview is held by someone who has little or no authority in hiring, they are there to play their part in the system. The actual buyer would be the CIO or VP of engineering, who would sign your checks. They can’t be involved directly so they delegate to someone who delegates to someone else, leaving standing orders to fill a specific number of positions. The developer hired is as Erik puts it of no valuable than a stapler to an office manager, they are replaceable.  Erik explains the more you can talk directly to the buyer the more advantageous the situation is. He goes over examples of different types of economic buyers. The economic buyer you deal with will vary based on the size of the organization, the larger the organization the more vertically distributed the economic buyers get. The highest authority starts at the top and slowly trickles down, the economic buyers you deal with have varying names and degrees of authority. Next, Erik explains what difference this all makes from a sales and marketing perspective. With a system/algorithm it is very difficult as each process differs, so marketing to a system takes a lot of effort and time for each organization. With a buyers committee, it is possible to train yourself to address rooms full of people and maintain more control over the process. Buyers and research assistant/influencer situation is even easier with only two people to convince. The best situation is dealing directly with the buyer, with only one person to get to know and convince.  Erik gives advice on how to go from appealing to the whims of a system to working directly with the economic buyers. First, he suggests switching things up and marketing to smaller organizations that don’t have a system. Doing this could help you the credibility needed to work directly with economic buyers higher up in a larger organization.  Another way is by looking at the four-step problem-solving solution. This is where you diagnose a problem, prescribe a therapy, apply the therapy and finally, reapply the therapy. Start by looking at your context in the solution, most likely you are applying therapy. Knowing this you can work your way backward and find the diagnoses. The diagnoses made by the economic buyer can help you understand what the buyer cares about.  Another suggestion he gives is working your way up the value chain, working through each level of economic buyer, finding what the next level cares about and marketing towards them. Or, he suggests selling smaller offerings that will change up your economic buyers. Finally, he explains the first step to any of this is by thinking about who your economic buyer is, get your wheels turning on how to reach those people. Just doing this will help you market more efficiently which will lead to more work and help you be better in what you do.    Panelists

• Erik Dietrich

Sponsors  

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Sustain Our Software
• My Angular Story
• CacheFly

Links

• https://twitter.com/daedtech
• https://www.facebook.com/freelancersshow/

Picks Erik Dietrich:

• Million Dollar Consulting
• The Hit Subscribe Side-Hustle Email List

In this episode of The Freelancers Show the panel share advice and experiences for publishing technical books. Each of the panelists has experience publishing books. Reuven Lerner published a book, Core Perl back in 2000, using a publisher and has self-published two more books in recent years. He is currently republishing one of his self-published books using a publisher.  Erik Dietrich has written three books, two of which were published through a friend and the third was self-published. Jeremy Green contributed to The Independent Consulting Manual and runs a SAS called Remarq, a tool for those who want to self-publish. Why write a book? The panel warns listeners that if your goal is to make money that most likely will not happen. They explain that authors who make real money from their books are rare and authors who make money off of technical books are even more rare. One reason to write a book is so that people will know your name and want to hire yours. Another reason is that writing a book will give you more credibility with clients.  Having published a book can really impress clients, Erik shares how his book has brought him leads. Reuven explains how it shows prospective clients how knowledgeable and reliable he is, this is one reason he is republishing his book through an actual publisher. By having a publishing company publish his book it verifies his expertise for prospective clients, or as Erik puts it a book is social proof of your expertise. By having a published book, Erik receives a lot fewer requests for references or other proof of knowledge.  The panel addresses the profits made by publishing a book. Reuven shares a little of his experience both with a publisher and without one when it came to making money. His first book Core Perl he went through a publisher and didn’t make more than the advance they gave him. Frustrated he decided to self-publish his next two books. Reuven admits he was a fool for turning down the publisher when they approached him about one of his books. Since working with that publisher, they have sold more than 4x as many copies as he had in four years. He may not make more money but his name will reach more people.  Jeremy explains one of the downsides of going through a publisher. When a publisher sells your book you don’t get any information on who buys your book. You can’t reach out to them. You can’t share other products with them. When self-publishing you get all that information and are able to do those things to drum up more business. The panel explains that there are three parts to self-publishing a book. First is the production of the book, writing it. Next, how and where to sell your book. The last thing to consider is marketing, how do you reach the people who will buy your book. The panel addresses each step and shares advice.  Jeremy explains how Remarq uses markdown in the production step of publishing the book. Reuven shares what he is currently using for his publishers and admits he would rather be using Remarq. In the past, Reuven has used so many different toolsets and each one was frustrating. The once piece of advice the panel has for production besides the tooling is to focus on the informational content first and design second. Selling the book, Reuven explains how he used nearly everything to try and sell his book the first time around. Selling your book on your own is a major time suck and headache. Reuven suggests doing as he did and going through a third party, they have it all figured out.  Lastly marketing, Erik advises building a funnel to your site using youtube or other media, if you are unwilling to use amazon to market your book as he does. Reuven explains how he advertises his books like courses and mentions his book everywhere he can. It is hard to compete with publishers when it comes to marketing, they have the numbers and the followers.  Writing for a specific audience will make marketing easier. If you know who you are writing for then you will know how to market to them before your book is even done. Jeremy suggests using people from your target audience to read and review your book as you right, not only will this help you focus your book but will also have people who will spread the word about your book.  Now that they cover self-publishing, Reuven shares what it is like working with a publisher. It starts with a development editor, someone who finds authors and books to publish. Then you sign a contract with or without the help of an agent. Only after you sign the contract do you get assigned to an actual editor and a technical reviewer. These will read everything you write and give you feedback. His work is also read by a group of reviewers who give back feedback, some of which is a little harsh but all of which helps the book be better. Reuven explains how all of this has been a positive experience and that his book is better for it. The last topic address in this episode is when you should you write a book. First, you must like to write, the panel advises those who hate writing not to write a book. Second, you must have something to write about. Publish something in a niche. You won’t make any headway writing a book about a well-known language and a well-known topic. Next, you need to have a plan for your book. Ask yourself what you want to get from writing this book. Lastly, find your audience, write a book that will appeal to your client base, not your peers.  Panelists

• Jeremy Green
• Erik Dietrich
• Reuven Lerner

Sponsors  

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in Blockchain
• React Native Radio
• CacheFly

Links

• Core Perl
• Python Workout
• Blurb
• AsciiDoc
• Gumroad
• https://twitter.com/jagthedrummer
• https://twitter.com/daedtech
• https://twitter.com/reuvenmlerner
• https://www.facebook.com/freelancersshow/

Picks Jeremy Green:

• Remarq.io
• The Independent Consulting Manual. 

Erik Dietrich:

• Starting to Unit Test
• Developer Hegemony: The Future of Labor

Reuven Lerner:

• The Perfect Weapon: War, Sabotage, and Fear in the Cyber Age

Episode Summary In this week’s episode of The Freelancers Show the panel discusses the importance of defining success. Jeremy Green explains why this concept of defining what success means to you is so important. Without success behind defined you might put your nose to the grindstone and miss your own success. Inversely you might be grinding away, missing the signs that what you are doing isn’t taking you to success and you need to stop and reevaluate.    The panel considers some of the obvious signs of success like key performance indicators. Are you making enough to pay your bills, save and play? It is easy to think success is making a million dollars. If that is your definition of success, the panel explains that you will all your success along the way. They invite everyone to sit down and really think of what success means to you. How do you want to spend your time? Are you doing something you love? Do you want to spend more time with friends and family?    Jeremy explains why he wanted to talk about this topic. He went to a conference and this seemed to come up a lot during talks at the conference. It can be hard to reconcile how you feel about success when looking at other people and their circumstances. Deciding what success means to you can help guide your life and get rid of some of that uncertainty.   Erik explains the hedonic treadmill, which shows a phenomenon that says highs from successes wear off fasters than the pain of failure. No matter how high you climb there is always someone higher and your success of getting where you are is forgotten as you attempt to catch the person above you. If you set goals then you can more easily see the success as the come along.     Jeremy shares some of his success criteria. He realized at this conference that he was doing well enough in freelancing and consulting that could pull back and focus more on other things he has been wanting to improve. He realized he got sidetracked and started grinding towards saving as much money as he could for retirement. By figuring out his goals, he saw that was actually doing much better than he thought and didn’t need to grind so much.     Erik describes a similar moment of realization for him at the end of 2016. He was feeling pretty burnt out from traveling, so he sat down and quantified all his work for that year and decide what he wanted out of his lifestyle and made goals in his work life to help him reach that lifestyle.    Erik explains that by not having explicit goals, implicit goals be pressed on us by our surroundings. The panel considers how in this world there is never enough money, but by defining our earning goals and deciding what is enough for us, we can find success in more than one way.    The panel considers how easily freelancers can get carried away overworking and pushing themselves. Employees have an employer that won’t let them overwork, employees have gaurd rails that protect them from this sort of abuse. Freelancers constantly feel that pressure to use their time wisely, to do more. By defining success, you give yourself a way to take an objective look and say I am doing well, I can’t take the night off.    Erik shares his approach to this process. He explains that he starts by looking at his life and what will make him happy and work his goals back to work from there. He gives tips on how to quantify qualitative things in your life so you can evaluate your success.    The definition you give to success is very personal and will differ for each person. The panel considers it from a Maslow’s Hierarchy of business standpoint. The survival needs being are you staying afloat and the different needs moving up a pyramid all the way up to self-actualization or success.    Finally, the panel discusses the need to define failure as well as success. It’s important to know when to bail out or reevaluate a situation. Panelists

• Jeremy Green
• Erik Dietrich

Sponsors  

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in DevOps
• Views on Vue
• CacheFly

Links

• https://www.facebook.com/freelancersshow/

Picks Jeremy Green:

• Company of One
• The Mythical Man Month

Erik Dietrich:

• The 4-Hour Workweek
• Hit Subscribe

Episode Summary   In this week’s episode of The Freelancers Show, Reuven Lerner teaches about B2B and B2C business strategies, giving advice and examples from his own life. He begins by defining B2B or business to business, selling your services to businesses. This type of exchange usually happens behind scenes, Sysko being one example of a B2B company. B2B doesn’t necessarily mean businesses, it could be government agencies or non-profits.    Reuven defines B2C or business to consumer, selling a product or service to individuals. This type of business is seen all the time in advertisements and tv commercials, Coca Cola is the example he gives. The first thing to decide is what you want to sell and then to whom.    Next, Reuven explains why most freelancers go with B2B. It is an established and safer route, especially if you are offering something like web development or web design. Companies are always looking for that kind of help, using contractors and agencies. Reuven does Python training for companies, which is a B2B service.    Reuven goes on to talk about how to find B2B clients. There are two ways to do this outbound or outreach and inbound, which Reuven prefers. Outreach, he explains is reaching out to companies and offering them your services. Reuven gives some advice on this but explains that it is very difficult to get in and very easy to be brushed off. Inbound, meaning your clients find you. He explains that inbound is all about making yourself recognized as an authority, which can take years to build that kind of reputation.   Why works so hard for B2B business? The simple answer Reuven gives is money. He explains that if you do get in then you can become that company’s go-to person for years. An example he gives form his own life is a company that purchases trainings from him every year. Reuven gives the most common timelines from making contact to actually doing the job at 6 months to a year and advises listeners to plan ahead.    Reuven’s advice for getting in is to get in front of a head technical person. The way he does this is through speaking at conferences but webinars and blog posts will help with this. Webinars and blog posts could not only catch the eye of a head technical person but will also them you know what you are doing.    Next, Reuven prepares listeners by explaining what businesses will expect from you. B2B will be way more formal, including paperwork and contracts. He advises listeners that businesses will expect them to be incorporated and insured, treating them as a business.   Moving on to B2C, Reuven discusses the types of products developers might offer to consumers, e-books, online courses, training, and coaching. He explains that the main advantage of B2C over B2B is that there are a lot more people in the world than there are businesses. Rueven explains that the key to success with B2C is volume. He goes over ways of reaching people, videos, blog posts, and posts using Linkedin, Twitter, Facebook, Youtube.    Reuven spends a lot of time discussing mailing lists. He shares the doubts he felt about mailing lists when he first heard of them but strongly suggests that everyone has one.  He explains the advantages of using mailing lists. Reuven shares free content with subscribers, getting his name out there, while also including advertisements for his products. Reuven shares some of the specific details of how his mailing list works.    YouTube is the next topic Reuven talks about. YouTubers can get thousands of followers, Reuven himself is currently working on building up his following. In his videos, he shares free python information all while advertising his products and building up his credibility.    One last tip for B2C, Reuven suggests you have multiple products. More product means more for people to buy. People can become very loyal and you could end up with groupies waiting for your next product.    Cross overs between B2C and B2B, Reuven explains is very unlikely. He shares instances where this has happened which were quite rare. He explains a way he is hoping to see more crossover through his mailing list. Considering that both B2B and B2C both take considerable amounts of time, Reuven suggests focusing on one.   When it comes down to it, Reuven, for the most part, suggests B2B. He explains that it is easier to get started in B2B. B2C is very risky because you start out as an unknown and untested resource. Reuven talks about the time that he tried this in the beginning and it did not go well. The only exception he makes is if you have a niche market that fills a hole, a product or course that people are desperate for.  Panelists

• Reuven Lerner

Sponsors  

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in DevOps
• Views on Vue
• CacheFly

Links

• https://www.drip.com/
• https://www.youtube.com/reuvenlerner
• http://lerner.co.il/newsletter
• https://www.facebook.com/freelancersshow/

Picks Reuven Lerner:

• Lab Rats: How Silicon Valley Made Work Miserable for the Rest of Us
• AI Superpowers: China, Silicon Valley, and the New World Order

Sponsors

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in DevOps
• Views on Vue
• CacheFly

Panel

• Erik Dietrich

Summary Erik Dietrich, the owner of Hit Subscribe, does a solo episode on the journey from freelancer to agency owner. He starts by defining three different roles in this journey, freelancer, business owner, and agency owner. He overviews the typical journey from freelancer to agency owner and evolution of roles and responsibilities that occurs on this journey. He then outlines his own journey.    Erik discusses the possible motivations one might have for becoming an agency owner, money, equity, and time. He also addresses the struggles of being an agency owner. He lists questions to ask yourself before deciding to go down this path. He ends the episode by giving advice to those who decide this is something they want. Links

• https://daedtech.com
• https://join.dynamitecircle.com/
• https://www.facebook.com/freelancersshow/

Picks Erik Dietrich:

• Built to Sell: Creating a Business That Can Thrive Without You
• http://www.paulgraham.com/makersschedule.html
• https://www.hitsubscribe.com/

Sponsors

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• Adventures in DevOps
• Views on Vue
• CacheFly

Panel

• Erik Dietrich

Summary Erik Dietrich does a solo episode sharing his content marketing expertise. Erik runs a content marketing agency, Hit Subscribe, he starts by sharing his background and how he got to this point. He defines marketing as a strategy to show your goods to your customer, content marketing is doing this with content. He explains that by offering free content you build trust with your audience. Listing the various types of content, blogs, video, podcasting, email and more, Erik ranks them on their effectiveness and gives his recommendations.   Start with one source of content and make it sustainable, this is Erik’s first recommendation, once you have that down, expand but maintain that sustainability. Unless your situation is desperate, Erik encourages everyone to start content marketing. He explains the benefits, filtering out clients that are a bad fit, finding leads, and the value of an audience. He also explains that content marketing is the long game and to manage your expectations while staying motivated. Erik leaves the listeners with valuable tips for how to get started and to maintain and how to grow your content marketing.  Links

• https://www.hitsubscribe.com/
• https://devchat.tv/freelancers/choosing-content-marketing-topics/
• https://devchat.tv/freelancers/228-fs-non-writing-content-marketing-methods/
• https://www.facebook.com/freelancersshow/

Picks Erik Dietrich:

• Hit Subscribe’s Youtube Channel
• Whiteboard Friday
• Ahref’s Youtube Channel

Sponsors

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• CacheFly

Panel

• Erik Dietrich
• Jeremy Green

Summary Jeremy Green and Erik Dietrich discuss the unforeseen pain points of becoming a freelancer and share solutions that they have used in their lives and businesses to address these pain points. They considered pipeline management, not having enough work, having too much work and having ill-fitting work. How companies treat vendors and dealing with rejection are discussed. The loneliness of a freelancers life and how to combat it are considered. The hidden cost of working on your own and owning a business are addressed, including health insurance and taxes. The positives and negatives of time and money management are compared. They warn against bad clients and give warning signs against them.  Links

• https://www.facebook.com/freelancersshow/

Picks Erik Dietrich:

• The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It
• The Pumpkin Plan: A Simple Strategy to Grow a Remarkable Business in Any Field

Jeremy Green:

• The Independent Consulting Manual
• Increase Your Consulting Fees - Email Course

•  

•  

Sponsors

• Sentry– use the code “devchat” for two months free on Sentry’s small plan
• CacheFly

Host: Charles Max Wood Episode Summary Charles talks about his journey as a podcaster and his mission with Devchat.tv. Devchat.tv  is designed to home podcasts that speak to all developer communities. Charles also plans Devchat.tv to host shows for technologies that are on the verge of a breakthrough and will be a lot more widely available in the near future such as Artificial Intelligence (AI), Internet of Things (IoT), Virtual Reality (VR) and Augmented Reality (AR). There are new shows being added continuously to reach out to new communities, some examples of which are: a Data Science show, a DevOps show and an Open Source show. As a kid, Charles would record his own shows on a tape recorder. He was always interested in technology. While studying Computer Engineering at Brigham Young University, he worked in the University's Operations Center. Upon graduation, he started working for Mozy where he was introduced to podcasts. Listen to the show to find out the rest of Charles' story, some of the lessons and tips he learned throughout his journey and the evolution of the shows on Devchat.tv. If there isn't a show for your community and you would like there one to be, reach out to Charles. Also if there was a podcast about a programming related subject that ended abruptly and you would like it to continue, reach out to Charles. Devchat.tv would like to host these podcasts. Links

• Charles' Twitter
• EverywhereJS JavaScript Community
• EverywhereRB Ruby and Rails Community
• Find Your Dream Job As A Developer
• Devchat.tv on Facebook
• Devchat.tv

Picks

• EverywhereJS JavaScript Community
• EverywhereRB Ruby and Rails Community
• Netlify
• Eleventy
• https://github.com/cmaxw/devchat-eleventy