back arrowView show

6: Why do we podcast (and other projects)?

Episode description

LinksShow Transcript
Megan Schemmel: Welcome to This Old App, a podcast about learning, coding, smashing stuff together, breaking things apart, startups, failing, winning, and any other buzzwords we can think of. 

Don VanDemark: All right Randy. So I literally titled this  on our screen. What are we doing? And I think that's what we're going to talk about today is we've started to put together a number of things that you and I are working on together. So, yep. Um, let's just go over everything we're trying to do and why maybe the Why first or maybe the Why last the Why will probably be last. So let's just start listing all the things. We're trying to get done.

Randy Burgess: All right, uh number one. Uh, I guess I'll say CTO Think that is the podcast that we ramped up into summer that we talked about for maybe a year and half before it and actually launched it and now it has about 20 episodes in the can or published. We published 20 episodes. So. So that's one project.

All right. So what  why CTO Think, I guess the each of them needs kind of a why so why did we do that? Um, why did we why did we decide to start talking about boring, uh, technology executive stuff. 

Randy Burgess: So on the there's a selfish side and there's an unselfish side, um to it. I'm gonna go with unselfish first.

Unselfish is, after my teaching of the boot camp um last year there were so many side conversations. I would have one-on-one with students related to not dev, like development how to code something, but the anecdotes, the experience the side, um things about what does it take to be a good developer?

What does it take to um treat people well, work with other people well, managed things get projects done, and I was having these one-on-one conversations. I'm like, man, this advice is something that other people need to  see or hear or read or whatever and so I got more motivated after that to somehow bottle up some of this stuff.

I've learned to pass it along. All right, you can do this a number of ways, right? You can write a blog people have been doing that. You can write a book people do that. Everything I hear from authors, people that write books, is that it is a labor of love type of thing is hard to write books and you got to promote the dang thing and they hate that a lot of the time unless they love writing on a continuous basis and bloggers, it seems like the good bloggers can churn out an article every other day. Like I've never seen in my experience with writing is that I can write a ton of stuff in stream of consciousness type of deal, but then when it comes to editing I take forever and then I'm never happy with what I published right.

And then I listen to a lot of podcasts I learned a tremendous amount from hearing other people Talk Amongst their network interviewing other people about their experience. I've learned so much hearing people talk about their mistakes, what they've done well the things they ran into, how they approach scenarios where they didn't know what they are doing.

And that's really the medium that I've just captured more than any other is that me listening to podcast is very effective. And I think we see we're saying that the younger generation is moving from a  reading platform for their learning into a video or audio mechanism for learning and so I guess from my perspective if I want to spread the word about what I've learned to help other people out,

I see podcasting and maybe a future video casting as the best most time-efficient way for me to do it. 

Don VanDemark: No and and and from from a non selfish standpoint all that makes sense. I will say podcasting it took me a while to get to get fully into listening to podcasts. I would dabble in it from time to time.

I can't I I'm not one who can be sitting here working on something and listening to a podcast. Yeah, um because 15 minutes ago by and I won't have heard a single word. Um, it will have just been background noise. I don't want have whenever I'm in the car. I mean you don't drive around but when I'm in the car, I just plug in my phone and I start up my podcasts and my regardless of who's in the car.

My son's been around with me and he's listening to a lot of uh, the first season of startup from gimlet media and with me as well. So. 

Randy Burgess: Well, I listen I don't I can't listen and code. I can't even listen to the music lyrics and code. I have to have like, uh, spotify's focus section running for me to get code done typically with um, unless I like put this way in JavaScript where I have to think about everything and still learning a ton.

I have to have this like no lyrics. When it comes to rails. I can have on okay, how about rap and I'm fine because I know that stuff. When it comes to podcast, I just do it taking a shower making breakfast, um chores that I have put off and finally get around to doing um, sitting outside eating lunch, walking to the train, on the train, on the bus like I listen to podcasts when I am stuck in a scenario of my hands are free, I'm not driving a vehicle, um, which I never really do anymore. And like it's a hands-free type of or doing a menial task that otherwise my brain would just be looking for something to do. That's when I consume it. 

Don VanDemark: It's funny, you've mentioned uh, listening to podcasts in the shower before and I tried that and I it's my old man in me. I can't hear. I can't hear the uh the conversation well and I finish in the shower.

