WEBVTT

00:00:00.000 --> 00:00:04.000
Hey, Tim. How you doing? I'm all right. How you doing?

00:00:04.000 --> 00:00:08.160
Not bad. Not bad. How's your day been so far? It's been pretty hectic.

00:00:08.160 --> 00:00:10.800
Yeah, hectic. What are you working on at the moment?

00:00:11.520 --> 00:00:15.360
Well, we just we just came off of the 4060 and 7600 embargoes.

00:00:15.360 --> 00:00:19.600
And that was that was a big effort from the entire team.

00:00:20.400 --> 00:00:25.120
Right now we're working on some stuff that I can't directly talk about

00:00:25.120 --> 00:00:27.840
because it'll probably come out after this video has.

00:00:28.560 --> 00:00:34.080
But it's very, very cool. And I'm really excited for everybody to see what it is.

00:00:35.120 --> 00:00:37.920
Awesome. So how long have you been at LMG now?

00:00:38.800 --> 00:00:42.240
I think I would have started here sometime in July last year.

00:00:42.240 --> 00:00:44.800
So almost a year. How are you finding it so far?

00:00:48.400 --> 00:00:52.560
It's pretty hectic. That's a general theme here, isn't it?

00:00:53.760 --> 00:00:57.200
It's been a lot of fun. I made the decision to come here.

00:00:57.840 --> 00:01:01.760
When Gary called me up and I have not regretted it since.

00:01:01.760 --> 00:01:06.560
I'm very happy with it. For everyone watching that may not know, what is your role here?

00:01:07.600 --> 00:01:11.600
Well, kind of the meme is that nobody knows what I do here, which is, you know,

00:01:12.960 --> 00:01:16.480
well, it's six parts funny and six parts kind of like, okay.

00:01:17.120 --> 00:01:21.280
But actually the what I do is pretty diverse.

00:01:21.280 --> 00:01:26.400
So I work in the Labs, which is to say that I am part of the first round of Labs hires.

00:01:26.400 --> 00:01:33.040
But when I started, I was supposed to be part of the engineering development team.

00:01:33.040 --> 00:01:37.760
I was supposed to be creating the actual implementation for the test that we wanted

00:01:37.760 --> 00:01:46.640
to run the physical mechanical side of things. That turned into doing a lot of almost side projects working alongside the writing team

00:01:46.640 --> 00:01:51.920
and making sure that they have, you know, if a weird engineering thing pops up

00:01:51.920 --> 00:01:55.440
and they want to make something like the water cold Mac studio.

00:01:56.480 --> 00:02:00.240
Alex, I worked on that as well as the 24 Peltier cooler rack.

00:02:00.240 --> 00:02:04.400
Alex and I worked on that. A couple of other weird things like that.

00:02:04.400 --> 00:02:09.760
A video just came out, the Turbo Desk, which I guess we haven't titled it that,

00:02:09.760 --> 00:02:17.120
but that is the internal code name for the Carl Jacobs $100,000 desk PC.

00:02:18.320 --> 00:02:23.360
We've been calling it Turbo Desk. It's labeled Turbo Desk in all of my documentation.

00:02:23.360 --> 00:02:27.680
And I built that from scratch, designed, built, engineered everything.

00:02:28.480 --> 00:02:31.760
So there's that half of it where I work with the writers really closely.

00:02:32.320 --> 00:02:36.080
But then the other half, the part that I've been more leaning into in the last couple of months

00:02:36.080 --> 00:02:41.280
is developing all of the process documentation and all of our policies and procedures

00:02:41.280 --> 00:02:43.040
and the way that we do things within Labs.

00:02:44.320 --> 00:02:50.560
For example, if you, let's say that you unbox a computer, if you're a reviewer,

00:02:50.560 --> 00:02:55.440
what do you do with it? What are the specific steps that you need to take to collect all the specifications

00:02:55.440 --> 00:02:59.200
to make sure that you have the device that the company says that you did?

00:03:00.000 --> 00:03:03.920
What sort of measurements do you take to validate independently the things that they're telling you?

00:03:04.960 --> 00:03:10.080
And then on top of that, what sort of tests do you do? How do you run those tests at a very, very granular level?

00:03:11.440 --> 00:03:14.160
Step by step instructions for everything.

00:03:14.720 --> 00:03:18.960
And then on top of that, how do we interact with other departments?

00:03:18.960 --> 00:03:24.640
Labs creates a data set. How do we hand that off to the requester of the data set, which could be the writers,

00:03:24.640 --> 00:03:27.600
it could be a creative warehouse, it could be the social team, it could be anybody.

00:03:28.320 --> 00:03:31.520
All of those sorts of things need to be documented, need to be created in process

00:03:31.520 --> 00:03:34.640
so that we can be an actual professional outfit,

00:03:34.640 --> 00:03:37.440
because we are working towards becoming an academic laboratory.

00:03:39.280 --> 00:03:43.200
Wow, that is a, you have quite a lot on your plate.

00:03:43.200 --> 00:03:51.520
It's pretty intense, yeah. Plus, we have had a couple of people start pretty recently that I've kind of just fallen

00:03:51.520 --> 00:03:56.000
into managing, and so I'm making sure that other people have projects on top of that,

