Jakson Maya Posch: Coding, Curiosity & A Life Built Around Learning täydellinen litterointi

00:05:16.050 --> 00:05:21.269 the family computer initially. You can put in 00:05:21.269 --> 00:05:23.829 a floppy when it says this on the screen, things 00:05:23.829 --> 00:05:27.970 like that. And it was hard back then, because 00:05:27.970 --> 00:05:30.490 nowadays you get super descriptive messages. 00:05:31.430 --> 00:05:34.490 But back in the Commodore days, I never used 00:05:34.490 --> 00:05:36.350 one personally. But in the early Apple days, 00:05:36.949 --> 00:05:39.850 or the DOS -based machines, or UNIX sort of systems, 00:05:40.250 --> 00:05:42.529 it was just a terminal. And you had to do everything. 00:05:42.569 --> 00:05:45.889 Even to open Monkey Island, it was like run C 00:05:45.889 --> 00:05:48.730 colon slash slash, all these things that now 00:05:48.730 --> 00:05:52.069 we take for granted. Maya you have to understand 00:05:52.069 --> 00:05:54.870 that Felipe is like 12 years old so I understand 00:05:54.870 --> 00:05:56.610 everything you're saying because you and I are 00:05:56.610 --> 00:05:59.449 probably about the same age and I had a Commodore 00:05:59.449 --> 00:06:02.689 64 and you know Mike I learned through the family 00:06:02.689 --> 00:06:06.430 as well just like you but he's like 12 so He 00:06:06.430 --> 00:06:08.430 probably doesn't even know what a floppy disk 00:06:08.430 --> 00:06:11.410 is to be honest with you Just the smaller ones 00:06:11.410 --> 00:06:14.129 I never got to use the super big ones or cassette 00:06:14.129 --> 00:06:17.250 tapes But I did get to use I think it's three 00:06:17.250 --> 00:06:22.009 and a quarter inch floppies Yeah, that one. See, 00:06:22.050 --> 00:06:27.170 I don't even know the size. This is like a history 00:06:27.170 --> 00:06:30.550 lesson for me. Yeah, yeah. They're not CDs, Felipe. 00:06:30.829 --> 00:06:33.910 They're floppy disks. I consider myself like 00:06:33.910 --> 00:06:36.069 old school because I've been using Mac since 00:06:36.069 --> 00:06:39.490 like the, I don't know, the 90s. But, you know, 00:06:39.629 --> 00:06:42.870 it still had a mouse and a graphical user interface. 00:06:42.910 --> 00:06:45.329 So that's the earliest I know about computing, 00:06:45.449 --> 00:06:48.569 but... for us in general, technology has always 00:06:48.569 --> 00:06:50.449 been a part of our lives, even when we were little, 00:06:50.889 --> 00:06:52.689 but how did you get started with programming? 00:06:52.829 --> 00:06:54.649 How did you make the jump from being sort of 00:06:54.649 --> 00:06:57.589 interested in computers and sort of tinkering 00:06:57.589 --> 00:07:00.209 and hacking to actually writing your own code? 00:07:01.209 --> 00:07:05.250 The interest always was there, I guess. I can 00:07:05.250 --> 00:07:07.189 remember two things which actually stimulated 00:07:07.189 --> 00:07:11.759 me into actually trying some stuff was... On 00:07:11.759 --> 00:07:16.519 the DOS system we use Microsoft DOS 5 .5, I believe. 00:07:16.699 --> 00:07:20.980 It actually has the QBasic, Vernaval, et cetera, 00:07:21.120 --> 00:07:24.040 something installed there with some sample applications. 00:07:24.680 --> 00:07:28.579 So played around a bit with that. Also in the 00:07:28.579 --> 00:07:30.920 computer magazine, not a computer magazine, but 00:07:30.920 --> 00:07:34.300 a general technology science magazine we had. 00:07:34.639 --> 00:07:39.910 I was actually subscribed to at the time. code 00:07:39.910 --> 00:07:43.329 listings in it. Quick basic, of course. So I 00:07:43.329 --> 00:07:46.970 was like, oh, I've got this development environment. 00:07:47.470 --> 00:07:50.829 I've got a code there. It does stuff. Let's just 00:07:50.829 --> 00:07:52.850 start typing it into the computer and see what 00:07:52.850 --> 00:07:57.529 it does. Hey, it works! Modifying that, and I 00:07:57.529 --> 00:08:00.189 got this drawn circles on the screen in different 00:08:00.189 --> 00:08:03.110 colors. Seems like that's really basic, but... 00:08:03.129 --> 00:08:04.970 I was like, okay, I want to do more with programming. 00:08:05.209 --> 00:08:08.009 Quick Basic didn't really attract me for some 00:08:08.009 --> 00:08:11.949 reason. By the time I started to really think 00:08:11.949 --> 00:08:14.310 about doing programming, we had already Windows 00:08:14.310 --> 00:08:18.029 95 and things like that, so it's a bit more graphical 00:08:18.029 --> 00:08:20.149 and you're like, okay, new languages, what do 00:08:20.149 --> 00:08:23.850 you have? I got, I think for my birthday or something 00:08:23.850 --> 00:08:26.730 like that, I got a book about Visual Basic 5. 00:08:27.909 --> 00:08:31.509 So, teach yourself physical, basic five in 24 00:08:31.509 --> 00:08:34.289 hours. Oh gosh, I think I have that same book. 00:08:37.110 --> 00:08:40.350 They're still around. I still see the Sam's teach 00:08:40.350 --> 00:08:43.330 yourself C -sharp in 24 hours or in 21 days. 00:08:44.250 --> 00:08:46.990 Yeah, it's 24 hours. I have no idea what metric 00:08:46.990 --> 00:08:50.750 they use actually. I don't know. 24 hours per 00:08:50.750 --> 00:08:54.059 chapter? Sure, 24 hours for the whole book. No. 00:08:54.460 --> 00:08:56.700 Yeah, yeah. It's definitely just, I guess, a 00:08:56.700 --> 00:08:59.159 marketing plot. I don't think I've ever finished 00:08:59.159 --> 00:09:02.860 one of those books in under 24 hours. No, no, 00:09:02.860 --> 00:09:06.820 no. How did you get started, Tammy? Because I 00:09:06.820 --> 00:09:09.139 don't think I've ever asked you what your first 00:09:09.139 --> 00:09:12.740 language was. It's funny. I feel like... In talking 00:09:12.740 --> 00:09:14.799 with Maya, I'm kind of like talking to myself 00:09:14.799 --> 00:09:17.500 because you're saying a lot of the same things 00:09:17.500 --> 00:09:19.519 like, oh, you know, I started banging on the 00:09:19.519 --> 00:09:22.019 keys and wow, I can make it do that and then 00:09:22.019 --> 00:09:24.919 moving from basic to visual basic. And it's kind

