Erik Hougaard, Author of Microsoft Dynamics 365 Business Central Field Guide

Len: Hi I'm Len Epp from Leanpub, and on this episode of the Frontmatter podcast I'll be interviewing Erik Hougaard.

Based in Vancouver, Erik is Managing Partner at E Foqus Canada, "a Canadian Microsoft Partner developing products and solutions with Dynamics 365 Business Central", and has been part of the Microsoft Dynamics NAV community since 1990, having worked on a wide array of systems and projects over the years.

You can follow him on Twitter @eHougaard and check out his website at hougaard.com.

Erik is the author of the Leanpub book Microsoft Dynamics 365 Business Central Field Guide, a comprehensive companion book for implementing Microsoft Dynamics 365 Business Central for end users, super users, and administrators

In this interview, we’re going to talk about Erik's background and career, professional interests, his book, and at the end we'll talk about his experience using Leanpub and being a self-published author.

So, thank you Erik for being on the Leanpub Frontmatter Podcast.

Erik: Oh, thanks for having me.

Len: I always like to start these interviews by asking people to talk a little bit about their origin story. So, I was wondering if you could talk a little bit about where you grew up, and how you first became interested in computers and technology?

Erik: Well, as soon as I've said a few words, you'll realize that my accent is not native English. I'm actually Danish, and been living in Canada for the last six-plus years.

I grew up in Denmark and started playing with computers from when I was a kid, and got into programming quite early. Because my dad chose to get - this is the early eighties, I'm old - my dad, he was to get one of the first PCs, IBM PCs that came around. And of course I wanted to play games like any other kid.

There were a few games on the PC. We had King's Quest, we had Frogger. We have the very first flight simulator.

But other than that, there weren't really that many games for the PC. It had a BASIC interpreter, so I started learning BASIC so I could write the games I wanted to play. And that, well, it took on a life of itself, I guess.

Len: That's really interesting. I've asked this question of many people, and everyone has their own timeline - do you remember the model of the computer?

Erik: This was the IBM 5150. They were 256 kilobytes of RAM, two floppy drives. A four-color monitor, and the IBM Pro Printer, which was a re-batched Epson FX 80 printer. So yeah, I do remember.

Len: I washappy to hear you bring up King's Quest. That made me very nostalgic. I don't know everyone -

Erik: It was an awesome game.

Len: It was, and it's interesting, I'm still kind of traumatized from those days when you could - you had like the "true death" in games, where if you died, it was kind of over.

Erik: Yeah.

Len: You could lose progress if the power went out or something like that. I still remember, I think the very first King's Quest game I played, was just like gold colored. It wasn't multicolored.

Erik: It was out on many platforms. I think the one I played was - that was CTA, so four colors.

Len: Right, okay.

Erik: Very limited still.

Len: Not to go too much down this sort of nostalgic gaming path - but there was something I remember from that game, which I believe was that there was a bug in the spelling of the name, "Rumpelstiltskin." So in order to get past a certain challenge, you had to spell "Rumpelstiltskin" backwards. But a certain version of the game had a bug in it, where the name had been misspelled. So the only way to progress past that point was to actually recreate the bug.

Erik: That name was a way bigger challenge. Sitting in Denmark, I had no idea that anyone was called that. That was the only place we had to cheat. And this was before the internet, so it was kind of difficult to find the cheat. I think it was in a magazine at some point.

Len: Actually, speaking of magazines, so you said you started programming games and stuff yourself. Did you just do it from scratch, or did you go off programs that you found in magazines, and things like that?

Erik: I kind of just went at it. And the magazines were actually great. Because at some point, I figured out that if you sent in your program listings to them, they will send the Danish equivalent of $100 back. So I guess that was probably my very, very first publishing thing. Because you wrote a small program, a small game, and sent it to the magazine - they printed it and sent you money, so -

Len: That must've been really exciting.

Erik: That was fun, that was fun. It was a great time in IT at that point.

Len: And what was your first job in IT?

Erik: So, well, you've got time for a small story here, I guess?

Len: Sure.

Erik: I was playing with my PC at home and doing all sorts of stuff on that. And then in the Danish school system at that time, when you're in grade nine - you can have a week as an intern in a company as part of a grade nine thing. A buddy of mine's dad was head of an IT department in a big company in L'Occitane. And so I got this intern job there, to kind of help them with the PCs. Because that was a mainframe installation at the time, and PCs were mostly for fun. Actually, people didn't really consider PCs a real computer.