00:03:56.640 --> 00:04:02.400
and trying to find a balance between the stuff that I need to do on my own time,

00:04:02.400 --> 00:04:06.000
as well as making sure that other people keep their balls in the air, so to speak,

00:04:06.000 --> 00:04:10.400
is it's a new and exciting adventure for me.

00:04:11.360 --> 00:04:15.760
Yeah, so I'm guessing not a single day is the same for you here.

00:04:16.800 --> 00:04:21.520
No, I wouldn't say that. There's a lot of variety, and I talked about this during the

00:04:22.080 --> 00:04:27.360
What's It Like to Work at LMG video when I was interviewed for that, but it's a lot of fun

00:04:27.360 --> 00:04:33.920
because of the diversity of things that I get to work on and almost play with.

00:04:34.880 --> 00:04:41.600
Like, there's this one thing that I discovered when I was at work, and it's open source,

00:04:41.600 --> 00:04:52.480
so I think I can talk about it. Juice Labs or Juicy has this really phenomenal program where you can run a program on something

00:04:52.480 --> 00:04:58.640
that has, say, an integrated GPU, or something that's not very powerful in terms of graphics

00:04:58.720 --> 00:05:05.600
processing power, like a laptop. But you can run a program on that laptop, and then over

00:05:07.040 --> 00:05:14.080
TCP-IP, you can, over the internet, you can run the actual compute program on a different GPU,

00:05:14.080 --> 00:05:18.640
on a different computer entirely. So rather than moonlight streaming, where you're running the

00:05:18.640 --> 00:05:25.040
program on the GPU and you're streaming the frames to your non-powerful PC, instead you're

00:05:25.040 --> 00:05:30.240
running the program on your non-powerful PC, streaming the GPU compute to the GPU, and then the

00:05:30.240 --> 00:05:37.760
GPU streaming back as a fully post-processed equation or whatever the end result of it is

00:05:37.760 --> 00:05:42.480
for your thin clients to actually work on. And so I worked on that a little bit here,

00:05:42.480 --> 00:05:46.000
and I took it home, and I use it all the time now. It's super cool.

00:05:46.000 --> 00:05:49.840
So I guess going back a bit, where did all this begin? Where's your background from,

00:05:49.840 --> 00:05:58.240
I guess, start from, let's say, school? Sure. Well, I actually, I didn't go to high school. I was homeschooled when I was a kid,

00:05:59.200 --> 00:06:04.640
and I was kicked out at a fairly early age, like kicked out a number of times when I was a kid,

00:06:04.640 --> 00:06:13.680
but the last time for good was when I was 15. And so after that happened, I didn't finish high

00:06:13.680 --> 00:06:20.160
school, I didn't go and enroll in a public school or anything. Instead, what I did was I went and

00:06:20.160 --> 00:06:29.440
found a job as basically a tire jockey, a calitire, which is a local tire repair shop here in

00:06:29.440 --> 00:06:38.000
Canada. I don't know if they have locations elsewhere. Anyways, I got a job in an auto shop,

00:06:38.000 --> 00:06:44.800
and I went down that road of working towards actually becoming a journeyman mechanic. I never

00:06:44.800 --> 00:06:49.120
went to school to be a mechanic, because there's kind of two pathways. You can either take the

00:06:49.120 --> 00:06:52.880
courses prior to doing the work, or you can do the work and then just write the tests afterwards

00:06:52.880 --> 00:06:57.680
to get your hours. And that's the one that I did. So I'm a journeyman mechanic, but didn't

00:06:57.680 --> 00:07:03.600
actually go to school for any of that. But then after that, I actually, when I got my GED, because

00:07:04.480 --> 00:07:09.120
there were a number of factors around that reason, that decision. But it was basically just,

00:07:09.120 --> 00:07:15.200
I felt like I could do better with my life, and I wanted to. So I got my GED, and then I moved

00:07:15.280 --> 00:07:25.440
to Calgary and started in academic upgrading at SATE with the help of some close family members

00:07:25.440 --> 00:07:30.560
who were able to provide me some support. And after I finished academic upgrading, I went into

00:07:30.560 --> 00:07:35.760
the mechanical engineering technology program at SATE, which is basically an associate's degree.

00:07:36.320 --> 00:07:41.760
It's a two-year diploma that I took over three years, because I wanted to do work on the side,

00:07:41.760 --> 00:07:46.320
as well as working pretty heavily in the student's association at that time. I wanted to start to

00:07:46.320 --> 00:07:52.000
give back to my community from the support that other people give me. And how do you know this

00:07:52.000 --> 00:08:02.800
was happening? Yeah, when I was at SATE, I would have been 23, I think. Fairly young, but late

00:08:02.800 --> 00:08:09.440
when it comes to going to college. Yeah, so I went to MET, I graduated top of my class,

00:08:10.320 --> 00:08:16.560
second Tuvalo Victorian. I am still ticked off about that. I know why the other guy got it,

00:08:17.280 --> 00:08:24.480
and it's favoritism, it's not me. But either way, so I graduated that class, and then I went

00:08:24.480 --> 00:08:30.240
immediately to enroll in another program on Vancouver Island over at Kamosan College,