00:09:24.919 --> 00:09:28.120 of like a progression thing. You know, it's baby 00:09:28.120 --> 00:09:32.100 steps. You know, my first job, my first real 00:09:32.100 --> 00:09:35.200 job doing computers, I was just a bench technician. 00:09:35.240 --> 00:09:37.740 I didn't do much more than put wires together. 00:09:38.240 --> 00:09:40.200 And if I didn't electrocute myself, it was a 00:09:40.200 --> 00:09:43.169 good day. And then from there, I just moved up 00:09:43.169 --> 00:09:45.889 to support, to programming, to development, to 00:09:45.889 --> 00:09:48.990 design. I always say that I'm like the Homer 00:09:48.990 --> 00:09:51.549 Simpson in this field because I just sort of 00:09:51.549 --> 00:09:54.309 step into the next thing. And Maya, I looked 00:09:54.309 --> 00:09:57.870 at your CV. It almost looks like you're like 00:09:57.870 --> 00:10:00.649 a mirror image of me. It's so cool. I'm just 00:10:00.649 --> 00:10:02.950 sitting here so quiet listening to you. But now 00:10:02.950 --> 00:10:05.129 he asked me a question and is forcing me to talk. 00:10:05.230 --> 00:10:07.669 So I'm going to let you talk and tell us from 00:10:07.669 --> 00:10:11.039 Visual Basic, where did you go next? Well, to 00:10:11.039 --> 00:10:13.059 be quite honest, I didn't do a lot of this, but 00:10:13.059 --> 00:10:16.120 mostly because the demo code was supposed to 00:10:16.120 --> 00:10:18.679 be on the provided CD, didn't really mess up 00:10:18.679 --> 00:10:21.120 with the book for some reason, publishing error, 00:10:21.340 --> 00:10:25.840 sorry, Sam's. So I kind of just was like, oh, 00:10:25.919 --> 00:10:29.139 and it didn't really work for me, whatever, weird. 00:10:29.740 --> 00:10:33.659 Then I got a book, not a Sam's, something else 00:10:33.659 --> 00:10:37.360 about Java. I think it was a really old version 00:10:37.360 --> 00:10:40.360 of Java 4 or 5, something like that, you know, 00:10:40.580 --> 00:10:44.340 ancient history. Back when road types are still 00:10:44.340 --> 00:10:48.559 accepted in Java. There's a bit of programming 00:10:48.559 --> 00:10:51.240 with that, so it's like, okay, yeah, that's really 00:10:51.240 --> 00:10:53.360 interesting for some reason. It didn't really 00:10:53.360 --> 00:10:56.139 catch my attention. It doesn't really until, 00:10:56.440 --> 00:10:59.000 I don't know, I've been on the internet for a 00:10:59.000 --> 00:11:04.259 while and I guess I stumbled over C++. That's 00:11:04.259 --> 00:11:06.700 like, OK, it's a cool language. It's used everywhere, 00:11:07.080 --> 00:11:11.279 and I like cool. And Java, it was even back in 00:11:11.279 --> 00:11:14.279 the 90s, especially, was that hipster thing, 00:11:14.940 --> 00:11:18.259 like those Mac users, eh, stay away from it. 00:11:19.860 --> 00:11:22.639 It wasn't as easy back in the day, because you 00:11:22.639 --> 00:11:25.559 mentioned you got your first basic book and then 00:11:25.559 --> 00:11:30.250 Visual Basic in 24 hours, miraculously. But now 00:11:30.250 --> 00:11:32.470 we have the internet, so you can just go online, 00:11:32.610 --> 00:11:35.190 buy a book on Amazon, get it on Kindle. If something 00:11:35.190 --> 00:11:36.990 doesn't work, for example, this is something 00:11:36.990 --> 00:11:39.090 that I ran into as well, where you would get 00:11:39.090 --> 00:11:42.570 CDs, like it was common for HTML or any sort 00:11:42.570 --> 00:11:45.090 of programming book to come with a CD. And if 00:11:45.090 --> 00:11:47.230 there was errata or something, you were pretty 00:11:47.230 --> 00:11:50.330 much doomed because there wasn't internet where 00:11:50.330 --> 00:11:52.289 you could just go to a forum and say, hey, Mr. 00:11:52.450 --> 00:11:54.350 Author, or tweet the person and say, you know, 00:11:54.409 --> 00:11:56.789 your code is broken here. And they tweet back 00:11:56.789 --> 00:11:59.970 in like 24 hours. It was a struggle. It was, 00:11:59.970 --> 00:12:03.389 it was really, you know, I do admire people who 00:12:03.389 --> 00:12:05.850 did it back then. I gave up on physical basic 00:12:05.850 --> 00:12:09.450 five because of that issue. And we, well, actually, 00:12:09.590 --> 00:12:12.570 no, uh, we had, I think by the internet on my 00:12:12.570 --> 00:12:15.129 father's computer, but we couldn't really use 00:12:15.129 --> 00:12:20.210 it a lot. So we weren't used to actually, well, 00:12:20.370 --> 00:12:22.690 I have a problem. I go to the internet and I 00:12:22.690 --> 00:12:25.129 search because we didn't have Google either back 00:12:25.129 --> 00:12:28.580 then. So. It's like, okay, internet, blinking 00:12:28.580 --> 00:12:33.480 cursor, what? But with C++ it's kind of funny, 00:12:33.580 --> 00:12:37.320 because I was like, I want to learn C++. I just 00:12:37.320 --> 00:12:39.720 need a good reference book, because yeah, I like 00:12:39.720 --> 00:12:44.740 my dad's read books stuff sometimes. So this 00:12:44.740 --> 00:12:48.399 is a really good book from the creator of C++, 00:12:48.620 --> 00:12:52.419 Jan Søsterup, with the C++ programming language, 00:12:52.720 --> 00:12:56.299 very creative title. That's pretty much the definitive 00:12:56.299 --> 00:13:00.460 book on C++. Back then things still is. It's 00:13:00.460 --> 00:13:03.320 updated for new versions, but I looked it up 00:13:03.320 --> 00:13:07.440 on the internet. Got the ISBN number. I went 00:13:07.440 --> 00:13:10.460 to the local bookstore, had them order it for 00:13:10.460 --> 00:13:16.120 me. No Amazon. Yeah, so I went picking it up 00:13:16.120 --> 00:13:18.559 at the bookstore and delayed by the counter, 00:13:18.679 --> 00:13:21.220 but I was like, I've got it here and flipping 00:13:21.220 --> 00:13:23.399 through it a bit and like, you can understand 00:13:23.399 --> 00:13:28.809 that. It's incredible. I was like, meh. So what 00:13:28.809 --> 00:13:31.190 caught your attention about C++? Were you intending 00:13:31.190 --> 00:13:34.029 to do some high performance