Randy Burgess: Oh, well, I have a Mini Boom. Like I have a speaker Bluetooth speaker that's pumping the sound not the phone.

Don VanDemark: I do too. I've got I've got I've got a Bluetooth speaker sitting there in the shower and it's the acoustics of it or something. It's just too too much echo-ey that to hear. Anyway, interesting. So non selfish part. What about the selfish part? 

Randy Burgess: Um, the selfish part is we had an episode on CT0 Think about networking for introverts and you know, I feel like when I when I pay attention to the people that I listen to on podcast they have a network and they have a network not just because they meet people face-to-face but because they get their name out there about what they do and how they do it and to some extent there is a one of the side effects of putting yourself out there is that people listen and get to know you um without you having to necessarily go and shake a hand and meet everybody and now that can be positive and negative. Um, I think for the first time last week, or on our what an upcoming episode we discussed a little bit about politics.

And as I thought I said I mentioned I'm a liberal in some of my views are in a lot of my Views. So it may listen to that and go, oh, I don't I don't like that dude now and to me, it's fine. I'm gonna put myself out there and you either take it or take a walk, but you know, I feel like I'm trying to now build a network because I'm consulting more and more and you know, I'm happy to give advice as efficiently as I can through this medium, but also build a brand for myself build a little bit about who I am and how I approach things and and it's helped I mean, I've already talked to people, um that have maybe, are on the verge of hiring me that are like, yeah, listen to that episode and I liked what you had to say and I'm like, that's interesting. I didn't even think about it really from a, oh, this is a pre-interview of sorts, kind of thing. But I don't have a humongous network.

Like I actually have more of a network sometimes than I think because of how people seem to find me but I'm I don't do conference circuits and I haven't written a book and that seems to be the way that most people have built in their their networks and I feel like oh, you know, um, maybe I've waited a long time to time to do this, but you know, I want I believe in the fact that lead generation opportunities are a needle in a haystack and I guess I feel that doing a podcast, publishing things is a way to increase the haystack size and maybe there's more more needles in it. Um, I guess that's the kind of the way I'm approaching it.

And you know, I don't really care to be a big political like you, "must hear my opinion, because it is right." It's just more of like this is I've worked this long. I've learned some things, made some mistakes and then corrected them and this is how I did it. Maybe you can listen to me and not follow it.

And by the way, if you want to if you're trying to get something built and or you  need a team put together or you need to build a business and you need a person with my skill set. If you listen to me and like what you have to hear and you don't want to do it yourself, hire me for it, talk to me about it.

And so that's a selfish part. But I don't know that are, I don't know that we'll have like the type of podcast is humongously popular, but we have a slowly growing audience and I still like talkin about the stuff, regardless. So it's kind of like well, what if we keep talkin about the things you like and then we just put it out there and see if other people do this. That's kind of the side effect, I guess.

Don VanDemark: Yeah, and and I I've been I've been consuming a decent amount of uh, Gary Vaynerchuk's works lately, um his content, and he's prolific on on all of this and um, it's it's the it's the same thing right which is, document what's going on put content out there and then let the market judge what what the worth is.

Yeah, and and I think that there certainly is a part of this all that that is is selfish  and it is a it is brand building and if in all our discussions people like what they what we're saying and they they want to engage us for conversations regarding their particular businesses that something we're both interested in that something we we both um have done.

Randy Burgess: Yes. So, um, there's a bit of risk in this to you can also publicly fail people can see you screw up people you and I think an example

Don VanDemark: I gave up caring. I and that's we for everyone listening, we recorded a CTO Think probably 12 months ago. If not, yeah, and then I or we tried to but what we tried to do is I tried to write up an outline and and prepare everything and get everything prepared and it just did not fly because it was too much preparation.

Um. And then when we rebooted it you were like no, we're just going to turn on the microphone and go. Um, well, we're not even gonna talk about what the topic is ahead of time. We're just going to surprise one of us will come up with something will go 

Randy Burgess: the motivation was the domain name was going to bust and I was like am I paying another $13 for this are we going to do something? Yeah. Yeah, and finally we did but it was. You know, it's a there's like this little leap forward you have to take and I wasted a week, like in hindsight now. I just talked to someone last week about their at their went to do a podcast and I'm like don't do what I did do not build a middleman static website generated podcast site for yourself. It seems fun if you're a dev, you learn a lot, but then you'll end up wasting your time. You'll want to you're dying to get on to a a SaaS product that can do it for you, which is what I feel like for CTO Think. When we did This Old App, I was able to just to like get it posted in one day and I don't have to worry about it at all.