00:08:30.240 --> 00:08:34.480
which was the mechanical engineering bridge. So it would have taken the associate's degree that I had

00:08:34.560 --> 00:08:42.320
from SATE, and then turned it into kind of a transfer credit program into UBC, which is one of the

00:08:42.320 --> 00:08:48.560
best engineering schools in Canada. So I did that, I graduated through that program, and then Gary

00:08:48.560 --> 00:08:52.560
called me up, and he's like, hey, would you like to put aside school? Your resume is already really

00:08:52.560 --> 00:08:57.360
impressive, and we'd like to have you on our team. And I was like, you son of a bitch, I'm in.

00:08:57.760 --> 00:09:05.280
So I put school on hold for a year, and I'm now 27, almost 28 in a couple of days.

00:09:05.280 --> 00:09:12.080
And the plan is to continue to go to UBC. I'm actually enrolled in classes right now,

00:09:12.640 --> 00:09:16.800
at the same time as I'm working full-time for LMG. That's kind of where I'm at.

00:09:17.440 --> 00:09:21.360
So you said, in all of that, you said you moved to Calgary at one point.

00:09:21.360 --> 00:09:24.800
Yes, yes, sorry. So I grew up in Regina in Saskatchewan.

00:09:24.800 --> 00:09:33.680
Were you a fan of LMG before this? Yeah, I had seen at least some of LTT and

00:09:33.680 --> 00:09:37.280
ShortCircuit content before this. I wouldn't say that I was a superfan, but I definitely

00:09:38.000 --> 00:09:44.320
was aware of it. Like when I was a kid, like early teenage years and later teenage years,

00:09:44.320 --> 00:09:47.840
I volunteered really heavily with this organization called Computers for Schools,

00:09:47.840 --> 00:09:51.600
which is a phenomenal group, like absolute phenomenal group. If you have a local

00:09:51.600 --> 00:09:56.160
computer for schools, I would heavily recommend that you go and donate some of your time to them.

00:09:57.200 --> 00:10:02.480
They're great. Basically, they take old electronics, typically in bulk from Crown

00:10:02.480 --> 00:10:07.520
Corporations, if you're in Canada, or from other organizations who just want the tax

00:10:07.520 --> 00:10:11.280
receipt rather than creating more e-waste. They'll refurbish them, they'll remove all the

00:10:11.840 --> 00:10:16.640
personal information from those computers, and then they will donate them either to nonprofits

00:10:16.640 --> 00:10:23.920
for a very low fee or to schools for free. Taking e-waste out of the ecosystem and turning it

00:10:23.920 --> 00:10:29.440
into actual useful things for people who are disadvantaged to be able to learn. So I donated

00:10:29.440 --> 00:10:35.920
a lot of my time to Computers for Schools, and one of the things that I learned there was

00:10:37.360 --> 00:10:41.840
basically around the entire, like, how does personal computing work and how do you build a

00:10:41.840 --> 00:10:46.560
computer, but also getting into that kind of, like, this is gaming, and these are, you know,

00:10:47.760 --> 00:10:51.680
cool people who are doing cool things. So I've been watching LTT for a fairly long time.

00:10:51.680 --> 00:10:59.600
All right. So you've been here for just under a year now, right? Yeah. Cool. So what would you say is your most favorite project that you've worked on so far?

00:11:00.400 --> 00:11:06.560
In terms of projects that I've worked on, in terms of videos, I think, honestly,

00:11:07.360 --> 00:11:14.480
the TurboDS video probably takes the cake. I want to probably say that this video has come out

00:11:14.480 --> 00:11:17.680
after the actual build video, because we're releasing it at least in two parts,

00:11:17.680 --> 00:11:22.240
where it's the glam one that's already come out for sure, and the actual build process,

00:11:23.360 --> 00:11:29.200
and that video was super, super fun to shoot. I got to spend eight hours with Linus and Alex

00:11:29.200 --> 00:11:34.800
and Tyvee, and I think Colin was there. We were building this thing that I had been designing for

00:11:34.800 --> 00:11:40.480
months and months and months, and I had already built it almost completely once before, because

00:11:40.480 --> 00:11:44.400
we had to set it up beforehand, and I had been doing that over the course of two weeks, and then

00:11:44.400 --> 00:11:49.520
we had to take those two weeks and compress it into eight hours. And so, like, I had done all of

00:11:49.520 --> 00:11:54.080
the test fitting. I had made sure that all of the coolant loop was cut to fit for all the tubing.

00:11:54.080 --> 00:11:58.560
I'd made sure that all of the wires were effectively harnessed and soldered correctly.

00:11:59.280 --> 00:12:04.320
Everything booted correctly. I had to do a little bit of drilling and some welding for some parts

00:12:04.320 --> 00:12:08.240
that didn't fit. Like, everything had to fit perfectly, so we could get it done in one marathon

00:12:08.240 --> 00:12:16.800
shoot. We did, but it was absolutely terrifying, because at the end of that shoot, the thing wouldn't

00:12:16.800 --> 00:12:24.960
turn on. Ah, so it turns out, it was either there was, if I'm recalling correctly, there were either

00:12:24.960 --> 00:12:28.640
one of two issues that could have happened, both of them were Linus' fault. Either something had

