Hey everybody, thanks for coming to another episode of Adventures in Angulo. I'm
the host, Aaron Frost. I work with Hero Devs and Ergi Komf and
a couple of my friends. Today on our panel, we have one of
everybody's favorites, Brian Love. How's it going? Where are you at today?
I am in Austria, in a small town in the Alps called Saint
Johan m Pangau. I might be butchering that. I'm sorry if I did.
Anybody who's Austrian or German? Yeah, time here in the Alps.
Oh thanks. It sounded like he's yeah, yeah, yeah. For those
following Brian's adventure, he's now done in mainland Europe and he's on his way
down. Sounds like where are you gonna edd Spain? So from here we
go back to Munich to grab a flight to Barcelona, and then we're gonna
spend about two weeks in Spain, but we haven't decided where yet, so
and then back to the US. Back to the US A man, yep,
be nice to get back and have some like taco bells. It was
a friend of ours from Munich, I remember, I asked him. I
know, I'm going on a little bit of tandag here. But I asked
him. He had his spouse was from Florida, and you know he went
to the States several times to visit family and stuff. And I said,
I said, so, what's your what's your favorite thing about the United States?
I kid you not Taco Bell. Shut up. That's his favorite thing.
That's all we got. We got, yep, whatever whatever. At
this point in time, it's difficult to disagree, right. I thought it
was. It was good and I'll never forget that. As our guests today,
we have Zama. I guess, Zama, you you're from Dallas.
You're you're living in Dallas. Yeah, yeah, I'm living in Dallas originally
from India from is your Your full name is Mohammed Zama Khan. Yeah,
Hamaza For those wondering, Mohammad Zama Khan Khan spelled like Kubla Khan the Conqueror.
Mohammed Zama Khan. That's his Twitter handle if you guys want to go
out and read more about him on Twitter. We wanted to bring you on
because we saw that you just wrote a book and we know you're an open
source contributor. You We're like Hey, let's let's get Zaman and have some
conversations about what he's working on, just to kind of get him to know
get the community to know him a little better. So yesterday, actually,
in a really timely tweet, Minko actually tweeted out about your book right right.
He said it was it was a great way to sing Angular through different
contexts. So tell us a little bit about this book. It sounds I've
heard this isn't the first time I've heard someone say it was good. Tell
tell us kind of what what are you talking about in this book? So
what I do here in this book it takes a different approach for programming,
especially Angler. It takes you from the different projects perspective rather than you know,
concept perspective. It takes you in the first chapter it introduces some basic
you know setup for how you can set up Angler, how you can install
Angler Cli, Angler Console, which is really good for beginners to begin with.
And then in the first chapter I go with basic project for the building
of flash based application where you create flashes and very small project for biginners to
get in. And I also try to cover like Angler console in that so
that biginners don't have to go into Angler CLI and learn a lot, and
then I go into something like Angler router by using creating a brand new project
from scratch. And then I go into progressive web apps server, cyber rendering
application, ironing application, native scare application and show the users about how they
can actually use the whole platform and build coose stuff, not just by learning
through product, but also by maybe taking these concepts and applying them in their
own projects. That's really cool. I think it's interesting that you mentioned PWAs,
so that's something obviously not everybody in the Angular community is leveraging. Perhaps
was there a reason why you chose to kind of include that in the book
or did it just felt like something natural to you? So some my basic
idea was since before I wrote this book, or take took this book,
I worked on a lot of different projects in my company, and I was
able to achieve like I created an Ironic application with couch TB and stuff and
was able to build it in like in a month. I know the power
of Angler. Even though like most of my Carrier I have worked in the
recent past, I've been working on React but also developed applications with Angler and
was able to build rapidly and to show that power of how you can create
an application like a progressive a app in a matter of few commands, anglicialized
beauty schematics. That was really my understanding was to teach people how easy it
is to achieve all these different capabilities and add those things and go from there,
like try to learn and also create some good applications for your app,
you know, for your companies and for your own If you're creating your own
project, then ye just utilize it. So that's really cool. It is
cool. So with every chapter it sounds or with every concept, it sounds
like you kind of have the reader engine new up a new project and then
kind of dive in. I like that approach. Why did you choose to
do that approach? Like why did you say, hey, let's not just
do it for the same project, let's build. Yeah, the main thing
was I wanted to cover not just the different uh you know, capabilities,
but I also wanted to use a new component library or something new, like
you know, in our chapter, I bring in a chapter where I use
native script, I use NGX translate, so maybe the same eng ex translate
can be used in some other chapters and some new cool like uh, complment
libraries like Momentum, Ui, Material Design, Bootstrap, Bulma. Except so
I just wanted to put more and more tools for people to like look at
different stuff and know about the community, how deep and rich the community is,
and utilize those tools. That's really great. I like that you're bringing
in all those different things from the ecosystem right around Angular, Native Script,
Ionic. You mentioned the Angular console, especially for you're not comfortable in the
terminal. I mean, these are all things that are not you know,
shipped by Google, right, but it's part of the larger Angular ecosystem that
really makes the Angler fantastic and a good solution for a lot of projects and
companies. And it is all Angular, right, like you're all you're writing
in you know, all of it. But like with Native script, you're
going to bring in some I think they're called tel Tilaric or progress yeah yeah,
Claric, yeah yeah, And so you got to bring in some Telaric
modules. And then if you're doing Ionic, you got to get used to
the on it build stuff, right, So it's probably pretty good to take
those separate just because they're pretty distinct, right, Yeah, Yeah, they're
distinct but they also have some similarities. Yeah, what makes them so great
is the framework thing that comes with it. Like, I don't think Native
script would have been such a great tool if Angler wouldn't have been a part
of it. I mean, I know that there is a Manilla JavaScript thing
that you can do with native script or use review. But then what gave
them a lot of push was having them integrated into the framework and making it
easier for development native like Reactnative. I don't think it would have been popular
without Reacting. Sure, I think native script you can do like Vanila JS,
and I think XML maybe for like the view layer, but it's pretty
challenging. Angler puts a nice rapper almost, if you will, on top
of that, and uh yeah, you know allows you to you know,
go faster and to make things easier. So yeah, that's cool. I
was just wondering did we mention the name of the book, the title of
the book, and the publisher and how read you know, readers if they're
listening at this point, going oh, this is a really cool book.
I want to get my hands on this. What's the title and the publisher
and how do we go about getting it? It's called Angler Project. It's
published by Fact Publishers and you can find it at Angler projects dot com.
Awesome, thanks Either projects dot com. So I'm certainly wondering this some guesses,
maybe some other readers. You're wondering, how insane do you have to
be to write a book? And then two, how long does it take
to write a book? I decided to do one one time, and it
took me a long time and I never shipped. So I'm just wondering,
how long do this? Oh yeah, so that's a story behind it.
Like when I got an offer from Fact about writing a book, my wife
was expecting, like she was in her beginning. She was like in third
or fourth month that we were expecting a baby. And it was really a
challenge for me to like take this project up. And I knew that I
could write this book because working on so many multiple Anger projects makes me eligible
to write this book. And I could have done a lot of justice to
the title of the book. So contributing the community was one of my passion.
And I know that writing a book is is a big task that you
will take up, and I took up. And then once my wife,
Dally were I took a four months break, like three or four months break
and then finished my book. But then, yeah, so it's a big
task that you have to take up and think about writing a book. Is
I actually after writing this book, I got a couple of offers for writing
another book. I was like, Okay, not not yet. I have
different plans. Maybe way to the kids too exactly girls up. I just
see Zama like baby in hand, MacBook pro on the knee, just kind
of one typeing it out. So when I think I was writing a book,
I feel like it's kind of like selling a multi level marketing, Like
you have to get all your friends on board to like like proof read your
book and give you feedback on your chapters and your examples and stuff. Was
that pretty hard or did Pact help make that easy? They made it a
very made it a lot better. I mean they have editors and they have
proof readers, et cetera. Doing it write down. Like when I started
writing my book, I was using Anglo seven, and then when when the
book was published, it was Angler eight and I was also taking up NX,
so I exchanged a lot. So I had to like change a lot
of stuff by the end. And they really helped me for I mean,
for the first time writer, I would suggest to take a publisher. Maybe
in future, if you're maybe thinking of writing a book, maybe self publishing
might be an option. But for the first time publisher or author, I
would suggest go with the publisher and go with the structure. And yeah,
that's good. Yeah, it's so hard to me, so I'm glad that
you did that, got that assistance from them. Yeah, you mentioned NX.
Is NX also included in the book in one of the projects or one
of the chapters. Actually, it's included in a couple of chapters. I
had one chapter where I developed an e commerce application using PWA, and then
I took that and converted that into a MONORYPOO application and created an admin application
or on top of it, got it. Then another chapter where I am
I'm trying to teach how to build angler components and how to publish them on
MPM and stuff. I used NX because that makes sense to have a mono
repot where you have a demo application as well as your library application, and
you can have a very good interaction with both of them. That's interesting.
I've never thought of using NX for that particular solution. I've always just used
the CLI because it has libs and then it does all the energy packager stuff
for you. That's cool. I'll have to check that out. Yeah,
that's cool. Doing this book. Wasn't your first kind of adventure into the
community. It sounds like you've done some open source stuff too. It sounds
like me and you are probably gonna have to get in a fight by the
time the podcast is over. We have we have kind of a competing open
source project. Not competing, I mean we probably I wrote mind, I
didn't know if there was any other out there, so we should see how
many GitHub stars I have. Yeah, well he has way more get ub
stars in mine. He has a good name, all right, and I
mean it's a good project. I didn't mean to say anything about so ngx
loadable and what else. I saw something else on the CV. So I
started with Tom Lee. Oh yeah, So I used to work at Cisco
and we used to when I'm used to do Angler dot JS, we used
to use formally and we were going to Angler and I wanted to for my
own project have a similar kind of a project for Angler two. I started
when Angler two wasn't release candidate, and from release candidate. In one and
two there was a really big change, and right like we introduced ENGI modules
and service, I started my Angler two and benches from their building Angler formerly
and worked on it, and then I went into a React project, and
then I slowly reduced my contributions to njx formerly but now looking at the community,
it has twenty thousand downloads per week, which is great. And then
I was a bit busy in React community, you know deview context. My
company is a digital transformation company working for multiple different clients. Sometimes I work
for two clients and stuff, so some of them projects are in Angler,
React and mixed. So even though I'm currently developing using React, I know
my peers and I have to do code reviews for people that are working on
an Angular and I always saw this thing with codalizer, you know, accessibility
stuff which brings up to me like a lot of people that are working here
are junior and they don't focus on accessibility. And when I used to work
on React projects, I know that there are accessibility tools within like a Liner's
es lint world, and we didn't have that in Angler. So I tweeted
about it on Twitter and said, okay, do we have something like this
or do we have to create a new project, a ts link project for
accomplishing this. And I pinked Menco and Vassine and they said, oh,
yeah, we could do this, but we could do this in codelizer,
and they asked me to contribute to it. I was like, okay,
let's pick that up. It's kind of a different project, like I'm not
used to working with linders and stuff, but I I picked that up and
added like ten different accessibility rules. You can check them out on web dot
desk slash angler and the accessibility you know article. You can read it all
about what are the different rules and why they were added to the codaalizer.
That's great, and that's on web dot dev. You said, yeah,
that's awesome. Cool, that is really great, man, Codalizer sounds like
a hard project to contribute to. Yeah, that's what I was thinking.
Yeah, it's kind of like you have to understand the ASTs and stuff.
But yeah, that was something different. But yeah, it's it's not I
mean, Minko developed it like it's maintaining that repositively, so he maintains it
in a very maintainable ways, so it's very contributed as well. That's good.
I think eighty five percent of the people I know have contributed to formally
somehow, Like I feel like that's like the most popular open source project of
guests on the show and of my friends. So that one sounds maybe more
doable. But codalizer that sounds intimidating because it's still so much like and it
was bill by someone who's so smart, but to your point, maybe he's
smart enough to make it maintainable. He too, right, So yeah,
that's good, that's cool. And then at last, coming to the competitor
library. Oh yeah, yeah, I knew React looadable, which makes it
loading components very easy and simplifies that process. And something that it also gives
you is you know showing loading, you know, indicator while something your component
is loading, showing time out, showing preloading your component right like even before
you even show that up. So maybe you have a model which has like
dependency on D three and all that stuff, and it takes a while to
load, so preloading that is a very good feature which we have for routes,
but not for lazyloading components. So yeah, I wanted to build this.
Jake's looadable didn't see and like I didn't even like when I read about
it. I was doing React and it was like a revelation for me that
oh you could do this and Angler, because I wanted that feature to be
Angler. Yeah, I was like, okay, but this when I read
the articles about it, it looks annoying, like it's so complicated to do.
And that's where I was like, okay, we can create a rapper.
I didn't even try to find existing rappers. I just said, okay,
there's React loladable as an example for me to recreate my ngxloadable and try
to create all those features. But in an angular context. Yeah, that's
awesome. I'm looking at it. So for those who don't know what it
is, when you want to lazyload something like D three or maybe an Angular
component in Angler, it's super easy. If it's a route change that's happening,
right, But like, what if it's in a modal, Like maybe
you've got a model with the PayPal library in it, and like anyone who's
worked with PayPal, that SDK is like big, it's at least as big
as your framework. You don't want to load that, you know, you
want to load that when you open up. I think the best example when
we gave about loading it is not just model, but think about dashboard design.
Like you have like fifty different widgets. Maybe the user just wants to
show five different widgets. Do you want to load all the fifty different widgets
JavaScript in the bundle of your route and then included or do you want to
you know, just load it on demand, just include five? Yeah,
I agree. And then there's also maybe if you are listening to the network
speed, which is an API in the browser, you might want to load
things immediately if they're fast, but you might want to definitely delay load it
if it's a slow network speed. Right, So there's a lot of reasons
why you would want to not you would want to laserload something other than our
route changes. And so this ngx looadable gives you a library that you don't
have to build. And trust me, it's not easy to do on your
own, Like it's eificuly complex to do this thing without JX looadable. And
so that's what this library is good for. It it makes it so that
anyone can kind of have like that that expert level control over the size of
their bundles. And when things get loaded in, so it's really really handy.
I think that like always try to update your library, is my I
mean, you learn a lot of stuff, like once I developed. I
think that I developed this library in February and then I was like, Okay,
I think I covered most of my features that I wanted to look into
this library for and then I think I stopped my development for two or three
months, and then last month I picked up the stat okay, can we
make this better? And I came up with version two, where in version
one you had requirement for like adding the lazy modules that way to the Angler
Jason, etcetera. And version two you don't even have to do that.
I use chematics to make it even better so that you just run and g
generally and Jake's looadable module to create them all that for you. And it
doesn't includes that in Anglo Jason. So it's cool. It's really cool that
Anglosia gives you all these capabilities to make things easier. It doesn't make it
easier, right, right, that's awesome. That's a lot of open source
stuff. So I guess I'm gonna ask a couple other questions. Do you
have like a crazy stack Overflow score two sounds like no. You know,
you never know people who are as passionate indid you sometimes they're like two million.
I was like overflow r. I figured it has Besides this, I
mean, what else have you been up to? Are you at conferences and
stuff? I haven't been to any conference as yet, but I'm planning for
enng cons next year hopefully nice nice that's right? Is open? Right?
Yeah? Yeah yeah yeah, CSPs I open. I submitted a couple of
them. I'm planning to submit more, hoping something from that side. Even
if not, like, I will try my company to you know, get
me there next year. Hopefully very cool. You definitely get there. It's
a lot of fun, it is, Brian. You're teaching a workshop there
this year. I am. I'm doing the Today workshop before the conference,
and that'll be on Angular fundamentals. So if you're you're new to Angular and
you kind of want to learn all the ins and outs about Angular and RxJS
and everything that goes into the Angular framework, come joint it. It's really
great to be a part of the community. Like it's not just like conferences
or podcasts, but like things like workshops, are really helpful, like teaching
getting people into the room and getting teaching them the fundamentals and teaching them how
to do stuff from scratch. It's really important. I think that would be
great Anglo fundamentals looking up for that. Yeah yeah, I was like,
you don't need to be there, but for anybody listening there class, you're
doing no, you're doing what to workshops. So what I saw, you
know, Brocky and I it was like, weird, We're like, let's
do an observables class. Nice brocking Now we were like, we're like,
we're gonna do an observables class where we kind of go through you know,
zero to hero on absurables. Right. Yeah, yeah, today, Like
everyone has their own way of teaching, and I've seen absorbable from different speakers
and different angle and I think everyone for us brings a different perspective, Like
he brings some promises and then teaches that and it's really interesting. Yeah.
So we're hoping that we can peel it back a little bit easier for everybody.
And the important thing about teaching observables, at least in this course is
they're difficult not only to learn, but they're hard to explain. So part
of this is helping others be better at teaching observables. It's not just about
teaching the class to learn it to use abserbles. It's not also about teaching
developers like us to teach them better because we're not very good. Like do
either of you guys remember when you were first learning RX and someone was like,
hey, what is an array of numbers array of click events in common?
And you're like, nothing, they they have nothing on in five dimensions
in common. They're they're not they're not nothing common. They're in an array.
That's it. That's it. And then the instructor's like, nope,
there that's not even an answer, like anyway, So that's not a way
to teach it. So there's better. We got to get better at teaching
these things too, So that's good. I like that anyway. So we're
doing a two down that, but we're also doing a one day on reactive
angular because I personally think that's the most important skill for a you developers to
kind of masters being reactive. Are you going to be in two places at
once? Is there usually only two days of workshops? So I have a
twin brother, so no, I know that I know that, but so
I didn't know that he was a developer. Day one, I'm with Brocky,
and then day two I might go do my own thing. Oh got
it, and then he'll just y he'll be yeah, yea yeah ever yeah
by himself, Okay, got it? Yeah yeah, So it'll be fun.
I was wondering how you're gonna do that. But Reactive Angular it's gonna
be it's it's gonna be an amazing class. Like people are gonna walk in
wondering, what did you know? What does that word even mean? Reactive
and they'll walk up No. Yeah, but there's a lot of good workshops.
I feel like we just derailed the podcast. But I'm gonna keep once
that. Now that it's off the rails, I'm gonna keep going down this
path. Tara, she's gonna be there giving a jam stack yep, I
saw that, like Angular, John and Dan. Obviously you've got three architects,
three days actually three days of workshops. Oh I didn't know that.
Oh wow, there's one on Sunday. Wow. So yeah, they've got
a Sunday one. They'll be the only one on a Monday Tuesday. So
they've got three days of classes. And then you've got uh Ionic. I
saw that the geniuses from NARWAL will be there. Mike Hardington's the Ionic guy,
by the way. I was just gonna ask me Mike's doing Ionic,
and then Jeff and Victor are doing an ex mono repos. I think Victor
may not be there. I think he's got some, you know, exciting
family stuff going on, so he's he's probably not going to be there,
but Jeff will be there. And I guess the main contributor from not from
NX will be there too. I'm trying to remember his name. I think
it's yes, Jason Y. Yeah, he's awesome. I think Jason will
be there too. So it was good. It was good. That's good.
Brandon Roberts and Mike Ryan they'll be doing two day in jr X by
the Creators in j X, which would be good. Some great workshops,
Yeah, lots of good workshops, bro. And those tickets are available now
or why Okay, already on sale, so buy before they run out.
But yeah, and then in like the next week or so, we're gonna
announce the theme of the conference. We haven't announce it's also on this concurrently,
right, the discount sold out and so it's kind of on like regular
ticket prices. So so yeah, so what if I already bought my ticket
and I'm listening to this podcast and I'm saying, oh, I really want
to go to this workshop. Can I go back and still get a workshop
ticket? Or am I kind of sold out at this point? You know
it? Just go buy the tickets. Like if you're local and you just
want to go to the workshop, or you you just want to go to
the workshop and other conference, yeah okay, yeah, yeah cool. Workshops
just kind of a separate ticketed item, so yeah, buy it on Yeah,
and if you don't want to go to all three days or just you
don't want to go to it, you only want to go to one or
two or whatever, just buy those as well. So there are individual day
tickets too for the workshops, yeah, not for the conference. Yeah yeah,
the conference is just a single ticket, right yeah, So Zama,
what else? What else are you working on? Man? Like? What
else keeps you wake at night besides your book and your baby? So can
only like, uh, I'm trying to improve the library that I said,
and Jakes Loo, but like I have a Vision three coming up, So
what I want to do is utilize ivy angler ivy in that and we know
that modules are not required in version nine for laserloading components. I want to
explode that area and see how we can improve that. I know that the
ivy API is not public enough so that you can create wrappers around it,
and it should be stable by probably Angler ten. But then I'm just playing
with it and saying where we can take this library to make it much better,
and like not even requiring a module to be created for laserloaded a component.
That's really exciting. Yeah, I'd love to if you get a chance
to write a blog post about that, or you know, kind of teach
the community and what you learned. A lot of US blogger at angcon am
a Engi Coon Champaigon by the way. Nice, Yeah, that's awesome.
Well I look forward to seeing that blog post. Then. Yeah, I
feel like I got to go work on my loader now, Like I feel
like you're calling me out. Yeah, I mean I think I created an
issue for on your library and asked you to like implement a bunch of stuff
like time out sloading indicator. All right, is that issue open or exactly?
I'm probably open. It's open life's too busy. Uh, maybe you're
going to get some anonymous tickets or your libraries. Actually, I think it's
it's a great use of this month. As you probably have heard about Hacktoberfest
going on this month. In my library, I created a bunch of issues
with with the labels as hackaber Fest, and a lot of people actually help
you, like like they came up and helped me. So it's really great,
Like just use that mame, like try to get some new contributors too.
It's a great idea, good suggestion. That's a great idea. So
I'm also saw Brocky and just saying and justin doing some had table fest on
their quitch account last week. Oh nice, yeah, nice fun. So
zom, I have a question. So you've created and engither formally. I
know that's used. I've used it in a couple of production and applications at
large enterprises, and you've got all these projects some kind of cures. What's
been the biggest challenge maybe that you've run into when writing your own library and
publishing it and getting out there? Is it? The is it building it?
You know? I've heard from some people and I've built a very small
library myself, and sometimes the typescript declarations and all the all the typescript stuff
can be very difficult with all the generics and everything. Or is it the
publishing process or is it like the maintenance, like kind of can you give
us a little clue, you know, if I'm interested in contributing to open
source, what are some of the struggles that you've you've kind of faced as
part of this. So firstly, publishing is one thing that you have to
understand how version works. I can give you an example like where I made
a small issue and it's all the process. Like you should do open source
not for the sake of doing open source, but also for learning stuff.
So that's where I feel like, you know, contributing to open source will
give you more value where you learn a lot. You learn to see what
a framework can do and what are the possible ways of doing and what's the
best way of doing it? And that's where I see the value of open
source and you learn a lot of stuff. Like in NNGX two point zero,
when I was releasing, I created a branch, like I pushed a
new version called two point zero point zero alpha zero, and I didn't know
that I have to like put a flat called alpha to push it. And
then I saw like people who are using it coming and creating issues saying,
oh, why does it say it's not working now? So there was a
breaking change in that alpha version. People automatically when the NPM installed, they
got the latest version. So basically you learn a lot of stuff, Like
publishing is one thing that you learn. Like it's so when I was developing
formally and there was like Angler was a release candidate, and we didn't know
how to dynamically load the component. You know how formally works it It basically
dynamically loads your you know, all the components in place for you where you
just provide a configuration for the form. You just say you just have an
area of objects and say what are the different form feels, et cetera,
And then on runtime, formally actually dynamically loads that up and shows that on
the screen. So when it was Angler to release candidate, you didn't had
that much visibility about what are the different internals of Anglo and how to achieve
things. Yeah, once you learn those things, you will get So if
you are a programmer, you actually you know, get to an expert level
where you understand some things which are not normally known, so I think that's
very important. Like just go ahead if you have an idea, if you
have a passion for building something, then start implementing it. And then even
if you don't know that how to do some stuff, you will learn it.
I mean, there would be ways of school learn. Yep, that
was really great advice. I like it. Yeah, that's fantastic. There's
a lot of people out there wondering these questions, so I'm glad that you're
giving such good answers. There's a lot of people who are looking to the
first time contributor, so thanks for thanks for coming on and talking about that.
It's also like just go to Hacktoberfest and just select typescripped and maybe search
for Angler on GitHub with Hacktoba label and then try to contribute to those repositories
and open source projects. I mean that that would be very good, good
for your new time open source developers who wants to focus on Angeler. And
there are things like first time only label. They are like up for grabs,
issue hub at your way people can and find it. Yeah that's cool.
Yeah, that's awesome. I haven't been to octoberfest dot com. So
I should probably give them and check it out. So if anyone wants to
kind of reach out to you online and engage with you, what's the best
place for them to get a hold of you? Twitter? I think I'm
trying to get more into Twitter. So yeah, you can find me at
Mohammed Zamakhan. And the only thing in my Twitter handle is that you could
I couldn't have like double M in my name because of the length of my
Twitter account, so it's basically instead of m M, so it's Mohammed Zamakhan.
Okay, awesome. Cool. So if anyone wants to reach out did
him on Twitter? All right? Let's uh, let's move on to z
pics. Brian, you got any picture you want to start with? You
you go? I got one pick and related to NGICOMF right, So we've
talked about workshops, we talked about the CFPO being open. So my pick
is the live office hours and I imagine Ar you're heavily involved with that.
So that's October fourteenth at twelve pm Mountain time, and there's a link you
go up on what YouTube dot com search for NGI COMF and I think there's
like a video, it's like set up already. Yeah, I'm sure if
you follow ERGCOMF on Twitter, you'll be tweeting out the link to that as
well. So if you're if you're listening to the podcast and you're like,
hey, you know this is awesome. I want to speak at NGI COOMF.
I'm interested in submitting a proposal. What do I do? How do
I get started? What's important? What's not important? Kind of that process.
Aaron and the organizers will take you kind of through that, right,
Yeah, definitely, we'll try and we'll try and make it easier. It's
kind of nerve wrecking, if we could be honest, like it makes me
nervous. Nice submit talks and we're trying to make it as least scary as
possible. So we're trying to do an office hours where I don't care if
it's your first time or your one hundredth time. You can come ask questions
about hey, what should I do? And the questions can be like are
you going to pay for my flight? Right? And and one valid question
is valid question, it's a seriously, are you going to help coach me?
Yeah? We are. We have a professional speaker coach, are you
going to are you gonna review my slides? Yeah, definitely. We won't
let any sides go on stage without making sure that it's like approved content that
isn't gonna kind of offend the community. And so yeah, like there's there's
a lot you could ask, how should I structure my talk? How should
I structure my my submission? There's a lot of questions, and so we're
there to kind of answer them and make it as easy as we can.
And we do kind of assume that role of know it alls that you can
ask questions too, and and that kind of might come across as weird,
but we are. We are just there to try and help us all.
So yeah, yeah, yep, that's definitely my pick. I remember that
you probably don't know this, Aaron. This was before I think i'd even
met you. I watched like The Office Hours, I think in twenty seventeen
or something, because I was so intimidated to even submit. I was just
like, no, nobody wants to hear what I have to say, right,
nobody cares, or or here's the other one. It's like, oh
that's already been done, or I'm not the expert in this or you can
talk yourself out of submitting. So right, and so I watched those office
hours, and I'm I'm here to even say, like I did not submit
that year because I was like, nah, I'm not going to do it,
even after going to the office hours. But then the next year I
got the courage did it and submitted and and so it's a great experience.
So certainly check that out. Yeah, don't pull the rip cord. Definitely
submit, just submit, win in doubt. Submit right, because here's the
fact there's probably on every topic twenty talks. So you're just gonna be one
of twenty. It's not like you're it's not like we only want one submission
for each time. Oh there's a router talk no more submissions, like,
no, we actually want twenty and well, well we'll pick the one that
we think represents the community the best, you know. So right, And
what's the deadline? So I know it's open. Now, what do I
have until like December or something now? Or you have till January third?
Yeah, Well that's right. You mentioned that that's right through the holidays right
now. We like people to take that that, you know, the holiday
break and they get through and kind of finish up their ideas and then sure,
I think it's also good for people like since angler IVY is coming out,
maybe yeah and hack it some you know, APIs and yeah, cool
stuff the new talks. Yeah, that's a good point if you're if you're
just sitting there right now, I'm glad you said that, Zama, and
you're like, what should I talk about? I'm telling you everyone wants to
know about IVY. YEP, myself included. If you create a brand new
project with the a UCLI right now, it's turned on in a your nine.
So go create a new project and start buggering with it and come up
with a talk title like come up with yeah, teacher learn. Yeah.
You know, like there's only any one conference one NTI coff where IVY was
new, and you can get those new IVY talks, and so this is
kind of the first one. It's the only one you're gonna get a chance
to do that, So definitely do that. That's my suggestion is to definitely
do an intro the IVY Beginner IVY X, you know, something like that
type talk, because this was the only time that's going to be like a
valid topic level so yeah, anyway, Yeah, good pick. I'm gonna
I'm gonna move on my picks. So this is the pick that kind of
keeps me a little bit same, Brian, anymore of the days are a
little bit weird twenty sixteen. It seems like it was forty five years ago.
The last two years have gone by a little bit slow for me.
So Late Night with Seth Myers that's my pick. It keeps me fresh a
lot of days. And uh so Late Night with Seth Myers is my pick?
Is he the one that does it's a closer? Uh? Yeah,
it's look, it's so good. I love that man. Yeah, so
he ties it together at the end. So well, his writers are fantastic.
So anyway, absolutely, yeah. With John Stewart going on on Seth
Myers is probably he's pretty that So I'm gonna pick Seth Myers. I was
also going to pick the office hours. I think by the time this podcast
goes out, the office hours will have gone out earlier that morning, so
I think, well maybe actually I think this goes out on Monday, and
the part the office hours Monday noons, so so I'm not actually sure.
If you're listening to this, it might be too eight, but try and
get down the office hours. So yeah, those are my picks, Ma,
you have any picks for the community. Yeah, I saw a new
to eight from Dominic Elm. He created this library called NJX Tempede stream and
there you can actually use emojis. Instead of like n GAF and n G
four and stuff like, you can use emojis and it's called hacking the Angler
compiler. He has slides up there and you can go through the slides and
they're really awesome. That's awesome. I love Dominic. He's so cool.
Yeah, I mean, especially when they deal thanks with machine learning and start.
It's really amazing because I kind of love that space of machine learning and
stuff. I'm thinking of doing something that tends to flow dot ja, so
yeah, great. I got a chance a few months ago to kind of
work with on a project too. I think he's fantastic. I really really
like Dominic. I'm glad you picked that. Yeah, go check out that
talk all weak to the slides in the show notes so people can go find
those slides. All right, Well, Zama, thanks for coming on.
Brian, thanks for taking time away from your vacation to be on the podcast
of course, happy to be here and to the listener I will say thanks
and we will see you next time. Please