Chase Douglas: There's a lot of interesting stuff happening in AI
where we're starting to realize on the coding front, like what does it mean?
To code efficiently with AI when you get into spec driven, test driven development.
Corey Quinn: Welcome to Screaming in the Cloud.
I'm Cory Quinn, and I am joined by dear friend of mine and yours, chase
Douglas, CEO at Archodex these days.
Chase, how have you been?
Chase Douglas: I, I've been good.
I've been good.
Corey Quinn: You've gone through an interesting series of evolutions.
You were the CEO at a startup called Stackery before you did that.
No one knows.
No one has any idea what your past is,
Chase Douglas: just to be clear.
CTO.
'cause I'd worked alongside some amazing people.
Corey Quinn: Ah, my apologies, I'll.
Those three letter titles are strange.
CTO at Stackery and co-founder, let's forget that part of it.
Chase Douglas: Exactly.
Exactly.
Corey Quinn: Which honestly means your job is whatever needs to be done in
the, in that moment, you have five things that must get done today.
Chase Douglas: On a good day, you'll get to, here's a thousand question
questionnaire for compliance about printers, about your SaaS product.
Corey Quinn: AI can do it.
Yeah.
So then you got acquired.
By AWS, which was interesting because the way I found out that you got
acquired was I got an email as a Stacky customer, and then I emailed
a few of you be like, what the hell?
Like, hey, that we've been like that for months now and we haven't
been allowed to tell anyone.
Thanks for noticing.
So yeah, that was.
Amazon Marketing, once again, taking a vow of silence for no discernible reason.
You were there for a few years.
You got a few things out the door.
The second coming of Stackery, but it's a UI focused product at AWS.
So it's of course doomed that company cannot build a good UX to save it's
life and then decided that, alright, I'm gonna go do something else.
What makes me unhappy unreasonably.
So, and then you just had to go tilted a windmill.
What windmill is it?
Chase Douglas: I'm building a project, it's called Archodex.
Uh, it's me and a fellow principal engineer from AWS.
There's a lot of really interesting, uh, fun stuff happening with AI.
Uh, when companies go out there and they say like, we have a great idea for how.
We can give people an amazing feature, an amazing solution, a product, whatever,
and is gonna use AI on the backend.
Uh, a lot of times you get these product teams, they dive in, they do
some cool stuff, some POCs, and then they're like, we're ready to launch.
And then they start talking with their lawyers, their compliance teams,
especially in enterprise departments with like five different security teams.
And the skids, uh, happen and you have to figure out.
What do we do to solve a lot of compliance stuff, and especially because
AI, like people are sending all kinds of crazy stuff into these systems,
uh, freeform text and, and whatnot.
And so it's a, it's a challenging space, but what's really interesting
is leading companies doing AI.
So these are companies like A DFS themselves.
Have their own AI products.
Not like Bedrock is an AI product, but I mean like more like their DevOps
agent, like it's using AI inter intercom with their, their fin, especially AI
enabled customer, uh, service solutions.
Sentry with, again, their kind of DevOps focused AI stuff.
I've talked with people at companies like these and there's a lot of
common things where they'll say, okay.
To solve for security and governance and compliance.
We have this kind of like central pipeline that we send
all our LLM AI interactions to.
And from there we figure out what do we need to do, audit
logging, where do we send the raw logs, uh, analytics, how do we.
Anonymize these things and send it to the right analytics warehouse
or operational o hotel service, vendor of choice, potentially
anomaly detection for security.
But the point is there's a central.
Pipeline where this is all governed and managed because of how radioactive
it could be if this were mishandled.
Corey Quinn: Yes.
Even now at a, we're, we're a small startup.
We're building software at Duck Bill, and in fact, this is probably a good.
Point to wind up doing the sponsored read.
Since we are now the only sponsor of this after years I have gotten
it down there, uh, we are helping companies solve their cloud contracts
with software and services to boot.
If your cloud contract is expiring within the next year, please reach out to us.
If nothing else, you can get that sad dead look in your eyes that we all get
when talking about contracts combined with cloud billing and commiserate.
Odds are we might be able to help you out with things.
Our product Skyway is doing amazing things around contract management.
Please kick us out at duckbillhq.com.
But as we were mentioning from the AI perspective, yeah, we have an entire
policy internally around which systems we're allowed to put AI through for
models, how we get those models, and we have a standing policy that customer data
does not touch AI just for, you know.
Customer comfort if nothing else.
Chase Douglas: Right?
So there, there's a bunch of stuff in this space about how do you handle
this, whether you're dealing with public information, customer data, you're
mixing things, whatever it is, how do you make sure you have confidence?
There's one place where all of this flows through a single pipeline
that is properly anonymized.
If it needs to be for certain endpoint destinations, you
know, who accesses those?
You've got logging on like, who can see my Snowflake cluster?
Or you know, wherever I. Got my audit logs.
Once you've got that in place, then you can have confidence to turn on the gas
and really enable your product teams to build, deliver, ship awesome new features.
So that's what we are working with customers to do, is
to make this turnkey easy.
Uh, and that's where, you know, my, uh, co-founder myself ap Perva being, uh,
a previously AWS principal engineers working in an enterprise environment.
Working with legal teams to define and develop processes and
implementations for compliance, considerations, security, and whatnot.
As we worked on AI enabled solutions, if you're saying to yourself that.
You are in this problem space, having to figure this out, and you wish
you had two AWS principal engineers working on this and helping you solve
this and figuring out how to talk with your lawyers internally or externally.
Give us a, a ring.
You can hit me up on on LinkedIn, chase Douglas.
You can go to our site.
It's uh, Archodex.com.
That's A-R-C-H like architecture, A-R-C-H-O-D-E x.com.
Quest a demo, hit our contact form.
Uh, whatever you wanna do.
We're here to help you.
We're early days, so we're building things that meet what our customers
are asking us to build for them.
Uh, hit us up so that we can help you.
Corey Quinn: I, I do want to highlight.
That this has become a problem.
What, what are the approaches?
I do, 'cause I do a lot of random one-offs with ai.
Go vibe code me a thing.
I, I just redid my entire email newsletter production pipeline
over the break for that reason.
I've been sitting on that for six years.
It was $50,000 of development effort to have a human do it.
Or I can now finally get to a point where I can just poke Claude code for
a few weeks and it winds up spitting out something that works for me.
And.
The way I do this is I have, I run Claude in its own EC2 instance.
It has root on the box.
I run this in its own AWS account.
It has an administrator access IAM role for that entire account.
And that account is called Superfund, as in the government program
to clean up toxic waste sites.
It's expensive and it's toxic and it does a whole lot of terrible
things, but there's nothing persistent in that account.
And there's no long-term data.
There's no data that lives there at all.
That is, has any sensitivity.
So everything to get out of there has to go through a CI/CD pipeline that has
more guardrails on it because I don't want the innovation to get slowed down.
But I also, you know, don't want to accidentally the database.
I can't run quad code in dangerous mode on my laptop that has stuff on
there that cannot see the light of day.
So I have to be a little bit more cautious.
Chase Douglas: Yeah, and it's.
Also a challenge when there's this thing that people started calling Shadow AI.
It's this idea of, oh yeah.
When we are, uh, rolling out our AI enabled products, we put it through
Bedrock, so it's going through all the AWS guard rails and everything.
That's great.
But what are your developers on the teams doing when they're spiking their
POCs and they're testing out, you know, some, some changes or whatever?
I've talked to so many engineers from so many companies who say, yeah, we have
Bedrock, but like, it's locked down.
I can't use Bedrock to really figure out what model's gonna work best and,
and, and how to prompt it the right way.
So I reach for things like, uh, open router.ai, which now lets me hit any
number of models and test them out.
But, uh, ahead of security and compliance at your company.
They're like, wait, you're doing what?
We're, we don't have any relationship with Open Router.
We don't know where that goes.
We don't know how they log things.
We don't know what data you're mixing into it.
So that's the so-called shadow.
Corey Quinn: Did you study your entire code base for this thing into Claude Code?
Well, in my case, jokes on you.
Claude Code wrote the whole thing.
Anyway, so.
Chase Douglas: Really being able to capture that and
understand what's going on.
Um, that's the other really kind of interesting, innovative part of,
of what we built is, uh, with kinda like a zero instrumentation approach.
You can slap on a little bit of instrumentation to your like compute
cluster and we'll be able to capture.
Every AI LLM interaction and tool interaction, uh, that your workloads
do, whether they're in dev test, production, qa, whatever it is.
And so that's kind of an exciting thing too, that not only are we helping
make sure that people have these centralized guardrail pipelines on
the backend, we're making sure that they're capturing everything on the
front end too, even in dev and test.
Corey Quinn: I wanna kick the tires on this myself.
Uh, one of the things that even in the Superfund account, as you can
imagine, it uses in some cases the clo, the Anthropic, API, in some cases
bedrock in one Godforsaken instance.
It's using a lot of Vertex AI over on Google Cloud for unrelated reasons.
And one of the challenges heard.
Well, it's, it's great.
The challenge I've got is that every quarter when they come out with new
models, I get to play Whack-a-Mole throughout a bunch of different micro
repos and figure out what's calling what, and I've been able to do it so far by
API key and guess in check, but I don't wanna be running sonnet two anymore.
So seeing what's making what called to aware would be helpful.
Chase Douglas: My co-founder, he was just playing around with our demo that
we built yesterday, and he noticed that.
Open router now one of their previously free models.
It's just returning errors saying, uh, we no longer do this anymore.
We're not doing free tier of this model, so you gotta go find a different model.
You know, I don't know how many people are using open router in production
per se, but like this is a kind of challenge, like it is, as you said,
whack-a-mole of how do we keep this stuff operational when there's.
Thousands of different models out there and how you access them,
what their price points are.
They're changing all the time.
You even noted AWS is changing their price points on some of their,
I don't know if it was models.
It might have been, what was it again?
They changed their pricing recently on.
Corey Quinn: Capacity blocks for MLS raised, uh, by 15%.
Uh, they do claim to adjust them every quarter and everyone's whining.
It's like spot dynamic price.
Changing things once every three months is not my definition of dynamic.
Maybe that's enterprise dynamism.
Chase Douglas: Yeah.
I suppose maybe, maybe the enterprise CFO is totally fine with that.
Corey Quinn: Speaking of enterprise dynamism.
I am curious as far as what it is that you have seen about re:Invent this year.
Chase Douglas: So I went to re:Invent.
I, uh, went there to have conversations with people, a little bit to
learn, but most of the time I don't go to like sessions or whatnot.
It's about like networking, finding people in the hallways
at the events, and both like.
Expanding the people I know who I can then follow up with when I
realize, oh, they know a thing that I don't know and I wanna know more.
And I could do that after the fact.
But also just like, you know, in real time learning, what's the, what's the
state of play, what are people doing?
And yeah, this year.
This year was interesting.
I, I didn't go last year, but I had been to previous to that eight
re:Invents in a row, so this year things felt a little different.
I don't know what you kind of sensed in it, but it was getting harder.
To just have those networked conversations with people I was talking with like Ben
Keho and we were struggling just to meet up, like where where are we gonna meet?
Because if you've been to re:Invent in the past, you know that it's in this sort of
like very large casino conference center.
Place, and if you are walking around, there are places where
there you're, it extends even into a mall and there's benches.
There's this place called like St. Peter's Square with a ton of tables and chairs
and you can sit and have a conversation.
There are restaurants lining all of these venues that 10 years ago
you could just go to any of these restaurants during the day and just sit
down and have a coffee or something.
Over the past few years.
They would get sort of like locked down in the evening for private events.
Uh, but this year, every single one of those places, including the ILI
coffee shop, was locked out as a private event the whole day and night.
Corey Quinn: Mike, my business partner, was saying that the catchphrase for
re:Invent is closed for private events.
God forbid you're making a terrible decision to vacation there that week.
Where are you supposed to eat?
Every restaurant is booked up and closed.
It's awful.
And he couldn't find a cup of coffee at one point, which if you know Mike, that's
like three quarters of his personality.
Chase Douglas: I just needed to get some easy, quick food.
I ended up going like one block down, which Vegas one block is not a
a block anywhere else in the world.
One block down to get to the closest.
Easily accessible fast foods like Subway or whatever, which is in like the very
back of a low key like slots casino.
And I was like, you know what?
At, at least, at least if I went this far, it, it's semi quiett here.
I got the bling going on of like the slots, but I, I don't
know, like, it, it's hard.
It's hard, you know, like I'm friends with, you know, many other
people from lots of different.
Companies.
I was talking with some people from one company that has sponsored,
uh, re:Invent in the past and had had booze, uh, at their expo and
everything, and they're like, yeah, we're not even doing that this year.
Like, it's so expensive as a vendor to show up and the leads are.
It's hard to justify what you're getting out of it as the expensive had gone up
and up and up, uh, for the conference.
And so this is kind of happening on both sides.
You got like a ticket to go to the conference is $2,100 this year.
The sponsorship is like crazy entry price probably of like 50
to 70 5K for a tiny little booth.
At this point, I don't actually know and it reminds me of like Cory Eros.
Idea of like in ification,
Corey Quinn: it's, it's gotten terrible.
I still, it, it was burned into my memory years ago that at re:Invent
in the opening keynote Andy was talking about, what is this for?
Is it a sales conference?
No, he lied.
Given how expensive everything has become.
Is it a, is it a training event?
What is it?
He said it's about education.
It's about learning things.
Yeah.
The problem I'm seeing is that the educational has a very,
speaking from, uh, doctrine.
As opposed to speaking from reality perspective, I couldn't find places
to sit this year, and I don't know if that's because there were fewer
places to sit or I just wasn't invited to some of the special places.
I too got to sit with Ben Kehoe and chat, and the reason I was able to
do that is because I snuck my way into a place I didn't belong because
everyone thinks I'm an AWS hero.
This episode is sponsored by my own company, duck Bill.
Having trouble with your AWS bill, perhaps it's time to
renegotiate a contract with them.
Maybe you're just wondering how to predict what's going on in the wide world of AWS.
Well, that's where Duck Bill comes in to help.
Remember, you can't duck the duck bill.
Bill, which I am reliably informed by my business partner
is absolutely not our motto.
To learn more, visit doc bill hq.com.
Chase Douglas: There was some like ex AWS hero allowances that I availed
myself of as well in the same way.
But, but to your point, the thing I found hilarious was the Venetian entrance.
Uh, so the Venetian is like the, the casino hotel that this is in, and it's
got its own entrance, separate from the palazzo, separate from a bunch
of other places you can get in The Venetian entrance had historically.
This kind of like, you'd almost think it was a fountain, but there's
actually no water fixture in there.
It's just kind of like a planted area in this rotunda.
And you could sit there on these low like areas.
It was almost like a bench.
And this year there were these like metal decorative grates
that had like spiky tips.
On those benches.
You could not even sit there.
I had to laugh when I was walking and I'm like, oh, I know I can go down there.
And I walk a quarter mile down to that place and I get there and it's like,
what's greeting me is metal spiky things.
So I, I can't even sit there.
So this is while I was doing a FaceTime with my family, uh, one of
the evenings and I'm like, oh, turns out I'm just gonna be pacing around
this rotunda as I talk with you.
'cause I, I got nowhere to just sit.
But yeah, like.
Corey, Dr. O, the, like other Corey,
Corey Quinn: he spells his name incorrectly, but I like him anyway.
Chase Douglas: Right.
Uh, is like phase one of gentrification is like, you know, making it, what was
it like super awesome for the consumers?
Like, you know, re:Invent 10, 15 years ago is all about education and then phase
two is we're making up not so awesome, but the consumers we're making it super
awesome for, for like vendors businesses.
So like, okay, now you know, it's a great.
Place to go and, and, and have a booth and vendor or whatever.
And then like, phase three is we're now raking in so much money.
This is our business.
We're not making it any awesome for either the consumers or the businesses.
And it's, it's just a money machine now.
And I feel like that's what re:Invent is.
It's like a WI, I don't actually know what the revenue profit is like
for re:Invent itself, but you know, I, I just look at the pricing and
everything and I'm like, well, who's.
Who's actually making out well here and it's like, well I think
it's AWS is primarily making out well here for their conference.
So, yeah.
Corey Quinn: So one thing I'm curious about is.
I need to talk to more folks in various spaces, but re:Invent
has lost all sense of itself.
I gave a talk two talks this year, last year, now that this is January, and
it was the only time for those talks where I left the Venetian and it was
like a completely separate conference.
There was entire world.
I never got to see this.
It could have been two separate conferences for all I noticed.
So it was a. I don't fully understand the value or who people, what value
people think they're getting from it.
We're looking at budgeting for marketing for the year, and that's
pretty expensive to sponsor that stuff.
Like people like, uh oh, it'd be great if we had like a plate, like
a desk we could do a demo at at our booth, rather just the kiosk.
It's like, yeah, that, that's.
That's gonna have a six figure build hatch to it if we want that.
Like, is it worth that much?
I don't know.
It's a, it feels like a cash grab.
Chase Douglas: I do have to say the best event I went to at
re:Invent this year was your event at Atomic Liquors, because it was.
Well off strip over in the Fremont area,
Corey Quinn: it was free.
The good people show off.
Some people just show fly into town just for that event.
Chase Douglas: And the people who end up there are there because
they know it's going to be good.
They're not just there like, where's my next free drink
on the strip kind of thing.
Uh, and I had such great conversations there that was like re:Invent of
the old, but you have to find it in pockets here and there now.
Corey Quinn: Uh, that is my favorite part of re:Invent.
I would do that regardless, but the rest of it, ugh.
I am at a point now where I don't go to sessions other than the ones I'm speaking
at, because I don't like waiting in line forever to get turned away at the door.
I a, a lot of the people I normally want to talk to just aren't there
in the way that they used to be.
Uh, I talked to like some of the folks that I love spending time
with and re:Inventing the most of 'em just weren't showing up.
It is a shadow of itself and I get nothing good can stay.
That is, that is the inherent problem, like nostalgia.
We always want things to be like they used to be, but I do find myself
wondering who this conference is for, because increasingly it's not for me.
And maybe that's okay.
There's a lot more people out there who are not like me than
people who are thank the world.
And maybe that's the right answer.
I'm sure AWS has a vision for this.
I hope, I just don't know what it's,
Chase Douglas: yeah, and the other interesting thing is I was curious when I
was just seeing, like I follow the what's new feed to, to keep up with AWS and
especially, uh, at re:Invent every day.
It's like, okay, so what was actually released here?
And uh, I remember.
Five to 10 years ago, every day at re:Invent was like another hundred
releases, and it would actually take me a couple hours just to sift through them.
I'm not reading every one of 'em, I'm just sifting through the
headlines and then poking in on the 10 that that are interesting.
Now, that was also during the heyday of them just.
Releasing anything for any niche that anyone said.
Yeah, sure.
That sounds like I would like that from AWS Yeah, go build that.
And they would, it's not necessarily good either.
But, uh, I went back, uh, I could only go back in their, uh, feed history to
like 2022, but you could see like the amount of releases has, uh, dwindled too.
So like 2022 was something like.
101 releases, that's still coming outta COVID a little bit.
Twenty twenty three, a hundred twenty seven releases.
And then, uh, 20 24 66 releases, 20 25 69 releases.
So it's really coming down and.
You know, some of that is, I think like pivot to AI and having to re-figure out
what are, what are they doing in AI.
But I think some of it is also a little bit of like where is the continued
innovation that they're known for.
I'm gonna be very curious to see like just kind of how the future
continues to unfold for AWS.
'cause a lot of the people there.
Who remain, who are super smart and doing amazing stuff.
And you see that in some of the stuff that, that continues to get released.
And you've also seen, you know, as I have, I'm sure, uh, a lot of people have left
AWS for various reasons and I, and I kind of like, what, what is happening with
the innovation And if that's part of what has also driven re:Invent over the years
and what's been amazing about it, like.
Where is that going to, that input that feeds into what makes re:Invent great.
Corey Quinn: I am deeply curious to see how that's going to shape up.
I, I just, at this point, it feels like it can't be getting results
for folks like you take a look at some of these sponsor packages for
tens of millions of dollars and.
Are, are you generating that much business from re:Invent for that
Chase Douglas: brand marketing?
I think it's, I think it's brand marketing at this point.
Uh, when you can go up and down the strip and see on every casino's, giants
video board, about every two out of every three ads is for a tech company.
Come see us at Expo booth number 5 92, and then hilariously the other
third are for like Rodeo Cowboy.
Gear because like as soon as re:Invent leaves, it's now like a, a like
a PBR rodeo event or something.
But yeah, it's, uh, it's, it's crazy.
I, I don't know.
Not a CMO at a, at a giant company, so
Corey Quinn: it's a weird mess.
If I really wanna thank you for taking the time to chat with me about this.
Uh, what are you looking forward to this year?
It's 2026.
We are on the cusp of something interesting happening, I think.
What are you excited about?
Like there's a lot of pessimism is out there, but what do you
actually, what makes you smile when you think about this cove year?
Because if it's re:Invent, we're done.
Chase Douglas: This is a little bit more like individual, a little
bit more, more personal sized.
I'll tell you what I have really enjoyed.
I have had moments of, of skepticism about AI, and I also wanna say I'm not, like, I
know there's environmental concerns about it too, and I want to hope that, uh, we
will find ways of lessening its impact on all kinds of different ways, uh, and
not just try to shove it under the rug.
But that said, there's a lot of interesting stuff happening in AI
where we're starting to realize on the coding front, like what does it mean?
To code efficiently with AI when you get into spec driven, test driven development.
And I have actually found it fun.
Midpoint of last year, I was like throwing spaghetti at the
wall, like AI, go do this for me.
Try it, and getting terrible results.
And then, you know, talking with people, it's like you need to do
this spec driven kind of development.
And all of a sudden it's like unlocked so much productivity and yet I still
get enjoyment when I get to say to my.
AI coding tool of choice being like, yeah, cool.
I see what you did there, but my, my Rust program that you wrote, like you shouldn't
be using threads for parallelism.
You should be using Async Tokyo mechanisms and being able to take the raw.
Computer engineering.
You know, like I, I went to school for computer engineering using stuff I learned
from the operating systems class back then still today, to mix that in, even
though I'm not handwriting the code, I am still activating that part of my brain
that's putting that to use and knowing that it's creating better software.
Because I'm putting the right guardrails around the stuff.
So I will say that coming out of 2025, I'm much more hopeful about just what it means
to be a software engineer than I was.
Coming into 2025 and hearing all this AI stuff, and yet
feeling very unsure about it.
I would say that I, I'd say that
Corey Quinn: I'm very happy with a lot of what Claude Code is putting out and yeah.
Does it, is it architecturally inconsistent?
Yes.
So is my own nonsense what of it you can iterate forward on it and
efficiency of code versus does it work?
Is important.
So the question there right now is how do we review all of this
slop code that's being generated?
Well, how do we build systems that do that?
Because on some level, like, well then I won't know what every
line of code in production is.
Yeah, you're right.
You won't.
Do you look at the compiled output in some languages?
Of course you don't.
No one does.
So how do we wind up making sure it does the thing that we think
it's doing and that leads to better test harnesses, uh, better.
Controls around things that have criticality in them.
But if I'm building something for fun or a demo for shit posting,
I don't care as much as I do.
If it's the payments code.
There's a difference here, and that is, and there's a different
level of rigor that I bring to it.
Chase Douglas: And, and also I, I think it's useful to point out early career
for myself when I reviewed code, I would review it line by line, like,
is this actually doing the right thing Later career for myself to this point,
as you start to get seniority and, and tenure and you're actually helping.
Organizations of teams, build, ship, deliver, and, and manage
their, their, uh, their code bases.
You start to realize, like, it, you can't do line by line reviews.
It's way more about what are the things I'm seeing here?
What kinds of like.
How did you think about the tests you chose to write?
How did you think about the architecture you chose?
How did you think about some of your implementation choices?
The library choices?
And I'm gonna poke in and just ask you this and ask you that.
And if you're giving me good answers, then I'm gonna have way more confidence.
This is doing what it should be doing.
And if there are issues, it's probably just a bug that we need to address.
But like every code has bugs you gotta address eventually.
And if you're giving me not so good answers, then it's like, okay, now
we need to dig a little deeper.
That kind of skillset is still highly applicable to AI.
I will have times where I'm like, I see what you're doing there, but
I want you to change it a little bit because I know we needed to be
doing it a slightly different way.
There are other times I was dealing with some code yesterday where I'm.
No, you're doing it wrong.
And I'm telling you, I know you're doing it wrong.
Uh, you need to be doing it this way.
It was like it was even just trying to put some heavy dependencies into
regular dependencies instead of just developer develop, uh, dependencies.
And I had to like really say, no, you're doing this wrong.
And eventually it's like, you know what?
You're rights.
That should be in the developer dependencies, so it doesn't
end up in the container image.
We're gonna be shipping to customers.
That kind of skillset is still applicable in AI driven, uh, or, or augmented
development today that, that has me happy about being a software engineer.
Still,
Corey Quinn: I find that, and this is gonna be controversial, I get it.
People tend to view.
Software engineering in different ways.
For me, it's never been typing, it's never been wrestling with
weird syntax or boilerplate.
It's never been getting all of the weird things set up correctly.
It's been more about architecture and designing the overall flow.
Uh, maybe I'm the weird one.
I've never been a professional software engineer, just enthusiastic, amateur.
That's the part of it that I like and.
I think that people are some, in some cases missing the forest for the trees.
I'm sure that'll come back to bite me
Chase Douglas: at least.
There's always gonna be software that needs to be written, just like we are
always gonna be engineering buildings to be constructed, and we're always
going to be like engineering as just a skillset is always going to be needed.
And so it's just a matter of figuring out like what are our best tools to use today
and how do we figure out how to use them?
Efficiently and hopefully enjoy using them in the process.
Corey Quinn: We should all be so lucky.
Maybe that's something to look forward to.
Chase, I wanna thank you for taking the time to speak with me Again.
People could visit you at archoex.com to learn more.
Chase Douglas: Hit me up A, as I said, LinkedIn even it may be easier for
you to just remember, chase Douglas.
Send me a message.
Connect like, there's lots of ways to reach me.
To reach us and what we're doing with AI, governance, security
compliance, that kind of stuff.
Uh, for organizations, you know, we're, we're new so we don't have
the gargantuan marketing reach yet.
But yeah, if you, like I said, if you want Amazon Caliber Principle
Engineers helping you figure out how to do compliance and governance and
security for your AI workloads, find us.
We'll help you out.
Corey Quinn: And hopefully you don't want Amazon caliber UX
designers implementing the same.
Chase, thank you so much for your time.
I appreciate it.
Chase Douglas: Yeah, yeah, yeah.
This has been so much fun.
Anytime, anytime.
Corey Quinn: Chase Douglas, CEO at Archodex.
I'm cloud economist Cory Quinn.
This is Screaming in the Cloud.
My thanks to my own company, duck Bill HQ for sponsoring.
And if you've enjoyed this podcast, please leave a five star review on
your podcast platform of choice.
Whereas if you've hated this podcast, please leave a five star review on
your podcast platform of choice, along with an angry, insulting comment
featuring an annotated copy of the re:Invent sponsorship prospectus.