00:12:28.640 --> 00:12:33.440
gotten into the socket when he had installed the CPU, or there was too much mounting pressure,

00:12:33.440 --> 00:12:39.600
because he had installed the bracket for the block upside down. And so we fixed that, we figured

00:12:39.600 --> 00:12:46.480
it out, but it was like 8.30 or 9 o'clock at that point. It was just, it was stressful, so stressful.

00:12:46.480 --> 00:12:50.800
And we were still operating under a time crunch for that point, because we didn't know that they

00:12:50.800 --> 00:12:53.920
weren't going to pick it up for like two months, but we were like trying to get it out the door.

00:12:55.040 --> 00:12:59.200
So that was, that was a lot of fun in terms of, like, actual shooting a video. But then I also

00:12:59.200 --> 00:13:04.000
want to say, like, in terms of projects that have been really cool, as far as my favorites go,

00:13:04.640 --> 00:13:10.720
reviews and embargoes are a super double-edged sword, because we've come a massively long way

00:13:10.720 --> 00:13:16.880
from where we were when the lab kind of came online for AM5. That was our first review launch video.

00:13:18.400 --> 00:13:23.600
Nick and Danes and Gary were the ones that were testing it. I remember coming up into this room,

00:13:23.600 --> 00:13:28.720
which hadn't even been set up. It looked basically like a junkyard with all of the wire and all of

00:13:28.720 --> 00:13:34.080
the like ceiling panels and the boxes. It was a massive mess. And I came and I set up some tables

00:13:34.080 --> 00:13:37.760
and I set up the benches and I messaged Gary. I'm like, hey, these are ready to go. Let me know

00:13:38.400 --> 00:13:45.200
if you want me to start testing or what you want to do. We didn't even have a project plan at that point. We had no idea what we were doing. We're just like, you know what, this is a bunch of things

00:13:45.200 --> 00:13:49.120
that they've done. They, LTT doesn't really have project plans before. They don't really have

00:13:50.160 --> 00:13:54.720
actually records of the things that they run. So we're going to have to kind of start from

00:13:54.720 --> 00:14:00.400
scratch. And we did. And it was hell. It was absolute hell. AM5 was a massively problematic

00:14:00.400 --> 00:14:05.360
launch, but then it led to us learning a ton and then putting some processes in place for the next

00:14:05.360 --> 00:14:10.160
one. And then 4090 happened. And then we got wrong data on a massive graph and we got called out for

00:14:10.160 --> 00:14:16.160
it and it's like, okay, so I guess we needed a review process too. And so like every one along

00:14:16.160 --> 00:14:22.800
the way until the 4070TI, 4070TI is when we really started to hit our stride in terms of like,

00:14:22.880 --> 00:14:28.800
we're putting good data together. We're getting out a lot of the issues with potential data

00:14:28.800 --> 00:14:32.960
handoffs. And that was the first one where it really started to feel like everything was kind

00:14:32.960 --> 00:14:40.240
of coming together. We kind of nailed it and hit it out of the park. We got a couple of big

00:14:40.240 --> 00:14:43.680
shout outs from a couple of other members of the community and other reviewers being like,

00:14:43.680 --> 00:14:50.080
this is actually coming together. And then we kind of realized at that point, A, this was working,

00:14:50.080 --> 00:14:55.840
that the process changes that we were doing were correct. And B, the reason that this was so hard

00:14:55.840 --> 00:15:01.120
for us and not for everybody else was that we were the only people that were actually testing

00:15:01.120 --> 00:15:09.920
all of the cards, every project. Everybody else reuses data. We don't. And that's the big

00:15:09.920 --> 00:15:16.000
differentiation. When we pull a graph that has 12 different cards, that means that we spent

00:15:16.000 --> 00:15:22.800
10 to 12 hours on each of those cards prior to the week before the embargo happens.

00:15:23.520 --> 00:15:26.960
Nobody else does that. You look at any of the other reviewers, they have either dates on their

00:15:26.960 --> 00:15:31.920
charts or they just don't admit it. And if you look and compare their old data from previous

00:15:31.920 --> 00:15:37.280
videos to their new data from a current video, it will be the same. Ours isn't. The only one

00:15:38.000 --> 00:15:42.720
where we reused data was a couple of days ago. And that was for a specific reason,

00:15:42.720 --> 00:15:48.240
because the 7600 and the 4060 Ti came out within the same time. So we needed to put them together

00:15:48.240 --> 00:15:54.240
in the same data set. And so that that's a fair use of data. But we're not going to reuse that

00:15:54.240 --> 00:15:59.360
data set, because those aren't comparable. What we are doing in the lab is we're creating a big

00:15:59.360 --> 00:16:04.640
bucket of separate data sets, lots of little bubbles within the bucket, you can kind of like

00:16:04.640 --> 00:16:08.880
hold up to each other and say, Oh, you know what, that kind of looks like it's approximately the

00:16:08.880 --> 00:16:13.760
same. But those bubbles can never coexist or can never collapse into each other. They can only

00:16:13.760 --> 00:16:19.920
coexist separately, independently of each other. So everything that we do is on a new project

