39:11
2024-05-06 08:57:50
3:11:28
2024-05-06 10:30:19
24:39
2024-05-07 07:20:20
19:49
2024-05-07 08:03:25
1:14:35
2024-05-07 08:35:13
15:41
2024-05-07 10:06:25
38:33
2024-05-07 10:37:03
2:48
2024-05-07 11:19:01
59:37
2024-05-07 11:33:56
6:10
2024-05-07 14:55:25
39:40
2024-05-07 15:02:44
9:45
2024-05-08 06:44:21
29:27
2024-05-08 08:09:24
2:51:40
2024-05-08 12:09:24
Visit the Apache Nifi - GROUP 1 course recordings page
WEBVTT
-->
What will be your primary provider for that kind of content for the verbal section?
-->
Yes.
-->
Okay.
-->
This is great.
-->
All right.
-->
So, what I'll do is I'll create some status review update meetings throughout the schedule,
-->
kind of put those out to the team.
-->
We can make those, you know, as long or as short as possible to make sure that
-->
we have a, you know, a good feel for the content being developed and making sure that we make
-->
the schedule base as we're proposing here.
-->
So, I'll add that to the calendar also.
-->
Any other concerns that we kind of kick this development out of the way?
-->
Well, I'll take that as a no question at this point.
-->
At any time.
-->
I would certainly if you get through this, anything that comes up, please let us know.
-->
I'll be working with the team for the other sections that need to be delivered.
-->
And we can address questions, take them up.
-->
But with that said, I appreciate everybody's time this morning.
-->
And certainly if any other things come up, please let us know.
-->
As we go through this, we have this Saturday, the 28th May recovery, targeting 27th May,
-->
if we can, to, for you know, for Tata to submit.
-->
But with that, I appreciate everybody's time today and look forward to working
-->
with the team on developing the planning proposal here.
-->
Awesome.
-->
Thanks, Michael.
-->
All right.
-->
Well, thanks everybody for your time.
-->
I can hear you.
-->
Yeah, we're hoping Logan's going to pick up.
-->
Okay.
-->
I just want to talk to you real quick about Dylan and I's conversations more.
-->
I did not.
-->
What happened is, is you shared a link that he was working on, right?
-->
So he can see I'm in the document.
-->
Hey, Logan.
-->
That doesn't make sense.
-->
Yeah, that's...
-->
Are you there, Logan?
-->
Okay.
-->
So Logan, this is the first time I've ever asked you to do this.
-->
Yes, this absolutely takes high priority.
-->
You don't know what you're working on.
-->
But my goal is, and my hope is, and the way, the best way to do this,
-->
hope Josh agrees with me, if he doesn't, I don't care,
-->
is that the vast majority of this should already be written.
-->
It's the proposal team's job to clean it up and make it better.
-->
It's not your job to make a beautiful document.
-->
So you've done a lot of...
-->
So the way I've always done this process before is that you've already done...
-->
You've already done...
-->
There's John's con line document.
-->
There's the DIA architecture document.
-->
And there is the marketing documents out there.
-->
So you go get that, and then you put it in, and then you add some words.
-->
Does that make sense?
-->
Okay.
-->
Where would I find that documentation?
-->
Because I don't believe I've worked on any of those.
-->
A team documentation?
-->
So what I've worked on for DIA is I built an install guide for it,
-->
and I have developer documentation for it,
-->
which is how I build some of the components for it.
-->
But as far as the architecture thing,
-->
didn't you work on the architecture for that, Josh?
-->
Or was that someone else?
-->
No, that's John and I and Rhonda.
-->
Is that the con line share point?
-->
Okay, yeah, because I haven't touched much of the con line documentation,
-->
I think, other than providing images and stuff for that.
-->
So, but I can go and find that and look through it.
-->
And maybe, okay, so maybe, really, if possible,
-->
then I'd really like you to take the main ball here,
-->
because you haven't had a chance to do it previously.
-->
And I think that would be a good idea.
-->
Yeah, yeah, so if you just point me to where all the documentation is,
-->
I'd like to look through it.
-->
Okay, and it's not going to be perfect,
-->
and you're going to be like, well, that's not exactly right, or whatever.
-->
I don't see what I can respond to.
-->
I mean, this is just a draft,
-->
and then I assume the whole team is going to actually make sure it's presentable.
-->
Josh, do you have any better ideas for how to approach this?
-->
Because the idea is to get something down on paper as quickly as possible
-->
and then start working with it.
-->
Yeah, I mean, just whenever I work on proposals,
-->
I always have the proposal on one screen and the document,
-->
what I'm writing on the other screen, Logan.
-->
I also take the requirements that they're asking for out of that proposal
-->
and I copy it into my document.
-->
And so what happens is, as I'm writing,
-->
I'm making sure I'm answering every single thing they're asking for.
-->
Never skip.
-->
You want to make sure you answer every bullet they have.
-->
So what I do is I just put all the bullets
-->
or whatever the requirements are in my document and as I'm writing,
-->
and if I think that they are complete,
-->
I will cross those out and I'll move on to the next one.
-->
And so just keep that in mind.
-->
I see a lot of proposals get rejected by the government
-->
just because something failed to meet the criteria.
-->
So keep that in mind.
-->
Actually, Rhonda, you and I were talking about some of the architecture stuff
-->
just a couple weeks ago.
-->
So Logan, I'll send you over links that I have
-->
and then that way it may be easier to share in SharePoint
-->
because Rhonda and I were just talking about these literally.
-->
There's a lot of really good stuff in this because he's a good writer
-->
and it's got good philosophy stuff in it.
-->
Drafted architecture and implementation, white paper,
-->
talks about how it was, you know, that way.
-->
While we're talking about this, since we mentioned it before
-->
when we were re-entering the campus last week,
-->
I know that there are a couple of things that we said
-->
that we probably don't have an answer to
-->
or I'm not sure if we have an answer to.
-->
What do we do about those?
-->
I ask people to put together their questions.
-->
We need to put together our questions and get back to, like, with those questions.
-->
But I assume we don't have those questions anymore
-->
because nobody put them together in question.
-->
Well, I would get those questions asked rather quickly
-->
and then it sounded like Smiley, I think this is his name,
-->
had some other information potentially.
-->
So I noticed Michael just sent out some calendar invites.
-->
So maybe we can actually get some additional information.
-->
But, you know, definitely get those questions out ASAP
-->
and get them answered.
-->
I think you're giving us two weeks.
-->
I think it's two weeks on this.
-->
So and half the time it's Red Team and others.
-->
Oh, I missed you.
-->
I'm only part of the Red Team, which means...
-->
No, you're going to have to go back
-->
and make changes based on people's comments.
-->
Okay.
-->
Or the whole process, probably.
-->
So, yeah, I understand what you're saying, Josh,
-->
about classic writing proposals.
-->
What I'm worried about is writing everything from scratch.
-->
We shouldn't have stuff written into this.
-->
Oh, absolutely.
-->
That's why we at L.E. can do it,
-->
is because we have stuff written into this.
-->
Oh, absolutely.
-->
My way of traditionally approaching these that works,
-->
it sounds any different than we don't have documents, right?
-->
That's not the case.
-->
We have a ton of documentation on this.
-->
That's why I was saying,
-->
Logan, I'm looking for the email now to send to you,
-->
you know, because I found some of the documentation
-->
just a couple weeks ago.
-->
And I just put two links in chat.
-->
I just put two links in chat.
-->
Perfect, perfect.
-->
And I've got some more.
-->
So those could be helpful.
-->
But the sooner you can get ahead of it
-->
and, you know, and get something out fast
-->
and say, okay, this is what I got.
-->
This is where I'm stuck.
-->
I'm going to start on that today.
-->
So when do we want to make it a go?
-->
Well, how do you want me to help, Rhonda?
-->
Well, I would say what I'm hoping is that
-->
what I'm thinking is that Logan would take a first shot at it
-->
and then either before we turned it in
-->
for rent to you and I would need it.
-->
What I'm thinking is whatever holes we have,
-->
that's the key to the problem.
-->
Does that make sense?
-->
Yeah, no, it's not a problem.
-->
I'm just wondering, you know.
-->
And of course, you would help with, you know,
-->
so I need you to look at it.
-->
Do you have any questions,
-->
anything you thought our solution by the rules
-->
that we need to address?
-->
No, I don't.
-->
So not necessarily holes,
-->
but answer me this,
-->
what is innovative about this,
-->
in your opinion, about our solution?
-->
Yes, we think.
-->
What's innovative about our solution?
-->
Yeah.
-->
No, I'm asking you.
-->
I was asking you.
-->
And I'm asking you.
-->
Okay.
-->
So, okay.
-->
Well, I feel like this is, you know,
-->
I do feel like we're going to need to talk to you about some,
-->
you know,
-->
analytic capabilities,
-->
some of that type of stuff that we normally don't really,
-->
I mean, we talk about,
-->
but we don't just because of the way the proposals,
-->
asking for that agility layer, for instance.
-->
You know,
-->
I feel like we don't have a lot of that type of content.
-->
And so, you know,
-->
we would need to come up with some of that.
-->
So you don't think that,
-->
okay.
-->
Okay.
-->
I mean,
-->
whatever Rhonda,
-->
like,
-->
okay.
-->
So I can,
-->
like,
-->
I don't like that response.
-->
Because like,
-->
I'm just asking you a question.
-->
At some point Josh needs to lean on my engineers.
-->
And not have to answer every single question.
-->
It's a high level question.
-->
But,
-->
but,
-->
okay.
-->
I don't,
-->
I get it.
-->
Okay.
-->
Let me see.
-->
So,
-->
what's interesting about our solution is that you build a platform that allows you to choose any algorithm
-->
and you can make it a modified pressure processor.
-->
And it becomes part of your library of algorithms that you choose or not choose.
-->
It's up to you.
-->
It also takes away the,
-->
again,
-->
the APIs that Robert John put in the original time on by paper.
-->
And allows you to connect both to legacy and new solutions.
-->
And,
-->
so,
-->
I think that's suffice,
-->
right?
-->
You know,
-->
just a high level,
-->
30 second elevator pitch.
-->
Why this,
-->
you know,
-->
why this is innovative,
-->
why this answers the call.
-->
Because I think that as a leader that helps set the stage for the writing of this proposal.
-->
But,
-->
I mean,
-->
obviously I'm wrong.
-->
So,
-->
you know,
-->
I'm just curious,
-->
right?
-->
I just need a few second elevator pitch.
-->
On what,
-->
what,
-->
what Rhonda feels like.
-->
Okay.
-->
I will find the elevator pitch to provide it.
-->
What else?
-->
I'm good.
-->
And,
-->
anything else?
-->
I assume,
-->
since you want to review it Josh,
-->
I'll just write all my responses in a separate document and send it to you for writing the proposal.
-->
so you want me to write it into the proposal and just ask me to look at it?
-->
Well,
-->
I won't look at the whole proposal.
-->
So,
-->
whatever works best for you.
-->
Just let me know.
-->
I don't mind either way.
-->
If you can,
-->
though,
-->
share it early and then that way,
-->
and I know it may not be complete,
-->
but I can at least start reading it.
-->
and I'll make some changes too,
-->
unless it changes like the subject or it changes,
-->
you know,
-->
drastically,
-->
then I'll,
-->
I'll send you a comment.
-->
Make sure we have editing turned on so you can see those comments and changes and stuff like that.
-->
Right.
-->
Just like,
-->
if you're writing a paper or,
-->
you know,
-->
in collaboration with somebody else.
-->
Yes.
-->
Okay.
-->
All right.
-->
Sounds like we have a plan.
-->
I will come up with an elevator pitch.
-->
Logan's going to start writing to the
-->
section.
-->
Hopefully,
-->
if we have questions,
-->
we will beat those
-->
over to Smiley and the team.
-->
And Josh has been review
-->
as we come along and confer with Logan
-->
as we
-->
move forward.
-->
Is that what I'm understanding?
-->
Works for me.
-->
Sounds good.
-->
All right.
-->
Josh,
-->
do you want to call separately or stay on?
-->
I can stay on.
-->
Sounds good.
-->
All right.
-->
You're not needed here anymore.
-->
You're not needed here anymore.
-->
You're always needed.
-->
Logan's not here right now.
-->
What was that about, Rhonda?
-->
I mean,
-->
seriously,
-->
I just asked for a quick elevator pitch
-->
and you threw me into the bus.
-->
And then right before that,
-->
I don't care what,
-->
you know,
-->
I'll ask Josh,
-->
but then I don't care what he thinks.
-->
I mean,
-->
Rhonda,
-->
I'm trying to help here.
-->
So I don't understand.
-->
I don't understand what was wrong with my question.
-->
I don't understand.
-->
I just don't understand it.
-->
Josh,
-->
I don't know.
-->
You're absolutely right.
-->
Not like my wording on the first part,
-->
on the second part.
-->
I wish that everyone on the team
-->
had an elevator pitch.
-->
I wish that Bebe had an elevator pitch.
-->
I am struggling with consistently
-->
trying to describe what I believe is innovative
-->
and having the sense that time
-->
could almost spot on a regular basis.
-->
And when I describe what I think is innovative,
-->
being told,
-->
no, that's not innovative.
-->
And it's not just from you.
-->
It's from others on the team
-->
and I don't like being put on the spot anymore.
-->
I get it.
-->
But I wasn't trying to put you on the spot.
-->
No, I get it.
-->
But at that time,
-->
you asked me a question,
-->
you asked me what that was all about.
-->
I have answered you.
-->
You have.
-->
But again,
-->
I wasn't putting you on the spot.
-->
I wanted to hear from the VP
-->
what her thought was.
-->
You know,
-->
quick, here it is.
-->
Because I want to make sure
-->
that from a high level,
-->
the rest of the team is getting aligned.
-->
You know,
-->
again,
-->
it's not to put you on the spot,
-->
tell you you're wrong,
-->
or anything else like that.
-->
You tried to get my attention multiple times.
-->
I get it.
-->
No, I get it.
-->
And you just said it too.
-->
You just said it as well,
-->
where you wish they could all give an elevator pitch.
-->
But it's not that the team
-->
is not aligned again.
-->
I want to make sure we are aligned
-->
with what Rhonda says.
-->
This isn't,
-->
again,
-->
it's not the team that I'm talking about here.
-->
I am talking to make sure,
-->
here's Rhonda's vision,
-->
and let's make sure we follow it.
-->
And then I get shit on.
-->
And I'm trying to help you.
-->
I wish you didn't feel that way.
-->
This is the response you gave me.
-->
And then you tell me how,
-->
like,
-->
it doesn't matter what I think.
-->
I get it.
-->
Guys,
-->
I regret the words I used at the beginning of the call.
-->
Yeah.
-->
I hope that I return to that subject
-->
and left space for that.
-->
And I feel very respectful
-->
of the way that you respond to
-->
and turn my attention to your standard
-->
and your capabilities
-->
and not the way
-->
that I potentially would do things.
-->
Again,
-->
I'm never trying to put you down
-->
or put you on the spot.
-->
I'm always just trying to help you.
-->
And you as my manager,
-->
that's one of my jobs,
-->
is to make sure I'm helping you.
-->
And that was all that was.
-->
But I need to get a cigarette.
-->
Real quickly,
-->
Dylan reached out to me
-->
because he noticed I was in the document.
-->
And I didn't.
-->
And so then he started complaining about it.
-->
And then again,
-->
I'm hearing him helping you
-->
because he doesn't want to put all your fluff
-->
that he calls it in the document.
-->
And I'm like,
-->
well, Dylan,
-->
I don't have, for instance,
-->
a lot of these things set up.
-->
So we're going to need to know
-->
the prerequisites and things like that.
-->
That's all I wanted to talk to you about
-->
when Dylan is...
-->
I didn't reach out to him.
-->
He reached out to me
-->
because he can see I'm in his document.
-->
And then second of all,
-->
again,
-->
hearing him trying to defend
-->
and help you
-->
and deliver your message to the team
-->
that, hey, look,
-->
this is why she's asking for this.
-->
This is why she's wanting this.
-->
And here is why I'm telling you
-->
we're going to need to do this.
-->
But again,
-->
I need to go get a smoke or coffee.
-->
If you need anything else,
-->
just send me a message.
-->
All right, bye.
-->
Thank you.
-->
Good morning.
-->
For those that are already on the call,
-->
give it another couple of minutes
-->
and get started.
-->
Good morning.
-->
It's me, Ben, Aaron, and Lislet
-->
in this room here.
-->
Awesome, awesome.
-->
Okay, here we go.
-->
Hello.
-->
Can you hear me?
-->
Hey, good morning.
-->
Hey, good morning.
-->
Hey, my,
-->
the address is destiny for passwords.
-->
Really?
-->
Let me look,
-->
let me look at that right quick.
-->
Good morning.
-->
Usually when you were just
-->
to get to the desktop,
-->
you should have set up all passwords.
-->
Is this the same one?
-->
Yes, so just use the same one.
-->
You can log in here.
-->
Let's see if I can get this
-->
link here unchecked.
-->
It's really weird.
-->
It's asking for a password
-->
because mine never,
-->
never does,
-->
but I have the teacher one.
-->
I don't know if that's any different.
-->
Yes,
-->
every participant when they register,
-->
they have a set of passwords.
-->
Okay.
-->
Login credentials.
-->
Yes, that's why I always encourage
-->
to make sure to write them down.
-->
We'll get Aaron in a couple of minutes.
-->
And then we will get started.
-->
You know,
-->
this morning we are going to
-->
build a more complicated flow.
-->
I feel like this data flow,
-->
this data flow will resemble
-->
a lot of work that we see within 9.5
-->
where we're bringing in data,
-->
we're converting,
-->
we're ETLing,
-->
we're converting a CSV to JSON,
-->
you know,
-->
things like that.
-->
So this is going to give
-->
a really good hands-on,
-->
you know, for that,
-->
we're going to this time
-->
dive into some controller services.
-->
I went over a little bit of that,
-->
but I want to make sure that we,
-->
you know,
-->
get that going.
-->
Aaron,
-->
I see you've rebooted the machine.
-->
Hello, guys.
-->
I have the same issue.
-->
And she rebooted
-->
and I let her log in.
-->
Am I trying to password
-->
that I had to do before?
-->
No.
-->
So I'm doing the same thing she did.
-->
Okay.