So I've like that would be my lesson right now is don't do everything you can do yourself just because. Like to just use the tools that are out there 

Don VanDemark: developers curse, right? If you know how to do it. You kind of want to build it yourself. 

Randy Burgess: But there but going back to the failure thing. One of the risks is that you talk about something a project and then you get to a point and you either if fizzles because people will be get disinterested in it, and then what do you say to all these people that have been listening to your great idea. Um, you could be where it just fails, like you know, it's not working. Um one example is a very prolific. Um poster Nate Kovotny. I think he was he's a Serial entrepreneur developer based out of Chicago. He took a gig as the CEO of high-rise, which is a product from the base camp 37signals folks.

And he has been he video casts and audio casts and he's been working with Jason Freid one-on-one and then last month all of a sudden he came out his like yeah the Basecamp basically took the entire product back in-house myself and my team are now all unemployed and without getting into... They didn't broadcast the details.

It seems to be that basically whatever was happening between the the powers of the both parties Nate got fired and his team quit with him. Now. I those details I have to only I can only um guess on this, but the bottom line is that now he's been post making lots of posts that seem much more about someone struggling to find out what do I do next?

He handled it terrific. Um on him the way that he severed the himself from Highrise why whether it was forced or not. I thought he handled himself terrific. He really represented his his team and how he would run a company well, but now if you watch you realize he's human. He he talks like he has everything together, but he's also trying to find out what happens next and that's just that's hard to publish when you're feeling that way 

Don VanDemark: is that also part of the unselfish unselfish side effect is we're also showing people that it's okay to fail 

Randy Burgess: To be vulnerable. Yeah, I guess campaign my students so. I might students need it. I think everyone on India hackers needs it because everyone in Indie Hackers in a way feels vulnerable like their have miniature like this failing continually. Um, I mean development in itself is nothing but a bunch of bugs and failures until you get to a something that works and then you find out that oh, yeah JavaScript just made another leap forward and your code is old as crap, even though you wrote it two months ago.

So yeah, I mean the more that my students the more that I would talk to my students about those kind of little failures and not knowing what I'm doing. The more that they actually felt emboldened to keep going forward when they felt that way. So right. Yeah, definitely a good part of the unselfish part, I guess

Don VanDemark: So on ancillary note that's CTO Think, why did we decide to tackle two podcasts? Why did we start? This Old App

Randy Burgess: To me? It was more of a CTO Think was more about management. Leadership less of a technic in technical details and we kept on going down this path of talking about the details and I and I I wanted to talk about some tech but I also didn't want, if an audience was listening to CTO think about, how do I run a team? How do I become a CTO or a tech leader in my organization? And now these guys are talking about something as in like lower level of, "Can you use flutter or to build a hybrid app" kind of thing? I didn't want to confuse those two subjects I guess but I still want to talk about it.

And I also didn't want us to feel compelled, each of us, to always be the only like we have to be on every podcast talking to each other and so it gave an outlet to be a little looser to talk more detail. I could talk to my wife learning how to be a dev, I can talk to Mark who's trying to build his own company, but it doesn't we don't have to sit there and talk about well, how would you run a team of people doing that?

And how do you work like empathy empathy empathy is what we definitely keep coming back to and CTO Think but empathy, empathy and your struggle with your router and your house or dude, they're not necessarily the same thing. I want to kill that thing right now. So that's why that's to me why we started This Old App, plus the fact that we had already learned how to do CTO Think, I'm like. This is not that hard. If you don't waste your time building your own middleman generated homepage for it, 

Don VanDemark: and and my editing of the of the audio got a lot faster too, because I started cutting out. I started not cutting out every silent and pause and every um, and trying to really get it tight. I was just like, nope sounds good enough.

So, um, it's certainly that the the length of time it takes to edit. It is like 1 times the time it takes to listen to it. So it's not. Too bad. The only problem is I have to listen to everything we just said again. So yeah. Well, I mean I do that too, but now I have that Descript App, which lets me do my normal routine and do the transcription of the same time, right?

