-: So I think the thing that
I really enjoy most is the variety of types of projects
and problems that we encounter on a regular basis and that
I get exposed to by supporting the individuals
who do the work hands-on with different engineering groups
within the company.
So for me, you know, it's, I'm always curious,
I wanna learn new things, and this is a way
of doing that kinda through the job
while kind of applying the same general set of skills
and approaches to problem solving in different domains
from like, how to make, you know, planning decisions
for subsea fiber optic cables to what to put
into big data centers and where, as to, you know,
what's the right architecture for a software system.
You know, we work on a variety of different problems
and I help people solve those problems, right.
And I need to help them understand
when a problem is solved enough versus solved totally
versus not solved enough.
And most of the problems I work on are super open-ended,
there is no right, clear right answer, that means
you don't know when you're at the finish line.
So having,
you know, helping people learn how to make
that call when they've put enough effort into one place
and it's good enough and they can move on
to that next problem that they could be tackling that
they're not on because they're, you know, trying to finish
something out to the nth degree in one area, making
that trade off and balance and doing so on the fly
on a regular basis is
probably the biggest challenge that I face right now.
Dealing with uncertainty and how to know
when good enough is good enough to move on.