00:16:19.920 --> 00:16:24.640
with new parameters, as we're revising, as we're changing things. And that should, as far as I'm

00:16:24.640 --> 00:16:30.640
aware, never change. Yeah. And I think, I think it is super important to be using freshly tested

00:16:30.640 --> 00:16:38.160
data. Because I think, like for example, things as simple as a new driver update might have caused

00:16:38.160 --> 00:16:42.880
the same card to perform differently than to a year ago. Yeah. And we've done tons of regression

00:16:42.880 --> 00:16:49.920
testing. We've found out that this is an actual thing that needs to happen. You cannot reuse data

00:16:49.920 --> 00:16:55.680
from October and then call it comparable to data from March. It is just not acceptable. And for

00:16:55.680 --> 00:17:02.320
reviewers outside of us to do that and say that they are presenting an argument that is fair and

00:17:02.320 --> 00:17:09.040
valid. I can't accept that. I absolutely can't. It's it has working here. If it has done anything,

00:17:09.040 --> 00:17:13.360
it has made it really hard to watch tech content without pointing out flaws.

00:17:14.320 --> 00:17:21.440
That is so true. That is so true. Okay, let's flip for a little bit. And let's talk about

00:17:22.480 --> 00:17:34.160
what are you doing in spare time? What do you do for fun? I don't know. Spare time? What's that? I'm still I'm still working on making a community for myself

00:17:34.800 --> 00:17:40.880
here, here out in Vancouver. So I don't do a whole lot of like, group events, but Adam from

00:17:40.880 --> 00:17:44.800
the writers team, and I have been going to a lot of concerts together lately. And that's been a lot

00:17:44.800 --> 00:17:51.280
of fun. Awesome. Yeah, I really enjoy, really enjoy seeing live music. I've worked around live

00:17:51.280 --> 00:17:56.080
music with live music for a long time in, you know, bars and coffee shops and stuff. And that's

00:17:56.080 --> 00:18:05.760
that's been a shout outs to any artists? Trivium, Thrice. We just we just went and saw nothing more

00:18:05.760 --> 00:18:10.400
for I don't know how many times I've seen them at this point, three, four at this point. Absolutely

00:18:10.400 --> 00:18:16.560
phenomenal show. Yeah, yeah, really good stuff. I also do a lot of a lot of like little side

00:18:16.560 --> 00:18:21.520
projects at home, you know, just experimenting with either my home lab or like designing and

00:18:21.520 --> 00:18:28.800
building things for, for, you know, various use cases here and there. And I also, I, it's kind of

00:18:28.800 --> 00:18:34.560
nerdy, but I do a lot of miniature painting. I don't, I don't play a lot of D&D recently, because

00:18:34.560 --> 00:18:40.880
again, I don't have really a community, but I do normally, or I have in the past played quite a

00:18:40.880 --> 00:18:47.760
bit of D&D and I tend to be the DM for, for any sort of tabletop caning, because I just really

00:18:47.760 --> 00:18:53.280
enjoy it. And yeah, I paint a lot of miniatures and draw a lot of maps and I really enjoy that.

00:18:53.840 --> 00:19:00.560
Also keyboards, also cooking, really enjoy cooking and also everything outdoors because I'm

00:19:01.520 --> 00:19:06.880
the majority of the way to being an ACMG mountain guide. So I really, I really enjoy that too. I

00:19:06.880 --> 00:19:11.280
don't know how many, how many hobbies should I list? Hey, that's a, that's, that's quite a few, but

00:19:11.280 --> 00:19:19.120
I do hear that, I think we've seen a little glimpse into your, I guess, enthusiast coffee scene.

00:19:19.120 --> 00:19:25.120
Yeah, yeah. During the, what video was I called, uh, tax show and tell or something?

00:19:25.920 --> 00:19:32.080
Yeah, a couple of months ago, they, they asked me to come and show off some coffee technology. And

00:19:32.080 --> 00:19:37.840
so I, rather than show off the technology, I demonstrated the technology and I guess I took

00:19:37.840 --> 00:19:43.760
up like three quarters of the video, just showing how to make third wave, like decent coffee that you

00:19:43.760 --> 00:19:49.840
can actually extrapolate the specific variables and, and adjust for them and understand why things

00:19:49.840 --> 00:19:54.640
are doing the way things, why things are doing the things the way that they are and it would adjust

00:19:54.640 --> 00:20:00.320
for them. Um, and that was a lot of fun. Yeah. Uh, I've worked in coffee for a long time, uh,

00:20:00.320 --> 00:20:06.000
in, in various different cafes and, and so on. You're a barista? Yeah, I've been a barista. I,

00:20:06.000 --> 00:20:09.840
I've worked as a bartender for a number of years, uh, just, you know, part-time here and there while

00:20:09.840 --> 00:20:15.120
I was in school and before that. Uh, yeah, it's, it's a lot of fun. It's, it's super in-depth and

00:20:15.120 --> 00:20:20.720
like there's, there's this like subsection of the internet and I guess society at large, or at least

00:20:20.720 --> 00:20:25.520
Western society at large that is like super gatekeep-y about it, but I'm not a part of that. I just,