That's to me beautiful because one of my goals was to run a podcast where we could do transcriptions with every episode in the cost was just kind of prohibitive. Because I understand you're gonna pay a transcriber a human to do this well, I mean your wife does this for a living and I don't think that the costs are too high for the work they do.

I just know that this is the budget I have and being able to find a tool that will kind of let me work in my own normal editing process about an hour per episode and not add time to it and then get that result is like. Sweet now, I can really do these podcasts the way we kind of originally envisioned them.

So that's cool too. 

Don VanDemark: Right? So what um, so enough about podcasting we've got about 40 other things going on as well. Um, let's talk about let's talk about Chasms here. Um, Chasms is a project that we started based on a need. I have within Construction Specialties where we have technicians in the field texting one of us in the office with updates and pictures of the work that sort of thing and that was a one to one relationship.

And if the person in the office didn't update, um Trello which is what we use to manage all our work orders. Didn't update Trello with that information. It got lost in somebody's text messages. So yeah, I was looking for a solution where it would not a group text because a group text would be all the technicians and all the office people together, which is just too noisy.

Um, what I wanted was a one-to-many relationship from the technicians to the office. Um to where each technician could reach in, send in a text and pictures and everybody in the office would see it. So, um, we kind of cobbled together a solution, um that the technician can send in a text to a single number and then that text pops up in Slack.

That it's working great, um or two weeks in it's working just fine. Um really are not having any issues with it. We had a couple of times last week where somebody would try send a text. It wouldn't I'm sorry, uh, somebody in the office would try send a text to a technician it wouldn't go through but that problem has not reappeared.

So I did. Oh did it? Yeah. Okay. I saw log today that had two failures. I will go look at that Papertrail. Um, but we already know how to fix it like this. It's the same issue. Anyway, yes. So yeah, so talkin about it. The concept is working. Um now it's not worth it to this point it's been worth your time to help out on it.

Um, simply because it helped you dive deeper on Node and and express and all that. Um, but I think we're also trying to make it commercial. Yeah. We're trying to take it to other companies that might have similar problems. I'm so far. I've talked to two and one, um, just turns a blind eye to the problem and says, "Well, we don't we don't allow our technicians to text information, we require them all about email it" which is a solution I guess.

Um, but that requires a technician to have data on their phone. Whereas SMS messages can sometimes get through where data can't, um, and the second company had talked to use as a field service management solution, um to do all their communication as well. Um now again, that's a data that's a data on the mobile phone problem.

Um, but that also integrates the communications are doing right in that system. So, um, that's something we've talked about as well that I'm I'm still struggling with was all the field management of field service Management Solutions. I have looked at don't match what we specifically need at Construction Specialties.

Um, so we've we batted around the idea of building one, but I'm reticent to make that jump. I'm just because of the uh, it's the same problem. I have with project management tools. There are thousand project management tools out there because everybody has their own way of doing things. Um, and I have a feeling it's the same way with field service maintenance is.

Everybody has their own way of doing things. So if you build one, you won't necessarily get people to think yours is the best but that's that's kind of the Chasms product. What what so I had I had plenty of reasons to get it working and I was going to get it working on my own what benefits did you see of jumping in and helping 

Randy Burgess: selfishly like just for my benefit, working on real problems and building the solutions is how I learn everything and I can do a million To Do apps I can do a million video tutorials, but nothing bakes it into my brain, a technology, like taking a real problem and working through all the edge cases to get it working as close to how a human being needs a solution done.

And I this was the this was a very easily explained problem where you could solve most of it without having to invent a completely integrated system that required huge onboarding problems. I mean, you got two people on your team on-boarded in like 30 seconds to our solution and that was amazing like it was amazing.

It was just more of. That's not hard to get hundreds of people involved in then right? 

Don VanDemark: So so just so you're aware. Are you talkin the office side or the technician side to side? Okay. I'm outside. We're up to like 10 or 12 now. Yeah, and I saw the two and I was like, that is the simplicity of onboarding at its best.

Don VanDemark: And that special we were striving for is it the solution did not work if it was too difficult for the technicians to do because technicians are busy people they they do not typically have patience for for figuring out a new application. So the whole goal was let's not give them a new application.

All we're gonna say is, here's a new phone number to text information to don't worry about the details after that. 

Randy Burgess: So with that problem-solution simplicity and my knowledge of I could have built this in Rails within a week and had a well-tested and stable system, but the problem would have been that you are not a Rails developer and that would have distanced you from working on it.