operations, write 00:13:34.029 --> 00:13:36.429 your own compiler language, play around with 00:13:36.429 --> 00:13:39.850 that, game engines? Yeah, just the whole performance 00:13:39.850 --> 00:13:42.710 stuff. Just the things C++ were being used for 00:13:42.710 --> 00:13:46.570 back in the 90s when it caught my attention. 00:13:47.029 --> 00:13:50.110 I mean, your rights operating systems in C++. 00:13:50.600 --> 00:13:53.559 you write compilers, you write pretty much every 00:13:53.559 --> 00:13:58.200 single series application you write in C++. And 00:13:58.200 --> 00:14:03.000 because C++ is a superset of C, why not? I mean, 00:14:03.139 --> 00:14:05.899 it makes perfect sense. So I just got started 00:14:05.899 --> 00:14:10.580 with, they had the free command line Borland 00:14:10.580 --> 00:14:13.820 compiler. That is the one I started with. So 00:14:13.820 --> 00:14:17.440 everything command line and I had used Crimson 00:14:17.440 --> 00:14:24.259 editor at the time as my IDE. So Maya is writing 00:14:24.259 --> 00:14:26.759 her own little CPU architecture just to play 00:14:26.759 --> 00:14:28.879 around. I think it's just a hobby project, but 00:14:28.879 --> 00:14:33.879 she wants to write it. With some possible commercial 00:14:33.879 --> 00:14:40.759 outcomes, if it works. So I think, no idea. I'm 00:14:40.759 --> 00:14:43.840 just actually on my programming block. I also 00:14:43.840 --> 00:14:47.419 am beginning to document. development of this 00:14:47.419 --> 00:14:50.419 processor architecture. The architecture itself 00:14:50.419 --> 00:14:57.019 is called NGS, Nyanco grid scaling system. It's 00:14:57.019 --> 00:14:59.059 the name kind of says what it is about. It's 00:14:59.059 --> 00:15:01.919 mostly about HPC, high performance computing. 00:15:02.600 --> 00:15:06.340 So a bit more streaming oriented and just getting 00:15:06.340 --> 00:15:10.220 many threads going as possible and the increased 00:15:10.220 --> 00:15:13.370 amount of overheads you have. That's the thing 00:15:13.370 --> 00:15:15.470 which really annoys me with current processor 00:15:15.470 --> 00:15:18.690 architecture is that you have the immense amount 00:15:18.690 --> 00:15:21.309 of overhead from the operating system and from 00:15:21.309 --> 00:15:26.809 context switching and on x86 you've got a whole 00:15:26.809 --> 00:15:30.730 ring 0, ring 1, ring 2 nonsense to switch from 00:15:30.730 --> 00:15:34.549 kernel space to active space, user space. It's 00:15:34.549 --> 00:15:39.029 like you can almost see the layers of history 00:15:39.029 --> 00:15:41.850 there. It's like, you peel it back, oh yes, back 00:15:41.850 --> 00:15:45.090 there in 1980, whatever, they were like, well, 00:15:45.110 --> 00:15:47.830 that's a good idea. And then back in 1992, they 00:15:47.830 --> 00:15:50.090 were like at Intel, well, let's change the status. 00:15:50.970 --> 00:15:54.590 It's like you've got the, yeah, dating back to 00:15:54.590 --> 00:15:59.669 the original X68 architecture, X86 architecture, 00:15:59.909 --> 00:16:03.330 you've got the memory gap at 20 megabytes, I 00:16:03.330 --> 00:16:09.450 believe. So if you go past the address thing, 00:16:09.529 --> 00:16:14.029 you go past 20 megabytes, you loop back to the 00:16:14.029 --> 00:16:18.450 first memory address, things like that. Because, 00:16:18.450 --> 00:16:21.029 I mean, if you look at processor architecture, 00:16:21.269 --> 00:16:23.669 you cannot escape looking at older architectures, 00:16:23.750 --> 00:16:27.830 like, for example, the PDP 11, PDP 8, even the 00:16:27.830 --> 00:16:30.690 INIAC, and architectures like that, because you're 00:16:30.690 --> 00:16:34.210 like, well, they had ideas back then. We have 00:16:34.210 --> 00:16:37.429 ideas right now. we can look at their ideas back 00:16:37.429 --> 00:16:40.009 then because, I mean, computing hasn't changed. 00:16:40.870 --> 00:16:43.649 One of the programming languages I also like, 00:16:43.850 --> 00:16:46.830 Ada, is actually named after the first female 00:16:46.830 --> 00:16:52.529 programmer in history, 19th century. So, yes, 00:16:52.889 --> 00:16:55.809 there were also computers back then, although 00:16:55.809 --> 00:16:59.570 they were mechanical in nature. Like the Turing 00:16:59.570 --> 00:17:04.519 machine or? Yeah, just like from Bobbing. You 00:17:04.519 --> 00:17:08.720 know, just those with a lot of moving parts and 00:17:08.720 --> 00:17:11.380 a bit more fixed function, not a generic function 00:17:11.380 --> 00:17:17.000 like today's. But yeah, let's look at why they 00:17:17.000 --> 00:17:19.740 did certain things like that back then and why 00:17:19.740 --> 00:17:24.220 we're doing things like we're doing today. Can 00:17:24.220 --> 00:17:26.559 we learn something from back then? Why did we 00:17:26.559 --> 00:17:30.640 end up here? What is your preferred language? 00:17:30.680 --> 00:17:36.349 Is it C++? Definitely C++. The thing which makes 00:17:36.349 --> 00:17:40.490 me like C++ so much is that C++ doesn't limit 00:17:40.490 --> 00:17:44.130 you in any way. Because C++ is so close to C 00:17:44.130 --> 00:17:47.549 with itself is basically this high level assembly. 00:17:49.109 --> 00:17:51.769 C++ also has the more higher level concept like 00:17:51.769 --> 00:17:55.609 object -oriented programming. So C++ adapts to 00:17:55.609 --> 00:17:58.630 whatever programming style you'd like or which 00:17:58.630 --> 00:18:01.890 you need for a certain application. One moment 00:18:01.890 --> 00:18:07.710 I can just be doing some really low -level bits 00:18:07.710 --> 00:18:12.450 -wise operator, whatever, byte -shifting codes, 00:18:13.029 --> 00:18:15.190 C++, and next moment I'm doing some high -level 00:18:15.190 --> 00:18:18.690 framework programming in Qt. It's only high -level 00:18:18.690 --> 00:18:23.069 classes and messaging and signaling, and it also 00:18:23.069 --> 00:18:26.099 works. There are no real limitations, and that's

00:18:26.099 --> 00:18:29.700 what I like. That's what I always found about 00:18:29.700 --> 00:18:32.279 languages like Thistle Basic and Java. They're 00:18:32.279 --> 00:18:35.500 really specific for business programming, like 00:18:35.500 --> 00:18:38.539 business applications usually means you've got 00:18:38.539 --> 00:18:40.839 some text stream, you manipulate it, you read 00:18:40.839 --> 00:18:44.460 some from a database, you return it. That's about 00:18:44.460 --> 00:18:50.900 it. And so in that sense, I like to have the 00:18:50.900 --> 00:18:55.009 general... languages. That's why my second favorite 00:18:55.009 --> 00:18:59.109 language is Ada. It was actually developed in 00:18:59.109 --> 00:19:03.049 the 1980s at the request of the US military because 00:19:03.049 --> 00:19:05.710 they had something like 30 different languages 00:19:05.710 --> 00:19:10.150 being used at the time, early 80s. So they actually 00:19:10.150 --> 00:19:14.069 had this competition to get one program of languages 00:19:14.069 --> 00:19:18.269 for the entire US military. Wow, so kind of like 00:19:18.269 --> 00:19:20.210 they're doing with the whole space program where 00:19:20.410 --> 00:19:23.369 they're competing to win the NASA contract. Something 00:19:23.369 --> 00:19:26.509 like that, yes. So the winner of that contest 00:19:26.509 --> 00:19:31.109 was ADA, and it's been used ever since. It runs 00:19:31.109 --> 00:19:34.450 pretty much all of the avionics, also in commercial 00:19:34.450 --> 00:19:38.250 airplanes, but especially military airplanes. 00:19:38.470 --> 00:19:42.809 It runs on the ICBMs, all the control software, 00:19:43.009 --> 00:19:45.769 because the main thing about ADA is that it's 00:19:45.769 --> 00:19:47.970 supposed to be, well, the only way to make an 00:19:47.970 --> 00:19:51.859 ADA application press. is to just blow the heart 00:19:51.859 --> 00:19:55.420 around. Wow, I guess I'll have to look into that. 00:19:55.660 --> 00:19:57.059 Yeah, I know what I'm gonna be doing tonight. 00:19:57.220 --> 00:20:00.799 Thanks, Maya. Like, I didn't need to sleep. Yeah, 00:20:01.160 --> 00:20:03.759 you don't anyway, so... I know. Such a lie. You 00:20:03.759 --> 00:20:06.519 might have something to do. I can stay up and 00:20:06.519 --> 00:20:09.740 read. When I wanted to start programming, my 00:20:09.740 --> 00:20:11.559 goal was to become a game programmer. Obviously 00:20:11.559 --> 00:20:13.220 I was young and I thought it was like, oh my 00:20:13.220 --> 00:20:15.700 god, so easy and so, you know, this this utopic 00:20:15.700 --> 00:20:19.490 dream, but... So I started with C++ as my first 00:20:19.490 --> 00:20:22.869 language, and it was hard. Pointers and bitwise 00:20:22.869 --> 00:20:25.970 operations and all that, it was tough. But I'm 00:20:25.970 --> 00:20:28.130 glad I did it that way and didn't start with 00:20:28.130 --> 00:20:30.730 something like JavaScript or something simpler, 00:20:30.869 --> 00:20:33.029 because it gave me a solid foundation that I 00:20:33.029 --> 00:20:36.450 can now apply to other languages, generics, templates, 00:20:37.890 --> 00:20:40.910 pointers, which are very important. And every 00:20:40.910 --> 00:20:43.230 other topic that I seem to be wanting to learn, 00:20:43.750 --> 00:20:47.279 for example, OpenGL, most of the books, you know, 00:20:47.339 --> 00:20:49.779 I'm trying to look at OpenGL for iOS, and there's 00:20:49.779 --> 00:20:52.640 some videos, there's a book or two, but most 00:20:52.640 --> 00:20:54.779 of them are basically cool. You can run it on 00:20:54.779 --> 00:20:57.059 iOS or on Windows Phone or on Android in this 00:20:57.059 --> 00:20:59.720 way, but we'll write the entire book in C++. 00:21:00.480 --> 00:21:03.750 So every pretty much... hardcore thing I want 00:21:03.750 --> 00:21:06.569 to do, which is learn assembly, learn how to 00:21:06.569 --> 00:21:08.650 write a compiler, write my own language, write 00:21:08.650 --> 00:21:11.650 OpenGL, maybe by the time I'll die, seems to 00:21:11.650 --> 00:21:14.150 use C++. So I agree with you. I haven't used 00:21:14.150 --> 00:21:16.650 it in years, but it's my favorite language. It's 00:21:16.650 --> 00:21:19.869 so powerful. You can do anything. I know it's 00:21:19.869 --> 00:21:22.049 harder than other languages, but you can do anything. 00:21:23.210 --> 00:21:25.349 That's pretty much like, like I said, I mean, 00:21:25.769 --> 00:21:27.890 assembly is the most powerful language, but also 00:21:27.890 --> 00:21:31.410 the hardest to use. So I try to find... that 00:21:31.410 --> 00:21:35.269 level where it's actually comfortable to work 00:21:35.269 --> 00:21:37.170 at, where you can still do everything you need 00:21:37.170 --> 00:21:42.150 to do. And well, I've used C as well, but C is 00:21:42.150 --> 00:21:45.130 quite low level. I mean, just strings, for example, 00:21:45.269 --> 00:21:49.170 C -style strings, memory allocation in C is a 00:21:49.170 --> 00:21:51.569 bit of a pain. So the nicest thing about C++ 00:21:51.569 --> 00:21:55.450 really is that it takes away those fuzzy details, 00:21:55.589 --> 00:21:59.710 like, well, I have this array of characters and 00:21:59.710 --> 00:22:02.750 I need to get something out of it. Well, that's 00:22:02.750 --> 00:22:06.250 easy with C++, with the strings library, and 00:22:06.250 --> 00:22:13.990 C is like, right. So that's pretty much like, 00:22:14.490 --> 00:22:16.549 if you need to write an operating system, write 00:22:16.549 --> 00:22:20.650 a really low -level fuzzy real -time driver, 00:22:21.210 --> 00:22:24.170 probably C. If you need to write anything higher 00:22:24.170 --> 00:22:28.769 level than that, C++. So you're developing games 00:22:28.769 --> 00:22:31.369 too, right? And I think I'm not even going to 00:22:31.369 --> 00:22:33.430 try and pronounce your company name, because 00:22:33.430 --> 00:22:35.829 I'll just butcher it. Can you pronounce your 00:22:35.829 -->