00:20:25.600 --> 00:20:31.440
I just enjoy it and I enjoy the science behind it and like being rigorous about it and just having,

00:20:31.440 --> 00:20:37.360
having a fun time. So yeah, try to demonstrate that. Do you have any pro tips for someone? I guess

00:20:37.360 --> 00:20:45.280
that's a rookie or a noob in the, in the coffee scene? Uh, I mean, there's buy better beans,

00:20:46.080 --> 00:20:49.840
always buy better beans, grind them yourself. That's the first step. If you are, if you're

00:20:50.720 --> 00:20:58.400
in the middle of having whatever coffee, you're probably not drinking the best quality beans that

00:20:58.400 --> 00:21:04.560
you could, like a, a nice Katerra or a Pacamara or a Nestle 32 or a Ruru or something that along

00:21:04.560 --> 00:21:09.360
those lines, a better quality bean is going to get you probably a solid 60% of the weight

00:21:09.360 --> 00:21:13.840
actually having decent quality coffee and then start to, if you have the money and have the

00:21:13.840 --> 00:21:18.400
interest in upgrading your coffee setup, then start to upgrade equipment, but don't do that first.

00:21:18.400 --> 00:21:22.560
Nice. I guess on that note, what are some of the other jobs you've heard in the past?

00:21:24.560 --> 00:21:30.560
Well, like I said earlier, I was, I was a mechanic for, for a number of years. I, I worked

00:21:31.520 --> 00:21:35.120
in lots of different shops and lots of different types of, of, of work there.

00:21:36.960 --> 00:21:44.000
I, I was the chair of my students association at SAIT for, for three years with that organization,

00:21:44.880 --> 00:21:50.640
um, which was a wild ride, uh, because I was working effectively full time at the same time

00:21:50.640 --> 00:21:58.800
as taking classes effectively full time. And the entire time I was, I was completely revamping,

00:21:58.800 --> 00:22:03.600
revamping the, the way that the organization worked from a fundamental level. We rewrote the

00:22:03.600 --> 00:22:08.000
bylaws, we got it passed in a nonprofit environment, which if you're in Canada and are aware of that

00:22:08.000 --> 00:22:16.480
is quite hard to do. Um, we, uh, rewrote and got passed a full new set of policies and procedures

00:22:16.480 --> 00:22:22.000
for the entire organization and the entire way that we interacted with students. And yeah,

00:22:22.000 --> 00:22:25.920
like that was, that was a massive undertaking at the same time as going through an engineering

00:22:25.920 --> 00:22:30.880
program, which if you're aware is typically quite hard, not gig keeping it. It just generally is.

00:22:30.880 --> 00:22:36.560
And at least for me, it was really tough. So I did that for far too long. Honestly,

00:22:36.560 --> 00:22:40.800
I should have quit my second year, but it gave me a lot of fun experience. And at the same time,

00:22:40.800 --> 00:22:46.960
I was also being the, I was working, uh, as the president of my community association in Calgary

00:22:47.840 --> 00:22:53.360
and working part time, uh, just, just weekend nights, like Saturday and Sunday nights at the

00:22:53.360 --> 00:23:00.640
campus bar at the gateway. Uh, and yeah, those, those were, those were fun. I was, uh, I was having

00:23:00.720 --> 00:23:07.840
a lot of fun, but also it was really stressful. And honestly, LTD doesn't really compare. There's

00:23:07.840 --> 00:23:12.800
a lot of stress here, but that was, that was a period of my life. I mean, it's kind of cliche,

00:23:12.800 --> 00:23:17.040
but it is, it's kind of a different stress. Like there's a lot more at stake here, or at least

00:23:17.040 --> 00:23:21.920
it feels like there's a lot more at stake here. Um, but Nick has a really good line. He, um,

00:23:21.920 --> 00:23:28.720
he, he says that, uh, he measures, uh, the way that a project goes by the severity of its worst

00:23:28.720 --> 00:23:34.720
problem. And a lot of the problems that we're encountering, at least lately in the last six

00:23:34.720 --> 00:23:40.960
months of Labs have been pretty low severity. So it feels like we're doing things right. We're

00:23:40.960 --> 00:23:46.720
getting our ducks in a row consistently and on time. And that's been really good to feel just,

00:23:46.720 --> 00:23:52.000
just to like watch the, the, the momentum of the big stone wheel start to carry itself. It's been

00:23:52.000 --> 00:23:59.280
nice. Something interesting, uh, I want to ask you about is you were an engineering designer

00:24:00.480 --> 00:24:06.000
at an oil field manufacturing company. Yeah. So, uh, one of the, one of the jobs that I, uh,

00:24:06.000 --> 00:24:13.440
worked in a summer between school, uh, I, uh, was at this company called drill form. Um,

00:24:14.080 --> 00:24:20.160
and that was, that was kind of my first like foray into actual engineering design. Um, as

00:24:20.240 --> 00:24:25.920
opposed to just like the, the math behind it. Um, design work is different. It's kind of the

00:24:25.920 --> 00:24:33.600
glamorous work of engineering, but it's, it's different when you're manufacturing something

00:24:33.600 --> 00:24:37.840
for actual service in a company than it is for designing something for, you know,