So now we both share a code base that we can both work in and that this product project has helped that tremendously I have learned much more about Google Firebase and I've been kind of I mean, I've been using cloud services forever, but I haven't used a system. I've been using Heroku for a lot of Rails stuff and I've used AWS for all sorts of things.

But now I'm using a system even more managed like, Google does even more of the management with the Firebase. so I started to push deeper into that of course is pushed my Node and JavaScript skills, and now React I'm building building our an interface for the admin stuff in React and it's just pushed all that so much faster forward because I have something to work towards despite the fact that.

You know you made the statement to me a week ago, you know, "I don't want you to work on this and think that like it may only be for Construction Specialties and then it doesn't go anywhere," and I'm thinking that is the that's that's not even the worst thing. The worst thing is that I work on all this and then somehow I forget it all.

To me. It's like I'm pushing forward with building something, learning a completely new framework, learning more and easier to manage backend. Um, and I'm able to sell those skills later at the very worst case scenario. So that's to me the motivation Plus. Honestly, I like working for myself. I don't I don't mind working for people or companies but there's always something to be said for being able to manage your time, um and work directly with users and clients, which I love to do.

And so if we can build this into a some kind of business that actually has an income. Um, I'm all for trying that and making it work. 

Don VanDemark: You and I have known each other for about 10 years and been friends for probably seven. We've been trying to get to this point for seven years to where we're working on the same thing and we finally got there mainly because you moved uh technology-wise there were times. I tried to move into Ruby and I just there was there was no. There was no uh incentive um, and and and there were times it was tough. So, um, so this now before we did all this and before we did Chasms, uh about six months ago, we both left into Alexa skills as well.

And we're trying to learn how to how to do that now that you took a I'll call it a novel approach? Um, I don't I don't think you'd take that approach again today. But but uh, but we've also got a Alexa skills knowledge at this point that we at least know how the platform works. I wrote one for reviewing High School football rules.

You worked on one for um, the local train station arrival times up there.

Randy Burgess: Yeah, like how do I feel about Alexa and oh like these little robot talking things. Um, I feel like I need a kid to really show me the most show me that utility. Like I hear that people like children and younger, um, people are able to latch onto these devices and really use them efficiently and I feel I feel like I'm talkin to a freaking Palm Pilot like this. This can't be all you're good for, your clunky. I mean Megan and I can be watching TV and it just starts talkin to us randomly and I'm like, there's nothing that I should have triggered you said right now, right and.

And so even though I built I built like you said I kind of I used Rails to build a back-end that let that would let me easily build a um an app that could talk back and forth and I could can expand upon it pretty quick. But then I was like what am I really going to do with this? I don't even I don't I'm not either.

I'm not in the mindset of using these things. Or in which is not often with tech but I feel like I just don't feel like this iteration of it is really effective. But I think I lack I don't somewhere there's this gap and it could be age. It could be other things I've used but I just haven't seen a demand for it.

I don't I don't sit there and go. I wish this device would manage my Spotify choices for me, or I use my hands in the mouse and a keyboard too much like every time I get involved with this device, I feel like I'm climbing a wall just to get it to understand what I'm saying, and I'm not talkin foolishly.

Don VanDemark: So. I agree with I I don't think it's quite the Google Glass, um stage. I think it's a little bit further down the line than that was um, I feel like it's still missing that killer app, um, which is everything that that eventually turns a technology on right is the killer app.

Randy Burgess: It's called. I think it's called Jarvis and eventually becomes the Vision who can shoot things out of his forehead? That's what I think 

Don VanDemark: that's not yes that is technically a killer app, but not the not the definition of the word killer I was looking for so so no, that's um, I I'm going I think we both also suffer from the issue of we have so many ideas and only so much time.

Because I'm still working on not working. I'm not technically not working out right this minute, but there's not a day recently that hasn't gone by that I'm like I need to I need to refine that that high school rules app because the national officials conference is coming up in July. If I were to have this ready by then, it might actually be a skill that might get used.

Um, So it's one of those things. I'm like, it's it's just not high enough on the priority. If I put that on my priority list that I'm not working on Chasms enough because Chasms needs my attention. And if I'm not and if I'm working on both of those then I'm not paying enough attention to Aspiredu or Construction Specialties, which are the two things I've really need to be paying attention to and yeah,