So it was fine, as a school kid I came in, and I could install stuff, and I could keep those PCs running. After that week, they kind of offered me a job. After school, I was just helping out with the PCs, which I did all through high school. And then at the end of high school, I didn't really exactly know what I wanted to do.

And then one day the phone rang, and this was a guy who said, "Hey, Erik, that program you wrote for me, what was the language?" And this was - at this company, there was a guy who - this is before a lot of things. At a certain time he had, for a couple of months - he had to go into work every night at ten to upload a file to a mainframe, in order to run a process - I can't remember what it did.

So I wrote a program for him that would automatically upload that file to the mainframe. And apparently I told him that the language I did that in was Turbo Pascal, at the time. So I actually made it. That was in Turbo Pascal. He said, "Ah, do you mind coming up for a job interview next week?" I said, "Yeah, why not?" And that turned out to be IBM at that point, that had just announced a new ERP system.

Len: Enterprise Resource Planning.

Erik: Yeah, an accounting system, for the sake of this story, called Navision. And they needed somebody to - this was a partner who were working with IBM. They needed to integrate this new accounting system with a IBM point-of-sale system. Everything was Pascal anyway, so they needed to find somebody who could do Pascal. At this time, this is 1990, Pascal was the language of Northern Europe. Turbo Pascal is actually a Danish product. Very few people know this. Anders Hejlsberg, who now did Delphi and did C# and now had done TypeScript at Microsoft, is a Dane also.

So Turbo Pascal was big, everybody did Pascal at that time. I stepped into the world of Navision. And Navision was, at that point, an IBM product, but not owned by IBM. And then they became themselves, and then twelve years later, they got acquired from Microsoft. Len: And they were Danish as well, right?

Erik: Yeah. Erik: So I kind of stumbled into everything because I used to program games on a PC.

Len: That's a really great story. Thanks for sharing that. It's interesting, I don't know if I've ever spoken to someone who got their first job in grade nine in tech. Although I have spoken to people who did - there's a refrain in the history of IT, where people who get into it really early, like as teenagers, sometimes find themselves amongst adults who are like, "You can actually do this?" And they get jobs where they're doing things that you just wouldn't expect a teenager to be doing.

Erik: No, so this was - that was a very, very specific time. The late eighties, were - in a lot of settings, PCs weren't still not considered serious. If you were an enterprise of any kind, of course you ran your business on a mainframe or a mini computer, or stuff like that. Because that's what you needed to run a big business.

But then the PC sort of slipped in and took over a lot of things. In 1987 when IBM introduced the PS/2's and Token-Ring Network, and all that - kind of validated it.

At the same time, that's actually the origin story for what we call, "Business Central Today," or "Dynamics," or, "Navision." Same product, many names. Is that, at that time - because, with the introduction of Token-Ring - IBM wanted to sell a multi-user accounting system in Denmark to begin with, and other places. But the only accounting systems IBM had on the shelves that would do multi-user were American.

American systems at that time could not do VAT. And currencies was not really supported. Selling in one currency and buying in another, and all that stuff. Which was the situation in Europe, because every country had their own currency. So of course a European accounting system would have to support multiple currencies.

So they looked around and found a Danish company that had made a great product, and asked them, "Hey, can you create a multi-user version of this for us?" And they did. And that is what we know today as Dynamics 365 Business Central. But it started that way.

Len: That's really interesting. And so the muli-user aspect would be that you could log into the same system with the same data, from different terminals?

Erik: Up until that point, computers weren't networked. So lots of companies, smaller companies - you had a accounting system, it was just sitting on that single computer. In accounting, that's where you had your accounting system. And if you needed to work on that, you would work on the accounting computer, and do the work.

Len: It's amazing how far we've come.

Erik: Oh yeah, yeah.

Len: And so did you ever study Computer Science formally?

Erik: Yeah, at the University of Copenhagen, but I was too busy working. So I did some stuff, and then I kind of completed it on self-study, on the subjects that interested me the most.

Len: It's really interesting, this subject comes up a lot, because people have their own ways into IT and tech. So I always ask various versions of the same question. But do you wish you'd - if you were starting out now, with the intention of having a career like the one that you've had, would you advise your now younger self to take a full four-year Computer Science degree, or to take a path more like the one you took, with all the many more resources available now.

