Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:00):
I want to talk to you
about how to think about
selecting the technologies foryour respective SaaS build. So
this is something that myself asa, I guess, a degreed engineer
and I only say that to basicallygive you the impression that the
education that I have hasinstilled certain, I don't know
(00:20):
if they're principles or maybethey're just restrictions in
terms of how I think about thesethings. But for me, I have a
tendency to borderline obsessover like the tools or the
technology I'm using orwhatever. And what I want to
tell you in this episode is forthe most part, not universally,
but for the most part it doesn'treally matter. And what I'm
going to recommend is where Ilanded myself which is to use
(00:44):
what's most familiar for you andincreasingly so these days it's
becoming relatively agnosticbecause the AI essentially has
the capability to use whatevertechnology you want.
To me, the connecting element isyou understanding what it is
about that technology that youneed in order to be comfortable
(01:04):
using it effectively andunderstanding how it works,
which I still think is a veryimportant part of the process.
So as you're leveraging AI foryour build, work with it to help
you better understand how youmight structure your project and
or what the best technologiesare to use for your build. I do
that a lot. And I get a lot ofhelpful information that checks
(01:25):
a couple of boxes for me. Numberone, it gives me the confidence
and the reassurance that I amusing technologies that are
appropriate for what it is thatI'm building.
And I'm going to refer back tothe SaaS product that I'm
building in public on my YouTubechannel as an example here
because it is going to deal withsome numbers. It's going to do
some crunching. It's going tohave access to a number of
(01:45):
different APIs. Not too terriblydifficult from anything that I
build these days, but point istechnology that I want to use
for that is probably Python. AndPython may be overkill in terms
of the back end and having anappropriate version of that and
being able to do heavy numbercrunching or whatever
consistently, which Python has anumber of libraries, which are
(02:06):
really good for that.
But I take more of a myperspective is on it is more
like, I'd rather have it and notneed it than need it and not
have it, if you know what Imean. Because previously, when I
was doing coding manuallybefore, you know, AI exploded, I
was using basically fullJavaScript stack stuff like MEAN
(02:26):
and MERN. And it was all likeMongo, Express, Angular, React,
Node, whatever. And it's justnot necessarily the best fit for
building products like these orstuff that's like fintech based
products because JavaScriptdoesn't necessarily handle
numbers all that well. But youcan eliminate almost all of this
anxiety in choosing these toolsand picking out your stack by
(02:47):
working with Claw dot ai inorder to help you design your
project.
Even better than that is AI isgoing to have probably the
capability beyond that of acompetent developer to be able
to leverage whatever technologyyou want and walk you through
process of wiring everything up.So I want you to do a couple
things. If you're not sure,like, which technology to use or
(03:08):
if you're using the ideal onesor you're stuck at this past
this part of the process in yourproject, work with AI to help
you through it, right, to helpyou better understand the
differences between thedifferent technologies, like
what you might recommend whenand where and what probably
works for the ideal stack forwhat it is that you're building.
You no longer really need tojust use what you're comfortable
with because AI has got thecapability to pretty much use
(03:30):
anything these days. That adds aa level of versatility and
flexibility that we didn'treally have before because we
needed to kind of like masterthe technology or use it
extensively in order to feelmost comfortable with it.
Those days are largely gone, andAI has solved that problem for
us. So it can help us not justdesign but pick out what it is
that we want to use. It can helpus with building it, obviously,
(03:51):
as well, too. The key, though,to me along the way is I highly
recommend you learn as much asyou can while you're doing it,
too. So if you see somethingthat you don't know or
understand or you're learning itfor the first time or whatever,
whether you're in like cursorsask mode or you're using cloud
dot ai, you know, web interfacewith Opus or something like
that, ask questions along theway, right?
(04:12):
Get to learn these differences.Educate yourself as well. Use
the AI to not just do it foryou, but to train you and help
you understand these things.Because, you know, as you're
looking for work or working onthese projects or whatever it is
you're doing, you're gonna wannaadd these skills along the way.
Right?
We're not just doing the vibecoding thing. We're doing
context engineering. We areleveraging traditional and
(04:35):
typical, like, professionalengineering as part of what it
is that we're doing. But we'releaning on AI extensively to do
a lot of the heavy lifting andthe grunt work, Right? That, I
think, is the best combinationof how to leverage these
technologies today to setyourself up as best as possible
for succeeding in building yourSaaS, whether that's a side
hustle or becoming a primarything, and or in your career as
(04:57):
well too if you're also workingin tech.
So that's what I've got for youtoday. Thanks for tuning in, and
listen. I appreciate it.