00:22:38.410 company name for us and then tell us what kind 00:22:38.410 --> 00:22:40.390 of games you guys are writing and maybe some 00:22:40.390 --> 00:22:43.750 other stuff that you're doing? The company name 00:22:43.750 --> 00:22:47.950 is Nyanko. That means a small kitten, a kitten 00:22:47.950 --> 00:22:52.049 in Japanese. Not to be confused with Hello Kitty, 00:22:52.190 --> 00:22:54.690 who is no longer a cat. Yeah, I know about that. 00:22:54.990 --> 00:23:00.539 It's really choking this whole world. So your 00:23:00.539 --> 00:23:04.619 company does game development? As well, we just 00:23:04.619 --> 00:23:08.099 kind of general software development. It's also, 00:23:08.180 --> 00:23:10.119 well, we haven't really published much. Mostly 00:23:10.119 --> 00:23:14.380 I've done some freelance stuff for people, written 00:23:14.380 --> 00:23:17.880 some Android applications and things like that. 00:23:19.480 --> 00:23:21.759 Mostly my colleague, he has done most of the 00:23:21.759 --> 00:23:26.089 work on this game engine we have. So it's an 00:23:26.089 --> 00:23:28.170 entire game engine. It's pretty much on the level 00:23:28.170 --> 00:23:33.410 of, well, I don't want to brag, but it's probably 00:23:33.410 --> 00:23:38.869 a bit on the level of the, what's it called again, 00:23:39.069 --> 00:23:44.410 the Unreal Engine release. It's just really advanced 00:23:44.410 --> 00:23:47.250 with its feature set. It's not as polished. We 00:23:47.250 --> 00:23:50.450 don't have such nice tools as the Unreal Engine 00:23:50.450 --> 00:23:53.509 has because, well, And it's been around since, 00:23:53.509 --> 00:23:56.549 well, Unreal 1 was published in the late 90s, 00:23:56.549 --> 00:24:01.170 I believe. So it's been around for a while. We're 00:24:01.170 --> 00:24:05.990 not that far yet. But just, we have a good game 00:24:05.990 --> 00:24:08.930 engine. We're kind of working towards actually 00:24:08.930 --> 00:24:12.930 creating the first game using it. Does the engine 00:24:12.930 --> 00:24:15.970 have a name? Is it commercially available? It's 00:24:15.970 --> 00:24:18.230 not commercially available yet. Right now it's 00:24:18.230 --> 00:24:23.700 an in -house engine. OK. but we do have plans 00:24:23.700 --> 00:24:27.099 to develop the proper development tools so that 00:24:27.099 --> 00:24:31.279 it can be used easily by other people as well. 00:24:31.660 --> 00:24:34.200 The game engine itself is completely generic. 00:24:34.440 --> 00:24:36.259 It can be used for any type of game. It's not 00:24:36.259 --> 00:24:41.720 limited to anything in specific. The game we're 00:24:41.720 --> 00:24:45.259 actually kind of developing at this point is 00:24:45.259 --> 00:24:53.329 I guess more RTS style game. Sweet! But it would 00:24:53.329 --> 00:24:56.970 work just as well for an FPS or, well, I'm actually 00:24:56.970 --> 00:24:59.750 also considering a number of more visual novel 00:24:59.750 --> 00:25:04.930 style, because why not? I

like writing, so. Yeah, 00:25:04.930 --> 00:25:08.490 I saw you were doing, you're rewriting The Legend 00:25:08.490 --> 00:25:12.609 of Zelda I saw on your page there. Yeah, pet 00:25:12.609 --> 00:25:15.529 peeve of mine since 98 when I first played that 00:25:15.529 --> 00:25:19.190 game. You're a Zelda fan? Yeah, just a little 00:25:19.190 --> 00:25:22.970 bit. It's a retelling. Yeah, it's pretty much 00:25:22.970 --> 00:25:26.650 like, I mean, I can dream Ocarina of Time, I 00:25:26.650 --> 00:25:29.170 can dream Majora's Mask, I can dream Twilight 00:25:29.170 --> 00:25:31.829 Princess. It's just, I know every single detail. 00:25:31.990 --> 00:25:33.670 If you ask me, especially for Ocarina of Time, 00:25:33.849 --> 00:25:35.730 if you ask me there in the dungeon, at that point 00:25:35.730 --> 00:25:37.369 what you have to do to solve the puzzle, I'm 00:25:37.369 --> 00:25:40.549 like, I can explain it. Was that your first Zelda 00:25:40.549 --> 00:25:44.680 game, Ocarina of Time? Well, Zelda 3 on the Super 00:25:44.680 --> 00:25:47.400 Nintendo was actually the first one, I guess, 00:25:47.500 --> 00:25:50.220 but I didn't really play it. This is what my 00:25:50.220 --> 00:25:52.839 younger brother played a bit and me watching. 00:25:53.299 --> 00:25:57.099 Well, it's okay, but just the whole magic of 00:25:57.099 --> 00:25:59.480 Ocarina of Time. I remember this. This is actually 00:25:59.480 --> 00:26:03.779 the game I bought an N64 for with my own money. 00:26:03.960 --> 00:26:07.859 My first console, which I actually owned. Back 00:26:07.859 --> 00:26:12.539 to why I was like, I need to... re -write the 00:26:12.539 --> 00:26:14.680 story of Ocarina of Time, because you can, well, 00:26:14.740 --> 00:26:17.819 be like, if you re -write the story of a game, 00:26:18.099 --> 00:26:21.519 you must not like that game. On the contrary, 00:26:21.680 --> 00:26:25.920 I love Ocarina of Time, but I like to improve 00:26:25.920 --> 00:26:28.740 on it, because I think that the concept itself 00:26:28.740 --> 00:26:33.839 is good, but it needs some additional work. Can 00:26:33.839 --> 00:26:37.599 you write exquisitely? So, are you going to write 00:26:37.599 --> 00:26:40.539 the entire, re -write the entire story? That's 00:26:40.539 --> 00:26:45.279 my intention. I think I quit Chapter 6 for now, 00:26:45.400 --> 00:26:48.279 somewhere around there. I've been meaning to 00:26:48.279 --> 00:26:52.400 get back to it, but it takes quite a bit of time 00:26:52.400 --> 00:26:55.339 to write that and other obligations. You know, 00:26:55.400 --> 00:26:58.740 real life is... Your own engine and the end engine 00:26:58.740 --> 00:27:02.920 book and the CPU architecture and work. And moving 00:27:02.920 --> 00:27:08.690 to Germany stuff. This is... There's a lot of 00:27:08.690 --> 00:27:10.450 stuff happening at the same time and you're like, 00:27:10.650 --> 00:27:13.910 okay, I need to fit everything in well One human 00:27:13.910 --> 00:27:18.609

