November 6, 2025 • 51 mins
In this episode, Katerina Skroumpelou joins us to talk all things Supabase — from what it is and how it simplifies life for everyday developers to why Angular devs are starting to love it. We chat about real-world use cases, security best practices, and how Katerina keeps learning new tools with confidence and curiosity. She also opens up about standing out in a tough job market and the mindset that got her where she is today — no “auth” required.
https://supabase.com/docs/guides/getting-started/tutorials/with-angular
More about Katerina:
https://twitter.com/psybercity
https://bsky.app/profile/psyber.city
https://github.com/mandarini
https://psyber.city/
https://github.com/supabase/supabase-js
Follow us on X: The Angular Plus Show
Bluesky: @theangularplusshow.bsky.social
The Angular Plus Show is a part of ng-conf. ng-conf is a multi-day Angular conference focused on delivering the highest quality training in the Angular JavaScript framework. Developers from across the globe converge every year to attend talks and workshops by the Angular team and community experts.
Join
Attend
X
Bluesky
Read
Watch
Edited by Patrick Hayes
Stock media provided by JUQBOXMUSIC/ Pond5
https://supabase.com/docs/guides/getting-started/tutorials/with-angular
More about Katerina:
https://twitter.com/psybercity
https://bsky.app/profile/psyber.city
https://github.com/mandarini
https://psyber.city/
https://github.com/supabase/supabase-js
Follow us on X: The Angular Plus Show
Bluesky: @theangularplusshow.bsky.social
The Angular Plus Show is a part of ng-conf. ng-conf is a multi-day Angular conference focused on delivering the highest quality training in the Angular JavaScript framework. Developers from across the globe converge every year to attend talks and workshops by the Angular team and community experts.
Join
Attend
X
Bluesky
Read
Watch
Edited by Patrick Hayes
Stock media provided by JUQBOXMUSIC/ Pond5
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:00):
M hm.
Speaker 2 (00:08):
Welcome to the Angular plus Show. We're app developers of
all kinds share their insights and experiences. Let's get started.
Speaker 1 (00:21):
Hello everybody, and welcome to the Angular Plus Show. My
name is Brooke and I'll be hosting today with two
very exceptional human beings. We have Laura.
Speaker 3 (00:31):
Newsom, Hello, how's it going?
Speaker 1 (00:35):
And mister j Bell here again.
Speaker 4 (00:38):
I made it this time. Somebody else made it this time.
I'm also here.
Speaker 3 (00:47):
It's supposed to be Yon, but he's a bad, bad host.
Speaker 4 (00:56):
Under the bus.
Speaker 3 (00:57):
He goes under the bus.
Speaker 1 (01:01):
But to make up for y'all not being here, we
have like we're really pumped to be joined by someone
who has made really quite a big impact on the
Angular ecosystem and I think the developer community in general.
Welcome to the show.
Speaker 5 (01:15):
Katerina, Hello, it's very nice to be here.
Speaker 1 (01:20):
I'm going to have you pronounce your last name for me.
Speaker 3 (01:27):
Yep, that would not come out of my mouth.
Speaker 4 (01:29):
That I feel like we do this every single time.
Speaker 1 (01:34):
I know's so old. We're just we're Americans and we
really suck it saying names. We're North Americans who suck
it name pronunciation.
Speaker 4 (01:50):
There you go.
Speaker 3 (01:54):
I think that like listeners will probably realize the more
they listen the the that there are names like we
tend to go with first name. Yeah, welcome Katerina to
the show. Say your full name the way that people
should say it.
Speaker 1 (02:12):
I figured this way. At least the next person will
know how to say it. So there you go. I
did you all a favor, yes, but but yeah, welcome
to the show. Katerina is so excited to have you here.
You're actually going to be talking all about super bass,
so we're excited to learn more about that. But just
(02:32):
kind of like the ins and outs why you'd want
to use super Bass, how it can help make your
make building applications faster and easier. That said, though, we
also need to say congratulations because you've recently just started
working with super Bass, So congrats on the new job.
How's that going so far?
Speaker 5 (02:52):
Thank you? It's quite amazing. I've been there three months now, okay,
and it feels like much longer because I don't know,
I feel right at home. To be honest, I really
like it is.
Speaker 3 (03:06):
Is the super based team? Are they because you're located
in Greece? Correct? Is is your team also in Europe?
Are they all over the globe.
Speaker 5 (03:18):
It's a heavily distributed team. Yes, nice. Yeah, we have
people from all over the world, so it's nice.
Speaker 3 (03:25):
Nice.
Speaker 1 (03:26):
So Catherine, I have a question for you too, because
you got a job, and it is not an easy
market right now to get a job. So do you
have any suggestions or tips for listeners on if they're looking.
What are some things you felt like maybe you did
that helped get you.
Speaker 5 (03:44):
Oh, I have a lot of tips. Yes. Actually the
thing is my husband right now is is job hunting,
so I have tried to tell him some tips. But
then also it's not nice to always tips to your
to your spouse, So I will give you all the
(04:04):
tips here and.
Speaker 1 (04:10):
I love it.
Speaker 5 (04:12):
Yeah, yeah, so yeah, I found the supervised job in
the normal way, like I applied. I didn't know anyone
who worked there, so I applied and went through the
typical hiring process of having like four or five interviews
I don't know how many, and getting the offer, accepted
(04:33):
the offers, And I had actually applied in the past before,
and I had I hadn't, I hadn't been even to
an interview, soight was the second time I applied that
I got the job. But usually the way I I
would find a job in the past, or I would
(04:55):
see people finding jobs in the past, is through personal connections,
which I think is a very strong asset to have
personal connections because it's a way to get at least
your resume read. You know, it's the first step because
because a lot of people are looking for jobs, you
(05:16):
may have like a stellar resume, but it may never
even get to the red stage. I don't know. So
I wouldn't get disappointed if I wouldn't listen here back
from a job while job harding. It is the most
important thing I have in mind, right, and there's always
(05:36):
going to be someone who is better than me out there,
so you know, maybe not maybe I'm the best, but.
Speaker 3 (05:43):
Well, I think that's just it though, Like you never
really know exactly what kind of you know, Like I've
seen people who have not gotten jobs that they would
be very well qualified for. And it doesn't mean that
you're not a good candidate and that you don't deserve
a job. Just means that what that company is looking
for right now, they had somebody that was a better
(06:06):
fit for whatever reason.
Speaker 5 (06:07):
Oh yeah, it could.
Speaker 3 (06:08):
Be a dumb reason like nepotism or promiism, or it
could be you know, something unexpected, like oh, we actually
wanted somebody with a little more experience in this area
than what you have.
Speaker 5 (06:21):
Yeah. For example, the job I had applied that super
Base was for client library engineer, which I am not.
I'm working on the SDKA team, but they needed someone
to oversee the JavaScript and the Python libraries. Right. I
told them I have no experience with pithon, Like I
(06:43):
have written like a flask API at some point on
some server, but that's it. But they were like, Okay,
you're very You're like a very experienced dipscript developer. You
have so much experience with open source, so okay, you're
a fit. We don't care about Python, you know. So
even that, I think tell something. Also. One other thing
(07:06):
that I think in my case helped a lot is
the online portfolio. Right if you have if you have GitHub,
and you have even some of your code on GitHub,
the recruiter or the HR person, the hiring manager can
instantly go on your GitHub account and see that. I
(07:28):
don't think they're necessarily going to see the code you're right,
but they're just going to see if you're slope you're not,
or if you're organized or not, Like if you have
nice reposors with the read mes and everything and everything
is tidy. They're not going to go through life by
like your JavaScript code, but they are going to see
if you're organized or not, or they're going to see
(07:50):
if you have some PR comments or your PR reviews
or whatever. So I think this online presence code presence
also helps. The final thing that I think helped in
my case is my online presence in general, Like at
the conference, is the meetups, the this thing that I'm
doing here right now with you all. But I don't
(08:12):
think this is necessary obviously, so but.
Speaker 3 (08:16):
What some companies care more than others to like it
kind of depends on what.
Speaker 5 (08:24):
But I think what does play a big part is
the portfolio, like the.
Speaker 3 (08:29):
GIT Absolutely it's it's hard when people I get pinged
a lot by people that are looking for jobs at Cisco,
and I want to help people get jobs, but I'm like,
I don't actually know you, I don't know your code,
like I don't know that. I really want to put
my name on a referral that says like, yeah, I
refer so, and so I don't know them at all.
I've never met them. I can't see their code like.
(08:51):
It makes it a lot harder to feel comfortable doing
that because it is also like the people that you ask,
it's their reputation on the line, So it's a lot
easier to say, hey, can you refer me for this position?
Here's my repository. Go you know, if you can, like,
this is how I write code, this is what I've
worked on. I think it's also important to note that,
(09:13):
like I know, for a lot of people coming out
of school, they'll have like school projects online too. A
lot of companies are looking for something beyond that. They
don't want to just see what you did for class work.
They want to see like, what things are you what
problems are you trying to solve? What things are you
interested in? And yeah, what have you worked on as
(09:35):
opposed to you know, what did you get assigned to
do in college?
Speaker 1 (09:38):
So so, okay, question, then Katerina, had you I'm assuming
the answer, but I could be wrong. So had you
put something in your portfolio where you had used super
base and do you feel like, you know, like I
don't know, how did you use that experience to help
(09:59):
you get the job?
Speaker 5 (10:00):
Then oh yeah, totally, Aer had things in my portfolio
that used superbased, because I think I had created, for example,
an application for this event that we had with an
X in April. I had put together just like a
conference application that checked people in and use suba based.
(10:21):
And also I had built the NX AI chat bot,
you know, the AI docs her assistant with superbas and
the super base example that they had, So this definitely
played the role.
Speaker 1 (10:40):
Yeah, okay, well then that said that was more for
listeners who've maybe never used superbase. Can you tell us
more about what it is and why why a developer
would even want to care?
Speaker 5 (10:56):
Yeah, so stranger enough, I have not practiced super based peach.
Speaker 3 (11:01):
I practice my.
Speaker 5 (11:03):
NX pach when I was working at an X. But yeah,
I'm just going to read the pitch from the website,
but then I'm going to tell more about my experience.
So it's a postgress development platform. It gives you a
postgress database, gives you authentication, you can create an API.
(11:28):
It gives you its functions so you can do micro
services and stuff, real time subscriptions, storage, and also vector embeddings,
which I think super based really made it easier for
people to build dogs assistance because it provided so easily.
These vector are beddings database and the vector search with
(11:48):
pitch vector and everything. So yeah, it started. I think
the original pitch back in the day. I don't know
if we use it still. I don't think we do.
Was the fire based alternative open source, the fire based
open source alternative. It's beyond that now. But if you
use fire base you would be familiar with with some
(12:12):
of the things that super based offers. But yeah, I
have used all of the features I think we have.
I think one of the favorite features that we have
is the real time thing that we have some nice
demos as well, like the real time cursor tracking, the
(12:32):
broadcast messages, like you can build a chat up very easily.
Let me think, I did want to mention something specific.
I can't think right now.
Speaker 3 (12:46):
It'll come to you.
Speaker 5 (12:47):
Yeah, yeah, yeah, it will, it will. Oh yeah, And
I wanted to say no, I wanted to say that. Yeah.
If you're using no code day, itols like both or lovable.
Let's say they have super based integrations that you can
just connect your data, connect the database instantly, so while
(13:11):
you're building a website, you can just easily or rather
the AI is building a website, AI can instantly connect
the database as well. Back there was actually explaining this
to my parents today because my parents are old people.
They're eighty, they're eighty years old, so they see technology
(13:32):
as magic. Obviously some things they see it as magic.
And my father today was telling me that he read
on this ad that there was this application that you
could do this and that, and they told him, okay,
that this is a scam. And he's told, how is
it possible? It's a scum. It took so much work
to be told no, no, no, that it didn't take
(13:53):
much work today ten minutes, one prompt, ten minutes and
against get a full application with a database and stripe
integration for people to pay you. It's not much. This
person spent ten minutes and maybe ten dollars and they
have a full working scam for you, ready.
Speaker 3 (14:14):
Right, yeah, yeah, And it's hard. It's I mean, it's
hard even as like a you know, younger person that
grew up with technology to always recognize scams.
Speaker 4 (14:27):
So yeah, the tools are taking them so much easier now.
Speaker 1 (14:30):
Right, Yeah, yeah, a generation.
Speaker 4 (14:33):
Ease of databases, ease of payment payment processors, like everything's
so easy for depths now that like it's way easier
to automate this like quote unquote real looking thing.
Speaker 3 (14:44):
Yeah exactly. So then you just ask yourself like, does
this seem does this seem like too good a deal?
Speaker 4 (14:51):
Yeah exactly.
Speaker 5 (14:52):
Yeah, yeah yeah yeah, nobody's giving them my money anyway.
Speaker 1 (14:56):
Yeah.
Speaker 5 (14:56):
I didn't want to like this whole thing the AI
called generation with scums, because that's not the case. Obviously.
The good thing is that it's making lives a lot
easier for a lot of people, either to build a
full work in application, either to have a demo, either
to go full production ready. So yeah, just making things
(15:17):
smoother and easier.
Speaker 3 (15:19):
So who who do you see as like, who are
the biggest users of superbase obvious? Is it people with
small businesses? Is it enterprise level or is it the
whole spectrum?
Speaker 5 (15:34):
I think it's the whole spectrum.
Speaker 3 (15:37):
Yeah, I mean it says skilled millions building a weekend
scale to millions, which implies it's true.
Speaker 5 (15:44):
It's true, it does, it does scale two millions, and
it is very stable and as I see in our website,
if you go on your website, you can see a
lot of a bigger customers mentioned there. So yeah, it's
it's definitely uh it's definitely also built for enterprise and
(16:06):
can support enterprise and it's big scale businesses.
Speaker 1 (16:12):
You do you suggest like you know, like I guess
I'm trying to say that what's the learning curve withis?
So you know, what what would you suggest for a
developer to have for any kind of background knowledge or
you know, is it pretty easy just to pick right
up and go with?
Speaker 5 (16:29):
Good question? I think, like like a lot of tools,
it's the more sophisticate you, the more sophisticate that you
want to get, the learning becomes a steeper let's say,
but I can I can explain a little bit more
what I mean about this generic thing. You can start
(16:50):
right off and not know anything like I had, Like
I had not worked when I first used supervised, I
had not worked with with Sequel a lot, and I
didn't have a lot of database experience when I first
started using super Base let's say two or three years ago,
Like I have never really needed to use seql for
(17:11):
production other than you know, side projects or school projects.
Like we said, you don't really need it to get
started because you can set things up very easily. And
now with the super based MCP, and also we have
some ai as systems. You can just even set up
a row level security more easily, or we give you
(17:32):
reduated sequel queries that you can run to create tables
for example, or you can create tables from the UI
even But if you want to go more sophisticated SUA
basis postwards, right, it's a it's a big relational database.
You can use SEQL queries with it, and it's you
(17:55):
can get as complex as you want. I think one
of the greatest challenges for me when we're in with
Superbase was understanding how I can work with role level
security and how I can use your level security to
use it for filtering as well, and you know, go
dip into sequel and postcar stuff. But other than that,
(18:17):
I would say, it's it's just your service that you
can use.
Speaker 4 (18:25):
And yeah, I remember roll level security being one of
the like I've never had to use roll level security before. So,
like when I was looking to put the super Base in,
like the postgersenal, I was like, okay, so how is
this secure for I don't understand how we're not leaking
data all over the place.
Speaker 5 (18:45):
I know and I know that we're now working to
make this easier for people to set up. I think
we already have some sort of assistance to set it
up more easily. From the dashboard, I think.
Speaker 3 (19:00):
Nice, nice, And it looks like there's a they support
a lot of migration schematics as well.
Speaker 1 (19:06):
Yeah, so that's that's cool.
Speaker 3 (19:08):
Because a lot of people, you know, I mean, I've
worked at plenty of just small companies that own their
servers and so they everything's on prem but at some
point they have to make the decision like do we
want to like where do we want those things to live?
You know, do we want to keep buying servers? Do
we want to move to the cloud. So tools to
(19:31):
make that easy, make that decision easier, that's true.
Speaker 1 (19:37):
Are there any examples of, like an application with super Base,
something that you think is a you know, a good
a good demonstration of what it can do for an application?
Speaker 5 (19:53):
I would say the super based website itself, So oh yeah,
I will say that the super Base website itself and
the super based dashboard.
Speaker 1 (20:05):
Okay, so then I'll take that a little bit, a
little bit further. So maybe could you walk us through
like a simple use case where like how someone might
add Superbase authentication to an Angular project oh.
Speaker 5 (20:19):
Yeah, definitely. I can tell you, for example, I build
a devil for the Angular Connect, and I can tell
you for example what I build. I wanted to build
a multiplayer game, right, so I just add that. I
think I added either Google or GitHub authentication through Superbase.
(20:42):
So you get your WT token and everything through the
authentication service of Superbase, and then you authenticate your user,
and then I would have then you can have your
pretty standard your table for your users, your table for
your user data. For example, for the demo that I
built for the interconnect website, I wanted to have like
(21:07):
a ign of emojis, let's say, and people would top
on emojis and whoever collects the most emojis winds, right.
But I needed that to be synchronized through all the
different devices so that it's fair. So I used the
real time, the real time subscriptions of superbased offers for that.
(21:31):
So I was streaming the X and y location on
the browser across through super based different devices, so that
everyone saw the same emojis on the right locations, and
whenever someone would top one, I would capture that top
and I would broadcast a message to Superbase that said, okay,
(21:51):
this one is claimed and in the table with emojis,
I would add that this one is claimed and it's
claimed but by that user ID. Right, So this one,
for example, would be like building a multiplayer game.
Speaker 3 (22:09):
Let's say, nice, I do have to call out on
the website it says use super Base with any framework
and there is no Angular logo there.
Speaker 5 (22:23):
Fo let me see. I'm pretty Oh yeah, that's true.
Speaker 3 (22:31):
I mean they got.
Speaker 5 (22:34):
Yeah, but we do have some Angular demos and I
know that someone came up to me an Angular connect
saying that they have submitted a pr H which update
the Angular dogs. I should look at that pr and
(22:55):
try to get it mercy, Yes.
Speaker 3 (22:59):
Get our a little logo on there.
Speaker 5 (23:01):
Yeah, I'm looking. Oh there it is. Okay, I found it.
If you scroll deep down. I'm going to paste it
in the chat here. Build a user management up with Angeler.
Speaker 4 (23:16):
Perfect.
Speaker 5 (23:18):
Yeah.
Speaker 1 (23:19):
One thing I'm always curious about too, is like, I mean,
obviously superbas is already solved or is helping developers to
solve a lot of problems, right, But is there something
and maybe this is too top secret, I don't know,
but is there something that super Base is kind of
stepping into? Is there a new problem that maybe it's
(23:39):
not already solving that you guys are going to start
trying to help.
Speaker 5 (23:44):
I don't know, No, I literally don't know.
Speaker 3 (23:49):
No, that's totally that's totally fair because what like, as
you were, so, what what exactly do you do at
super Base?
Speaker 5 (23:57):
So I we have an STKA eighteen and we have
we used to call it the client libraries, Like we
have client libraries for javascripts. I think they're all on
GitHub JavaScript Cattling, Python Swift, so I oversee the JavaScript sdcase.
(24:19):
So the JavaScript s the case are sdcase for all
of the features that superbase has, like the functions, the
real time, the storage, the post quest and the authentication.
And when I joined, all these used to be six
different repositories. Guess what they are now?
Speaker 1 (24:46):
I wonder where that came from.
Speaker 3 (24:49):
If only they had someone that had some experience with
Mono exactly. Now, was it a Mono repo before you
joined or was that something that you were able to
help implement.
Speaker 5 (25:03):
Yeah, I was able to help implement that. It was
one of my first tasks when I joined, and it
took me about a month to get everything worned up correctly.
And now it's been live for about three weeks and
we're happy.
Speaker 3 (25:24):
Yeah, yeah, that's it is hard, like trying like it's
one thing to start something new with mono repo, but
it's another thing to try to pull things back into
a mono repo just to get everything.
Speaker 5 (25:39):
Yeah, it was, so there were some challenges. This is
all open source and you can see the gecub. You
can see the whole process on GitHub, step by step
how it happened. So one of the child the first
challenges was that every package was a different version. So
(25:59):
first we have to choose okay, we'll take the largest
latest version and just bump it a minor. And then
the other thing was when I pulled everything, I used
NX import to bring everything into the NX monory, but
which retains history, which was nice because I wanted it
(26:22):
wasn't like I needed to think, but I wanted to
retain history, which was done in a very good way
that I like because it's nice to be able to
get blame yourself and other people.
Speaker 3 (26:36):
The migration. It's literally you are get blame on literally everything.
Speaker 5 (26:40):
Which yeah, exactly.
Speaker 3 (26:42):
I had that happen when we I didn't know how
to move things in the mono repoke collectory correctly, and
so I moved a bunch of legacy code and people
were picking me like why is it like this? I'm
like I found it Like that mean.
Speaker 5 (26:57):
No, no, we know we gets blame in the nxmport.
The other thing that was challenging was you know, what
did you do with the old ripers right? Because we
pulled everything. There was one one main client that imported
the other five libraries like super based JS, so we
(27:18):
imported everything into there to retain the gehab bases, the
pull requests, the stars, but all other fiber posters still
had full requests and issues, so I had GitHub is
very nice with that because you can transfer issues and
even if you have a link to an old issue,
it will get you to the new one that is transferred,
(27:39):
so it's good. That is very good from GitHub. So
I transferred all the issues that were I don't know,
one year old or something and the prs I try.
I manually copy pasted transferred the ones that were one
year old, which were not very many. Let's see, I
(28:00):
had to manually do the work which was just copy basting,
and you know, Git commit a mandauthor and put the
original offer there you know, ah, but yeah it was Finally,
it was just managing how GIDA would work out with
all of that.
Speaker 6 (28:19):
Good morning You know, that moment when your coffee hasn't
kicked in yet, but your leg is already blowing up
with Hey did you hear about that new framework that
just dropped? Yeah, me too. That's why I created the
Weekly Death Spur, the newsletter that catches you up on
all the web def chaos while you're still on your
first cup. Oh look, another anger feature was just released,
(28:41):
and what's this typescripts doing something again? Look also through
the poor request and changelot grama. So you don't have
to five minutes with my newsletter on Wednesday morning, and
you'll be the most informed person in your stand up.
That's better the wiki desperate, because your brain deserves a
(29:03):
gentle onboarding to the week's tech matters. Sign up at
Weekly Brew dot Death and get your dose of deaf
news with your morning caffeine. No hype, no clickpick, just
the updates that actually matter. Your Wednesday morning self will
thank you.
Speaker 4 (29:18):
Yeah, that's gonna be quite a task, merging like a
bunch of different reposts together into one massive repo like
I know, I know an access to put out guides
and stuff in the past about how to like migrate
a bunch of Polleys into a single mono, but like
I couldn't imagine migrant especially like a bunch of client
s DKs the size of super Based because of like
how many features you guys have, Like it's crazy how
(29:39):
much stuff superbas does.
Speaker 5 (29:42):
Yeah, it's luckily the clients are a sort of thin
wrappers around the main thing, so it's it's not that
big a code, not still, but still because it's open source,
you have a lot of issues and pull quest from community.
So ah, yeah, but it was. It was a nice
(30:05):
experience and also I got I got down to a
lot of DEVOPSI work, you know, setting up all the
pipelines because imagine six different opposters, six different pipelines bringing
them all into one. I felt it was very rewarding
learning more about DevOps.
Speaker 4 (30:25):
Yeah, I see expert now.
Speaker 3 (30:32):
I had that happen at I worked at a job
where I joined a team that was like twenty people.
It was crazy, and they would open the sprint and
all of the like UI tickets would immediately disappear and
the only thing that would be left to be CI tickets.
And that's actually how I learned how to do any
of that, because I'm like, well, I guess i'm writing
(30:53):
hell today.
Speaker 1 (30:55):
Yeah. I like that word by the way to DEVOPSI.
Speaker 3 (31:02):
It does like like it feels like DevOps feels like
next level stuff. You know, you're like, okay, I know
how to put a button on a screen and put
a click event, but like, yeah, but do you know
how to get it to prod right?
Speaker 5 (31:18):
And I'm also set up some of them. I'm so
proud of these things. I want to set up some
of them. So whenever we cut a release, it triggers
a pull request in the other post, in some other
posty to trigger an update. Oh yeah.
Speaker 4 (31:36):
Once it works, you're like, oh, this is awesome. I
got such a dope, mean head every step.
Speaker 3 (31:43):
Up until try to tell you your family about it,
and they're like, I don't know what you're doing. Just
smile and nod until.
Speaker 1 (31:52):
Job in my back? Is there anything that's Like you mentioned,
you've been there for three months, so in that three months,
you know you'd already worked with super bass before, you
already were familiar with it. But do you feel like
you've learned something in the in the last three months.
That's just really been like, oh my gosh, that is
(32:13):
so cool.
Speaker 5 (32:15):
I just find it really cool that I get to
work on this repostery. Yeah yeah, and I was working
on robinsurs before, but I don't know, I find I
find it very exciting. Yeah. Yes, they're very different products.
(32:36):
But you know when I when I released something and
I know that the next day there's going to be
a million downloads, like oh my god, yeah.
Speaker 3 (32:47):
Yeah, you know. Okay, so we we saw that last
week at uh at NG comp Marco from njr X
was talking about Signal Store and he was he showed
like how many downloads there were last year when he
talked and then this year, and the look on his face,
I'm like, okay, like that's awesome, Like it's it's cool
(33:07):
when people because like you don't always get paid to
do open source work. I mean, like you you do,
but you know, like there are what fifteen yeah, yeah,
like they're not fifteen hundred people getting paid to do
open source work on super based So it's really cool
that they you know, just seeing those downloads happen and
people using your product talking about your product, and yeah,
(33:31):
I never get to do that or is this all
enterprise that was bad? The best I get is somebody
being like, I used that utility you built, it was awesome.
I'm like, oh my god, thank.
Speaker 1 (33:43):
You for doing.
Speaker 4 (33:49):
Classic nice.
Speaker 1 (33:52):
All right.
Speaker 3 (33:53):
So one thing I noticed looking through the repository is
that there is a cursor. Uh, there's a cursor directory.
So what are what sort of AI tools do you
prefer to use with your coding.
Speaker 5 (34:10):
I use Warp a lot and WARP code. I find
it's very easy because it's integrated in the terminal and
the thing I like a little bit over Cloud. I
also use clod code like for maybe it doesn't you know,
But the thing I like a little bit more in
(34:30):
Warp is that I feel that you can more easily
run some commands. But I will change between all the
different tools, to be honest, depending on what I want
to do. If I want to write code, I will
just either use Warp or Cloud. But and I use
(34:51):
cursor sometimes for I like cars or for documenting things.
But I think that maybe I'm not doing something that sophisticated,
but I find the one word less the same. Yeah,
maybe if you're doing more sophisticated work, then it it
shows the difference.
Speaker 3 (35:11):
But yeah, I think like from what I'm gathering, it
feels like some tools are a little better here or
there at certain types of tasks. And there are so
many tools that unless you have some way to crowdsource
the knowledge of what things are better at, it's it's
(35:32):
like I don't have time in the day to be
like I'm going to do this thing. Oh now I'm
going to see if cursor does it better. Now I'm
going to see if Windstorm does it better. Like I
don't have time for that, Like like I'm going to
do the job and try to get it done and
get my pull request raised. And but yeah, so it's
I think that and a lot of the tools are
(35:52):
if they're not the same, they share similar concepts like
Herzer has rules, files, copilot them instructions. But in general,
there's ways to kind of provide more context to your
coding tool, like your AI tool.
Speaker 5 (36:08):
For example, for some of the workflows. If something wouldn't work,
I would ask the integrated kitub compiloting that is on
the gitthub UI because I thought, if something knows about
the Git help, maybe this is what you.
Speaker 3 (36:26):
Would like to think. That would be a thing that
would be good at that job. Yeah, that makes sense exactly.
Speaker 5 (36:33):
But yeah, the reason so in the oppository, Yeah, I
have added caresor rules, I have added cloud instructions, I
have added warp instructions, and I think they're all the same,
just because I figured if someone wants to contribute to
this repository, let the AI tool, they usually know what
to do, right because the tools, the rooms that you
(36:57):
give the tools, I have found that there's super important. First,
they save you time, and they save the two time.
And if they save time, they save credits and they
save money as well. And also if someone is just
randomly contributing, I want them to be as close as
to the contributing guide as possible.
Speaker 3 (37:18):
Yeah, yeah, exactly. It's hard to It's really hard. One
thing that we've talked about on this show a lot
is that when developers use AI to contribute code, like
sometimes we get some like sometimes it's the code is
just never going to get merged. As my nice way
to say that I never merged.
Speaker 1 (37:36):
It should never get merged. Yeah.
Speaker 3 (37:38):
Yeah, And there was there was actually a talk at
ng comp. I'm just going to show up. I got
to go to ng COMPFLUS Michael Lackie gave a good
talk about where we talked about the context window and
the more times you prompt, it's like you're degrading your quality.
(37:59):
Like it seems like the more prompts I give it,
I should be improving the quality. But it starts to
expand that context window. And apparently what happens is it
starts to just sort of forget the first stuff you
told it and then only pay attention to the last stuff,
which then starts to make responses that get weird. So like,
the closer you can get with your initial prompt, the
(38:21):
better off your I think you're gonna the more successful
you're gonna be, is my takeaway from his talk. Maybe
I misinterpreted that, but.
Speaker 5 (38:29):
I watched the talk live to a tangular connect it was.
It really changed the way and I was already using
a itoms. It really changed the way I use AI tools.
I think it's an amazing talk and people should go
watch it. And I gave a talk a month agot
a lot calumet up about AI agents. I quoted Ricael Alout.
(38:52):
I think his talk is amazing.
Speaker 3 (38:54):
Absolutely, I'll see if I can find it. I'm not
going to try to spell as names.
Speaker 1 (39:02):
It starts with an age.
Speaker 3 (39:06):
I was super close. I was so close.
Speaker 1 (39:09):
Yeah, I'm kind of curious Katterina Wall, she's trying to
find that. I've been working a lot with just different
security efforts at my company, and so it's kind of
fresh on my mind. But I think it really should
be in this age of AI, like security is something
we need to really be amping up and really being
(39:29):
conscientious of. So what are some of the best practices
that you would suggest when using super base for things
like authentication and security in our applications?
Speaker 5 (39:44):
A row level of security the first thing you should
you should work on and enable and use. I think
it's the most important thing. Like if you ever like
the when I you so first, I was using supa base,
I was using Firebase. I had watched all the videos
(40:06):
and tutorists, I could find them security rules. So coming
to super based rules work in a different way because
now we're talking about the sequel. They're the is. But
it's the first thing that you should be aware of
and set up correctly.
Speaker 1 (40:23):
Also, I have to say, like, one thing I've always
admired about you is that you have like a good
depth of understanding of things and it's always really like,
you know, I feel like I could ask you anything
and you'd have like a good answer for it. But what, like,
how how do you go about learning new concepts, like
(40:44):
if you've had a new tool or just whatever skill
that you needed to learn, Like what's kind of your
learning process?
Speaker 5 (40:52):
I try things out, so the I tried to build something,
and I want to see it work and try it
out first hands on, and then I try to read
about it as much as I can. I tend to
read less in the past year, I think, unfortunately, because
(41:13):
I think, okay, I'll just rely on ChiPT explaining it
to me. But if it's something important, I will try
to find like a blog post or something or a
video to watch or read about it. For example, right
now I'm trying to see I'm trying to read more
(41:34):
on release mechanisms and release methods, let's say, different ways
that companies choose to go about the release cycles. My
first instance was to not to ask GBT, but I thought, no,
this is far too important, and I try to find
(41:55):
like blog posts and like official documentation from companies like
Google or Microsoft and how they do it. And they
do have documentation how they do it. Microsoft has a
lot of resources, for example on how they manage releases.
I'm not going to follow their example because I didn't
like some things. But still I read this, and then
(42:17):
there is Google that has this other. But yeah, I
try to find like official things and read and try
to understand like that.
Speaker 1 (42:26):
Yeah, but hands on first, so testing it out, playing
with it, then going and reading the docs.
Speaker 5 (42:33):
Yeah. So for example, now with the releases, I'm going
to create a test repository and try out the different
release types, like the release from brush trunk based release,
you know.
Speaker 3 (42:45):
M Yeah, I think that, like for me, it's always
hands on, has always been the best way, and just
not being afraid to like, Okay, I don't understand this.
Maybe if I actually open the source code, I can
figure it out, but I it more out of Sometimes
people can't describe it to me. It doesn't matter what
(43:06):
words you use. It's going to go right in this
ear and write out that one. And so I have
to like actually open source code and try to understand
what's happening that way too. I do want to report back.
I didn't find Michael's talk online, but he will be
in Tel Aviv in November at Angular Tel Aviv, So
(43:27):
if you are in that area and can get to there,
November twelfth is that conference, and then of course I
know Angular and gi Komp will be releasing the videos eventually.
They like to make you wait, that's your punishment for
not buying it.
Speaker 1 (43:41):
Well, but you can subscribe to their newsletter and they oh, okay, yeah,
updates on that.
Speaker 3 (43:46):
So yeah, yeah, there you go. Definitely, definitely, but yeah,
I think that that's one thing that sets apart people
that are successful as engineers. And this goes right back
to talking about job hunting, Like, I'm more in find
if I have two people and one is maybe has
less experience, but they're more they have better tools for
(44:07):
teaching themselves how to learn something, I would be more
inclined to want that person on my team than somebody
who maybe has a lot of experience but doesn't know
how to like actually dig in and digest a problem.
So so yeah, like the fact that you're like, oh yeah,
like the fact that you're like, I'm going to I'm sorry,
(44:31):
we're just talking over each other. I think we're just
agreeing with each.
Speaker 4 (44:34):
Other, We're trying to say the same thing.
Speaker 3 (44:36):
We're just finishing each other's sentences like we always do.
Speaker 5 (44:39):
I don't.
Speaker 4 (44:40):
That's finishing more than like saying the same sentence.
Speaker 3 (44:44):
We're trying to be identical twins. It's not working. I
have no beard, I'm shorter than Jay.
Speaker 4 (44:50):
There's a lot of things not identical about you and Aila.
Speaker 3 (44:53):
Not a lot of things. But yeah, alright, So.
Speaker 1 (45:02):
Does anybody have any kind of final questions? I know
we're kind of wrapping up, or Katerina likewise, do you
have any final things that you'd like to share about
super Base your experience with it?
Speaker 5 (45:15):
No, just say go use Superbase because you'll be amazed
at how how smooth it makes it to have a
full working application right out of the box. Almost I
will say, I'm really amazed.
Speaker 3 (45:30):
Is there for somebody that just wants to try it out?
There's a I assume there's a free tier.
Speaker 5 (45:36):
Yeah, yeah, there is. There is a free tier.
Speaker 3 (45:39):
Nice. And then you linked in the show notes are
getting started tutorial, which is great. You said both dot
New works with it.
Speaker 1 (45:48):
Yeah, unlovable nice and I.
Speaker 5 (45:51):
Think other are no colde platforms, but these two definitely
too nice. Nice.
Speaker 3 (45:56):
So you can go in and do some vibe coding,
spin yourselves up as scam website in just a weekend.
Speaker 5 (46:10):
No, but really you can kick start your business with it.
You're full of jitimate, scale uply normal business with it.
Speaker 3 (46:18):
Absolutely, And you know, I think that's the cool thing
about modern web development is that, you know, when I started,
I had this little crafting business. It was like the
early two thousands, and it was not easy to set
up e commerce, right, Like, there is no way I
was going to like I could have I could make
a website that could show off my products, but I
(46:40):
did not have the skills to integrate any sort of
payment system or anything that was like secure enough that
I could you know, do that to people. So it's
it's cool to have these resources like super Base out
there to make it so that you don't need to
(47:01):
have you know, decades of experience and you know, a
whole team working with you can.
Speaker 5 (47:08):
Get Definitely that's amazing. And you know a lot of
people may say like that small founders that have this
small app that they're being super bases. The CEO of
the company, you know, yeah.
Speaker 1 (47:25):
I was just going to say, I've been working on
this little side project and it is like we're building, uh,
basically a social media app, and there was the people
coming together. We're all volunteers, we're all just kind of
doing this in our free time, but we all come
with different backgrounds and experiences and you know, some I
(47:47):
don't know, Like long story short, It's just made it
so nice because when we made the decision to use
super Base, it just took out a lot of that
other decision making, you know, and it saves so much time.
So for that we were really grateful. And and then,
like we've been saying over and over, it just helped
us to kind of hit the ground running, like you know,
everything was right there. It just it was so nice
(48:09):
just to go.
Speaker 4 (48:11):
It's made a lot of things that used to be
really complicated really simple.
Speaker 1 (48:15):
Yeah.
Speaker 3 (48:17):
Absolutely, CTOs are going to be a thing of the past.
Speaker 4 (48:20):
J Oh definitely. Day versus super Bass, I don't want
to I don't want to be super bass that I
do have no desire to pit myself.
Speaker 1 (48:32):
Against well, Katerina, If if someone would like to follow
you or connect with you, what is the best way
to do that on social media?
Speaker 5 (48:44):
I have Twitter, I have Blue Sky. It's uh at
cyber City, so it's at ps Y b E R
C I.
Speaker 1 (48:54):
T Y nice and definitely when you can. I know
maybe the recordings aren't AVAI yet, but from Angular Connect
check out her her presentation and yeah, keep an eye
on Katerina. She's always up to some pretty amazing things.
Thank you, thank you so much, and thank you to
(49:15):
Laura and Jay. Love being on the show with both
of you. But yeah, everybody, go back listen to some
of our previous episodes. I can guarantee you Katerina has
been on.
Speaker 3 (49:30):
Specifically, remember you being on with your NX, the work
you did NX with. Oh shoot, now my brain stopped working.
Speaker 4 (49:39):
The AI chat or oh no, story book.
Speaker 5 (49:43):
There we go.
Speaker 3 (49:43):
I'm like, I almost sid play right, but I'm like, no,
that's not right, like that, it's like a it's a
it's a storybook. I just revealed to the audience how
my brain actually wore.
Speaker 1 (50:00):
Uh funny. But yes, definitely go check out her previous
episodes and we'd love to have you listen in the
future book See everybody later.
Speaker 7 (50:09):
By Hey, this is Prestol. I'm one of the NGI
Champions writers. In our daily battle to crush out code,
we run into problems and sometimes those problems aren't easily solved.
Ngiecomp broadcasts articles and tutorials from angie champions like myself
that help make other developers' lives just a little bit easier.
To access these articles, visit medium, dot com, forward slash ngcomp.
Speaker 2 (50:33):
Thank you for listening to the Angular Plus Show in
Chiecomff podcast. We'd like to thank our sponsors, the ngiecomf
organizers Joe Eames and Aaron Frost, our producer Gene Bourne,
and our podcast editor and engineer Patrick Kay's. You can
find him at spoonful Ofmedia dot com.
M hm.
Speaker 2 (00:08):
Welcome to the Angular plus Show. We're app developers of
all kinds share their insights and experiences. Let's get started.
Speaker 1 (00:21):
Hello everybody, and welcome to the Angular Plus Show. My
name is Brooke and I'll be hosting today with two
very exceptional human beings. We have Laura.
Speaker 3 (00:31):
Newsom, Hello, how's it going?
Speaker 1 (00:35):
And mister j Bell here again.
Speaker 4 (00:38):
I made it this time. Somebody else made it this time.
I'm also here.
Speaker 3 (00:47):
It's supposed to be Yon, but he's a bad, bad host.
Speaker 4 (00:56):
Under the bus.
Speaker 3 (00:57):
He goes under the bus.
Speaker 1 (01:01):
But to make up for y'all not being here, we
have like we're really pumped to be joined by someone
who has made really quite a big impact on the
Angular ecosystem and I think the developer community in general.
Welcome to the show.
Speaker 5 (01:15):
Katerina, Hello, it's very nice to be here.
Speaker 1 (01:20):
I'm going to have you pronounce your last name for me.
Speaker 3 (01:27):
Yep, that would not come out of my mouth.
Speaker 4 (01:29):
That I feel like we do this every single time.
Speaker 1 (01:34):
I know's so old. We're just we're Americans and we
really suck it saying names. We're North Americans who suck
it name pronunciation.
Speaker 4 (01:50):
There you go.
Speaker 3 (01:54):
I think that like listeners will probably realize the more
they listen the the that there are names like we
tend to go with first name. Yeah, welcome Katerina to
the show. Say your full name the way that people
should say it.
Speaker 1 (02:12):
I figured this way. At least the next person will
know how to say it. So there you go. I
did you all a favor, yes, but but yeah, welcome
to the show. Katerina is so excited to have you here.
You're actually going to be talking all about super bass,
so we're excited to learn more about that. But just
(02:32):
kind of like the ins and outs why you'd want
to use super Bass, how it can help make your
make building applications faster and easier. That said, though, we
also need to say congratulations because you've recently just started
working with super Bass, So congrats on the new job.
How's that going so far?
Speaker 5 (02:52):
Thank you? It's quite amazing. I've been there three months now, okay,
and it feels like much longer because I don't know,
I feel right at home. To be honest, I really
like it is.
Speaker 3 (03:06):
Is the super based team? Are they because you're located
in Greece? Correct? Is is your team also in Europe?
Are they all over the globe.
Speaker 5 (03:18):
It's a heavily distributed team. Yes, nice. Yeah, we have
people from all over the world, so it's nice.
Speaker 3 (03:25):
Nice.
Speaker 1 (03:26):
So Catherine, I have a question for you too, because
you got a job, and it is not an easy
market right now to get a job. So do you
have any suggestions or tips for listeners on if they're looking.
What are some things you felt like maybe you did
that helped get you.
Speaker 5 (03:44):
Oh, I have a lot of tips. Yes. Actually the
thing is my husband right now is is job hunting,
so I have tried to tell him some tips. But
then also it's not nice to always tips to your
to your spouse, So I will give you all the
(04:04):
tips here and.
Speaker 1 (04:10):
I love it.
Speaker 5 (04:12):
Yeah, yeah, so yeah, I found the supervised job in
the normal way, like I applied. I didn't know anyone
who worked there, so I applied and went through the
typical hiring process of having like four or five interviews
I don't know how many, and getting the offer, accepted
(04:33):
the offers, And I had actually applied in the past before,
and I had I hadn't, I hadn't been even to
an interview, soight was the second time I applied that
I got the job. But usually the way I I
would find a job in the past, or I would
(04:55):
see people finding jobs in the past, is through personal connections,
which I think is a very strong asset to have
personal connections because it's a way to get at least
your resume read. You know, it's the first step because
because a lot of people are looking for jobs, you
(05:16):
may have like a stellar resume, but it may never
even get to the red stage. I don't know. So
I wouldn't get disappointed if I wouldn't listen here back
from a job while job harding. It is the most
important thing I have in mind, right, and there's always
(05:36):
going to be someone who is better than me out there,
so you know, maybe not maybe I'm the best, but.
Speaker 3 (05:43):
Well, I think that's just it though, Like you never
really know exactly what kind of you know, Like I've
seen people who have not gotten jobs that they would
be very well qualified for. And it doesn't mean that
you're not a good candidate and that you don't deserve
a job. Just means that what that company is looking
for right now, they had somebody that was a better
(06:06):
fit for whatever reason.
Speaker 5 (06:07):
Oh yeah, it could.
Speaker 3 (06:08):
Be a dumb reason like nepotism or promiism, or it
could be you know, something unexpected, like oh, we actually
wanted somebody with a little more experience in this area
than what you have.
Speaker 5 (06:21):
Yeah. For example, the job I had applied that super
Base was for client library engineer, which I am not.
I'm working on the SDKA team, but they needed someone
to oversee the JavaScript and the Python libraries. Right. I
told them I have no experience with pithon, Like I
(06:43):
have written like a flask API at some point on
some server, but that's it. But they were like, Okay,
you're very You're like a very experienced dipscript developer. You
have so much experience with open source, so okay, you're
a fit. We don't care about Python, you know. So
even that, I think tell something. Also. One other thing
(07:06):
that I think in my case helped a lot is
the online portfolio. Right if you have if you have GitHub,
and you have even some of your code on GitHub,
the recruiter or the HR person, the hiring manager can
instantly go on your GitHub account and see that. I
(07:28):
don't think they're necessarily going to see the code you're right,
but they're just going to see if you're slope you're not,
or if you're organized or not, Like if you have
nice reposors with the read mes and everything and everything
is tidy. They're not going to go through life by
like your JavaScript code, but they are going to see
if you're organized or not, or they're going to see
(07:50):
if you have some PR comments or your PR reviews
or whatever. So I think this online presence code presence
also helps. The final thing that I think helped in
my case is my online presence in general, Like at
the conference, is the meetups, the this thing that I'm
doing here right now with you all. But I don't
(08:12):
think this is necessary obviously, so but.
Speaker 3 (08:16):
What some companies care more than others to like it
kind of depends on what.
Speaker 5 (08:24):
But I think what does play a big part is
the portfolio, like the.
Speaker 3 (08:29):
GIT Absolutely it's it's hard when people I get pinged
a lot by people that are looking for jobs at Cisco,
and I want to help people get jobs, but I'm like,
I don't actually know you, I don't know your code,
like I don't know that. I really want to put
my name on a referral that says like, yeah, I
refer so, and so I don't know them at all.
I've never met them. I can't see their code like.
(08:51):
It makes it a lot harder to feel comfortable doing
that because it is also like the people that you ask,
it's their reputation on the line, So it's a lot
easier to say, hey, can you refer me for this position?
Here's my repository. Go you know, if you can, like,
this is how I write code, this is what I've
worked on. I think it's also important to note that,
(09:13):
like I know, for a lot of people coming out
of school, they'll have like school projects online too. A
lot of companies are looking for something beyond that. They
don't want to just see what you did for class work.
They want to see like, what things are you what
problems are you trying to solve? What things are you
interested in? And yeah, what have you worked on as
(09:35):
opposed to you know, what did you get assigned to
do in college?
Speaker 1 (09:38):
So so, okay, question, then Katerina, had you I'm assuming
the answer, but I could be wrong. So had you
put something in your portfolio where you had used super
base and do you feel like, you know, like I
don't know, how did you use that experience to help
(09:59):
you get the job?
Speaker 5 (10:00):
Then oh yeah, totally, Aer had things in my portfolio
that used superbased, because I think I had created, for example,
an application for this event that we had with an
X in April. I had put together just like a
conference application that checked people in and use suba based.
(10:21):
And also I had built the NX AI chat bot,
you know, the AI docs her assistant with superbas and
the super base example that they had, So this definitely
played the role.
Speaker 1 (10:40):
Yeah, okay, well then that said that was more for
listeners who've maybe never used superbase. Can you tell us
more about what it is and why why a developer
would even want to care?
Speaker 5 (10:56):
Yeah, so stranger enough, I have not practiced super based peach.
Speaker 3 (11:01):
I practice my.
Speaker 5 (11:03):
NX pach when I was working at an X. But yeah,
I'm just going to read the pitch from the website,
but then I'm going to tell more about my experience.
So it's a postgress development platform. It gives you a
postgress database, gives you authentication, you can create an API.
(11:28):
It gives you its functions so you can do micro
services and stuff, real time subscriptions, storage, and also vector embeddings,
which I think super based really made it easier for
people to build dogs assistance because it provided so easily.
These vector are beddings database and the vector search with
(11:48):
pitch vector and everything. So yeah, it started. I think
the original pitch back in the day. I don't know
if we use it still. I don't think we do.
Was the fire based alternative open source, the fire based
open source alternative. It's beyond that now. But if you
use fire base you would be familiar with with some
(12:12):
of the things that super based offers. But yeah, I
have used all of the features I think we have.
I think one of the favorite features that we have
is the real time thing that we have some nice
demos as well, like the real time cursor tracking, the
(12:32):
broadcast messages, like you can build a chat up very easily.
Let me think, I did want to mention something specific.
I can't think right now.
Speaker 3 (12:46):
It'll come to you.
Speaker 5 (12:47):
Yeah, yeah, yeah, it will, it will. Oh yeah, And
I wanted to say no, I wanted to say that. Yeah.
If you're using no code day, itols like both or lovable.
Let's say they have super based integrations that you can
just connect your data, connect the database instantly, so while
(13:11):
you're building a website, you can just easily or rather
the AI is building a website, AI can instantly connect
the database as well. Back there was actually explaining this
to my parents today because my parents are old people.
They're eighty, they're eighty years old, so they see technology
(13:32):
as magic. Obviously some things they see it as magic.
And my father today was telling me that he read
on this ad that there was this application that you
could do this and that, and they told him, okay,
that this is a scam. And he's told, how is
it possible? It's a scum. It took so much work
to be told no, no, no, that it didn't take
(13:53):
much work today ten minutes, one prompt, ten minutes and
against get a full application with a database and stripe
integration for people to pay you. It's not much. This
person spent ten minutes and maybe ten dollars and they
have a full working scam for you, ready.
Speaker 3 (14:14):
Right, yeah, yeah, And it's hard. It's I mean, it's
hard even as like a you know, younger person that
grew up with technology to always recognize scams.
Speaker 4 (14:27):
So yeah, the tools are taking them so much easier now.
Speaker 1 (14:30):
Right, Yeah, yeah, a generation.
Speaker 4 (14:33):
Ease of databases, ease of payment payment processors, like everything's
so easy for depths now that like it's way easier
to automate this like quote unquote real looking thing.
Speaker 3 (14:44):
Yeah exactly. So then you just ask yourself like, does
this seem does this seem like too good a deal?
Speaker 4 (14:51):
Yeah exactly.
Speaker 5 (14:52):
Yeah, yeah yeah yeah, nobody's giving them my money anyway.
Speaker 1 (14:56):
Yeah.
Speaker 5 (14:56):
I didn't want to like this whole thing the AI
called generation with scums, because that's not the case. Obviously.
The good thing is that it's making lives a lot
easier for a lot of people, either to build a
full work in application, either to have a demo, either
to go full production ready. So yeah, just making things
(15:17):
smoother and easier.
Speaker 3 (15:19):
So who who do you see as like, who are
the biggest users of superbase obvious? Is it people with
small businesses? Is it enterprise level or is it the
whole spectrum?
Speaker 5 (15:34):
I think it's the whole spectrum.
Speaker 3 (15:37):
Yeah, I mean it says skilled millions building a weekend
scale to millions, which implies it's true.
Speaker 5 (15:44):
It's true, it does, it does scale two millions, and
it is very stable and as I see in our website,
if you go on your website, you can see a
lot of a bigger customers mentioned there. So yeah, it's
it's definitely uh it's definitely also built for enterprise and
(16:06):
can support enterprise and it's big scale businesses.
Speaker 1 (16:12):
You do you suggest like you know, like I guess
I'm trying to say that what's the learning curve withis?
So you know, what what would you suggest for a
developer to have for any kind of background knowledge or
you know, is it pretty easy just to pick right
up and go with?
Speaker 5 (16:29):
Good question? I think, like like a lot of tools,
it's the more sophisticate you, the more sophisticate that you
want to get, the learning becomes a steeper let's say,
but I can I can explain a little bit more
what I mean about this generic thing. You can start
(16:50):
right off and not know anything like I had, Like
I had not worked when I first used supervised, I
had not worked with with Sequel a lot, and I
didn't have a lot of database experience when I first
started using super Base let's say two or three years ago,
Like I have never really needed to use seql for
(17:11):
production other than you know, side projects or school projects.
Like we said, you don't really need it to get
started because you can set things up very easily. And
now with the super based MCP, and also we have
some ai as systems. You can just even set up
a row level security more easily, or we give you
(17:32):
reduated sequel queries that you can run to create tables
for example, or you can create tables from the UI
even But if you want to go more sophisticated SUA
basis postwards, right, it's a it's a big relational database.
You can use SEQL queries with it, and it's you
(17:55):
can get as complex as you want. I think one
of the greatest challenges for me when we're in with
Superbase was understanding how I can work with role level
security and how I can use your level security to
use it for filtering as well, and you know, go
dip into sequel and postcar stuff. But other than that,
(18:17):
I would say, it's it's just your service that you
can use.
Speaker 4 (18:25):
And yeah, I remember roll level security being one of
the like I've never had to use roll level security before. So,
like when I was looking to put the super Base in,
like the postgersenal, I was like, okay, so how is
this secure for I don't understand how we're not leaking
data all over the place.
Speaker 5 (18:45):
I know and I know that we're now working to
make this easier for people to set up. I think
we already have some sort of assistance to set it
up more easily. From the dashboard, I think.
Speaker 3 (19:00):
Nice, nice, And it looks like there's a they support
a lot of migration schematics as well.
Speaker 1 (19:06):
Yeah, so that's that's cool.
Speaker 3 (19:08):
Because a lot of people, you know, I mean, I've
worked at plenty of just small companies that own their
servers and so they everything's on prem but at some
point they have to make the decision like do we
want to like where do we want those things to live?
You know, do we want to keep buying servers? Do
we want to move to the cloud. So tools to
(19:31):
make that easy, make that decision easier, that's true.
Speaker 1 (19:37):
Are there any examples of, like an application with super Base,
something that you think is a you know, a good
a good demonstration of what it can do for an application?
Speaker 5 (19:53):
I would say the super based website itself, So oh yeah,
I will say that the super Base website itself and
the super based dashboard.
Speaker 1 (20:05):
Okay, so then I'll take that a little bit, a
little bit further. So maybe could you walk us through
like a simple use case where like how someone might
add Superbase authentication to an Angular project oh.
Speaker 5 (20:19):
Yeah, definitely. I can tell you, for example, I build
a devil for the Angular Connect, and I can tell
you for example what I build. I wanted to build
a multiplayer game, right, so I just add that. I
think I added either Google or GitHub authentication through Superbase.
(20:42):
So you get your WT token and everything through the
authentication service of Superbase, and then you authenticate your user,
and then I would have then you can have your
pretty standard your table for your users, your table for
your user data. For example, for the demo that I
built for the interconnect website, I wanted to have like
(21:07):
a ign of emojis, let's say, and people would top
on emojis and whoever collects the most emojis winds, right.
But I needed that to be synchronized through all the
different devices so that it's fair. So I used the
real time, the real time subscriptions of superbased offers for that.
(21:31):
So I was streaming the X and y location on
the browser across through super based different devices, so that
everyone saw the same emojis on the right locations, and
whenever someone would top one, I would capture that top
and I would broadcast a message to Superbase that said, okay,
(21:51):
this one is claimed and in the table with emojis,
I would add that this one is claimed and it's
claimed but by that user ID. Right, So this one,
for example, would be like building a multiplayer game.
Speaker 3 (22:09):
Let's say, nice, I do have to call out on
the website it says use super Base with any framework
and there is no Angular logo there.
Speaker 5 (22:23):
Fo let me see. I'm pretty Oh yeah, that's true.
Speaker 3 (22:31):
I mean they got.
Speaker 5 (22:34):
Yeah, but we do have some Angular demos and I
know that someone came up to me an Angular connect
saying that they have submitted a pr H which update
the Angular dogs. I should look at that pr and
(22:55):
try to get it mercy, Yes.
Speaker 3 (22:59):
Get our a little logo on there.
Speaker 5 (23:01):
Yeah, I'm looking. Oh there it is. Okay, I found it.
If you scroll deep down. I'm going to paste it
in the chat here. Build a user management up with Angeler.
Speaker 4 (23:16):
Perfect.
Speaker 5 (23:18):
Yeah.
Speaker 1 (23:19):
One thing I'm always curious about too, is like, I mean,
obviously superbas is already solved or is helping developers to
solve a lot of problems, right, But is there something
and maybe this is too top secret, I don't know,
but is there something that super Base is kind of
stepping into? Is there a new problem that maybe it's
(23:39):
not already solving that you guys are going to start
trying to help.
Speaker 5 (23:44):
I don't know, No, I literally don't know.
Speaker 3 (23:49):
No, that's totally that's totally fair because what like, as
you were, so, what what exactly do you do at
super Base?
Speaker 5 (23:57):
So I we have an STKA eighteen and we have
we used to call it the client libraries, Like we
have client libraries for javascripts. I think they're all on
GitHub JavaScript Cattling, Python Swift, so I oversee the JavaScript sdcase.
(24:19):
So the JavaScript s the case are sdcase for all
of the features that superbase has, like the functions, the
real time, the storage, the post quest and the authentication.
And when I joined, all these used to be six
different repositories. Guess what they are now?
Speaker 1 (24:46):
I wonder where that came from.
Speaker 3 (24:49):
If only they had someone that had some experience with
Mono exactly. Now, was it a Mono repo before you
joined or was that something that you were able to
help implement.
Speaker 5 (25:03):
Yeah, I was able to help implement that. It was
one of my first tasks when I joined, and it
took me about a month to get everything worned up correctly.
And now it's been live for about three weeks and
we're happy.
Speaker 3 (25:24):
Yeah, yeah, that's it is hard, like trying like it's
one thing to start something new with mono repo, but
it's another thing to try to pull things back into
a mono repo just to get everything.
Speaker 5 (25:39):
Yeah, it was, so there were some challenges. This is
all open source and you can see the gecub. You
can see the whole process on GitHub, step by step
how it happened. So one of the child the first
challenges was that every package was a different version. So
(25:59):
first we have to choose okay, we'll take the largest
latest version and just bump it a minor. And then
the other thing was when I pulled everything, I used
NX import to bring everything into the NX monory, but
which retains history, which was nice because I wanted it
(26:22):
wasn't like I needed to think, but I wanted to
retain history, which was done in a very good way
that I like because it's nice to be able to
get blame yourself and other people.
Speaker 3 (26:36):
The migration. It's literally you are get blame on literally everything.
Speaker 5 (26:40):
Which yeah, exactly.
Speaker 3 (26:42):
I had that happen when we I didn't know how
to move things in the mono repoke collectory correctly, and
so I moved a bunch of legacy code and people
were picking me like why is it like this? I'm
like I found it Like that mean.
Speaker 5 (26:57):
No, no, we know we gets blame in the nxmport.
The other thing that was challenging was you know, what
did you do with the old ripers right? Because we
pulled everything. There was one one main client that imported
the other five libraries like super based JS, so we
(27:18):
imported everything into there to retain the gehab bases, the
pull requests, the stars, but all other fiber posters still
had full requests and issues, so I had GitHub is
very nice with that because you can transfer issues and
even if you have a link to an old issue,
it will get you to the new one that is transferred,
(27:39):
so it's good. That is very good from GitHub. So
I transferred all the issues that were I don't know,
one year old or something and the prs I try.
I manually copy pasted transferred the ones that were one
year old, which were not very many. Let's see, I
(28:00):
had to manually do the work which was just copy basting,
and you know, Git commit a mandauthor and put the
original offer there you know, ah, but yeah it was Finally,
it was just managing how GIDA would work out with
all of that.
Speaker 6 (28:19):
Good morning You know, that moment when your coffee hasn't
kicked in yet, but your leg is already blowing up
with Hey did you hear about that new framework that
just dropped? Yeah, me too. That's why I created the
Weekly Death Spur, the newsletter that catches you up on
all the web def chaos while you're still on your
first cup. Oh look, another anger feature was just released,
(28:41):
and what's this typescripts doing something again? Look also through
the poor request and changelot grama. So you don't have
to five minutes with my newsletter on Wednesday morning, and
you'll be the most informed person in your stand up.
That's better the wiki desperate, because your brain deserves a
(29:03):
gentle onboarding to the week's tech matters. Sign up at
Weekly Brew dot Death and get your dose of deaf
news with your morning caffeine. No hype, no clickpick, just
the updates that actually matter. Your Wednesday morning self will
thank you.
Speaker 4 (29:18):
Yeah, that's gonna be quite a task, merging like a
bunch of different reposts together into one massive repo like
I know, I know an access to put out guides
and stuff in the past about how to like migrate
a bunch of Polleys into a single mono, but like
I couldn't imagine migrant especially like a bunch of client
s DKs the size of super Based because of like
how many features you guys have, Like it's crazy how
(29:39):
much stuff superbas does.
Speaker 5 (29:42):
Yeah, it's luckily the clients are a sort of thin
wrappers around the main thing, so it's it's not that
big a code, not still, but still because it's open source,
you have a lot of issues and pull quest from community.
So ah, yeah, but it was. It was a nice
(30:05):
experience and also I got I got down to a
lot of DEVOPSI work, you know, setting up all the
pipelines because imagine six different opposters, six different pipelines bringing
them all into one. I felt it was very rewarding
learning more about DevOps.
Speaker 4 (30:25):
Yeah, I see expert now.
Speaker 3 (30:32):
I had that happen at I worked at a job
where I joined a team that was like twenty people.
It was crazy, and they would open the sprint and
all of the like UI tickets would immediately disappear and
the only thing that would be left to be CI tickets.
And that's actually how I learned how to do any
of that, because I'm like, well, I guess i'm writing
(30:53):
hell today.
Speaker 1 (30:55):
Yeah. I like that word by the way to DEVOPSI.
Speaker 3 (31:02):
It does like like it feels like DevOps feels like
next level stuff. You know, you're like, okay, I know
how to put a button on a screen and put
a click event, but like, yeah, but do you know
how to get it to prod right?
Speaker 5 (31:18):
And I'm also set up some of them. I'm so
proud of these things. I want to set up some
of them. So whenever we cut a release, it triggers
a pull request in the other post, in some other
posty to trigger an update. Oh yeah.
Speaker 4 (31:36):
Once it works, you're like, oh, this is awesome. I
got such a dope, mean head every step.
Speaker 3 (31:43):
Up until try to tell you your family about it,
and they're like, I don't know what you're doing. Just
smile and nod until.
Speaker 1 (31:52):
Job in my back? Is there anything that's Like you mentioned,
you've been there for three months, so in that three months,
you know you'd already worked with super bass before, you
already were familiar with it. But do you feel like
you've learned something in the in the last three months.
That's just really been like, oh my gosh, that is
(32:13):
so cool.
Speaker 5 (32:15):
I just find it really cool that I get to
work on this repostery. Yeah yeah, and I was working
on robinsurs before, but I don't know, I find I
find it very exciting. Yeah. Yes, they're very different products.
(32:36):
But you know when I when I released something and
I know that the next day there's going to be
a million downloads, like oh my god, yeah.
Speaker 3 (32:47):
Yeah, you know. Okay, so we we saw that last
week at uh at NG comp Marco from njr X
was talking about Signal Store and he was he showed
like how many downloads there were last year when he
talked and then this year, and the look on his face,
I'm like, okay, like that's awesome, Like it's it's cool
(33:07):
when people because like you don't always get paid to
do open source work. I mean, like you you do,
but you know, like there are what fifteen yeah, yeah,
like they're not fifteen hundred people getting paid to do
open source work on super based So it's really cool
that they you know, just seeing those downloads happen and
people using your product talking about your product, and yeah,
(33:31):
I never get to do that or is this all
enterprise that was bad? The best I get is somebody
being like, I used that utility you built, it was awesome.
I'm like, oh my god, thank.
Speaker 1 (33:43):
You for doing.
Speaker 4 (33:49):
Classic nice.
Speaker 1 (33:52):
All right.
Speaker 3 (33:53):
So one thing I noticed looking through the repository is
that there is a cursor. Uh, there's a cursor directory.
So what are what sort of AI tools do you
prefer to use with your coding.
Speaker 5 (34:10):
I use Warp a lot and WARP code. I find
it's very easy because it's integrated in the terminal and
the thing I like a little bit over Cloud. I
also use clod code like for maybe it doesn't you know,
But the thing I like a little bit more in
(34:30):
Warp is that I feel that you can more easily
run some commands. But I will change between all the
different tools, to be honest, depending on what I want
to do. If I want to write code, I will
just either use Warp or Cloud. But and I use
(34:51):
cursor sometimes for I like cars or for documenting things.
But I think that maybe I'm not doing something that sophisticated,
but I find the one word less the same. Yeah,
maybe if you're doing more sophisticated work, then it it
shows the difference.
Speaker 3 (35:11):
But yeah, I think like from what I'm gathering, it
feels like some tools are a little better here or
there at certain types of tasks. And there are so
many tools that unless you have some way to crowdsource
the knowledge of what things are better at, it's it's
(35:32):
like I don't have time in the day to be
like I'm going to do this thing. Oh now I'm
going to see if cursor does it better. Now I'm
going to see if Windstorm does it better. Like I
don't have time for that, Like like I'm going to
do the job and try to get it done and
get my pull request raised. And but yeah, so it's
I think that and a lot of the tools are
(35:52):
if they're not the same, they share similar concepts like
Herzer has rules, files, copilot them instructions. But in general,
there's ways to kind of provide more context to your
coding tool, like your AI tool.
Speaker 5 (36:08):
For example, for some of the workflows. If something wouldn't work,
I would ask the integrated kitub compiloting that is on
the gitthub UI because I thought, if something knows about
the Git help, maybe this is what you.
Speaker 3 (36:26):
Would like to think. That would be a thing that
would be good at that job. Yeah, that makes sense exactly.
Speaker 5 (36:33):
But yeah, the reason so in the oppository, Yeah, I
have added caresor rules, I have added cloud instructions, I
have added warp instructions, and I think they're all the same,
just because I figured if someone wants to contribute to
this repository, let the AI tool, they usually know what
to do, right because the tools, the rooms that you
(36:57):
give the tools, I have found that there's super important. First,
they save you time, and they save the two time.
And if they save time, they save credits and they
save money as well. And also if someone is just
randomly contributing, I want them to be as close as
to the contributing guide as possible.
Speaker 3 (37:18):
Yeah, yeah, exactly. It's hard to It's really hard. One
thing that we've talked about on this show a lot
is that when developers use AI to contribute code, like
sometimes we get some like sometimes it's the code is
just never going to get merged. As my nice way
to say that I never merged.
Speaker 1 (37:36):
It should never get merged. Yeah.
Speaker 3 (37:38):
Yeah, And there was there was actually a talk at
ng comp. I'm just going to show up. I got
to go to ng COMPFLUS Michael Lackie gave a good
talk about where we talked about the context window and
the more times you prompt, it's like you're degrading your quality.
(37:59):
Like it seems like the more prompts I give it,
I should be improving the quality. But it starts to
expand that context window. And apparently what happens is it
starts to just sort of forget the first stuff you
told it and then only pay attention to the last stuff,
which then starts to make responses that get weird. So like,
the closer you can get with your initial prompt, the
(38:21):
better off your I think you're gonna the more successful
you're gonna be, is my takeaway from his talk. Maybe
I misinterpreted that, but.
Speaker 5 (38:29):
I watched the talk live to a tangular connect it was.
It really changed the way and I was already using
a itoms. It really changed the way I use AI tools.
I think it's an amazing talk and people should go
watch it. And I gave a talk a month agot
a lot calumet up about AI agents. I quoted Ricael Alout.
(38:52):
I think his talk is amazing.
Speaker 3 (38:54):
Absolutely, I'll see if I can find it. I'm not
going to try to spell as names.
Speaker 1 (39:02):
It starts with an age.
Speaker 3 (39:06):
I was super close. I was so close.
Speaker 1 (39:09):
Yeah, I'm kind of curious Katterina Wall, she's trying to
find that. I've been working a lot with just different
security efforts at my company, and so it's kind of
fresh on my mind. But I think it really should
be in this age of AI, like security is something
we need to really be amping up and really being
(39:29):
conscientious of. So what are some of the best practices
that you would suggest when using super base for things
like authentication and security in our applications?
Speaker 5 (39:44):
A row level of security the first thing you should
you should work on and enable and use. I think
it's the most important thing. Like if you ever like
the when I you so first, I was using supa base,
I was using Firebase. I had watched all the videos
(40:06):
and tutorists, I could find them security rules. So coming
to super based rules work in a different way because
now we're talking about the sequel. They're the is. But
it's the first thing that you should be aware of
and set up correctly.
Speaker 1 (40:23):
Also, I have to say, like, one thing I've always
admired about you is that you have like a good
depth of understanding of things and it's always really like,
you know, I feel like I could ask you anything
and you'd have like a good answer for it. But what, like,
how how do you go about learning new concepts, like
(40:44):
if you've had a new tool or just whatever skill
that you needed to learn, Like what's kind of your
learning process?
Speaker 5 (40:52):
I try things out, so the I tried to build something,
and I want to see it work and try it
out first hands on, and then I try to read
about it as much as I can. I tend to
read less in the past year, I think, unfortunately, because
(41:13):
I think, okay, I'll just rely on ChiPT explaining it
to me. But if it's something important, I will try
to find like a blog post or something or a
video to watch or read about it. For example, right
now I'm trying to see I'm trying to read more
(41:34):
on release mechanisms and release methods, let's say, different ways
that companies choose to go about the release cycles. My
first instance was to not to ask GBT, but I thought, no,
this is far too important, and I try to find
(41:55):
like blog posts and like official documentation from companies like
Google or Microsoft and how they do it. And they
do have documentation how they do it. Microsoft has a
lot of resources, for example on how they manage releases.
I'm not going to follow their example because I didn't
like some things. But still I read this, and then
(42:17):
there is Google that has this other. But yeah, I
try to find like official things and read and try
to understand like that.
Speaker 1 (42:26):
Yeah, but hands on first, so testing it out, playing
with it, then going and reading the docs.
Speaker 5 (42:33):
Yeah. So for example, now with the releases, I'm going
to create a test repository and try out the different
release types, like the release from brush trunk based release,
you know.
Speaker 3 (42:45):
M Yeah, I think that, like for me, it's always
hands on, has always been the best way, and just
not being afraid to like, Okay, I don't understand this.
Maybe if I actually open the source code, I can
figure it out, but I it more out of Sometimes
people can't describe it to me. It doesn't matter what
(43:06):
words you use. It's going to go right in this
ear and write out that one. And so I have
to like actually open source code and try to understand
what's happening that way too. I do want to report back.
I didn't find Michael's talk online, but he will be
in Tel Aviv in November at Angular Tel Aviv, So
(43:27):
if you are in that area and can get to there,
November twelfth is that conference, and then of course I
know Angular and gi Komp will be releasing the videos eventually.
They like to make you wait, that's your punishment for
not buying it.
Speaker 1 (43:41):
Well, but you can subscribe to their newsletter and they oh, okay, yeah,
updates on that.
Speaker 3 (43:46):
So yeah, yeah, there you go. Definitely, definitely, but yeah,
I think that that's one thing that sets apart people
that are successful as engineers. And this goes right back
to talking about job hunting, Like, I'm more in find
if I have two people and one is maybe has
less experience, but they're more they have better tools for
(44:07):
teaching themselves how to learn something, I would be more
inclined to want that person on my team than somebody
who maybe has a lot of experience but doesn't know
how to like actually dig in and digest a problem.
So so yeah, like the fact that you're like, oh yeah,
like the fact that you're like, I'm going to I'm sorry,
(44:31):
we're just talking over each other. I think we're just
agreeing with each.
Speaker 4 (44:34):
Other, We're trying to say the same thing.
Speaker 3 (44:36):
We're just finishing each other's sentences like we always do.
Speaker 5 (44:39):
I don't.
Speaker 4 (44:40):
That's finishing more than like saying the same sentence.
Speaker 3 (44:44):
We're trying to be identical twins. It's not working. I
have no beard, I'm shorter than Jay.
Speaker 4 (44:50):
There's a lot of things not identical about you and Aila.
Speaker 3 (44:53):
Not a lot of things. But yeah, alright, So.
Speaker 1 (45:02):
Does anybody have any kind of final questions? I know
we're kind of wrapping up, or Katerina likewise, do you
have any final things that you'd like to share about
super Base your experience with it?
Speaker 5 (45:15):
No, just say go use Superbase because you'll be amazed
at how how smooth it makes it to have a
full working application right out of the box. Almost I
will say, I'm really amazed.
Speaker 3 (45:30):
Is there for somebody that just wants to try it out?
There's a I assume there's a free tier.
Speaker 5 (45:36):
Yeah, yeah, there is. There is a free tier.
Speaker 3 (45:39):
Nice. And then you linked in the show notes are
getting started tutorial, which is great. You said both dot
New works with it.
Speaker 1 (45:48):
Yeah, unlovable nice and I.
Speaker 5 (45:51):
Think other are no colde platforms, but these two definitely
too nice. Nice.
Speaker 3 (45:56):
So you can go in and do some vibe coding,
spin yourselves up as scam website in just a weekend.
Speaker 5 (46:10):
No, but really you can kick start your business with it.
You're full of jitimate, scale uply normal business with it.
Speaker 3 (46:18):
Absolutely, And you know, I think that's the cool thing
about modern web development is that, you know, when I started,
I had this little crafting business. It was like the
early two thousands, and it was not easy to set
up e commerce, right, Like, there is no way I
was going to like I could have I could make
a website that could show off my products, but I
(46:40):
did not have the skills to integrate any sort of
payment system or anything that was like secure enough that
I could you know, do that to people. So it's
it's cool to have these resources like super Base out
there to make it so that you don't need to
(47:01):
have you know, decades of experience and you know, a
whole team working with you can.
Speaker 5 (47:08):
Get Definitely that's amazing. And you know a lot of
people may say like that small founders that have this
small app that they're being super bases. The CEO of
the company, you know, yeah.
Speaker 1 (47:25):
I was just going to say, I've been working on
this little side project and it is like we're building, uh,
basically a social media app, and there was the people
coming together. We're all volunteers, we're all just kind of
doing this in our free time, but we all come
with different backgrounds and experiences and you know, some I
(47:47):
don't know, Like long story short, It's just made it
so nice because when we made the decision to use
super Base, it just took out a lot of that
other decision making, you know, and it saves so much time.
So for that we were really grateful. And and then,
like we've been saying over and over, it just helped
us to kind of hit the ground running, like you know,
everything was right there. It just it was so nice
(48:09):
just to go.
Speaker 4 (48:11):
It's made a lot of things that used to be
really complicated really simple.
Speaker 1 (48:15):
Yeah.
Speaker 3 (48:17):
Absolutely, CTOs are going to be a thing of the past.
Speaker 4 (48:20):
J Oh definitely. Day versus super Bass, I don't want
to I don't want to be super bass that I
do have no desire to pit myself.
Speaker 1 (48:32):
Against well, Katerina, If if someone would like to follow
you or connect with you, what is the best way
to do that on social media?
Speaker 5 (48:44):
I have Twitter, I have Blue Sky. It's uh at
cyber City, so it's at ps Y b E R
C I.
Speaker 1 (48:54):
T Y nice and definitely when you can. I know
maybe the recordings aren't AVAI yet, but from Angular Connect
check out her her presentation and yeah, keep an eye
on Katerina. She's always up to some pretty amazing things.
Thank you, thank you so much, and thank you to
(49:15):
Laura and Jay. Love being on the show with both
of you. But yeah, everybody, go back listen to some
of our previous episodes. I can guarantee you Katerina has
been on.
Speaker 3 (49:30):
Specifically, remember you being on with your NX, the work
you did NX with. Oh shoot, now my brain stopped working.
Speaker 4 (49:39):
The AI chat or oh no, story book.
Speaker 5 (49:43):
There we go.
Speaker 3 (49:43):
I'm like, I almost sid play right, but I'm like, no,
that's not right, like that, it's like a it's a
it's a storybook. I just revealed to the audience how
my brain actually wore.
Speaker 1 (50:00):
Uh funny. But yes, definitely go check out her previous
episodes and we'd love to have you listen in the
future book See everybody later.
Speaker 7 (50:09):
By Hey, this is Prestol. I'm one of the NGI
Champions writers. In our daily battle to crush out code,
we run into problems and sometimes those problems aren't easily solved.
Ngiecomp broadcasts articles and tutorials from angie champions like myself
that help make other developers' lives just a little bit easier.
To access these articles, visit medium, dot com, forward slash ngcomp.
Speaker 2 (50:33):
Thank you for listening to the Angular Plus Show in
Chiecomff podcast. We'd like to thank our sponsors, the ngiecomf
organizers Joe Eames and Aaron Frost, our producer Gene Bourne,
and our podcast editor and engineer Patrick Kay's. You can
find him at spoonful Ofmedia dot com.
Popular Podcasts
Stuff You Should Know
If you've ever wanted to know about champagne, satanism, the Stonewall Uprising, chaos theory, LSD, El Nino, true crime and Rosa Parks, then look no further. Josh and Chuck have you covered.
Dateline NBC
Current and classic episodes, featuring compelling true-crime mysteries, powerful documentaries and in-depth investigations. Follow now to get the latest episodes of Dateline NBC completely free, or subscribe to Dateline Premium for ad-free listening and exclusive bonus content: DatelinePremium.com
The Bobby Bones Show
Listen to 'The Bobby Bones Show' by downloading the daily full replay.