00:24:38.480 --> 00:24:41.840
school capstone or for at home, or if, you know, you're just printing something and

00:24:41.840 --> 00:24:47.760
putting it on thing, your births or printables. Um, so I, I worked for this company for the summer

00:24:47.760 --> 00:24:54.240
and we were designing things for severe service, uh, which is to say that the temperature ranges,

00:24:54.240 --> 00:24:59.360
uh, for actual service for these items were between negative 50 degrees Celsius and positive

00:24:59.360 --> 00:25:04.960
50 degrees Celsius. Um, as well as being in a heavily salted environments, uh, continuously

00:25:04.960 --> 00:25:10.560
underwater, uh, and a bunch of other things. And so we were designing a lot of really cool stuff

00:25:10.560 --> 00:25:15.760
that had to be incredibly robust. And so learning the iterative design process

00:25:16.480 --> 00:25:21.200
was very hands-on. Like there was a lot of, okay, I'm going to weld this together and see,

00:25:21.760 --> 00:25:27.200
uh, and put it under a, uh, uh, like a hydraulic tester and see what the actual press failure

00:25:27.200 --> 00:25:31.920
is going to be. Is that going to be strong enough? If I get that done a hundred times

00:25:33.040 --> 00:25:37.440
to see if, uh, if we can put this out into service in the oil field, that was a lot of fun.

00:25:37.440 --> 00:25:44.480
Um, so that was, that was four months, uh, during the summer and, uh, I worked for a guy

00:25:44.480 --> 00:25:49.760
named Mark Taggart, uh, who was actually the brother of one of my, uh, instructors at SAIT.

00:25:49.760 --> 00:25:56.480
And I had a lot of fun. Um, that job probably defines the majority of the way that I approach,

00:25:57.120 --> 00:26:02.880
uh, engineering, revisioning, um, especially the way that, uh, the way that, for example,

00:26:02.880 --> 00:26:09.120
I worked on turbo desk, the way that we started with, okay, this could be as a complex idea,

00:26:09.120 --> 00:26:14.240
um, a hunk of aluminum with a bunch of liquid channels flowing through it and a big heat sink.

00:26:14.560 --> 00:26:20.080
And that's a concept. And that's kind of what Alex came up to me and pitched as the idea just

00:26:20.080 --> 00:26:25.600
before he, uh, left for vacation, uh, when he threw it on me, uh, uh, in my first week.

00:26:25.600 --> 00:26:30.320
Uh, but that's not how you approach an actual engineering problem. You don't come up with

00:26:30.320 --> 00:26:35.360
the solution. You find out all of the specific problems that you need to solve. And then you

00:26:35.360 --> 00:26:39.520
come up with a bunch of potential solutions to those miniature problems. And then you draw

00:26:39.520 --> 00:26:43.360
a bunch of different lines through all of the options and you say, okay, this is solution number

00:26:43.360 --> 00:26:48.880
one. This is solution number two. This one is solution number three. What are those competing

00:26:48.880 --> 00:26:56.000
solutions for all of those problems? How do they look like within each of their contexts?

00:26:56.000 --> 00:27:00.560
Does this one make more sense than this one, than this one on a bunch of different scales?

00:27:00.560 --> 00:27:04.080
Like, are you looking through the lens of like the economics of actually manufacturing it

00:27:04.080 --> 00:27:09.120
over a short term or over a long term? What about the DFMA design for manufacturing assembly?

00:27:09.120 --> 00:27:15.840
Does this solution look like it's actually more createable than the other solutions are? Like there's a whole bunch of other lenses that you

00:27:15.840 --> 00:27:21.840
can do and you should never start with the actual end goal that you think you want to have, because

00:27:21.840 --> 00:27:27.840
it's very likely that in at least my limited experience, you will come to different conclusions

00:27:27.840 --> 00:27:32.720
than you thought you had at the beginning. And so that job really, like, there were a lot of like

00:27:32.800 --> 00:27:38.640
missed opportunities previously that I hadn't understood, but now in retrospect,

00:27:38.640 --> 00:27:46.080
I know from a design standpoint why they failed. So I've taken a lot of stuff from drill form

00:27:46.080 --> 00:27:50.320
into everything kind of forward and I'm really glad that I had the opportunity to do that during

00:27:50.320 --> 00:27:57.280
school. Tim, is there anything you hope to work on in the future at LMG? Something you're looking

00:27:57.360 --> 00:28:07.280
forward to? I'm looking forward to. If I was to say that I'm interested NVIDIA contents and like

00:28:07.280 --> 00:28:11.840
I wanted to be a part of video content, what I'd really like to see happen is that I get an AMD

00:28:11.840 --> 00:28:16.560
extreme tech upgrade for not not because I want the stuff because I want to show off something

00:28:16.560 --> 00:28:25.040
that I've been working on. Yeah. For my home lab, I have I'm designing a server rack that has a 3D

00:28:25.040 --> 00:28:31.760
printer and FDM 3D printer in the top of it, Voron Core XY, 2.4 if anybody who's watching cares.

00:28:32.720 --> 00:28:38.000
And specifically, it's a heated enclosure. So it'll take the heat of all of the server,

00:28:38.000 --> 00:28:44.880
the rack equipment in the lower section and based on whatever the specific temperature is that I'm

