At the moment Ohh, I'm sorry ohh,
I'd be quiet Ohh no, I'm sorry
yeah, my dogs are barking and so
I apologize. I'm getting excited. I yeah,
we're kind of we're remodeling my office
space so I'm sitting in the other
room and I have no way to
block them so.
So if I have to, I might have to walk
outside or let me just pause and scream
for a minute. At UPS, So
I apologize. Um, no, I think so far thing
I think it's OK. Like I said, we have
kind of the back burner work. I think
that. You know, since we
can kind of start making a dent in that,
that'll be good. Um, OK, I might have
some time again. I think after I finish
this flex, we'll see. I mean it. It's
just so hard to schedule not knowing, you
know, how fast and furious everything
comes in these days.
Ohh, so OK. And we've got,
um, you know, coming up very
soon, we're gonna, we're gonna have
that, um, big gaze practice test
sales task to really get going
on. Um, Cat reviewed our, our
demo with the, the larger team.
Um, ASD and and customer service and, um,
NIT they, they, they want to make a
couple of tweaks to our mock up, not
nothing too, too crazy. Um, and then and
then we can get started on that. So I
think that that we can talk about, you
know, how we wanna set up the JSON file
and then how we want to develop the UI I
think once. We get that the, the, the
model approved. I'll, I'll set up a
meeting with Brian D and the three of us
so that we can talk about next steps
because part of this is gonna be um, kind
of a new feature coming online to support
basically access through the cart and the
way we wanna do it and. They've
already started writing stories to beef
up some API's on the back end so that
basically, um, you know, the user and
angular can be clicking buttons and
adding things to their cart and and those
get, you know, kind of passed through to
the to the to the cart functionality and
CIS web. And that we can kind of and that
it actually it's gonna be two way
traffic, right. That we can pass through
with the user's doing and that we can
reflect on our end what's currently in
the user's cart and that's gonna and
that's gonna affect our UI. Mm-hmm. And
so, um, Brian was working closely with
Cat to develop those stories with the
back end team. So that. And So what I'm
thinking is that that he.
He's going to be involved somewhat in how
we, how we write the code in Angular to
use that API and, um.
I guess what they decided is that, UM,
you know, the first time a user clicks
the button to add a practice test to the
cart, we'll check and see if the user is
logged in and make them log in right
there if they're not. But once they're
logged in, they can keep the goal is that
they can keep adding things to the cart
without being taken to the card every
single time And, and so, so we'll. What
I'm thinking is that we'll be kind of
building this, this page, um, but you
know, with us doing some of the work,
with Brian doing some of the work and
then, um. And then we can
use this functionality in the future
because more and more stuff is going to
get moved to Angular and and come out of
CIS is the goal. So, so I think, I'm
hoping we'll have a lot more clarity
around that next week. Ohh.
But that's gonna be once that, once
that project picks up, that's gonna be
a lot. Um, and so.
That that will, that will happen next
week, um. So let's
see, So I know you're breaking away some
stuff right now. Michael, how do I, I'm,
I'm sorry, Matthew, how does your
workload look, do you, do you have enough
to keep you busy at the moment?
No, actually I was looking at that,
that ticket, um. Diane
mentioned about the old pages inside the
guest gaze test, Um.
I don't feel I'm I'm pressed on that
cause it says it's TDB and um.
We feel right now I can move on
and yeah, ask more questions on details
and then keep going. But um.
Not sure. If I need to.
Pressure on it.
OK. So you, you think you need to spend a
little a little more time with that one
and and get it a little more so you can
ask, you can ask some more questions.
Um, yeah, I'm still, I'm setting up
on the environment to develop that just
using proper credentials login. And yeah,
I got there and I was just
looking at the dull pages. Yeah. And
I'm investigating the how, what kind of
APIs inside the iframe.
So the yeah, using
um. Ohh, good.
OK, good. Yeah.
I think you could keep going here.
OK, excellent, Matthew, thank you. OK,
that's good. And then Dan, getting back
to your point there about kind of like
the, the, the this idea that we have, you
know, kind of our backlog and some of the
stuff that we wanted to do. I think, UM,
maybe maybe next week I wanna spend some
more time into sort of formalizing that
and building a list. I mean, I know that,
I know that it's sometimes you, you can
get. Started on something like that and
then have to put it on pause or whatever.
But I think I'm, I'm hoping we have some
capacity to, to go through some of that
because there are, you know, we, we've
had a couple of topics come up, um, you
know, like, like making sure that we can
get more of our pages into the JSON
format that if, if some aren't there yet,
I know at some point we want to. Optimize
a little bit better the way we have all
of our our test dates and reporting
dates. Set up, maybe we can kind of
take a step back and see OK, like how
many different schedules are there out
there? How are they linked to? How do
they display or are we, you know, are
they currently like?And it is as
efficiently set up as possible. Or should
we, or should we take this on as a big
project and make a conversion so that
everything's easier to handle in the
future?Like that would be
my #1 because like they added, like
something added last week with series or
New Hampshire, I forget, um.
And every time they pick up from a
program, they match that program setup.
So regardless of what we've been using
for Ness, it's like, ohh, no, they did it
this way. So we have to keep it this way.
So the so now we have like just wording
changes across the board for different
tests and different exams and, and it
just kind of goes against how. The
original program was set up. So in my
opinion, she's gotten very sloppy to
maintain and follow. Um, and I just think
it's gonna get worse because of the way
it's thrown in. And usually, like I said,
and it doesn't, you know, it's always the
last minute, it's always like, ohh, no.
And then it's got a match, you know, and
then the matching of different wording.
It's just gone, Yeah. I mean, it's got a
little bit better handle on it, but still
I feel like it's not error proof or and
then they're taking like what used to be
just the score report row and they bring
it it it into the test dates rows. Now
what used to be like a common test states
are now custom. So it's yeah, that whole.
Test states, test sites, score reports, I
think needs to be addressed and can be
done better. Yeah, it can be a lot more
straight, you know, streamlined, I should
say. Yeah, yeah, because we do. I know
it's like the more, the more exams we
bring into the series and, and whether
we're creating them from scratch or
bringing them in as adoptions from them.
Well, but yes, there, there are like some
oddballs, right where, um, you know, for
some of the languages and some other
exams that have like a just that follow a
different pattern. And, and so if, yeah,
you're right. If, if, if we're like doing
whatever we can do as quickly as possible
to get it out versus like thinking it
through. Those can be too definitely
different situations with different.
Yeah. And yeah. And then like I said, and
now that they've started modifying the
test dates row in along with the score
reporting row, it adds another. You know,
they could, it could almost have some
shared commonality, but it doesn't in a
way that it used to. So anyway, yeah,
that would be. Anyway, that's my two
cents. And then of course it. It affects
like the dialogue windows that open
because each one has different verbiage
there. And again, I like to just keep it
all in a test dot JSON format. This way
it'll be easy to update, easy to
maintain, and then they could say
whatever they want, you know, And on each
page, on each pretty much right, it gets
that there could be some common defaults
like we do. Almost for every other
program, like we have a, you know, here,
here's your score reporting one score
reporting 2 as they might change
whatever. And you kind of have those
outlines, um, and then they kind of
applied throughout. But this one is that
these are a little bit different. What
series has gotten a little bit more.
Just kind of especially with like the New
Hampshire a little bit different, but
different ones. Like I said, it's it's a
you know, it's there, it's working. But
yeah, as soon as we have time, I think
that would be a good use of redoing some
of it. And I did start, you know, I think
I have to pull it down and see what far
as I got use an AI and. API's
working well for me. I just feel like I
have to, you know, you kind of, you also
have to know AI when you tell it no,
that doesn't, you know, make it easier,
you know, and then it'll come back and be
ohh, OK, of course, you know, because it
seems like it'll give you the most
complicated fix and I love math. Know
what Matthew and I will look at the stuff
that you write sometimes and it's just so
simple and clean It's like, um, I don't
know all those shortcuts though, but the
stuff that I write really Ohg well,
YouTube Brian yes, but Matthew yes, for
sure all this stuff Matthew writes. OK, I
was gonna say yeah, that was saying any
sense? Ohh yeah yeah yeah no, some stuff.
Matthew's been writing it. It's just so
clean and, uh, you know, simplified and
some of the stuff I get back from AI when
I'm writing it, it's like, what? Ohk, OK,
you know, and you know what that leads me
into, into something else too, Diane,
Because I mean, we got those e-mail. Was
it today or yesterday from Ali Bebo about
this other new learning platform. No.
Did you guys get that? Yeah, I didn't
read it. I think I got it, but I didn't.
That's um yeah, the next installment. OK,
so this is yeah, cause it went on, but
there's this thing called the learning
hub powered by Degreed, which at the
moment is down because of Azure.
But apparently it's like another learning
path and, and skills kind of, I don't
know if it's courses or whatever it is.
So I mean, we have those LinkedIn ones. I
don't know if those are still available.
Maybe. So I'm, I'm meeting with Dan on
Friday and I'm gonna ask that like.
Janet or Janet and Wyatt or somebody
provide some clarification into what this
is supposed to look like. Because what I
would love is to work with everybody and
say, OK, what, what, what do you all want
to learn? Where do you want to upskill?
And, and, and like Diane, what you're
saying, you've learned a ton about, you
know, how Angular is, is set up and the
kind of JavaScript. It's used in Angular,
you're just using TypeScript versus. But
if you had, if you had the opportunity
to, to say twice a week, spend an hour
going through some lessons and, and, and
building up skills a little bit, you
know, should that be a thing? Should we
say, OK, everybody work with your direct
reports, See if there's something they
want to learn. Look through, look through
these. Questions that we have offered
and, and make the plan where it happens
and you and you check in regularly and,
and, and set aside time during the week
to do that. Like I would love because
what I've seen is this kind of stuff gets
introduced and I've gone to some of those
overall peers and meetings. Then they
have some for managers too. And sometimes
in the chat people ask like, well, how
does this work?So I take these classes
when I'm at work. When when do I do this?
And the questions never get answered.
So I think if they just, if they just
like send these emails at us but don't
tell us how to do it, nothing happens.
It's, it's been my experience, like I
haven't taken any of these yet.
Yeah, I too, I I kind of block out where
I was going to do the TypeScript every
week, but I don't know which just never
happens. I know, right. You have to
really dedicate, you have to say this is,
you know, I'm doing this and see that
that's what that's what I want some
guidance and some support on like from
the business saying, hey, like this is
obviously important to Pearson. I mean,
I'm sure setting up all of these
resources took effort and cost, but like,
how do they expect people to use them?
And then that way we can, we can like, do
it as a team. You know, we can say, OK,
hey, everybody, we're gonna set aside an
hour Tuesday morning and an hour Thursday
morning, and that's your time to take
your courses. And then we can, we can do
like something like maybe. You know, you,
you would be taking some that are a
little further advance, like Brittany has
expressed some interest in learning more.
Maybe, you know, she she needs to start
at a, at a, at an earlier stage than than
you would hop on on. And, and like people
can who are at like the same level, can
be doing the same things and like spend
some time, you know, going through the
courses themselves and then talking about
it afterwards. Like, ohh, you know, how
did you, what did you think? What do you
think about this? I didn't quite
understand that. Do you know, how do we
apply? You know, just so we kind of build
momentum around that. And then I think we
could, you know, and when we can have
Matthew kind of help with that because
he's got all this, this wonderful
experience that then we're seeing, you
know, like you were just saying, I like
how if you really know. How to do this
stuff, how elegant it can be sometimes,
how you can come up with a solution or
something that's just really graceful and
easy and it's built in and it and it's
maybe it's using some type of JavaScript
that we haven't seen before. Yeah. Which
just seemed refreshing, even though we
see it all the time sometimes just going
back to the basics and kind of refreshing
on, you know, when writing it. You know,
it's just something like that even, you
know, just kind of. There's
a lot, I think, yeah. And and I think
and, and not be useful. So I would like,
I would like, I'm so I'm gonna talk to
Dan about that on Friday. And if he asked
me to like reach out and ask Janet, I
will. But but I, I think something coming
from them, we would sort of set a policy
that we could then follow. And that's
ultimately that's what I would like to
see. So I guess I've got a couple of
things in the horizon. I'd like to do
that. Um, I think in next week's stand
up, I'm, I'm gonna, I'm gonna, um, you
know, pull up our spreadsheet and, and
what we can start kind of bringing
storming of those, the list of things
that we want to optimize at some point in
the future in the couple of things we
just talked about right here and anything
else. And then we'll start adding those
in his tasks. So we'll do that. And then
I also want to talk a little bit more
about like VR's and code reviews. I think
I think it would be a good idea for us
to kind of beef those up a little bit
where somebody's actually looking at the
code and making sure that things make
sense as opposed to just, you know, just
simply accepting. Now sometimes the very
straightforward, it's a little update.
It's a. Bring change to a JSON file or
something and that's, you know, no big
deal. But for the ones where we're adding
a feature or the code is a little bit
more complicated, I think it would be
good to have like, um, to put a little
discipline in place where we're going to
look at and really making sure that
things look OK. You know, you can't
always, of course, catch an error by
looking at somebody else's code, but. But
maybe there be a reasonable question, you
know, the dying, if you look closely what
Matthew did or vice versa, or, you know,
there's a better way to do this or, you
know, this might interfere with this or
that or ohh, gosh, this, this affected a
lot more than we thought this task was
going to. You know, can you look this
over with me or maybe even run my branch
yourself locally and just see, you know,
before things get accepted? And I know
sometimes we're under the gun and it's
not always going to be perfect. But I
think probably something like that makes
more sense too. Well, I think you're
right, because that is the purpose of
having another person approve it. It's
just yes. But you know, the whole idea is
that we're looking at the code and trying
to catch anything that might. Not
to say correct the code, but yeah, trying
to catch something that might not work
that would that is mostly the idea, yeah.
Why we do that. Yeah, yeah. So I think, I
think I'd like to, I'd like us to talk
about that. And Matthew, do you have
experience with that from in some of your
former positions? I don't know how, how
how are your processes when you submitted?
PR's did was there was there more of
a detailed review or when when you
reviewed another person's PR's, what
would what? What's been your experience
there?Well, we,
yeah, we always edit the default
reviews and and, um.
The most relevant person at at
this review and yeah.
Just to the divide each
other, uh comment on each
line. Uh.
Yeah, pretty structured review process.
Every pair went through the at least one
period. Yeah, for merging.
Like 1 feature or fixer type with
the clear contacts in description so it's
easy for someone else to follow up.
And when I review others PR I'll
focus on that logic like that's the
code make sense. Is it easy to
maintain later?I think, yeah, it's
more about helping teams so you can sit
down and catching bugs early. And
if someone drops like 2000 lines in
PR on Friday afternoon and you'll just
quietly agree to review it?
On Monday.
That makes sense. Yeah, yeah. And then
that's something else we could do. I I
think too is maybe kind, it's in certain
areas beef up the commenting in our code
to make it more maintainable. And and so
that, you know, if we have to go back and
touch something we haven't looked at in a
while, we will have our comments in
there. That kind of tells us ohh, yeah,
that's that's why we set this up this
way. That's why this runs the way it
does. Or to use A instead of B here or
something like that. Uh,
yeah. I wonder if, umm, I know Brian
Daubeny doesn't. Did you ever do that,
Matthew? Did you sort of did you how, how
did that work in your former positions as
far as like inline comments in your code
and that kind of thing to kind of explain
what goes where or did or did you do that
outside in documentation?
Ohh.
We actually did pretty often. We try
to keep comments meaningful, not just,
uh, restarting the code, but they're kind
of explaining the why behind what we
are doing. Don't use
specific algorithm or some logic to
handle data each or you know, kind of
cases. I would drop a quick comment
saying why the choice made sense at the
time.
At the time the I review, yeah, I
think that's a good idea. Yeah, that will
also help pull like we can do a
code rabbit.
Just open the eyes of copilot,
uh, GitHub Copilot. Be helpful for
that as well.
Ohh, that's true. Yeah, that's very true.
Ohh gosh. And I have to um, that's right.
I have to go back and, and, and make
sure that we can all get that right in
VS Code. So only put that back on my
list. I forgot about that. OK, yeah, they
can't hurt so, but I've noticed that.
Ohh, sorry Matthew, go ahead. Sorry, I'm
saying about that.
Um, peer review copilot, not that
views code 1. Um can see
the agent reviewing the PR and
yeah, leave the comments on the
GitHub PR chat.
Nothing. Ohh,
I see right? Yep.
Yeah. And I've noticed that,
um, like I, I didn't tell you that you've
seen more Ryan's code than I have. He
doesn't seem to leave a lot of comments
at all in the stuff that he writes.
No, she usually not. It's sometimes,
but not typically, No. Um, I
mean he has it with the
naming conventions that he uses because
he addresses the Jared number or
something like that. So if you
want to know more details about
it. But no, as far as the
code itself, he's given some, but not
typically. Um, I find AI is good for
adding comment lines in the code. Ohh,
that's good. Yeah, that's really, that
does it very. It does it really well. And
then it was interesting that we had a
tool that I used to work with a lot
with Brian. Which was the Angular DevOps
dev tool type of thing when you're in
inspect mode and you were able to really
drill down into the code and relations.
And they took that away from us. I'm not
sure why, but it was, I guess, ohh,
because it was the browser add-on, right?
Yeah, it was the browser add-on. So that
went away. So using AI, I was able to.
Built in some of that information into
the files, um, you know, in the debug
mode. But I just left like the important
stuff that kind of takes the place of.
What that tool used to do. So yeah. So
I don't know, Brian. I don't think that's
a whole lot. I, I do kind of glance
over his stuff. I don't scrutinize it too
much, um, because I know he's working on
stuff that he knows more about than I do.
So. Well. Exactly. Yeah. Yeah, for sure,
yeah. Yeah, I yeah, I don't
try to scrutinize what he's writing too,
too, too much. But yeah, I, I guess I was
more thinking that, um, like if you
would. Like if he had some kind
of a pattern that we could then follow
that, you know, he had used in the past
that worked for him and that kind of
thing. But it seems like, um, I think
that mostly he doesn't. He just, he's
just so familiar and good at it that he
just like can look at it and see what's
going on and make updates from there.
You know if he does have to go back and
do more work on something. Like
he uses some AI too. Ohh. Does he
need to troubleshoot? Yeah, yeah. And we
get oh, oh, that's yeah. OK, we can
you know, we can definitely ask them.
Yeah. Like he just added the it's not
live yet, but he just added the home
page and answer or like a shutdown
announcement feature. So. Put that in,
yeah. I know they
had been looking for that. Yeah, yeah.
Again, you, you know, it's interesting
because after some of the code has gotten
especially for the states page, you know,
after rewriting a lot of it with the
AI, because that has so practically
rewritten since he wrote it, but not his
his initial. Modules are also there and
you know, and looking at AI, I was like,
no, this is, you know, tells you no, this
is good, this is good, that's good, you
know, and then we just built off of that.
So and then a I put in, like I said,
a lot of comment breaks of what sections
do what.
But yeah, you're right, I haven't. He
hasn't added too much comments. Now do we
want to do it on the DevOps when we're
approving the PR or if we're sending it
back for any reason, keep those
documented in the PR itself, like Matthew
was saying, on a line by line basis.
Is that something that?Yeah, I
mean, I guess there's, there's, there's
different ways. I was just, I guess my
concern was, um, kind of maintainability
as we progress on and, and you know, we,
we build a feature and it's there and it
works and, and we push it live. And then
sometime in the future we need to do
something with it, either add on to it or
tweak it in some way. Or build something
alongside it. I'm just thinking it's, uh,
it would be so much nicer to kind of go
back to that and have either some
comments or some description of, you
know, the tricky bits. It's like, like,
what exactly is this logic doing Or why,
why did we have to what's, what's this
whole separate clause about what? Where
we guarding, guarding against here? Ohh,
that's right. There's, you know, we have
to catch this case or something like
that. Um, you know, just to make
it more maintainable going forward.
I was gonna say, yeah, I that's a good
idea because I actually built stuff in
there that we haven't come to fruition
because the other thing is we started
with day of the test and that set and
then we built it out and then there was
those questions and now that's. So I
still have things like built into the our
files somewhat that. Yeah, you know that
there's other parts of yeah, like you
said, there's, there's codes in there
that now is is irrelevant. There was some
today I just got rid of because it was
like I, we haven't used this in a long
time. But then I was like nervous about
getting rid of it because I'm like, I
don't think we're using it. So I had to
spend a little time like just kind of
searching for terms. Yeah. So I think
that's important too when we getting rid
of old code or you know, or doing
temporary code. With something,
yeah. Like
so.
All right, so we've got yeah. So what I'm
going to do then is I'll add a little bit
more onto our agenda for our next Tuesday
morning stand up for Jason series. Stand
up. And because it seems like the, you
know, the immediate short term work we're
doing really good on. And so, you know,
we know that coming up, we've got a
couple of big projects and then we we've
got we wanna get this list. Together so
that we can be tackling some optimization
tasks that we think are going to save us
a lot of grief in the future.
And so I'll make sure we talk about that,
um, next Tuesday and then, OK. So I
think, I think we're good then for, you
know, for the very short term right now,
it sounds like things are, things are in
good shape. And then, um, like I
said when we first started chatting a few
moments ago, when we, when we, I, I'm
hoping that we'll have requirements
finalized by early next week for the
Georgia practice test sales and then
we'll be able to flesh out our stories so
that we can get going on that work
because that, that is a big one.
Alright, be a short term right?
Now I know that's going live on December
2nd. So that doesn't, Yeah. I mean,
basically the week of Thanksgiving is
probably mostly a wash. So that's gonna,
we're gonna have like like 3 weeks to get
that in place. Yeah. And I pushed back. I
didn't realize, of course, I'm always
scheduling time off when on these big go
lives. So I did push back and I changed
some of my time. Off. So, um, anyway, the
uh, thanks Diane. Yeah, thanks for
thinking of that. Yeah, if I could
probably gonna, I was gonna ask a quick
question regarding that, but maybe it's
set up the tracking. Ohh, yeah, no,
please do Yeah. Do we have to update
our policies across the board that people
are now being tracked?Across the
site we might what did we already look at
that part that we said we use cookies and
that was enough? Yeah, We. I know that,
you know, Pam has been leading this with
with with and including with legal and is
looking at things so I don't do you know
what what point I mean I know they're
getting the code in place to test it. Do
you know what?When did you do? You
were calling that conversation when they
thought it would be going live. Well,
they've already pushed it through. It's
in trunk. Well, yeah. I mean, I I know
the code. The code is gonna go live, but
it's not gonna do anything until. Ohh.
Gotcha. No, I don't know what the Yeah.
You know that that's a good question
though. I, I can, I should probably
follow up and ask about that. And because
I know we do have that sort of general
statement that, yeah, we do use cookies
for these purposes, whatever that's
already like in our. I'm not sure how
else it's worded, but yeah, wouldn't
surprise me if like a week goes by and
then all of a sudden we get an ASAP
request to update every single website.
Yeah. I mean, years ago when I worked on
website and then used the Google
Analytics and I don't remember the
details of it, so I couldn't, you know,
chime in and give any useful information
about it. But I don't know, I guess maybe
things have changed. But we never said
anything about using Analytics on our
site at one time, though it might have
had an icon come to think of it and
wonder, no, maybe. Yeah, I don't remember
a whole lot about it, but we used to put
Google Analytics on all our sites and I
don't recall ever making it known. Umm.
That that was being used at one time,
but I guess it's just similar to.
What Google Analytics would do?
Because this is just curious, yeah.
And I know, like, I think in the, in the,
in the EU, the rules are much stricter
around that as far as like allowing
people to opt out and that kind of thing.
And so, you know, if you see some sites
that are sort of worldwide, they'll,
they'll have that, that kind of stuff on
there. But I don't, I mean, there are
plenty of sites that, you know, you visit
that like don't, don't put a pop up in
front of you saying, hey, you know, you
can agree you're up that, you know. And
I'm sure people are using Google
Analytics, so I don't know what the rules
are. Yeah. Well, I mean, I was looking
at, I don't know if you ever heard of
Ruggles. You know, they like those
washable rugs. Ohh. Yeah, yeah, yeah. And
like, and I got on their website one time
and I looked at their privacy policy and
it was basically like, we're gonna track
wherever you go from our site, you know,
And it's just like. It's like that close
the window because ohh, jeez. Ohh yeah,
because they're they're they're, you
know, they're thing was so it seemed to
me so invasive, like I'm coming here, you
know, as far as tracking goes. And I was
like, OK, well, they let me know about
it, you know, and I did read that, so
hopefully I understood it correctly. But
they were kind of. Prices. So anyway,
wasn't gonna buy one. It's
funny, but I've just come back to you.
Just kind of the the amount of tracking
and do you have to be notified if you to
what extent you're being tracked? I don't
know anyway.
Now that is a good question though. Yeah,
I should, um, should probably follow up
with like, cause I, I think Pam was
leading that one yeah, she did bring I
think too And our first meeting with her
she, she did bring that up and I think it
was one of those things that we didn't
have the answers for her, but something
she was gonna look into and I thought
maybe because. Mistake. We use cookies,
that was enough, but I don't know if this
is the same or not.
No, I I don't either. That's a good
question.
Alright, um. So I think
we got it done. Sounds good. Um,
alright, so I'll let you both go Um,
but obviously anything comes up, just let
me know, um, and then we'll talk more
as the week goes on. What is today?
It's already yeah, it's alright.
Wednesday. Yeah, today is Wednesday.
Wednesday. Yeah, it's gonna be Friday
soon.
Yes, Matthew, what do you got? Uh, so did
you check the e-mail from Mac? Ohh.
Have you got the day before yesterday?
Saying they're planning to.
The review on the series HTML score
reports.
Ohh yes, from Meg yes, I, I, I will
be, umm, I'll be replying to her today,
Matthew. What I'm going to do is, um, set
up a meeting for me and you and Meg
to kind of go over what we've got in
place so far and then I have to remind
myself what the. Other initiatives that
she was working on are going to affect
the HTML score report. Basically, there's
going to be a, um, different kinds of
add-ons that get added to the end of the
score report in certain situations. OK,
and So what they wanted to do was have
the HTML score reports go live 1st and
then they can start doing these other
projects. Uh, that's my understanding,
but I wanna talk it through with Megan
and remind myself kind of what's where
because there been so many initiatives
recently that I want to make sure um.
That I understand exactly what's going on
and get the details correctly. So yeah,
thank you for reminding me. I'm gonna,
I'm gonna reply to make today and then
we'll meet with her like, um, Thursday or
Friday, OK?OK.
Please add me and Diane. I'll probably
add you on. I'll, I'll, I'll, yes, yeah,
yeah, Matthew, I'll include you
absolutely. And Diane, I'll probably add
you in that meeting as well because it
will, it will most likely affect our
Angular code in the future.
OK. Now I think the conversion of series
score reports to HTML is going to be
interesting, right, Because we have
serious exams on CCS sites and on Angular
sites. So I'm not sure what the roll out
of that is going to look like. It was
easy for Georgia because it's Georgia's
only Georgia. I shouldn't say it was
easy, probably had a lot of work to do.
But but but at least it, you know, kept
it contained. Ohh. And this will
not be the same as what he already
developed. It's not pulling off what he's
done. It's not. It won't be at all. Yeah,
it won't be at all. Yeah, yeah, yeah.
Interesting. Because the series really,
except for like 1 new case, doesn't have
that Tesla model. They don't have this
idea that candidates get like, different
kinds of score reports.
Yeah, so.
Should be interesting. Yeah, that'll
that'll end up being a big one.
Seven, I have a quick question I'm sorry
Brian, I don't wanna get no, that's OK,
that's real quick. Um, so we have this
task that evidently they've been working
on for eligibility requirements. Brittany
talked about it to having some delay
issues with getting it work for series
yes so. I put
it back on her to, you know, to hold on
to it. So we have a go live date. So she
made a new go live date, but it still
says pending program team update.
I don't know if I should do anything with
it or just wait until we have a definite
date just I mean it's already out there
and we've been testing, you know it's on
test trunk and test. And is it is this
for us this is mostly affect the Alaska
State page or does it affect the test
pages too?Um.
It's I think, I forget what it was.
I think it's all of it, but it's
the 890 for Alaska. Yeah, I'm sorry. It's
the Alaska 890 where we edited. You're
right, it's eligibility requirements, but
it affects the build because we had to
build it in. So it is. Yeah, this
is this is tricky. Kerry keeps. Looking
to meet with it because they they keep
kind of not meeting their deadlines
because it's tricky for them all the
different teams to implement yeah, but
but yeah, this is just you know the
background Diane, this is you know that
Alaska is is going to be using.
A bunch of series flexes flex yeah. And
so that that in order to register for a
flex exam, you have to be eligible. And
that means you have to have taken the CBT
and scored within a certain amount of the
passing score. So just barely not passed.
And so the system needs to recognize so
on the series site if a user goes in
and starts registration. This the system
needs to recognize that this person has
tested for Alaska before and has achieved
a result close enough to the passing
score in one of these tests to even
to even see it as an option to
choose from on the test selection page.
Ohh. Yeah. Yeah. So that that's the
tricky part of the coding. Yeah. And and
so for us, it's it's just kind of getting
the content in place to tell, to tell
people that, yeah, you know, this, this
is your, this is an option for you,
right. It's basically, it's basically
aren't. Yeah. And so wasn't there. Is it
like 11-4? Am I remembering correctly
that they thought they could have it for
that's the new date? Yeah, Yeah. Yes,
because I have other stuff for 11
for now too, um.
That I just put out today, whatever it
was. Ohh, right start. Yeah, but that now
that might go sooner. It's at 11 four
soon, so I don't have no idea what that
day's gonna be. Um, if they decide they
wanted to go sooner than 11/4. Alright.
But actually what you just said makes
sense. It's possible the build would not
have any bearing. The build changes have
won't have any bearing even if they went
live as long as I don't put the state
page. Live or the program page, whatever
it is, um, JSON file that
might. Not have any bearing
on the build itself. That's the. It's the
build files that might I find, um.
Sometimes could be a little bit of an
issue. Coordinating changes OK. All
right. Well, thank you that. That might
work. Yeah, I hate to put it
in an 11 four build when I have other
stuff going out on 11/4, right. I know
it's it's tricky, right? Because I mean,
that's yeah, I'm looking I'm looking back
at a chat thread now and yeah, she said
that the new target for this is 1144, but
that's, you know, they're the teams are
gonna try for that, but it may or may not
happen. Yes, yeah. Hold on to it until
we get closer. I think it as long as
I get it out there for them to test.
Um, I think that's yeah, yeah, I think
that's OK.
Alright, yeah. So yeah, it's in the ASD
is really pushing on, you know, when can
we tell the client this is gonna happen
and it's. So it's getting a little
tricky, yeah. Yeah, that sounds
complicated. Yeah, this one is
complicated.
OK, uh, well, I do have to scoot now.
Dan's pinging me about something, so I
gotta go see what this is. Um, but thank
you both very much. Uh, Matthew, yeah,
look for that e-mail. I'll respond back
to Meg and then I'll invite you to, to
that meeting. I'll either set it up for
Thursday or Friday, depending on when
people are available. And do you know, I
do that one as well, But like I said,
it'll be all you know in our. Files and
that kind of stuff. OK, thank you. OK.
I'll talk to you both soon. Thank you
both. Thanks. Bye. Bye. Bye.