Randy Burgess: you're talkin about real life because now I'm. I got a new project that's launching in mid-May, which it does involve like a ReactNative app and Firebase back end and I have normal clients that I'm working with and a potential new client, um that I may be consulting with in the next month.

So real life does jump in and the thing is I'm not doing some of our side stuff to get rid of these clients because I I only work with people I really like and and the projects I like which is a nice thing. I've worked myself up too. So it's just a matter of finding the right mix of things to do.

I would prefer to be focused on one or two things rather than what I feel is like six right now. But I don't I don't feel like the podcasting is is that much of a project anymore and the sense of how do we do this? How much work does it take? Like, I feel like it's a the long-term benefit on the side that is not to me a distraction.

Don VanDemark: I didn't even list that as one of the things I'm doing. That's how that's how day-to-day it's become. It's actually not hard at all to it takes us the time to talk and then just about that much time again to edit and then I'm done. Um now two weeks ago, I forgot to do the editing and you had to jump into a real quick.

But um, but besides that it that the podcast I'm not even considering. So all of those things fall under fall under the things we're working on together. Um, And and we could have a whole we could have a whole discussion as well. As far as what do we do with all that do we create a company? Um to put an umbrella company like Alphabet at Google started to capture everything and we went through name iterations and and we talked about the Slicing the Pie mechanism for equity and all that and those are all things we still have to do and those are probably things will will go ahead and discuss on future episodes as well as as we make those decisions and I'm really I seen

Randy Burgess: I'm realizing a little that we are we're so old and out of it because we haven't mentioned Bitcoin at all. Like I'm happy about that. I'm not going to say it again. I refuse to say again, but no as far as 

Don VanDemark: as far as blockchain technologies. Yeah. I've been trying to keep an eye on it. But to be honest it just I I can't um, I've got too many other things that I I can see. A pathway to something, um blockchain, it's not that I doubt blockchain is that I doubt my knowledge in it in my honestly my interest I have no doubt it'll be a successful technology. I think I'm interested in. 

Randy Burgess: Yeah, I mean to me it just solves, it creates more problems than it solves right now. It seems um,

Don VanDemark: I was gonna say now all that said I am opening up my coinbase account. Um because I did invest and I'm finally ahead again. I was behind there for about six weeks. 

Randy Burgess: I put a I don't even to me. I don't know if it's a database with encryption yeah, exactly. Okay big deal show me it's utility versus the pain to get it working. And then everyone's like invest I'm like wait a second. I went from problem solving to investing in the span of the second talking about this. Okay, let's forget. I don't anyone talk about it. It's just such a waste of brain space for me right now.

But um, yeah, I think that's it.

Don VanDemark: I think that's all we're working on right now everything we've discussed but I mean, I think we wanted to put this episode together just so everybody understood what what we're trying to do and and and that there are other I know there are other people doing the same thing or, you know, having having 10 ideas and only being able to work on three or four.

Um, so what we're gonna do is we're gonna sit here and we're gonna document um our work with Chasms you and I have two or three recordings already in the can for it. Um, and we're about to do another stand up after this and and those were kind of splicing together just the interesting bits, um, instead of a recording the whole instead of putting out the whole thing.

Um, so that people can can see how products are how we build products. I'm not going to say our products are built 

Randy Burgess: So within the de sold app podcast, it'll be a sub series kind of right that we chained together and it may not be won't be serial. It will just have part 1 part 2 whatever it'll be about us hearing us talk about building this app together.

So. It's helpful to me when I hear people that are trying to work and build things as solo founders or developers where they hit roadblocks and what they do to get past it because then I know like I either feel like oh, yeah, I felt that way or oh I need to look after that myself. So I think that's kind of our we're going to have these conversations anyway, and because we never record everything might as well keep doing it and see if it becomes a value to somebody.

Don VanDemark: And I even mentioned the other day that uh on slack to you that I was gonna I was gonna put one of these on Twitch. Um, and I started to look into that just not because I expect anybody to actually watch it's figuring out the platform right? It's what does this platform do and and where does it because.

Just in figuring that out. I saw hey, there are other talk shows. So you know what it may not be a bad idea. Um, so you may see us on a twitch Channel near you sometimes 

Randy Burgess: well, I'm gonna because one of my goals is to move all of our Express server functionality that's hosted on Heroku and break it into Cloud Functions on Firebase.