life is such a brief time It really is. There's 00:27:18.609 --> 00:27:21.309 definitely not enough time to do everything that 00:27:21.309 --> 00:27:26.410 we want to do. So So, I mean, priorities, because 00:27:26.410 --> 00:27:29.390 if you start working on one thing first, and 00:27:29.390 --> 00:27:31.670 that little thing is called immortality, then 00:27:31.670 --> 00:27:33.529 you will have enough time to finish everything 00:27:33.529 --> 00:27:36.869 else. I want to be old, so I don't have to sleep 00:27:36.869 --> 00:27:39.210 as much, and I can just, like, stay up all night 00:27:39.210 --> 00:27:41.150 coding. No, it doesn't work like that. It doesn't 00:27:41.150 --> 00:27:43.569 work that way. Really? It's the other way around? 00:27:44.109 --> 00:27:50.880 Yep. Aww. You can stay up until 6 and get up 00:27:50.880 --> 00:27:53.839 at 8 and feel refreshed the entire day. I did 00:27:53.839 --> 00:27:56.559 do that when I was in college back in Argentina. 00:27:56.680 --> 00:27:58.640 I would stay up till like 3 or 4 a .m. doing 00:27:58.640 --> 00:28:01.539 3D or Maya and then I'd wake up and go to school. 00:28:01.539 --> 00:28:06.579 Back in 2010? 2002. Oh, okay. No, no, no. 2002, 00:28:06.819 --> 00:28:14.160 yeah. No, not 2002. 2006. He is a baby, I'm telling 00:28:14.160 --> 00:28:17.519 you. He looks like he's 18, but he's probably 00:28:17.519 --> 00:28:22.220 12. Yeah, it seems like it. Well, maybe 13, yeah. 00:28:23.380 --> 00:28:26.759 So, okay, I gotta know, because I'm also a writer 00:28:26.759 --> 00:28:30.359 and a developer and an artist, and I have my 00:28:30.359 --> 00:28:32.720 favorite. I'm curious what your favorite is. 00:28:33.039 --> 00:28:37.200 Do you prefer the writing, or do you prefer the 00:28:37.200 --> 00:28:40.259 development part of it? Or are you on task equally 00:28:40.259 --> 00:28:44.700 with both of them? Well... The thing is actually 00:28:44.700 --> 00:28:47.900 that writing and programming are quite similar. 00:28:48.579 --> 00:28:51.940 In both cases, I mean, as a writer, you are also 00:28:51.940 --> 00:28:54.839 constructing a kind of program, only it runs 00:28:54.839 --> 00:28:58.740 on a web bear inside your hands. So, I mean, 00:28:58.799 --> 00:29:01.559 when you're writing a sentence, it's just like 00:29:01.559 --> 00:29:05.920 a piece of code. The reader reads it, executes 00:29:05.920 --> 00:29:11.240 it, visualizes the scene that is part of that. 00:29:11.450 --> 00:29:15.210 sentence. So that's how I approach this thing. 00:29:16.289 --> 00:29:19.190 So it's kind of like when you're writing, you 00:29:19.190 --> 00:29:23.049 have this program inside your head. It's all 00:29:23.049 --> 00:29:25.230 nice and shiny, and you just have to decompile 00:29:25.230 --> 00:29:30.670 it, write it down, so another person can compile 00:29:30.670 --> 00:29:35.470 it and run it again. So I don't really see the 00:29:35.470 --> 00:29:38.710 difference between writing and programming. The 00:29:38.710 --> 00:29:42.289 cool thing about writing is that writing is more 00:29:42.289 --> 00:29:45.710 aimed at people, and you can do feelings and 00:29:45.710 --> 00:29:48.829 emotions with it, which you can't really do with 00:29:48.829 --> 00:29:51.230 a program. I guess, well, if you make a game, 00:29:51.410 --> 00:29:55.309 I guess, I mean, it can make people scared, crying, 00:29:55.769 --> 00:29:59.569 laugh. That's the more writing, really. That's 00:29:59.569 --> 00:30:03.390 the script for a game. It's like, yeah. So in 00:30:03.390 --> 00:30:06.299 the end, I think both. It's just that they both 00:30:06.299 --> 00:30:08.559 have different applications. What do you want 00:30:08.559 --> 00:30:10.819 to accomplish? I mean, if you're just writing 00:30:10.819 --> 00:30:14.240 some business transaction processing codes, you're 00:30:14.240 --> 00:30:18.980 like, well, man, it's not fun. You have just 00:30:18.980 --> 00:30:22.240 given me an entirely different look at things. 00:30:22.240 --> 00:30:27.700 At how coding is. Yeah. I've always had my favorite. 00:30:27.779 --> 00:30:29.799 This is my favorite. This is my least favorite. 00:30:30.000 --> 00:30:32.730 But the way that you just explained it now, I 00:30:32.730 --> 00:30:34.789 have to look back and go, wow, how could I have 00:30:34.789 --> 00:30:36.869 picked a favorite? Because like you said, they 00:30:36.869 --> 00:30:40.089 are about the same. I just never thought of it 00:30:40.089 --> 00:30:42.490 like that. So thank you. That's pretty epic. 00:30:43.450 --> 00:30:47.210 That's pretty cool. I consider code like poetry, 00:30:47.210 --> 00:30:50.029 I guess. It's got to be tidy. It's got to be 00:30:50.029 --> 00:30:52.170 pretty. It's got to be organized. It's got to 00:30:52.170 --> 00:30:55.250 be something that, like you said, Maya, if someone 00:30:55.250 --> 00:30:58.410 else looks at it, they can sort of comprehend 00:30:58.410 --> 00:31:01.150 what you were trying to purvey through your code. 00:31:01.640 --> 00:31:04.579 And they have constructs just like any language 00:31:04.579 --> 00:31:07.519 has its own grammatical rules and things that 00:31:07.519 --> 00:31:11.279 you must follow when writing, so. Yeah, so the 00:31:11.279 --> 00:31:14.740 other thing, I mean, I've got a lot of writers 00:31:14.740 --> 00:31:17.920 I really respect and I've read so many books. 00:31:18.099 --> 00:31:22.900 I think that if I just pure fiction, I've read 00:31:22.900 --> 00:31:26.819 a thousand books maybe. I have nothing there. 00:31:27.380 --> 00:31:31.309 I used to be, I think I was a teenager. child, 00:31:31.450 --> 00:31:33.869 don't remember, probably both. I used to read 00:31:33.869 --> 00:31:37.970 something like 10, 12 books a week or something. 00:31:38.789 --> 00:31:41.710 It was the whole time, just before I had my own 00:31:41.710 --> 00:31:45.329 computer obviously, but I would just lie on my 00:31:45.329 --> 00:31:49.029 bed every spare moment of my