Erik: That's really hard, to give general advice. I think the general advice I would give my kids, is to "stay in school."

But on the other hand, they need to study something that they have an interest in, that they're burning for. Not "just because we have to."

For me, it has always been the desire to learn, the desire to figure stuff out, the desire to build that has been the driver. If I needed to build a compiler, I need to figure out how to build a compiler. And that's part of the university course. So that's a natural thing to go that way.

Len: Thanks very much for sharing that. Everyone has their own answer, and it is - one of the things I've always found interesting asking that question, is how seriously people take it. Because it is so important to think about that. And some people are like, "School was a waste of time, I wish I'd never done it." Other people are like, "I regret not having done it." Fveryone has their own approach to that. But everyone takes it seriously. Whether they accept it or reject it or not.

So, the next question I'd like to ask you - I mentioned this before we started the interview, but one thing that we've started doing on the podcast is asking people about how the pandemic has affected them, and what it's been like in the place where they live. You're the first person from Vancouver that we've had to talk about this since the pandemic started, and I was wondering if you could talk a little bit about what your experience has been like over the past few months in Vancouver, and how everything is maybe affected you and your business professionally.

Erik: British Columbia has had a science-driven COVID response, which has been nice to see. We closed down our office in mid-March. Like everybody else, I went home to my basement and I have been here ever since. We actually at some point, a couple of months back, figured out that we are not going to get back to a shared office space anytime soon. So we cancelled our office lease, and are now a work-from-home company, until the world changes again. Business was a bit shaky at the beginning. Everybody's kind of looking at what's going to happen, perhaps the idea of investing a lot of money in IT was not top of mind, which I totally get.

But after a bit of time, from that perspective, business is back to normal. And well, the changes that we'll have, we kind of have to rediscover how to work together now that everything is online.

I think that's fine. It's also interesting to figure out that customers are also learning that, "Okay, we don't need to get Erik on site to have him help us". I used to travel a lot, and of course I'm not travelling anymore. But in fact, looking at what has happened over the last six months - there's a lot of traveling that didn't happen, and was not necessary. Because what we needed to do was accomplished anyway.

Len: Thanks very much for sharing that. So you weren't working remotely beforehand?

Erik: No. We had an office in downtown Vancouver, in one of the office towers, snd shared office space with a couple of other companies. And that - as management, in a shared office space - again this is, we talk about this a lot up here with kids in schoold, the bubble management, how to figure out who to bubble with - and I can't ask my employees to go down and bubble with so many strangers and share office facilities with them. It's not safe. I don't want to do that.

Len: Just a little bit generally about Vancouver. I haven't really left my neighborhood much, here in Victoria. I did actually finally leave the island for Thanksgiving to see a friend on Bowen Island, which is just off of Vancouver. And it was really interesting just to see - like, I hadn't been out in amongst the world, but - in your neighborhood, were people wearing masks all the time and stuff like that? They certainly weren't in mine.

Erik: They are. I live on what's known as the North Shore. And in general, that's - people are very well behaving, and following the rules, and so on. And we've got, thankfully, enough space, so there's room to take a walk without standing in the line to get access to nature and stuff like that. So we are really fortunate to be where we are in a time like this.

Len: Speaking of where you are actually, before we move on to the next part of the podcast and talk about your book, I actually wanted to ask you what led you to move to Canada?

Erik: Adventure. The semi-short story is that my wife and I, back in the late ninetis, lived a year in Florida, and that was fun. We knew we wanted to go, we had to move back to Denmark. But it's always been in the talk that, "Hey, it could be fun to do something like that again." And before the kids were too old, because you cannot move teenagers across the globe. So an opportunity came to simply move my job from Denmark to here and set up a bootstraped North American office of the company I worked for at the time - also called E Foqus. So we did that as an adventure.

But we decided that what we learned from the Florida experience was that we should never do something like that with a designated move-back date. Because then you're not really committing to the local community and stuff like that. So we moved here, end of discussion. And the adventure lasts until the next one starts.

So everybody's enjoying life in Canada. The kids are enjoying the schools and the - we are right next to a ski hill, now we're just waiting for the snow to come, so we can start skiing again.

Len: Oh that's fantastic. Was it actually - I'm curious, was it easy to move - like to get all the paperwork and stuff like that?