I might do a Twitch where I live do that. Oh for sure. It's scary as I don't videotape myself coding because I feel like I'm slow as crap, um mainly because of distractions. Maybe this will be where I don't look at baseball stuff at all. Well do it. I'm not gonna, I can't show the world how much baseball I watch during while I code.

Don VanDemark: Well, and you don't want to you don't want to reveal that that you traded away Otani either many years ago man.

Randy Burgess: I got Acuna I don't care about Ohtani, Acuna is where it's at 

Don VanDemark: for all those who don't under who don't follow baseball. They're completely lost now. 

Randy Burgess: Oh, they I got lost 15 minutes into this thing probably for sure.

Don VanDemark: So so that's that's pretty much what we uh, what we what we're doing here. Um, and we'll keep will keep recording we'll keep talkin and one thing we've started to get feedback and and that's that also feeds us, right. We are we are highly likely. To talk about something that somebody requests. Yeah that we talk about because we're not going to have all the ideas.

So, um, we will likely talk about it. If you if you tweet at us or hit us on Instagram or comment in the in the comment section on whatever podcast app you're using. Um, or did I miss a channel that I say email us.

Randy Burgess: Uh-uh, you can post review on iTunes and just say these guys are great, but I wish they would talk about this and then we'll do it guaranteed.

We got to review on CTO Think, 5 Stars. Yeah, um how many stars one five five out of five and they said, "that this is not just for CTOs. This is for everyone." They have a they have a username that looks like a Russian did it but and I don't know the name was Patty B, which is also my mom's name, but it didn't sound like my mom, so, I don't know, but if it was you Mom, thank you. But we need other people. 

Don VanDemark: So that's the other thing maybe maybe one of us did actually pay for Russian Bots to to garner reviews then and that's another way of testing a platform. I don't think either of us did um, but yeah,

Randy Burgess: Is that Mueller at your door because I hear a knock.

Don VanDemark: Anyone, uh, so I think that's everything for this. Um, and we'll fire up the next uh, next Chasms one here shortly

Randy Burgess: All right, talk to you later. 

Megan Schemmel: Thanks for listening to This Old App.

Notes and previous episodes can be found on our website at https://www.thisoldapp.online. 

Reviews on Apple and iTunes are always appreciated and help promote the show 

For questions, comments, or things you would like to hear on future shows, please email us at hello@thisoldapp.online

Show music is Guns Blazing by Fab Claxton, music licensed by pond5.

Voiceover work by MeganVoices.com.

You'll hear from us soon!


episodes iconMore Episodes

19: To Test or Not to Test?

September 18th, 2018

50:07
Topics Covered
  • Test Driven Development
  • RSpec
  • MiniTest
  • Rails Test
  • Jest
  • Mocha
  • Jasmine
  • Nightwatch
  • Cypress
  • Selenium
  • Good ol' fashioned browser refreshing

18: What to Use for Mobile Development?

August 28th, 2018

46:15

17: Grab Bag - GraphQL vs REST, Websockets, Uber Fusion, Redux Sux, and Firestore Search

August 7th, 2018

56:09

16: Returning to Game Development with Renee Lahoff

July 24th, 2018

41:03

15: Benefits of Coding While Streaming with Jesse Weigel

July 10th, 2018

47:21

14: Moms Can: Code with Bekah Hawrot Weigel

June 26th, 2018

52:22

13: Callbacks! and Promises! and Awaits! Oh My!

June 19th, 2018

28:50
  • JavaScript
  • Asynchronous
  • Callbacks
  • Promises
  • Async/Await
  • Typescript
  • Firebase

12: Relational vs Document DBs

June 12th, 2018

51:32
  • Lotus 123
  • Excel
  • Microsoft Access
  • SQL Server
  • MySQL
  • PostgreSQL
  • MongoDB
  • Firebase Real Time Database
  • Firebase Firestore
  • Amazon DynamoDB
  • Couchbase
  • PouchDB

11: Project Chasms - Part 3, Prototype Feedback and The Bug

June 5th, 2018

40:44
  • We talk about the success of the prototype as it is being used by a service provider
  • We talk about known costs for some of the APIs being used
  • We …

10: Appraising Alexa (and other voice interfaces)

May 29th, 2018

54:25
Loading ...

Download the RadioPublic app for
 FREE and never miss an episode.

Get it on Google PlayDownload on the App Store