day pretty much 00:31:49.029 --> 00:31:53.710 and just read. One book from Stephen King, I 00:31:53.710 --> 00:31:55.490 don't remember the title, I should know the title 00:31:55.490 --> 00:31:57.569 but I forgot it because it was a long time ago. 00:31:59.169 --> 00:32:03.829 1 ,010 pages took me four days to finish that 00:32:03.829 --> 00:32:09.710 one. Wow. So you're a bookworm. Yes. Do you prefer 00:32:09.710 --> 00:32:13.849 e -books or a printed book? I actually bought 00:32:13.849 --> 00:32:17.710 my first e -book reader a couple of years ago, 00:32:18.369 --> 00:32:21.210 and I must say I kind of like the experience. 00:32:21.710 --> 00:32:26.630 I do buy that three versions of books, but only 00:32:26.630 --> 00:32:28.829 of the books I really, really, really, really 00:32:28.829 --> 00:32:32.269 like. And the other ones I'm like, ah, digital 00:32:32.269 --> 00:32:34.529 works. So, I mean, it's easy to read in that. 00:32:34.690 --> 00:32:36.990 And it hurts less when the Kindle falls in your 00:32:36.990 --> 00:32:40.049 face when you're reading instead of one of those 00:32:40.049 --> 00:32:45.109 huge C++ books. BraveWonderLake .com is a site 00:32:45.109 --> 00:32:47.349 focused on high quality programming tutorials 00:32:47.349 --> 00:32:50.130 made by authors and editors from across the world, 00:32:50.410 --> 00:32:52.970 including Tammy and me. If you're looking to 00:32:52.970 --> 00:32:55.460 learn iOS development, This is the place to go. 00:32:55.839 --> 00:32:58.619 We have tutorials, books, and video tutorials 00:32:58.619 --> 00:33:01.059 for all levels of developers, whether you're 00:33:01.059 --> 00:33:04.359 a complete beginner or quite experienced. Check 00:33:04.359 --> 00:33:06.579 out our new Swift by Tutorials bundle on the 00:33:06.579 --> 00:33:10.099 site. Three brand new books on Swift, iOS 8, 00:33:10.400 --> 00:33:12.819 and core data that will help you level up your 00:33:12.819 --> 00:33:16.799 iOS skills. Also, if you want to meet us in person, 00:33:17.259 --> 00:33:19.720 sign up for our official conference next February. 00:33:20.220 --> 00:33:23.740 RW DevCon, the tutorial conference. To learn 00:33:23.740 --> 00:33:27.519 more, check out raywenderlake .com Nothing scary, 00:33:27.619 --> 00:33:29.440 nothing personal, but just something cool so 00:33:29.440 --> 00:33:32.099 people can get to know Maya on a different level 00:33:32.099 --> 00:33:33.579 and maybe some things they didn't know about 00:33:33.579 --> 00:33:38.059 you. So the first question is what is your favorite 00:33:38.059 --> 00:33:49.720 color? Favorite color? Pink. Yes. What is your 00:33:49.720 --> 00:33:58.259 least favorite color? Probably green. What is 00:33:58.259 --> 00:34:05.819 your favorite word? Kitten. What is your least 00:34:05.819 --> 00:34:13.260 favorite word? I guess... suffering. What do 00:34:13.260 --> 00:34:15.659 you hate the most? What is your biggest pet peeve? 00:34:21.329 --> 00:34:25.829 Idiocracy. Who is your favorite fictional character? 00:34:30.230 --> 00:34:33.190 That would take a while to sort through, sorry. 00:34:34.570 --> 00:34:41.449 It's okay. Who is your role model? Well I guess 00:34:41.449 --> 00:34:44.750 not just one role model but more like like I 00:34:44.750 --> 00:34:48.659 say standing on the shoulders of giants. my role 00:34:48.659 --> 00:34:52.079 model is every single famous scientist and other 00:34:52.079 --> 00:34:57.800 person instrumental in world history so everyone 00:34:57.800 --> 00:35:03.480 from einstein to eisenhower just yeah what do 00:35:03.480 --> 00:35:11.480 you fear the most death what is your biggest 00:35:11.480 --> 00:35:18.199 dream To become so influential and rich that 00:35:18.199 --> 00:35:21.639 I can actually, well, I'll scratch that. To become 00:35:21.639 --> 00:35:27.320 immortal. Then I have enough time for everything. 00:35:27.780 --> 00:35:31.300 Do share when you achieve that. I will, no worries. 00:35:31.760 --> 00:35:38.039 What is your greatest achievement? Well, to be 00:35:38.039 --> 00:35:41.059 quite honest, staying alive and sane up to this 00:35:41.059 --> 00:35:52.960 point. What do you regret the most? Well, the 00:35:52.960 --> 00:35:54.639 kind of thing that you want to go back in time 00:35:54.639 --> 00:36:04.500 and kick your younger self off. Not growing a 00:36:04.500 --> 00:36:07.619 backbone, having more self -confidence as a teenager, 00:36:07.619 --> 00:36:11.800 I guess. If you could choose another profession. 00:36:12.000 --> 00:36:17.219 What would it be? I would be a scientist. And 00:36:17.219 --> 00:36:19.659 the last question is, what would you do in a 00:36:19.659 --> 00:36:25.420 zombie apocalypse? The classic one. Well, I would 00:36:25.420 --> 00:36:27.739 first question the laws of physics at that point, 00:36:27.980 --> 00:36:32.340 because what the hell? Then I would question 00:36:32.340 --> 00:36:35.340 the laws of thermodynamics, because what the 00:36:35.340 --> 00:36:37.840 hell? Why aren't the things just dying from, 00:36:37.840 --> 00:36:40.960 well... Neglection, I mean, they're rotting, 00:36:41.119 --> 00:36:45.159 so what the hell? If there really is now, lots 00:36:45.159 --> 00:36:48.960 of physics have gone upside, inside, out, whatever, 00:36:49.360 --> 00:36:51.519 then I would be like, cool, let's figure out 00:36:51.519 --> 00:36:54.719 what I can do with my newfound superpowers, and 00:36:54.719 --> 00:36:58.420 destroy every single zombie in one fiery blast, 00:36:58.800 --> 00:37:00.900 and become the ruler of the new earth, and then 00:37:00.900 --> 00:37:05.099 of the universe. And become immortal, Mr. Manhattan. 00:37:06.019 --> 00:37:11.340 Standard superpower, immortality. Thank you very 00:37:11.340 --> 00:37:13.440 much for coming on the show if there is anything 00:37:13.440 --> 00:37:16.360 you would like to say to listeners Do you go 00:37:16.360 --> 00:37:19.280 ahead how they can contact you how you know?