Erik: That's what the lawyers are for.

Len: Right.

Erik: But, no. That wasn't easy. But this is not a podcast on Canadian immigration law.

Len: Yeah, no - it just comes up.

Erik: We could do an episode on that. I have lots of input, but —

Len: It does come up from time to time. Because - I mean, particularly in the programming world - actually, people are often really mobile. And so I've talked to people about immigrating to Canada, from Canada to other places and things like that. And yeah, when you have the benefit of lawyers, it does make it -

Erik: Yeah, it's complicated. I had the benefit of bringing a company in my luggage, which made everything much easier. But, yeah. That's too long a story.

Len: Yeah no, that's fine. Just to commiserate with people who've gone through it. They like to know that it's - everybody who's moved, has faced that challenge.

Erik: Oh yeah.

Len: So you've written a book, Microsoft Dynamics 365 Business Central Field Guide. It's quite the mouthful of a name, which you - you actually invoked the name earlier, and the names of these things change over time. And particularly maybe at big companies like Microsoft, you end up with these long names. But we'll call it "Business Central," like you do in your book. I was wondering if you could talk a little bit about what Business Central is. You've mentioned a little bit of its history, but if you could just talk a little bit about what it is and how it's evolved over time.

Erik: So Business Central is an accounting system, which is not - no longer the proper way of describing such a piece of software. It's an ERP system. Which makes no sense either, because nobody really understands what that actually means. And if you understand what it means, then it's Enterprise Resource Planning. And that's not really accounting, that's something else.

But anyway, it's an accounting system. It will do your general ledger, it will do your AR, your AP, your inventory, your warehousing, your job costing and so on. Everything a mid-sized company needs from a management software perspective - to handle your money, your inventory, your ongoing work, and all that.

Business Central is the current name. It used to be - the naming stuff gets complicated. So Microsoft decided, back in 2002 when they purchased two companies in Denmark, actually one company in Denmark and one from Fargo - and they had a CRM system in the works - they decided that all the business software should be called, "Dynamics". So it's like, yeah - you're just using "Dynamics".

And then some different ways of describing "Dynamic Something", depending on which flavor it is. "Navision" was the product name at the time when they purchased. So that became "Dynamics NAV." And then when it moved into the cloud to be a SaaS cloud offering, all Dynamics products that are in the cloud are called, "365." And then to separate it from the un-prem version and to indicate that it's something new - it changed to be called, "Business Central." And we kind of like that name. It works well for the product. But it's a long name. There were versions of it, at some point in time, that was actually longer. So we kind of like it now.

Len: And it can handle - as I gather, it's for small to mid-sized companies. Under that sort of definition, what's a mid-sized company? Like 100 people?

Erik: So I think it's actually easier to describe what it doesn't do.

Len: Okay.

Erik: It's not an enterprise product. Meaning, that you would not use this to run Walmart. You will not use this to run very, very big corporations.

And the definition of enterprise is also difficult. I think in Canada, Microsoft actually labelled that there are 800 companies that are enterprise companies. If you're not among those 800, you're small to mid-size.

Len: Okay.

Erik: So huge corporations are still in this bracket. I have done, in Denmark, work for some of the biggest corporations in Denmark, using Navision and Dynamics. Banks are using it and so on. So it's really a - sometimes Microsoft has the need to put things in boxes. And they have multiple ERP offerings. So they have put one product in the enterprise box, and then they're putting Business Central in the not-enterprise box.

Len: And it used to be - as I gather, that you kind of needed someone - to hire someone to set it up for you at your company. So you'd hire consultants to set it up. But that's not entirely true anymore.

Erik: And then basically now you're on the way into the premise of the book. Meaning that you get Business Central. You used to only be able to get Business Central from a - or get Dynamics NAV from a partner network. Meaning that a company has to become a Business Central partner at Microsoft and has all the knowledge and the setup for doing that. And that was the only places you could get it. But now Business Central is just another cloud offering from Microsoft. So you can get it through any outlet that will sell you a Microsoft cloud product. So all the added value, all the knowledge that's usually there when you would buy a product like this, it doesn't exist necessarily.

Len: Oh I see.

