Well, good to prime time. We're at the top of the hour, so go ahead and get started.
Um, this is your half hour. Sometimes hour, sometimes 45 minutes.
Depends on how chaotic things get,
Uh, section where I answer your questions about Resonate.
So if you drop the questions in the office hours, uh, questions thread.
I've linked it everywhere that people usually post questions, Um,
that aren't the correct place so that you can get questions in the right place.
Um,
someone is saying that I'm muted. I'm not muted.
Uh, if you can't hear me, I'm going to be very sad.
Uh, if someone else can hear me, do make some noise, let me know that you can hear me.
If no one can hear me, then,
OK, One moment. Here.
Hello?
Hello.
Am I there now?
Hi. You can hear me. Great. I had so much I was talking about. Oh,
I'm so sad. No one heard any of that.
Like most of it won't be on the recording either.
Cos it was before I started recording at the top of the hour.
Anyway, welcome to prime time, um, questions and answers for resume
um, get your questions posted in the question thread.
I do see some posters, so we'll go ahead and get started, right with those.
Great to see so many people here, uh, hanging out. I
see lots of familiar faces. Let's get going with questions. Um,
uh, So rhino rule says, uh so prime. How does it feel? Uh, that all the other rafa
hours are fairly quiet, but yours is always full of questions.
Uh, I don't mind. Um, I'd like that to change at some point.
Um, it's just the other ones are quite focused.
So moderation is like, purely like, you know,
uh, Santa's naughty list who's been bad or good,
uh, with stuff related to that. So, like, it's it's,
uh, you know, it's it's natural that that one has less,
um, rendering, um, like graphics. Um uh, at Gaines's office hours.
Uh, that's usually more technical questions,
cos the rendering questions get quite technical, and shades are very technical.
So, like, that's fine.
Um, Chromo does theirs, um, like sporadically as well?
So that's why there's there's not many questions, but mine is like, you know,
always we're always here.
We're always happy to answer
whatever
whatever's going on.
Uh, so, yeah, it's It's It's fine. Maybe one day it'll be less busy. Uh, snoop
says currently you're not able to remove contacts that haven't migrated.
Are there plans to allow that? I think there are.
I get confused.
Cos there were a couple of issues as we stood up our infrastructure in that mind, Uh,
we had, like, a fixing job that was gonna fix contacts.
I need to double check on the status of that.
Uh oh.
Ultimately, yes, though,
uh, Luna, Oscar. Any updates from when we can expect the wiki to be available?
No, I was about to say before the end of the year, but, like, uh uh,
but we're not having, like, I'm not having a good month for, like, just random work.
Adding in that that jumps around the priorities.
So if I said before the end of the year,
I'd step outside on my next dog walk and like a truck would hit me or something.
So I'm I'm not gonna give you a time.
Uh, as soon as we can get it done and we'll get it done
right.
Moving forward to Tiki's question,
how can I change the size and position of my hand colliders.
Changing the grab area collider doesn't do anything.
I'd have to look into how those are generated again. Cos I have forgotten.
I will open up the code base and if I have time, I'll take a look.
Otherwise, I'll DM you the answer Once I'm done,
I closed it, but I don't remember why I closed it cos I had to open earlier.
My computer didn't restart. I don't know.
Um
she
says that they forgot that you joined the stage and they heard Hello, it's
geographer.
Uh,
we had a requirement ages ago on a Gary's mod server that I helped run
that if you wanted to be on the staff,
you had to have a microphone and you had to prove that you had a microphone.
You didn't have to speak because we didn't want to like force people to speak.
But we had to, like, prove that people could speak.
Should there be a need to, um or at least that's what our our policy was.
We had a great person that just was mostly mute.
And I said, sorry.
Like, you know, it's my policy you gotta have a microphone just in case.
So the single word they ever said to me was Hello? That was it.
We gave them admin. Um, and they were a great admin on our Garry's mod server.
That was That was, like, 1015 years ago at this point in the,
uh, last prime time. Um, Tiki. Um uh uh. Let me see this again.
Tiki is asking last prime time I left on, uh,
the issue of my performance with more than one session being open, um,
or should be expected, can go down 25% with only 10 more people's session.
Would a bug report be in order? Absolutely.
Bug report Being able to make sure that you follow the format that is, uh, there
and just provide as much detail as possible.
Remember that The worst thing that can happen to a bug report is that we close it,
and when we close it, we're not, like, close it.
Oh, you're a bad person. Or close it.
Naughty, naughty. We're like, close it.
This isn't suitable for these reasons, et cetera. Like we still appreciate it.
Even if we do close it, it also allows it to sort of close in your brain.
It's like, Oh, OK, that that's not a problem. So yeah, always fill them in.
Um, do your very best to make sure that they are, as you know,
uh, understandable as possible. But if there are S step ups, that's fine.
We'll we'll just close them and talk about them.
Uh, I think your asks one. Will there be an open source? Pro
flux binding generator Just slightly waiting. Or is it planned? Um,
let's make sure we have a get up issue on that one. I'm not entirely sure that we do.
Um, I I seem to remember that we might, um I haven't found it or looked at it recently,
though, so let's make sure we have a get up issue on that one.
we can go ahead and discuss that over there.
Uh, I'm aware that that's an issue that is preventing, um,
uh, plugins and mods to some expect, um, aspects, uh, from making their own pro
flux nodes. So it's important that we get that one sorted.
So I I lo lost in, like, five discos by accidentally clicking discos.
Uh, Rucy asks what are your thoughts on mods?
Uh, that focus on bug fixes and not enhancements if mods wants to,
uh,
mod developers want to focus on trying to help the community
by providing mods that correct what is confirmed to be a be
on
github. How would that be interpreted?
Um,
I'm OK if you're doing that
on one side, but on the other side, like I,
I feel distraught that you're doing that because it's like that means that
in some aspects, we're not doing our job right?
If if people have to rely on a multitude of mods just to make the the application work,
Um, that's, like, distressing to me.
So,
uh, provided it's logged on the
github as a bug and that, you know, we know that we we can fix it when we're able to Yeah,
I got no problem
with Do also keep in mind with that that, like,
once we fix your the bug that's reported that mod
won't be needed and that might be a random day.
So if you wake up one day and your mod suddenly isn't needed,
please don't be disheartened.
It's just that we finally got around to fixing it
um, additionally, um,
one of the other problems I see when we have mods that fix bugs is, um,
people fix the bugs and then they go back to the the Bug Report and they're like, OK,
just so you're aware there's a mod here that's fine.
Sometimes it's like, just so you're aware there's mod here,
and here's exactly how I fix the bug and this is
like what you should do literally in your code base.
And I that, while can appear helpful sometimes isn't because, uh,
there is a sort of translation layer that goes through when you
go from non compiled to compiled when it comes to free extension,
et cetera.
So stuff sometimes looks a little differently.
We have to take in mind a lot more things as well when it's, uh, it's not a mod.
So maybe, um, the mod fixes all but
one case of that bug. And you weren't actually aware that there was more,
uh, another case of that bug occurring, but we were cos we had access to the source,
and we were like, All right, we fixed it in location one.
Location two, but location three. The mod left off, so it's not exact right?
So we still have to do that research.
And then occasionally it might be a performance problem
and our architecture problem where we can't implement it exactly
as the MoD says So provided you're not like coming back to the get up issue and going,
Ha,
ha, I fixed It is exactly what you need to do Absolutely fine.
The information ranges from incredibly helpful cos
there's some mods where it's just like,
Oh, that's where I can go fix that stuff or it's that easy to fix that stuff.
Uh, a good example.
Being like a long, long time ago when RT fixed the alignment of, uh,
some of the fields on inspectors, I'm like, That's all it took.
All right? I'll go do that. Keep it up and do it.
But do know that every single one that you publish, um,
makes a a kitten die inside my brain.
Cos I'm just like, damn it,
we should have fixed that. Damn it.
Um
uh Tiki. Wait.
That means grab Mod would not be fixed today, OK, if a mod exists to fix an issue,
but there is no
github issue,
then it's the same as the saying If a tree falls
in the wood and no one's around doesn't make a sound.
If we don't know about it, we can't fix it.
So if you have a mod that fixes an issue, make sure that there is a github
issue linked to it.
If you wanna be a, uh, proactive mod creator,
maybe add a link to the github issue that your mod fixes in that read me.
And that way,
people downloading the mod can see in the Read me what this fixes on our side.
And then,
uh, once the issue is closed, Uh, and it's linked in the read me, you can be like Cool.
Um, also don't, um, underestimate the power of archiving a github
repository.
So once we've fixed an issue, for example,
don't delete the mod just archive it right.
Um, at the very worst, that archived repository then becomes a sort of github
portfolio piece for yourself.
You know, it shows like, Hey, I did see shop programming at one point,
so I don't know, 20 years down the line or or whatever.
If you need to apply for a job that really needs harmony patching.
For some reason, you've got examples of you doing it,
so don't delete it when it's done.
Just just archive it or whatever.
Uh, for those who aren't aware, archiving a project on um github
means that you can't push to it or or change it in any way.
But all of the history is preserved.
You can still see the like, the effort and the work that went into it.
Um, lots of my repositories are archived right now because hey, Mixer died. And
like,
there's like API S and clients and SDKS that just
won't connect because there's no one to talk to.
You know, there's no line to get to mixer. It doesn't exist.
Um, funny story on that one,
months, months, almost like years after mixer died.
Uh, I was, um, still at Microsoft at the same, uh, at that time
and I was on the mailing list of people who would periodically email me and be like,
Hey, a mixer is still alive.
Can we kill it?
It was like, hilarious.
It was like we found another server running some mixer stuff. Please help us kill it.
But it's just like, oh OK,
I
think it was like, uh, the like search service or something was running.
It's like it's it's throwing errors. It's like of course, it's throwing errors.
It can't search for anything. There's no primary data, so it can't index from them.
Um,
etcetera, stuff like that.
Uh, shadow
says are are there any plans for anything related to cloud variables? Um,
yeah. So, um,
the amount of commands that you have to send
to the resonate bot right now is getting unwieldy,
right?
It's good,
because we can just sort of hammer more in and you can get more functionality,
so we're probably gonna keep doing it.
But it would be great if, like,
most of the stuff that is is sent to the Resonate Bot right now,
we could make U I or or panels or settings, which it's for right,
um, a good example. Here.
Um, I don't You know, I don't want to talk about settings, et cetera,
but it is like if you go over to the settings panel of for example, discord,
there is just so much there that you can change.
Uh,
can you imagine if a discord, you have to, like, message discord Bot
and did that. So it's not ideal.
So we want anything that's like in that resonate bot to
maybe have U. I maybe have some sort of smoother experience to doing that.
One of those is cloud variables where it's just like maybe there'll be
a U I at some point that makes it easier to create them.
Um, and you know,
it would utilise basically the same API S under the hood that those commands run,
but it would be driven by some U I or something. At some point,
I think they'll be a lot more understandable when they're not commands.
Um, I also think
I need to open a bug report on it,
but I think there's like one or two bugs that are preventing
me from from using cloud variables in ways that I like,
um, which are mostly memes.
But I'd have to look at that cos it's been a while since I've looked at those.
I remember when I got, like,
completely confused writing the Cloud variable Wiki article.
I just like I don't like there's too much stuff here.
They are incredibly powerful,
but because they're all driven by those commands they're kind of confusing.
Sometimes
that's all the questions I see for the moment.
Uh, if you have any additional questions, please do let me know.
Uh, lex, uh, asks, uh,
what decision making goes into completely reworking your SNET
system versus fixing parts of the current system.
It's a little bit difficult to figure that one out.
Um, I know that, like settings, you know, it's under rework. Fri is working on it.
Um, but occasionally we would add a new setting, et cetera.
You need to read our how we prioritise features to sort of understand that one.
That is the document that we put out. I think it was
last week. It was last week. I was just talking to Cromer about this.
So I was like, My brain hasn't decided that it's a new week and we're on Tuesday,
so it's a bit of a problem.
So I'm trying to, like, convince my brain.
Hey, it's a new week cos I, for some reason still think it's Thursday,
Friday last week.
Um,
it's it's basically that, though, like, isn't it? Like, let's do a worked example.
Let's say,
um, because we don't have a setting,
Uh,
someone is having a really bad experience or there's like
a security issue because we don't have this setting.
We'd probably add that setting to the existing setting system.
But if the issue was like small or didn't affect that many users,
it would need to wait for the new setting system.
And that's why we had lots of confusion there.
But do take a look at the, uh,
how how we prioritise stuff to understand that just a little bit more.
We're gonna go ahead and and expand and edit that content as, um,
uh, as we sort of grow and as we, you know, have more bandwidth.
It's an interesting conversation when we sort of use the word bandwidth.
Um, what we mean by bandwidth is like, How much more can we take? Right.
So how much more work can prime get? Can fruits get?
Can anyone on the team get before they just fall over?
And that has a fixed cap right now because of our team size.
But once we grow, we'll have more people, which means we can do more work at once,
et cetera.
Uh,
a O asks her how much yellow fur has to be
plucked out of the code before updates can be pushed.
Um,
occasionally, like I I I'll take the the the concept of yellow
fur and just say, like craft, right?
Cos sometimes there is craft when you're doing programming. I'm sure if you're, um,
well, everyone does this, but like even when you're newer to to to programming,
you'll do this even more where you just add,
like console dot log or console dot Right line everywhere.
You're just like I have no idea what's going on.
Let me just add console dot whatever everywhere I can to figure out what's going on
That stuff still happens. I've been programming for, like, you know,
almost two decades now
that still happens.
And so when I say removing the craft, you're like all right, now it works.
I can remove this from it.
I can remove all this junk from it.
And so then you spend like 5, 10 minutes,
just like removing random junk that you added just because you were distraught,
you were like I don't know how this works.
So there is a lot of that. Um, you also see that in commits a lot? It's like,
uh, you know, you think the code's perfect, and then you push a commit and it's like,
error missing semicolon. She's like, Oh, OK,
so the answer there, I guess, would be a little bit,
Um
Ozie says, with the recent, uh, github
issue of proto
flux running under disabled slots, how do you think the myth, uh,
that it was being design or intended around,
Um,
with the way that proto
flux was created. And, uh, the way that were released
there is, like, a little bit of confusion, like we didn't have good bug tracking.
We didn't have good decision making stuff stood up
like we're still standing up a lot of that.
So,
um, I don't think,
um, any of those myths are true or helpful.
Um, it's an issue. We want to look at it and we'll look at it when we can.
Um,
I don't like it when when those sort of weird myths come
up like I heard the other day that we had purposely,
like,
made full body worse so that people couldn't
use full body for adult activities in private.
And it's like who comes up with this stuff,
uh, to illustrate the problem with that sort of rumour mill.
Um, a long, long time ago, I banned ladders on a Minecraft server for like 15 minutes
because people would like walk around and chat, and they'd be like Is XYZ block band?
And I'm just like we have an official list of banned blocks over here.
Like it's you know, it was on the page for the Minecraft server, right?
So, like, if you've got a myth, ask about it and we can confirm it.
But once we've confirmed it, that myth should die.
I see fruits as typing, so maybe they'll have AAA statement on the proto
foxy stuff.
Uh, Xor says, Why does office hours have to take place while I'm working?
There are 24 hours in the day, and this lasts for half an hour.
I have to pick somewhere,
and I'm not able to survey the entire population
of Resonate to figure out when everyone's at work.
Unfortunately, that's that's exactly why it's happening.
I have considered doing additional segments, but
with other groups within the team or other people
making office hours later on in the week,
there isn't enough like room for more office hours content.
Um, so maybe attend one of those sessions if you like.
Uh, Shanna
has a suggestion for the wiki, Please. Uh, restructure How?
The wiki if things cloud variables. Uh, yeah, I probably will do that.
Um, you're also welcome to do it yourself. Um, once it's out,
uh, electronic
is not able to listen at the moment.
My understanding was ra was kind of a server Web guy.
It appears to be no longer part of the team who's handling servers and pages. Um,
the combination of fruits, gs
and myself are handling infrastructure. Now,
um, I have, uh, half a decade of experience running Linux servers.
Um, for racing events around the world.
Um, Geens has
I don't know where his experience is sourced from, but it's not like it's pivotal.
Like
I have half a decade running racing events around the world.
That's really impactful. But GS
does also know Linux.
Um, fruits is less confident on Linux,
but we're, um you know, we're we're teaching them as we go.
We're also making sure that anything we don't know we document now
it it's it's very important.
I do it with my life and all my personal projects, but it's basically like
I had to expend energy to figure out this thing.
I will write down my result.
Um, so a good example here is,
uh I have a page in my digital notebook called Things You keep forgetting.
And
it links to a bunch of other pages where I've made notes on things I keep forgetting.
One of them is how to run a very basic Web server.
So if I'm working on a website and I wanna run on
a very big like a very basic Web server so that the,
you know, the file links work correctly,
that's one of the pages on stuff I keep forgetting.
I'm gonna read for the benefit of the recording.
I'm gonna read fruits response to the github
proto flux thingy.
Um,
W, uh Fri says there's one thing I feel people don't do enough,
which is ask for sauces.
Ask for sauces. Do you want some ketchup? Do you want some? You know,
maybe some mayonnaise, um, sauces, not sauces.
Um, if you hear something, ask How do you know that?
Where did the information come from?
Is there a place where someone on the team said that.
And then they say, If you can't get to the primary source of in some information,
take it with a grain of salt.
It's not just for us and resonate,
it's good for critical thinking. Always look for primary sources.
There are lots of mis misinformation on the Internet about everything.
Um,
couldn't agree more back when I was in school. Um,
I remember this cos it was like it was early. As like,
uh, it's hard to always align my school system to everyone else's school system.
But, like, I'm gonna say year two. So, like, Year two is
the second year of education after,
like preschool. Um, we were talking about primary and secondary resources.
Um,
and I remember learning like bibliographies and how we couldn't use
Wikipedia cos it didn't cite its sources even though it did,
like everyone's done that right.
It
is so important in the technical world.
I mean, it's important everywhere, but it's so important in the technical world,
particularly if you're a trusted member within the community.
So, like ozy
just picking on you because you're there, you're awesome.
You're a moderator, and you're very good at being a moderator.
But that also gives you sort of a trusted place within the community,
which means you have more of a sort of
pressure to make sure that anything you say is correct
and ozie you do a great job doing that. So don't worry about it.
Um, but you know, that's an example. It's like, you know,
I am the proto
flux tutor.
Maybe we have a YouTube channel that picks up, and it's like I am the proto flux tutor.
And if they don't check their sources are primary.
Then I don't think they should have that title
like constantly be checking it, constantly updating it as well.
It's like, You know,
um,
I wish, like, academic papers were more, um, like,
approachable from people, not in academia cos they're usually written in, like,
really high level technical language.
But like just seeing how, like every single time they make a statement
that they can't back up in their actual paper,
they're linked to another paper or another thing that that, like, does it,
and it gets ridiculous. It's like, um,
there's an experiment I'm working on currently where we're looking at, um uh,
skin conductivity.
It's called the galvanic skin response, and they reference,
like four or five papers that talk about galvanic skin response cos they
need to build the foundation of knowledge that galvanic skin response is good.
A good measurement to have in that experiment.
Uh, Rhino says. Favourite Source. Um,
I really like
Big Mac sauce or or burger sauce like I could
put burger sauce and everything as far as I'm aware.
Like burger sauce is basically like ketchup
and mayo mixed together with some spices,
but I could put burger sauce on anything like I could I.
There have been times where I've squirted burger sauce into Mac and cheese,
and it's just, like added an edge.
Which reminds me, if you're making Mac and cheese, add some spices, guys.
Just a little bit of spice.
And it doesn't have to be like spice what I'm talking about,
like hot pepper or anything,
but like, you know, add some salt, add some pepper.
Maybe add some herbs, just like you'll make your Mac and cheese better.
You can take like a you know, a
box. Kraft, Mac and cheese Add some spices. It's like gourmet.
Gonna read a follow up uh, statement from fruits about this, uh, thing, because, uh,
there's more good information in it.
Do it of everything. Question why? You know things and why you know them.
It's good to do things overall to clear up your knowledge.
I try to do this whenever I can
and find some things I believed I didn't have a good reason to.
It's a good thing, too, because whenever you do that,
your knowledge becomes better when you do it.
And if you know something, you can find good information and confirm that
it helps to reinforce the knowledge, too. Yes,
I wish when I was taught science at school,
I wish I was more emphasised that the purpose of science was to
prove undeniably that something was true,
right.
That's that's the topic, and and most of the time, science actually can't do that.
So what they do is when they publish a paper,
they say our results seem to suggest you'll hear that word like seem to suggest.
So it's like our results seem to suggest that humans need water. Absolutely
good. That's easy to prove. Our result seems to suggest that,
um, the world is ending OK, that's that's more difficult to prove.
Uh, someone here, stompy DPD has said. Chopped onion in Mac and cheese? Absolutely.
If you like caramelise those onions a bit, shoot them in the Mac and cheese.
Absolutely
nothing you can do for Mac and cheese.
It's really easy is, um, if you make it, you can then put breadcrumbs on top
and then put it in the oven for a little bit.
Those breadcrumbs brown and then you get like a crunch
cheesy top layer on on on the Mac and cheese. I don't remember the exact context.
I hope someone knows it. Um, but
there was a science paper that was published purely
to make it like problematic that the science community was like that.
They were doing a paper on how, um,
parachutes reduced the chances of injury when jumping out of a plane.
But they made a critical error deliberately in their paper,
which was the plane was not in flight,
so people were jumping out of a plane, stationary on the runway,
wearing a parachute and not wearing a parachute.
And it's like
the results show there's no difference in wearing
a parachute or not wearing a parachute.
Everyone survived, but you had to read the details to be like, Ah,
they did this on purpose.
The plane was flying at 0 ft.
Uh, Russo was talking about how now it's on github.
It's easier to disprove rumours. That's correct. Um, Rousso
also talked about how they had an assumption that it was being tracked elsewhere.
Even if you have the assumption that's being tracked elsewhere, if you can't see it,
assume it's not being tracked.
We do have an internal private issue tracker, which has lots of stuff on it,
and there are some duplicates and they do do crosslinking.
But just assume that we wait. Assume we're silly, like Do do Take that.
Like assume that we're silly.
Be polite about it,
but assume that we're silly because let's be honest at 4 a.m. If I'm typing C# code,
I'm silly
again, I'm gonna read for, uh, the recording benefits Fruits says uh,
when
it goes the other way.
A lot of times, too,
people assume that something is intentional so they don't make an issue about it,
and then it ever gets fixed because we don't know about it.
If you make an issue we can at least look at it and say This is intentional and close it,
uh, which is a good thing because now it's on record and we can be like, Nope,
that's supposed to happen.
But if no issue is made, nothing can really happen.
The more issues we have closed, open stale, I don't care.
The more issues we have on that github, the better.
There are some points in the actual code base where I say this like in a comment.
This was done because of this. I also explained the reason in the code base.
But I put another line which is like this was caused by this in the comment.
And what that means is if, like we hire a programmer tomorrow like Rampa,
welcome to the team.
You're on the team and you open up the
and you scroll through it and you're like, Why the hell did prime put like
a humongous piece of cheese in the middle of this code?
And then there's a comment from Prime that says, Here's why I did it.
Here's the link to the original issue.
Rampa can then click that link,
go to the original issue And even though it's
closed and maybe it was closed a year ago,
there's the exact description of why it was closed.
All the log files, everything's there, and they can be like that. Makes sense.
Good job, Prime.
Um, Rampi, you're now fired from the team. You lasted about a minute in
this hypothetical scenario. Congrats.
Uh, although rampa does actually have a question here.
Um, any official statement coming on the topic of Raith leaving?
There's some confusion in the discussion about it.
I'm not sure if we have an official statement about that that I can provide here,
so I won't provide a statement.
Um, but yes, it is true that they have left. Glitch is shown as a cat, right?
I don't wanna, like, make a something. I mean, it looks like a cat. Is it a cat?
I'm waiting for freaks to type, cos you know
he should know. Uh, you know what the species of of of
soda is? I I'm
certain it's a cat, but like,
I keep doubting myself and I never like there was one point where I like I you know,
I had a conversation with someone and I was like, Oh, that's an awesome sonar.
It's
a insert species here and they're like, No, it's actually a insert species here.
And I'm like, Oh, I'm sorry.
I'd rather like ask. I know,
uh, lna says, Write self document code than document that code. Exactly.
Um, I really hate people who say like, but comments can get out of date.
It's like, OK, I test your comments. Then
it's like, What do you mean?
It's like when you edit the code, read the comment and see if it still makes sense.
There's this sort of alternative way of writing tests as well.
Um, I think it's called, like,
gin or something.
Yeah, GB DD
So gir is a type of testing. Um, that's called behaviour driven development. Um, and
you sort of, uh, you make
you make a specification
that is really difficult to read in discord. Dark mode. I apologise.
Um, but you basically you're like, here is an exact scenario. Here is what happens.
And here are my expectations.
And then in code, you sort of, um, back that specification up with some code,
and
that way you kind of prove that that business case has been met
I will link the Gherkin website. I don't know enough about it.
Actually, this is the cucumber website.
Is there like a A like specific gherkin website?
I I'll just link the cucumber website like there's there's there's stuff here, like
like we don't use it at, um at Rein.
I don't think we would for a while as well.
It's a it's pompous is the wrong word,
but like it's a little bit like further away from just like making the code work.
That means that, like, I'm a little bit hesitant on
exploring using it. But the reason it came up is because, like,
um, when you write tests like that,
the tests then actually become documentation.
Um, because, like you, you annotate the code of, like,
this is the part of the scenario that happens now, ET cetera it.
It's
I know a lot more about it that I'm trying
to explain here because I'm bad at explaining it.
But yeah, I'll take a look at it.
Uh, some people said, actually, here we go, Cory says, Uh oh, Corey, I don't
says, uh,
one tip I heard was Don't add comments to explain how your
code work adds a comment to explain why it does that.
Yep. Um uh, why it does that is very important.
Uh, fruits also says making mistakes is a natural part of being human in a lot of ways,
it's beneficial too, because you can learn from them Well,
which helps you improve your knowledge on why things are there.
And you better understand why they are not done
the other way rather than just being told.
It helps you build your intuition about things.
Uh, yes, um, practise saying, I don't know
and practise learning.
Um, most people, like stop actively learning when they they finish school.
Um, depending on their job role, of course. But, like, just always be learning.
If you don't know something, figure it out.
Like yesterday.
Um, I saw a clip on TIKTOK or something of, uh,
some thieves stealing catalytic converters,
and I'd forgotten what a catalytic converter did.
So I spent half an hour reading the Wikipedia article about catalytic converters.
I have since forgotten what I read,
but the point was there I was like, I don't know that I'll read it again.
Yeah. I thought nibble was half of eight.
Yeah, half of it.
Uh,
Carl sus here says I highly recommend learning to take the L to say I was wrong.
Yeah, that's really good as well. Like
sometimes when you do something wrong,
uh, and then you apologise to someone
like the apology is like 50% of the way.
But like, if you do, I'm sorry I was wrong.
That's like, that's a really good apology.
Cos you're like, not only are you sorry you're also admitting fault.
An admitting fault. Sounds like sort of, you know, like criminal or legal.
It doesn't have to be that. It's like, I am sorry. I forgot to put the dishwasher on.
I was wrong in assuming that you had done it.
No one's mad at anyone.
The dishwasher just wasn't put on.
I don't see any questions coming up at this point.
We're sort of going into philosophy et cetra. But,
uh um, that's cool. Uh, Carl.
So if you have a question, you are the last person that's allowed to ask a question,
and then we'll leave off from there.
All right? There are no more questions. We'll go ahead and leave off there.
Um, I think I'm a bit tardy. That means late, by the way. Sorry.
I'm using fancy words, Um,
on getting the office hours up on on on my page.
Um, I'll I'll sort that out. I've also noticed that, um,
G has been providing, um, audio files or the moderation office hours.
I'm gonna go ahead and upload those.
We haven't really decided where they go to long term, but I might as well.
Um,
getting those up also allows me to test something cos I'm not sure
how my transcription pipeline handles multiple speakers
cos it's usually just me speaking.
I don't know how it handles multiple speakers, so we we'll take a look.
If you have any additional questions, feel free to ping me.
Not all team members are OK with that. I am just because
I like being friendly that way.
Um, DM me or I'll make a get up issue.
Do you remember that?
If you ask about a bug or you ask about a feature and there isn't a get up issue,
I probably wouldn't talk to you about it.
Um,
I just I need the get up issue. Give me the github.
Um, I will speak to you guys later.