00:37:19.440 --> 00:37:21.059 They can reach you should they be interested 00:37:21.059 --> 00:37:24.199 in interacting with you or learning from you? 00:37:24.820 --> 00:37:30.179 Yeah, well Well, obviously my website is a good 00:37:30.179 --> 00:37:33.400 way to learn more about me to contact me and 00:37:33.400 --> 00:37:36.260 shockingly enough the address for my website 00:37:36.260 --> 00:37:40.349 is myapost .com I know, that's really shocking. 00:37:42.050 --> 00:37:44.429 We want to thank Ray Wunderlich and Raywunderlich 00:37:44.429 --> 00:37:47.469 .com for sponsoring this episode. Do check out 00:37:47.469 --> 00:37:49.769 their website. They're having sales now because 00:37:49.769 --> 00:37:52.329 they released new books and promotions for Swift 00:37:52.329 --> 00:37:55.010 and for iOS 8. There's new content, videos, and 00:37:55.010 --> 00:37:57.969 books available. Do check that out. And as usual, 00:37:58.150 --> 00:38:00.530 please check us out on iTunes or Stitcher Radio. 00:38:01.190 --> 00:38:02.969 Please leave a review and rate us if you like 00:38:02.969 --> 00:38:06.260 it. And also contact us on our website at roundabout 00:38:06.260 --> 00:38:10.860 .fm, on Facebook, on facebook .com slash roundaboutfm, 00:38:11.059 --> 00:38:16.599 or at roundaboutfm on Twitter. That a wrap? That's 00:38:16.599 --> 00:38:33.230 a wrap. That's a wrap. Thank you very much for 00:38:33.230 --> 00:39:09.590 your cooperation. That was a cool interview. 00:39:10.550 --> 00:39:12.969 That was a really cool interview. I've wanted 00:39:12.969 --> 00:39:18.829 to talk to Maya forever. And she's, gosh, I guess 00:39:18.829 --> 00:39:21.949 genius is the only way to describe her. Yeah. 00:39:22.090 --> 00:39:24.929 Well, you know, anytime you have a person whose 00:39:24.929 --> 00:39:28.710 primary goal is to learn, then you have someone 00:39:28.710 --> 00:39:32.329 who's interesting. Yes. And she's very creative. 00:39:32.550 --> 00:39:37.289 Again, creativity does not mean programming it 00:39:37.289 --> 00:39:42.389 means I mean it does not mean art it means anything 00:39:42.389 --> 00:39:44.949 and and the way she described how programming 00:39:44.949 --> 00:39:47.949 is to her kind of like writing that was really 00:39:47.949 --> 00:39:51.690 cool so I was super psyched I hope we stay in 00:39:51.690 --> 00:39:53.170 touch I'm always following and talking to her 00:39:53.170 --> 00:39:56.489 on Twitter but it's been a delight and I definitely 00:39:56.489 --> 00:39:58.730 love to have her back sometime next year or in 00:39:58.730 --> 00:40:02.579 the future Yeah, definitely on both those things. 00:40:02.579 --> 00:40:04.980 I would love to have her back, too. And the way 00:40:04.980 --> 00:40:07.780 that she described writing and programming as 00:40:07.780 --> 00:40:11.139 being almost like synonymous and one of the same, 00:40:11.739 --> 00:40:14.019 I'd never looked at it like that before. I was 00:40:14.019 --> 00:40:17.179 always like, oh, well, yeah, this is my logical 00:40:17.179 --> 00:40:19.519 side. And when I'm programming, I'm thinking 00:40:19.519 --> 00:40:21.579 of ones and zeros, even though I suck at math. 00:40:21.739 --> 00:40:24.500 Thank God there's only one and a zero. And then 00:40:24.500 --> 00:40:27.960 there's this whole creative side where... I'm 00:40:27.960 --> 00:40:31.300 writing or I'm drawing something. You know, the 00:40:31.300 --> 00:40:33.219 next time someone asks me, well, which do you 00:40:33.219 --> 00:40:35.380 like better? I now have a better answer than, 00:40:35.500 --> 00:40:37.519 oh, I like doing this one better. I'll just steal 00:40:37.519 --> 00:40:40.920 Maya's. What do you like doing better? Being 00:40:40.920 --> 00:40:43.659 Batman? No, see, now I don't want to be Batman 00:40:43.659 --> 00:40:46.539 anymore. I think I want to be like this superhero 00:40:46.539 --> 00:40:49.420 cat, this immortal cat who spits up hairballs. 00:40:50.199 --> 00:40:53.619 That's the superhero I want to be. I want to 00:40:53.619 --> 00:40:57.380 be able to fly. Commander Kitty. Commander Kitty. 00:40:57.760 --> 00:41:01.500 Commander Kitty. That sounds so cool. You should 00:41:01.500 --> 00:41:07.079 really illustrate that sometime. iPhone 6 or 00:41:07.079 --> 00:41:12.059 iPhone 6 Plus? I got the 6, 64 gigs, gold, gorgeous. 00:41:12.900 --> 00:41:15.639 And then I'm like, well, what about the 6 Plus? 00:41:16.280 --> 00:41:20.760 So today I got the 6 Plus and I'm probably going 00:41:20.760 --> 00:41:26.079 to keep the 6 Plus. I don't know why. But you're 00:41:26.079 --> 00:41:28.420 on the fence because your story is different 00:41:28.420 --> 00:41:30.340 and this is where the conversation starts. You 00:41:30.340 --> 00:41:33.519 want the 6 Plus or you're torn between both of 00:41:33.519 --> 00:41:35.019 them because you're going to keep your iPhone 00:41:35.019 --> 00:41:37.500 5S as your personal device. You love it, the 00:41:37.500 --> 00:41:40.380 size, the specs, everything. But you're a developer 00:41:40.380 --> 00:41:44.159 and you need a test device. To you, what are 00:41:44.159 --> 00:41:47.460 the pros of the iPhone 6 and what are the cons 00:41:47.460 --> 00:41:50.320 of the iPhone 6? The iPhone 6, if I were to get 00:41:50.320 --> 00:41:52.940 it, there is the very strong potential that I'll 00:41:52.940 --> 00:41:58.670 ditch my 5 in favor of using the new 6. While 00:41:58.670 --> 00:42:04.110 I may not like the size in theory, once I get 00:42:04.110 --> 00:42:06.889 it, I might find that completely wrong. I might 00:42:06.889 --> 00:42:08.630 be like, oh, you know what? I do like that. Because 00:42:08.630 --> 00:42:11.610 when I did use a Droid, I used the Droid Razer 00:42:11.610 --> 00:42:16.349 Max HD, and that's not a small phone. That's 00:42:16.349 --> 00:42:19.530 probably about the size of a 6. You've been down 00:42:19.530 --> 00:42:22.530 the path of sort of bigger phones than just the