Erik: I'd still suggest people to go to a partner with experience. But you can get it from any outlet who sells Microsoft. And basically, the whole idea behind a book is - if you go out and get the system, you will need some kind of guide to help you. Not a, "Read from, start on page one and then read until you're done on page 400." But more like, "Okay, let me look that up and see what's that about. If I need to do job costing." Or, "How do I handle backups or stuff like that?" So the idea behind the book is to be a companion when you walk into implementing Business Central.

Len: Yeah, that's really fascinating. I hadn't quite put that together. But since - given the history of the way that product was sold and maintained, there wasn't a lot of documentation out there for people to - that people could independently access?

Erik: Knowledge was within walled gardens where it was kept and nurtured.

Len: Oh, that's really fascinating. That's, yeah - that's - some of our bestselling books are books where somebody saw, "There's something missing that people really need." And if you have that knowledge, then that can be really valuable. I mean, both to yourself and to other people to provide that. And when you really meet people's needs, that's when you know you've got a good book.

Erik: The content of the book is questions I've gotten. So, "Let's put that in a book." We have a saying in the company, that, "Hey, it's in the book, just go find it," when people are asking something. But yeah, it is basically - whenever I think, "Oh that's a good trick," or, "That's something that should be known," I add it to the book.

Len: Thanks very much. Actually that gives me a great opportunity to segue to the last part of the interview, where we talk about your experience as a self-published author, and things like that.

You talk on your book landing page about how it's going to be updated over time. And in many ways, that's like the canonical Leanpub type book, right? One that can be updated, because the technology that it's about can be updated and change over time.

You mentioned just now that actually, you ask people for feedback and questions and stuff like that. How do you manage that feedback? So you ask - you put your email address and your Twitter out there on the book landing page and in the introduction, in the beginning of the book, and things like that. How do you manage those communications? Is it just kind of ad hoc, people email you and you just add it to the book, and publish a new version?

Erik: So, there is a new version of the software every six months - Microsoft is releasing a new major version every six months. They're releasing a minor version every month. The software is constantly developing.

So I got totally inspired by one of your other books, Paul Thurrott's Windows 10 Field Guide. And the fact that you know Microsoft's coming out with a new version of Windows 10 all the time. So he's updating a book, and that's actually a great way of doing it.

I had that Windows 10 book, it was in the back of my mind. And then at some point, one of your - not really your competitors, but a traditional publishing house called me up and said, "Hey Erik, we really love what you're doing on your blog and all that stuff. How about writing a programming book about Business Central for us?"

And I said, "Mmm." Not that convinced, because they already published five of them. So I'm not sure why you need another one. And the offer they made was ridiculous, from a monetary perspective. I said, "No, I'm never going to do that." But then that kind of sparked me and I'm saying, "Okay, but if I were to write a book about Business Central, what kind of book would that be?" And certainly not a programming book, even though that's what I do. That's my main area of expertise.

But, "What book is missing out there?" And then that kind of turned into, it's the field guide. It's the book that will help users get through this system - perhaps without a partner, perhaps with partner. And at some point, my brain met with the Paul Thurrott Windows 10 Field Guide and said, "That's it." So I looked up Leanpub, and that seemed fairly easy. So I started writing.

Len: Well, I hope it turned out to be fairly easy.

Erik: Yoy've got your own set of quirks in the Markdown stuff - that it takes a bit of time to figure out what's possible, what's not possible. I do love - so we didn't really talk about that - but since COVID, I'm not doing talks at conferences and all that of course, because there aren't any. So I thought, "I'll start a YouTube channel," and I've been doing that a lot since then, the approach being, I like creating content. But I do not enjoy editing. I do not enjoy pixel pushing and all that stuff. And I think - so with the YouTube Channel, I went with a sort of live approach using OPS.

And the fact with the book and Leanpub - I just create content. I don't necessarily sit in InDesign and move stuff around. I create the content and then Leanpub creates a good-enough looking book for me. I think that's - my wife, who is an architect and really obsessed with - it has to be correct and look nice - had a hard time accepting what Leanpub created. But then I asked her if she wanted to edit 400 pages of stuff, and she said, "No."

Because this is me, I created a piece of software that, when I do a screengrab and I paste that into Markdown in Visual Studio Code, then I have a program that grabs that screengrab and formats it into the right size, and puts a nice little shadow around it, and stuff like that. So all the screenshots looks the same, even though they're not same size. It's kind of automated. So if I need to add something, "That's a good one," I'll find the chapter, do the T bracket for adding a tip and grabbing a screenshot. I write the paragraph, and paste the screenshot in and then push to GitHub - and I'm done.