00:28:44.880 --> 00:28:51.200
setting in the G code, it will vent the heat to the enclosure of the printer above so that it keeps

00:28:51.280 --> 00:28:57.840
it consistent and ambient temperature for printing ABS or other materials that you want a nice enclosed

00:28:57.840 --> 00:29:03.200
area for. So it's scavenging waste heat from equipment that's already going to be running

00:29:03.200 --> 00:29:09.840
and it's just using it for, you know, to not waste energy. So I'd like to get that off the ground

00:29:09.840 --> 00:29:16.400
and actually do it. But in terms of like what I want to work on for like things that are actually

00:29:16.400 --> 00:29:23.920
useful to the organization, I think I think what I'd really like to see is for us to get some freaking

00:29:23.920 --> 00:29:31.280
whiteboards up in the lab. We've been waiting for them for so long. I just want to draw on the walls.

00:29:31.280 --> 00:29:35.680
Sorry. Sorry, swearing. I just want to draw on the freaking walls. Yeah.

00:29:38.000 --> 00:29:44.400
Like, I can't count how many times I will start to explain something to somebody and like go to the

00:29:44.400 --> 00:29:49.440
wall expecting there to be a whiteboard and just being like, okay, let's go find something else.

00:29:49.440 --> 00:29:52.480
Here's a piece of paper. Let's here's the actual thing that I want to show you. Like

00:29:53.280 --> 00:29:58.640
ideation happens visually. It's really useful to have things that you can place ideas down and

00:29:58.640 --> 00:30:02.400
leave them for a little bit and then come back to them. And we have one whiteboard that kind of floats

00:30:02.400 --> 00:30:07.120
around the room. But it's always full. It's always full because everybody uses it. I just want more.

00:30:07.120 --> 00:30:14.560
Can confirm I've seen this before. Yes. One of the one of the things that I would really like to see

00:30:14.560 --> 00:30:21.200
is once we've got once we've got like the base verticals outfitted onto our website. So like once

00:30:21.200 --> 00:30:26.880
we have headphones and keyboards and GPUs and CPUs and we've got all that stuff, I really,

00:30:26.880 --> 00:30:34.160
really, really wants to develop a like a wind tunnel. I am really interested in seeing the

00:30:34.240 --> 00:30:39.600
thermal differences, the way that you can cool using different pressures using different CFMs

00:30:39.600 --> 00:30:45.440
using the way that fans are structured is really fascinating to me. And I am by no means a thermodynamicist.

00:30:45.440 --> 00:30:52.240
However, I want to know more about fluid dynamics and getting my hands on the ability to do that

00:30:52.240 --> 00:30:58.080
from either whether it's just computer fans or whether it's the ability to scale up to a larger

00:30:58.080 --> 00:31:04.320
size, you know, even as big as like a box fan. What does that do for your ability to retain

00:31:04.320 --> 00:31:11.760
and expose heat to the atmosphere? Air is an absolutely shitty conductor. It does a terrible

00:31:11.760 --> 00:31:21.600
job of removing heat and the fluidic properties of actual air like as it flows through a room.

00:31:21.600 --> 00:31:26.560
And that's really fascinating to me. I would like to know more about the way that we

00:31:27.280 --> 00:31:33.760
the way that we use computers from a fundamental like a molecular level in that sense and designing

00:31:33.760 --> 00:31:38.880
a wind tunnel that we can test different fans and test different coolers across those fans would be

00:31:38.880 --> 00:31:45.280
super neat. So I'm really excited for the chance to potentially next year get to do that. I know

00:31:45.280 --> 00:31:50.720
of a couple of hobbyists who have some pretty neat setups, but I don't know of anybody who has

00:31:51.520 --> 00:31:58.720
kind of what I'm envisioning in terms of in terms of the actual design of an all-encompassing

00:32:00.160 --> 00:32:07.120
robust and academic and repeatable setup. That's the other thing is anything that we're

00:32:07.120 --> 00:32:12.960
building here, it's not just jank. We do not do that in the lab. We create something, we prototype

00:32:12.960 --> 00:32:18.720
it and then we refine it to make sure that every time we run a test, we get the same result. It's

00:32:18.720 --> 00:32:25.520
important. Do you have any final words for Floatplane? Final words for Floatplane. If you can

00:32:25.520 --> 00:32:32.880
apply pressure to the organization in any way, I would suggest that you do it as such. Ask Linus

00:32:32.880 --> 00:32:38.080
to make more bunny hugs. Bunny hugs are great. They're fantastic for people who have sensory

00:32:38.800 --> 00:32:42.560
problems and can't wear zippers. They're very comfortable if you just want to wear a hood because

00:32:42.560 --> 00:32:48.880
you have no hair. If you feel a little bit annoyed at something, you can just put your hands in your

00:32:48.880 --> 00:32:53.360
pockets and close your mouths and you're good. Bunny hugs are phenomenal and I would recommend

00:32:53.360 --> 00:32:58.000
everybody wear them and the lttstore.com sells more of them. So if you want to say anything on

00:32:58.000 --> 00:33:03.200
the comments of this video, please ask for a nice new bunny hug. Thanks Tim.