00:42:22.530 --> 00:42:26.389 iPhones provided. Yeah. so there's that the price 00:42:26.389 --> 00:42:29.050 obviously the six is like a hundred dollars cheaper 00:42:29.050 --> 00:42:33.210 because again i don't i don't need even the iphone 00:42:33.210 --> 00:42:36.789 5s that i have now is like a 16 gig phone so 00:42:36.789 --> 00:42:39.710 i'm not going to be getting a big one so there's 00:42:39.710 --> 00:42:43.469 the price it's a hundred dollars cheaper but 00:42:43.469 --> 00:42:46.530 that's really it you know those three things 00:42:46.530 --> 00:42:49.530 more people are using it so when i'm developing 00:42:49.530 --> 00:42:52.230 i'll be developing to what more people are using 00:42:53.349 --> 00:42:56.750 What about things like battery life? Not important. 00:42:57.150 --> 00:42:59.510 I never leave the house. So you're not cared 00:42:59.510 --> 00:43:02.090 about battery life or Touch ID or the camera 00:43:02.090 --> 00:43:04.469 or the resolution. You're mainly just talking 00:43:04.469 --> 00:43:07.969 from a price perspective and size at this point. 00:43:08.489 --> 00:43:11.989 Right. But again, I have to think as a developer 00:43:11.989 --> 00:43:14.530 because I already have a good working phone. 00:43:14.909 --> 00:43:17.769 If I were not a developer, I would not be upgrading 00:43:17.769 --> 00:43:20.050 because there's no reason for me to upgrade. 00:43:20.329 --> 00:43:23.429 Right. The phone I have works fine. I don't like 00:43:23.429 --> 00:43:27.349 to spend money, so as a consumer, I wouldn't 00:43:27.349 --> 00:43:29.150 buy a new phone. I don't need the best thing. 00:43:29.170 --> 00:43:33.289 Oh, when it comes to a Cintiq. No problem spending 00:43:33.289 --> 00:43:37.010 there on the best monitor, but $200 iPhone and 00:43:37.010 --> 00:43:39.289 I got to think about it for a month. But see, 00:43:39.369 --> 00:43:42.710 I'm not a very social person, so I'm not on my 00:43:42.710 --> 00:43:46.210 phone sending text messages or actually... I 00:43:46.210 --> 00:43:47.929 do send a lot of messages, but they're mostly 00:43:47.929 --> 00:43:50.969 for work. Yeah, all jokes aside, if I were to 00:43:50.969 --> 00:43:53.309 get a Cintiq, it would be a waste because I draw 00:43:53.309 --> 00:43:56.070 once a year. You are an artist and you use it 00:43:56.070 --> 00:43:59.449 daily. Right. For me, the phone, I use it daily. 00:43:59.530 --> 00:44:02.329 I have games. I watch books. I often put... You 00:44:02.329 --> 00:44:05.630 watch books? I watch books and I read videos. 00:44:05.909 --> 00:44:08.909 Okay, good. Because most other people, they watch 00:44:08.909 --> 00:44:11.929 videos and read books, but you're Felipe and 00:44:11.929 --> 00:44:17.230 you do it the Felipe way. Having QA devices is 00:44:17.230 --> 00:44:20.409 very, very important. It's not the same, and 00:44:20.409 --> 00:44:22.389 some bugs are not reproducible in the simulator. 00:44:22.789 --> 00:44:24.889 And sometimes, at least what I've noticed this 00:44:24.889 --> 00:44:28.869 week, today specifically, is that I have a bug 00:44:28.869 --> 00:44:32.570 on the simulator, but not on the device. And 00:44:32.570 --> 00:44:35.010 I don't know why it's happening on the simulator, 00:44:35.170 --> 00:44:37.710 and it's not happening on any device that I run, 00:44:37.789 --> 00:44:43.070 regardless of the version. What was that? It's 00:44:43.070 --> 00:44:47.929 my ringtone. Oh, look, I'm going to talk with 00:44:47.929 --> 00:44:53.650 my face. Oh, gosh. That was... I'm going to keep 00:44:53.650 --> 00:44:56.949 that in because that's funny. Is that really 00:44:56.949 --> 00:44:59.190 your ringtone? Yeah, that's my ringtone. It's 00:44:59.190 --> 00:45:02.050 just, I don't know, for some reason we were playing 00:45:02.050 --> 00:45:03.710 video games with a friend one day and we just 00:45:03.710 --> 00:45:07.690 started humming like, what's that TV show? And 00:45:07.690 --> 00:45:10.530 it just stuck and it's like, it's my ringtone. 00:45:11.289 --> 00:45:16.449 Oh, that's embarrassing. Hey speaking of TV shows 00:45:16.449 --> 00:45:19.369 Speaking of TV shows now that we're migrating 00:45:19.369 --> 00:45:22.030 away. I hear something about z nation from my 00:45:22.030 --> 00:45:24.170 girlfriend Okay, so we're looking for something 00:45:24.170 --> 00:45:27.349 to do night before last or whatever and I'm like, 00:45:27.369 --> 00:45:30.650 yeah Let's go see how much the the series cost 00:45:30.650 --> 00:45:32.369 on iTunes and it wasn't that much and it was 00:45:32.369 --> 00:45:35.679 like $20 that's very cheap for a series yeah 00:45:35.679 --> 00:45:37.760 i was surprised because walking dead is 30 which 00:45:37.760 --> 00:45:39.440 i haven't bought yet because i'm wondering if 00:45:39.440 --> 00:45:41.340 they're going to change the price between now 00:45:41.340 --> 00:45:44.500 and october 12th but they probably won't so anyway 00:45:44.500 --> 00:45:47.219 so i i purchased the series and we watched both 00:45:47.219 --> 00:45:49.900 episodes at episode two and three back to back 00:45:49.900 --> 00:45:54.000 and um i'm hooked now i really like it without 00:45:54.000 --> 00:45:57.780 spoiling it um how is it different from the walking 00:45:57.780 --> 00:46:00.559 dead I've seen a couple episodes and it's like 00:46:00.559 --> 00:46:02.860 the walking dead is people sort of trying to 00:46:02.860 --> 00:46:05.820 survive moving around cities or the city But 00:46:05.820 --> 00:46:08.300 there's still some sort of civilization left 00:46:08.300 --> 00:46:12.400 and the walking dead Like people there's still 00:46:12.400 --> 00:46:15.599 people it's not or is it completely chaotic. 00:46:15.599 --> 00:46:20.940 No, it's it's pretty chaotic You know, it's it's 00:46:20.940 --> 00:46:24.679 more about people surviving other people than 00:46:24.679 --> 00:46:27.159 it is about surviving zombies and the apocalypse 00:46:27.159 --> 00:46:31.349 because People are just cruel in general and 00:46:31.349 --> 00:46:34.329 even after the apocalypse after the zombies have 00:46:34.329 --> 00:46:37.829 arrived people are just as cruel. Yeah. Yeah, 00:46:37.829 --> 00:46:42.429 I mean With Z nation people are still cruel. 00:46:42.610 --> 00:46:45.389 So there's that commonality the world hasn't 00:46:45.389 --> 00:46:49.050 changed the world hasn't changed but it's It's 00:46:49.050 --> 00:46:52.190 a smaller group of characters and they have a 00:46:52.190 --> 00:46:55.460 more defined goal Whereas the walking dead their 00:46:55.460 --> 00:46:58.820 goal is to survive and in Z nation their goal 00:46:58.820 --> 00:47:06.420 is to get a a particular patient to the CDC Well, 00:47:06.420 --> 00:47:09.119 it's not the CDC because it's someplace in California 00:47:09.119 --> 00:47:11.719 and the CDC is not in California to the best 00:47:11.719 --> 00:47:14.699 of my knowledge So they want to get them over 00:47:14.699 --> 00:47:18.800 to California and see what the problem is You 00:47:18.800 --> 00:47:20.300 should watch it. You should watch it with Natalie 00:47:23.639 --> 00:47:25.719 Hey, I don't blame you. Flying is... Listen, 00:47:25.760 --> 00:47:27.639 if the good Lord wanted me to fly, he would have 00:47:27.639 --> 00:47:30.880 put wings on my back, so... Yeah, that's my superpower 00:47:30.880 --> 00:47:33.099 that I want to have. That's not a superpower. 00:47:33.159 --> 00:47:36.519 Get a cape. I can't fly with a cape? Yes, you 00:47:36.519 --> 00:47:40.539 can. You just have to believe. Listen, if I get 00:47:40.539 --> 00:47:43.900 a report that my co -host Felipe jumped off a 00:47:43.900 --> 00:47:46.500 cliff, he said he could fly. He had a cape. I 00:47:46.500 --> 00:47:49.820 don't know what happened. Watch me on TMZ tomorrow. 00:47:51.070 --> 00:47:53.949 Ah, that's too much. Yeah, no, but I guess, yeah, 00:47:54.030 --> 00:47:58.130 flying immortal cat with a cape. Commander Kitty, 00:47:58.210 --> 00:48:03.309 was it? Commander Kitty. I'm going to have to 00:48:03.309 --> 00:48:05.710 contact Maya and see if she wants to work together 00:48:05.710 --> 00:48:08.429 and create a graphic novel of Commander Kitty. 00:48:08.809 --> 00:48:10.530 Yeah, you can do the art and she can do the writing. 00:48:10.690 --> 00:48:14.230 Yeah, it'd be perfect. It'd be fun. Commander 00:48:14.230 --> 00:48:17.769 Kitty. Commander Kitty in the Isle of Puss Puss. 00:48:21.170 --> 00:48:23.289 Well, I hope you enjoyed listening to the show 00:48:23.289 --> 00:48:25.769 and I'm glad you made it to the end we'll catch 00:48:25.769 --> 00:48:29.489 you next time when we talk to I'm not gonna tell 00:48:29.489 --> 00:48:32.409 you you'll find out in two weeks. See you then