Len: Yhanks very much for sharing that actually. Hearing about people's processes is always really fun. For people who are thinking about writing books, to learn about how like people who've successfully done it - their tips and tricks can actually really save you a lot of time and make your book a lot better.

On the subject of formatting, that could be a subject of an entire podcast.

Erik: Yeah.

Len: Or a podcast series, even. I mean, because it's part of the history of publishing, and what the introduction of the ebook has meant. For example, if you want your book to be available in EPUB and MOBI- you just have to give up on the idea of formatting control. Because people can change the font size, they can change the font. They can kind of do whatever they want. And particularly because Leanpub is aobut in-progress publishing -

Although, making books look better on Leanpub is a hugely important thing for us in the future at some point. But, "just good enough," is good enough. And one of our jokes is that, "Until your book is done, formatting is procrastination." We know that from our own proclivities, right? You're sitting there working on your book, and then you're like, "Oh, let me get the formatting perfect." And then hours go by and you haven't written a word.

Erik: Yeah, and the problem with - in my case, my book that's covering a ever-moving target - is that the book is never done. So the concept of people buying it once and then be able to download updates is really cool.

Len: And you do have a print version out on Amazon.

Erik: Yeah.

Len: By the way, I'll make sure to link to that and to your YouTube channel, which I should've mentioned in the introduction.

Erik: No problem.

Len: How do you maintain the print version?

Erik: So the print version, I just use your export to print. The greyscales that you create are not the greatest. No sorry, so you export with the colors, and then when - so when Amazon is importing that and converting it into greyscales, their greyscale conversion is lousy. So I actually go through a loop of printing to black and white, before I upload to Amazon, because that makes the greyscales better.

Len: Okay, okay.

Erik: But that's the only thing. So I take that PDF and print it to PDF and upload that PDF to Amazon and be done with it.

Len: And how often do you do that?

Erik: Well now the book in reality is probably updated every three months, so every three months.

Len: Okay, okay. Well, thanks very much for that.

The last question I always like to ask on these episodes is - if there was one thing we could, one feature we could build for you or one bug we could fix for you - can you think of anything you would ask us to do?

Erik: Well, going back to the "people can download forever." At some point, I think it would be lovely to have - like people could download for three years. My plan with this book is that I'll continue to update it, because Microsoft is continuing to update their product. So at some point - should people get five years of free downloads, or they only get three years of free download, or -? Stuff like that.

Len: Thanks very much for sharing that. The one thing I would say is we do have a sort of "new edition" feature. When you create a book, you can go into the admin tools for the book and you can say, "This is a new edition of a previous book." And then if someone goes to the landing page for the old book, they'll see, "There's a new edition, click here to go there." And so the way people use Leanpub to - I think, to achieve what I think you're trying to get at - is after a few years, they just create version 2.0, and then people can go buy that one.

Erik: Yeah, but that doesn't really support the continuation. What I would love is that like - let's say two years or three years - something like, a period - from the moment you buy, that's when you can get the free updates. After that, you need to buy an extension or buy a new version or stuff like that. But doesn't really work if I put out a new edition, that the people who bought the old edition last week cannot get the new stuff.

Len: Yeah, it's not the same. They would have to have a new book in their Leanpub library, yeah.

Erik: Yeah, yeah, yeah.

Len: And that kind of thing. I mean it's - one thing we might have at some point, it's something if we get really - if we have our own app again and stuff like that, is - just sort of have the book update, without having to download an entirely new copy - which is actually the way it works now. So this issue of continuity, is something that we have a lot to work on. And yeah, thanks. I think you're the first person who's ever suggested that on the podcast. I'll definitely communicate that to the team, because that's really interesting.

Well Erik, thank you very much for taking some time out of a beautiful Vancouver afternoon to talk to us here.

Erik: Oh yeah.

Len: And thank you very much for using Leanpub as the platform for your book.

Erik: Thank you for creating it. I have had a lot of fun using it. So no complaints about the platform. It works tremendously well.

Len: Thank you very much.

And as always, thanks to you for listening to this episode of the Frontmatter podcast. If you like what you heard, please rate and review it wherever you found it, and if you'd like to be a Leanpub author, please visit our website at leanpub.com.