So what I do for me is I focus on two
things. I focus on preventing
the catastrophic events that absolutely bring us down and really, really
focusing on that. Whether it's our data being corrupted, a
hacking attack, a client who creates a study at a point where the
platform's in its infancy, and we haven't established a brand yet.
And it creates something that is, and they do, let's say they
do a poor job at creating it. And they call us out and say, "Hey,
this platform sucks." But we have to educate them on the way that
it's used. That's a killer for us. So really preventing those
catastrophes that bring you down on the one side. On the other side
of the barbell are those opportunities that can absolutely make you
and be your swan song. Building an architecture that is open has so
many doors open to those one-in-a-lifetime
experiences, like a client wants to come with you an they want
to essentially up your -- they want to up your producing by 10,000
percent. Like a Facebook or a Google comes along to say, "We
have this opportunity, multi-million dollar opportunity, and, but
awe need to increase your productivity on this platform." Making
sure you have the doors open both in the code, in the architecture, and
in your work flow processes to be amenable to those
opportunities, absolutely huge. The things in the middle,
and again, you pictures that barbell smaller as smaller the middle.
Things in the middle, you do pay attention to, but you know that it's
not gonna make or break you if you those things sit on the shelf
for a little bit.
