{"video_id":"kZr_5_5w68A","title":"Writers Showcase their First Script - Adam Sondergard","channel":"FP Exclusives","show":"FP Exclusives","published_at":"2025-05-04T14:53:29Z","duration_s":1460,"segments":[{"start_s":0.0,"end_s":5.4719999999999995,"text":"Adam: Hello I'm Adam, I've been a writer at Linus Media Group for about two? 2 00:00:05.472 --> 00:00:07.474 Almost three years. three years in November. 3 00:00:07.674 --> 00:00:09.275 So I actually applied twice, 4 00:00:09.275 --> 00:00:13.880 the first time I applied was probably in 2018 or 2019. 5 00:00:13.880 --> 00:00:16.816 And I remember at the time I was working at an escape room. 6 00:00:16.883 --> 00:00:20.153 As well- Part-time at an escape room, 7 00:00:20.153 --> 00:00:24.024 and part-time doing business to business sales in grocery stores. 8 00:00:24.024 --> 00:00:26.626 And I was just kind of doing writing stuff on the side, 9 00:00:26.626 --> 00:00:28.428 as well as doing a bunch of improv at the time. 10 00:00:28.428 --> 00:00:30.230 The first time I applied, I basically I got an interview. 11 00:00:30.230 --> 00:00:31.664 I basically bombed the interview. 12 00:00:31.698 --> 00:00:32.665 Sammy: *Laughs* 13 00:00:32.966 --> 00:00:36.302 Adam: Yeah, I think I talk about why if you go to my Meet the Team video, 14 00:00:36.302 --> 00:00:38.104 from like a year and a bit ago. 15 00:00:38.104 --> 00:00:41.041 Basically long story short is that I bombed the interview; 16 00:00:41.041 --> 00:00:46.279 but then six months later, they bought that script off of me, used it for a TechQuickie. 17 00:00:46.279 --> 00:00:49.616 But since that one was made into a video, I'm not going to check out that script today, 18 00:00:49.616 --> 00:00:52.152 because you can just watch the video on TechQuickie. 19 00:00:52.152 --> 00:00:55.922 I will however do the script from the second time I applied. 20 00:00:56.489 --> 00:01:00.560 Well outside of like doing writing in an academic setting for like university, 21 00:01:00.560 --> 00:01:02.595 I did not have a ton of writing experience. 22 00:01:02.595 --> 00:01:06.933 It was something I had a knack for, but not something I ever actually really tried to pursue professionally. 23 00:01:06.933 --> 00:01:11.871 At the times that I applied I had like a music blog, 24 00:01:11.871 --> 00:01:16.242 that I was kind of updating very infrequent, relatively infrequently 25 00:01:16.242 --> 00:01:17.944 a lot of the times when I was looking for writing jobs. 26 00:01:17.944 --> 00:01:19.946 I've just been in a creative field for a long time. 27 00:01:19.946 --> 00:01:22.449 I was a theater kid in high school and stuff like that; 28 00:01:22.449 --> 00:01:26.319 so I've always kind of wanted to- Liked creating stuff. 29 00:01:26.553 --> 00:01:31.491 Adam: I mean like, I guess it's tough to gauge; because definitely a lot of interest in tech. 30 00:01:31.491 --> 00:01:34.494 I had built my own computers and built computers for friends at that point. 31 00:01:34.494 --> 00:01:37.497 but I was just an enthusiast and a generalist, 32 00:01:37.497 --> 00:01:43.470 and I think also like I just had a deep passion for the tech side of things; 33 00:01:43.470 --> 00:01:47.474 as well as I think- I like to think I'm a quick learner. 34 00:01:48.441 --> 00:01:50.710 I think one of the things that I bring, 35 00:01:50.777 --> 00:01:52.846 that I was bringing to the table is that I have a background, 36 00:01:52.846 --> 00:01:58.218 I went to school for neuroscience; so I have a Bachelor of Science in neuroscience. 37 00:01:58.218 --> 00:02:04.424 And that kind of gave me a very like, human centric look at um, 38 00:02:04.457 --> 00:02:07.060 like thinking about tech and how it affects us. 39 00:02:07.894 --> 00:02:10.730 That was always a big part of it for me that made it me really interested. 40 00:02:10.730 --> 00:02:12.298 Adam: Oh, yeah, I'd been watching for a while, 41 00:02:12.332 --> 00:02:15.435 the reason I applied was because they put out a video for writers. 42 00:02:15.435 --> 00:02:18.671 The first time I applied, I think that's how they found writers. 43 00:02:18.671 --> 00:02:21.508 They didn't like do job postings; they like, put out a video. 44 00:02:21.508 --> 00:02:25.812 No, both- So the first script was um... yeah, it was my own prompt 45 00:02:25.812 --> 00:02:29.415 and I remember Linus being like this is more of a TechQuickie, and I was like, I know. 46 00:02:29.516 --> 00:02:30.383 Sammy: Hahahahaha 47 00:02:30.416 --> 00:02:30.550 Sammy: \"I know\". 48 00:02:30.550 --> 00:02:31.885 Sammy: It looks like your own prompt, It's- 49 00:02:31.918 --> 00:02:32.552 Adam: Yeah. 50 00:02:32.585 --> 00:02:33.386 Sammy: And now it's time to upgrade. 51 00:02:33.686 --> 00:02:37.090 Adam: And then the most- then this one that at the time was also my own prompt was like, 52 00:02:37.090 --> 00:02:39.292 I was more interested in answering a different question; 53 00:02:39.292 --> 00:02:42.662 and I wanted to show in my application that I was like, not- 54 00:02:42.662 --> 00:02:45.431 I didn't want to just write a review because like I think, honestly 55 00:02:45.431 --> 00:02:48.434 it's very easy to write a review; because you don't have to think of an idea, 56 00:02:48.434 --> 00:02:50.203 you just talk about a product. 57 00:02:50.203 --> 00:02:53.640 Easy is not the word, I think that there's a trap that you can fall into with writing reviews; 58 00:02:53.640 --> 00:02:56.643 where you just talk about a product, and 59 00:02:56.676 --> 00:03:02.382 It's important especially as like a new writer to be coming in with your angle, 60 00:03:02.415 --> 00:03:05.818 and finding your idea about the product, you don't just want to talk about like- 61 00:03:05.818 --> 00:03:09.355 It's a useful resource to just do a review that just talks about a product, 62 00:03:09.355 --> 00:03:11.824 that goes through all the features, and it's very specific; 63 00:03:11.858 --> 00:03:15.662 but it's important, that you also have to have an angle 64 00:03:15.695 --> 00:03:18.531 and you're telling a story at the same time with a review. 65 00:03:18.531 --> 00:03:21.100 which is why like there's kind of a difference between say, 66 00:03:21.100 --> 00:03:24.737 like how we've done CPU reviews, which are far more focused on being like 67 00:03:24.737 --> 00:03:28.141 here's the details about this specific product; 68 00:03:28.141 --> 00:03:31.544 and say a review that we do on like a new TV, 69 00:03:31.544 --> 00:03:35.448 Where we want to tell more about the story, or the coverage to CPUs 70 00:03:35.448 --> 00:03:38.785 versus the coverage we give To a TV, is a little bit different; 71 00:03:38.785 --> 00:03:42.755 because a TV is something that we can find an angle and a story with 72 00:03:42.755 --> 00:03:47.527 a bit easier than a CPU, and a CPU is also something that the audience wants to just know, 73 00:03:48.094 --> 00:03:49.629 like how does it do? 74 00:03:49.696 --> 00:03:52.966 I didn't want to do a review, also I was broke as hell; 75 00:03:52.999 --> 00:03:54.667 so I didn't have any products to review. 76 00:03:54.667 --> 00:03:57.604 Sammy: I think Eli had the same prompt as you, or he made the same prompt as you. 77 00:03:57.604 --> 00:03:59.472 Adam: Yeah, his was pretty similar, but I did it better. 78 00:03:59.472 --> 00:04:00.840 Sammy: Hahahahahaha! Adam: *Laughs* 79 00:04:01.341 --> 00:04:03.309 Adam: I mean, so part of it was an interesting discussion. 80 00:04:03.309 --> 00:04:05.645 For me a part of it was answering a question that I had, 81 00:04:05.645 --> 00:04:09.983 which was like is there a way to tell-? Basically who's gonna get ripped off? Is my question; 82 00:04:09.983 --> 00:04:13.186 is it the person who has to buy the cheap- who can only afford the cheapest thing at any given point? 83 00:04:13.486 --> 00:04:17.090 And has to upgrade more times? Is it the person who can buy the middle-of-the-road thing? 84 00:04:17.090 --> 00:04:20.226 And upgrade once every five years? Or is it the guy who bought the super best computer, 85 00:04:20.226 --> 00:04:23.263 the most expensive computer at the time; and only upgrades once every 10 years? 86 00:04:23.263 --> 00:04:28.635 There's a lot of places in life where being poor, or not being able to afford stuff 87 00:04:28.635 --> 00:04:30.570 ends up being more expensive in the long run. 88 00:04:30.570 --> 00:04:34.474 It's like if you buy, if you can only afford for like $20 or $40 shoes, 89 00:04:34.474 --> 00:04:39.012 you're gonna spend up more money over the course of 10 years buying shoes to replace them, 90 00:04:39.012 --> 00:04:43.149 because you have to replace a pair every 10 years; than if you bought like a solid pair of $200 boots. 91 00:04:43.149 --> 00:04:45.985 I wondered if that kind of applied to computers. 92 00:04:45.985 --> 00:04:48.888 When making a big purchase timing can be everything. 93 00:04:48.888 --> 00:04:52.458 The last thing you want to be is someone who purchased a 2080 Ti in May of this year 94 00:04:52.458 --> 00:04:55.261 only to find out you could have received the same performance for half the price 95 00:04:55.261 --> 00:04:56.996 if you had just waited another six months. 96 00:04:56.996 --> 00:05:01.467 But you also don't want to be the guy whose sluggish machine can barely play today's biggest titles. 97 00:05:01.467 --> 00:05:04.070 So is there an upgrade strategy that works best? 98 00:05:04.270 --> 00:05:05.772 Should we do cheap and frequent upgrades? 99 00:05:05.772 --> 00:05:09.142 Or buy big now and be happy with a beastly rig for the next few years? 100 00:05:09.609 --> 00:05:12.812 Well to answer this we've built three rigs that reflect the types of machines 101 00:05:12.812 --> 00:05:15.014 different people would have bought way back in 2013 102 00:05:15.014 --> 00:05:17.917 to find out if there is an upgrade strategy that works best. 103 00:05:17.917 --> 00:05:21.120 Speaking of an upgrade, upgrade your life with our sponsor. 104 00:05:21.120 --> 00:05:22.488 Honestly, it's not bad. 105 00:05:23.423 --> 00:05:25.124 It cuts straight to the point. 106 00:05:25.124 --> 00:05:30.530 I think the first sentence would be changed a lot, in terms of just kind of getting to the point. 107 00:05:30.530 --> 00:05:34.901 Being more specific sooner, you I could just cut out the first sentence, I could just say 108 00:05:34.901 --> 00:05:38.504 the last thing you want to be is somebody who purchased a 2080Ti in May of this year 109 00:05:38.504 --> 00:05:41.974 only to find out you could have received the same performance for half the price just six months later. 110 00:05:42.041 --> 00:05:45.545 Honestly, I dunno, this is like a pretty solid intro. 111 00:05:45.611 --> 00:05:46.913 Adam: It would be a little bit of just trimming the fat; 112 00:05:46.913 --> 00:05:50.316 but I think it gets to the point, we tell it we get the premise of the video, you're immediately hooked. 113 00:05:50.316 --> 00:05:53.419 There could be massage and improved, but I got to the point of it. 114 00:05:53.453 --> 00:05:57.557 I'd rate it like a 6 or a 7; I think it's solid but, 115 00:05:57.557 --> 00:06:00.893 it needs to be finessed to really get it to the last kind of like 8 or 9. 116 00:06:00.893 --> 00:06:03.496 Like I would just, I just like watched several LTT- 117 00:06:03.496 --> 00:06:07.100 I'd like remember writing this, and I was like how do LTT videos start? 118 00:06:07.100 --> 00:06:11.671 And I watched like 20 and 30 of them, where I just watched the first like minute. 119 00:06:11.671 --> 00:06:14.173 And that's basically I just was like, okay this is how they do it; 120 00:06:14.173 --> 00:06:17.877 so I'm gonna like try and make sure that my intro's formulated like that. 121 00:06:17.877 --> 00:06:21.614 Adam: So why 2013 you may ask? Now that consoles have such a massive place in the market; 122 00:06:21.614 --> 00:06:26.386 it is rare to see any games that made by AAA studios that are specifically for PC. 123 00:06:26.386 --> 00:06:31.758 This has got me thinking that the best time to upgrade is near, or shortly after a console launch; 124 00:06:31.758 --> 00:06:36.496 because game studios will now be creating releases that are targeting this year's console hardware 125 00:06:36.496 --> 00:06:39.999 for the next several years; which lends to the idea that if you buy a current computer hardware, 126 00:06:39.999 --> 00:06:43.503 you should be set for the next, most of the next console generation, 127 00:06:43.503 --> 00:06:47.273 assuming you don't mind console-like performance in your video games. 128 00:06:47.273 --> 00:06:49.008 That's a clunky sentence at the end. 129 00:06:49.041 --> 00:06:50.076 Sammy: Hahahaha. 130 00:06:50.343 --> 00:06:52.512 Adam: To test this we've set a budget of $1400 131 00:06:52.512 --> 00:06:55.882 to be spent over seven years spanning this console generation. 132 00:06:55.882 --> 00:06:59.318 The budget will be spent in three ways; a budget system with frequent upgrades, 133 00:06:59.318 --> 00:07:02.054 a mid-range system that has infrequent but more significant upgrades, 134 00:07:02.054 --> 00:07:05.491 and an all-out high-end PC that is still running unchanged today. 135 00:07:05.658 --> 00:07:10.329 I chose this budget, because I could use my own computer 136 00:07:10.730 --> 00:07:11.497 Sammy: hahahaha. 137 00:07:11.531 --> 00:07:15.101 Adam: to test, because that's how much I spent on my computer in 2013. 138 00:07:15.101 --> 00:07:20.606 And so then I did do an upgrade, it like, I ended up being the mid-range guy for this; 139 00:07:20.606 --> 00:07:22.708 so I could actually do some benchmarking for it. 140 00:07:22.809 --> 00:07:26.979 Funny enough, for the rest of the results I had to use UserBenchmark. 141 00:07:27.113 --> 00:07:32.618 Which is a, has a pretty bad reputation these days, but it was a practice not an actual- 142 00:07:32.618 --> 00:07:35.288 It was, the point of it was practicing, I couldn't- 143 00:07:35.288 --> 00:07:37.490 I didn't have hardware to test, let's keep going. 144 00:07:37.690 --> 00:07:41.027 Each of these systems will be benchmarked against games that released from their day, 145 00:07:41.027 --> 00:07:46.065 games from around 2016 to 2017 and... oh yeah, this is a weird sentence. 146 00:07:46.065 --> 00:07:49.469 Each of these systems will be benchmarks to games from their day, 147 00:07:49.469 --> 00:07:54.006 games from 2016 or 2017, right around the time of the PS4 Pro and Xbox One X releases, 148 00:07:54.006 --> 00:07:57.777 and games from this very year to see how their performance holds up. 149 00:07:57.777 --> 00:08:00.680 \"This year\" would have been 2020. 150 00:08:00.680 --> 00:08:04.684 So place your bets, who will end up on top financially? The high-end but patient enthusiast? 151 00:08:04.684 --> 00:08:07.887 The mindfully priced mid-ranger? Or the Bargain-seeking budget build? 152 00:08:07.887 --> 00:08:10.356 Here I see an issue where it's like, that's a great sentence; 153 00:08:10.356 --> 00:08:12.191 that could have been tossed up at the intro. 154 00:08:12.191 --> 00:08:13.159 So, and I have guidance; 155 00:08:13.192 --> 00:08:16.662 Linus will jump and turn on the spot, as a wipe comes across the screen, 156 00:08:16.662 --> 00:08:19.332 he'll be wearing his old \"Professional Unboxer\" shirt. 157 00:08:19.332 --> 00:08:21.968 I wanted Linus to look like he was from a 2013 video. 158 00:08:21.968 --> 00:08:28.641 Our first PC is the 2013 budget gamer, featuring an Intel Core i5-4430 Quad-Core locked at 3 gigahertz, 159 00:08:28.641 --> 00:08:34.914 8 GB of Patriot Signature RAM, and an NVIDIA 650 Ti graphics card. Clocking in at about $650. 160 00:08:34.914 --> 00:08:40.953 The second PC is the Mid-Range Gamer, with an Intel Core i5-4670k running at 3.4 gigahertz, 161 00:08:40.953 --> 00:08:46.859 16 gigs of Corsair Vengeance RAM, and an AMD R9 280x, totaling at $950 big ones. 162 00:08:46.926 --> 00:08:52.698 Our third PC is a high-end beast from 2013, with a top-of-the-line Intel Core i7-4470K- 163 00:08:52.698 --> 00:08:55.268 That's, probably not the CPU it should be... 164 00:08:55.468 --> 00:08:58.037 Adam: That should probably be like a 4770k. 165 00:08:58.037 --> 00:08:58.571 Sammy: I love how you're... 166 00:08:58.571 --> 00:09:00.473 Adam: Yeah, sorry, I don't why I edited it. 167 00:09:00.506 --> 00:09:02.408 Adam: You know, it's not as bad as I thought it was gonna be. 168 00:09:02.408 --> 00:09:03.743 There's a lot of things I would change, 169 00:09:03.743 --> 00:09:06.679 but I think it's got the bones of something that's good and makes sense. 170 00:09:06.679 --> 00:09:11.284 Like I wouldn't have slammed all of these specs back to back. 171 00:09:11.284 --> 00:09:14.020 And I think one thing that I've learned as I've written 172 00:09:14.020 --> 00:09:17.456 is that a lot of the stuff that I'm saying right now, can be shown on screen. 173 00:09:17.456 --> 00:09:20.893 I could be like, we have three gaming systems, 174 00:09:21.594 --> 00:09:25.631 one featuring an Intel Core and an NVIDIA 650 Ti graphics card. 175 00:09:25.631 --> 00:09:29.101 I could've just had like two pieces of hardware; the CPU and the GPU, 176 00:09:29.101 --> 00:09:32.138 then shown the rest of the parts; which is what I did. 177 00:09:32.138 --> 00:09:34.173 And it was like, kudos to me... 178 00:09:34.240 --> 00:09:40.446 I did specifically only choose the Processor, RAM, and GPU to talk about; 179 00:09:40.446 --> 00:09:41.781 because those would be the most relevant, 180 00:09:41.781 --> 00:09:43.916 I didn't bother talking about the motherboard or anything like that; 181 00:09:43.916 --> 00:09:47.520 so like, good that I had a knack for like what's actually important. 182 00:09:47.520 --> 00:09:50.456 It's just have to like be like bam bam bam, with so many specs. 183 00:09:50.456 --> 00:09:52.858 I would try and probably massage and space that out. 184 00:09:52.858 --> 00:09:56.262 That I would probably maybe move and talk about the results from one. 185 00:09:56.262 --> 00:09:57.930 I would go like, here's the budget gamer, 186 00:09:57.930 --> 00:10:00.967 how does it hold up in the games from 2013? Bring that in. 187 00:10:00.967 --> 00:10:04.270 Then I would introduce the mid-ranger, do the results in 2013; 188 00:10:04.270 --> 00:10:06.772 then I would introduce the high-end beast, that would make it less like 189 00:10:06.772 --> 00:10:09.208 oh my god, he's yelling numbers and words at me. 190 00:10:09.208 --> 00:10:11.010 And then we would go into just being like, 191 00:10:11.010 --> 00:10:16.182 okay and then how do they all do in the middle of the decade games. 192 00:10:16.182 --> 00:10:19.251 Also, this is the other kind of stuff that we would cut out nowadays. 193 00:10:19.485 --> 00:10:22.488 Now that we know what hardware we're dealing with, let's take a look at how they run; 194 00:10:22.488 --> 00:10:23.689 it's like shut up, just do that. 195 00:10:23.923 --> 00:10:27.860 We can and then you can see the variance in performance across these systems already in games like 196 00:10:27.860 --> 00:10:29.195 Tomb Raider and Bioshock Infinite, 197 00:10:29.962 --> 00:10:31.597 and I just have benchmarking graphs. 198 00:10:31.597 --> 00:10:32.732 So like this took a long time to write, 199 00:10:32.732 --> 00:10:36.402 because I had to find hardware that was also all like from the same source. 200 00:10:36.402 --> 00:10:38.804 So I could steal their numbers and write something that's relatively true, 201 00:10:38.804 --> 00:10:42.708 because I wanted to show that I had like the abilities to analyze data and talk about it. 202 00:10:42.708 --> 00:10:45.878 Our high-end system absolutely destroys these benchmarks at 1080p, 203 00:10:45.878 --> 00:10:48.881 and really stretches its legs at 1440p with the 780 Ti 204 00:10:48.881 --> 00:10:53.519 pulling out an impressive 71 FPS in infinite and at 1440p. 205 00:10:53.519 --> 00:10:55.221 Yeah, see this is now I'm jumbling; 206 00:10:55.254 --> 00:10:59.325 talking about 1080p and then talking about 1440p, and it's already confusing. 207 00:10:59.325 --> 00:11:03.162 So I really- I would have sectioned this off as, we're gonna talk about 1080p, 208 00:11:03.162 --> 00:11:04.563 then we're gonna talk about 1440p. 209 00:11:04.597 --> 00:11:09.135 The 650 Ti is already struggling to pull a steady 30 FPS and Ultra settings, 210 00:11:09.135 --> 00:11:13.572 but jumping down to medium and lowering anti-aliasing nets us a respectable 63 FPS average. 211 00:11:13.606 --> 00:11:16.709 Remember this card was made to be driven at 1080p. 212 00:11:16.709 --> 00:11:21.380 The 280x is doing a good job pulling 50 FPS, we see similar performance from these cards 213 00:11:21.380 --> 00:11:27.787 and we take a look at Tomb Raider where the 780 Ti and 1080p runs at a blistering 146 FPS. 214 00:11:27.787 --> 00:11:34.427 The mid-range system scores 105 FPS, and our budget system pulls out a solid 75 FPS. 215 00:11:34.427 --> 00:11:37.563 Again, this is one of those things where it's like now that I know how to- 216 00:11:37.563 --> 00:11:40.366 Especially after writing several reviews, I know that we're highlight- 217 00:11:40.366 --> 00:11:43.602 It's more like, it's less about talking about everything in the graph, 218 00:11:43.602 --> 00:11:50.309 and it's more about writing about what is the story that's being told in those graphs? 219 00:11:50.342 --> 00:11:52.178 Like that's where the whole point is, that the viewer can pause; 220 00:11:52.211 --> 00:11:56.782 so we don't feel the need in our videos to talk about every single point on the graph. 221 00:11:56.782 --> 00:11:59.285 We want to be like, here's the most important things to note; 222 00:11:59.785 --> 00:12:02.488 and this is what weaves the story. 223 00:12:02.488 --> 00:12:04.824 And so what I'm doing here is I'm just like reading out the graph, 224 00:12:04.824 --> 00:12:08.427 which is like what's the point of showing the graph if I'm just gonna read it out; 225 00:12:08.427 --> 00:12:12.498 but I do cut right to the chase, because I go, now let's jump ahead a few years 226 00:12:12.498 --> 00:12:15.401 and see how these systems are holding up around three and a half years later; 227 00:12:15.401 --> 00:12:20.439 when the PS4 Pro and Xbox One X launched, and I said launch, it's a typo right there. 228 00:12:20.439 --> 00:12:25.010 Here we're gonna benchmark our systems using Hitman 2016, Rise of the Tomb Raider, and Doom 2016. 229 00:12:25.544 --> 00:12:26.946 As we can see from our benchmarks, 230 00:12:26.946 --> 00:12:30.382 the budget system is already in dire straits with these more demanding titles; 231 00:12:30.382 --> 00:12:33.753 barely getting 20 FPS in our Hitman 2016 benchmark, 232 00:12:33.753 --> 00:12:38.190 and it isn't until we dial back the graphics to medium that we are getting 30 to 40 FPS, 233 00:12:38.691 --> 00:12:41.327 which is the cutoff to what we would call playable. 234 00:12:42.394 --> 00:12:44.497 It's kind of looking like a good time to upgrade. 235 00:12:44.497 --> 00:12:48.467 Our 2020 games clearly show those, our systems' deficiencies. 236 00:12:48.467 --> 00:12:52.638 So here again, I've just- I've changed the order of how we're talking about it, 237 00:12:52.705 --> 00:12:54.073 Are we talking 1080p? Are we talking resolution? 238 00:12:54.106 --> 00:12:56.509 Are we talking all of the things at the same resolution? 239 00:12:56.542 --> 00:13:04.850 Is the scenario for this video going system by system? Or Is it going year by year? 240 00:13:04.850 --> 00:13:10.422 And I've kind of mixed, like I've pivoted to talking about one system through multiple years, 241 00:13:10.589 --> 00:13:11.757 and that's what's gonna be confusing. 242 00:13:12.258 --> 00:13:15.027 Our 2020 games clearly show our systems' deficiencies. 243 00:13:15.027 --> 00:13:17.596 The budget system basically can't play modern titles, 244 00:13:17.596 --> 00:13:21.033 and the mid-range build is starting to struggl- Oh really I just- 245 00:13:21.033 --> 00:13:24.470 Okay no, now I'm getting it; it seems like I just kind of only talk about the mid-range... 246 00:13:24.470 --> 00:13:31.243 The budget system? I guess I was showing the graphs at the time; 247 00:13:31.243 --> 00:13:33.145 so I would have only been talking about certain things. 248 00:13:33.145 --> 00:13:36.882 One thing I will notice, I will note is that there's like no guidance in here; 249 00:13:36.882 --> 00:13:41.387 so much of this would be Linus just talking at a camera, I should have done way more guidance. 250 00:13:41.387 --> 00:13:45.124 Now we like to, we use coverage to site sources; 251 00:13:45.124 --> 00:13:46.859 to be like, yeah we said this thing, 252 00:13:46.859 --> 00:13:49.895 then this thing's backed up from this website that we got that information from, 253 00:13:49.895 --> 00:13:51.897 as well as to just add visual interest; 254 00:13:51.897 --> 00:13:55.701 but my brain didn't think like that, my brain was in a, I write things as text mode; 255 00:13:55.701 --> 00:13:57.670 because that's all I had done for most of my life. 256 00:13:57.670 --> 00:13:59.505 Sammy: I mean, I think that's what I thought, that they probably cared about 257 00:13:59.505 --> 00:14:02.808 is like how well you can write, and they can probably teach you how to like, 258 00:14:02.808 --> 00:14:04.476 just have more visuals, I guess. 259 00:14:04.476 --> 00:14:08.848 Adam: Yeah, and a big part of it, that they care a lot about just having the fundamentals there. 260 00:14:08.848 --> 00:14:11.750 Our 2020 games clearly show our systems deficiencies; 261 00:14:11.750 --> 00:14:13.886 the budget system basically can't play modern titles 262 00:14:13.886 --> 00:14:16.689 and the mid-range build is starting to struggle with games like Death Stranding. 263 00:14:16.689 --> 00:14:20.459 The high-end Build however is still giving us stable frame rates on intense games; 264 00:14:20.459 --> 00:14:24.096 but we're not really doing anything better than a console can put out right now. 265 00:14:24.096 --> 00:14:28.100 So let's imagine if we decided to upgrade our systems in 2016, 266 00:14:28.100 --> 00:14:30.870 to keep up- In 2016 to keep up with the console refreshes. 267 00:14:30.870 --> 00:14:33.105 Sammy: You have 15 \"so's\" in the script. 268 00:14:33.105 --> 00:14:34.607 Sammy: Hahahaha. Adam: Yeah, I realize, yeah. 269 00:14:34.607 --> 00:14:39.378 Adam: That's actually funny, that's a rule that I honestly disagree with on some occasions with Linus. 270 00:14:39.378 --> 00:14:43.082 So the \"so\" is banned thing, makes a lot more sense when you're doing a vlog. 271 00:14:43.115 --> 00:14:43.549 Sammy: Mmmm. 272 00:14:43.549 --> 00:14:48.320 Adam: Because a lot of people will start saying \"so\", as a preamble to the rest of their sentence; 273 00:14:48.320 --> 00:14:51.423 and when you cut a bunch of sentences together, it gets really obnoxious. 274 00:14:51.423 --> 00:14:55.060 When you're- In a script, saying the word \"so\" is a little bit better, 275 00:14:55.060 --> 00:14:59.164 but I do say so two sentences in a row, and one I don't need it. 276 00:14:59.198 --> 00:15:03.435 Going like, \"so let's imagine we decided to upgrade our systems in 2016\"; 277 00:15:03.435 --> 00:15:07.139 Is a fine usage of the word \"so\", because it kind of helps it ebb and flow, 278 00:15:07.172 --> 00:15:10.643 and it indicates to the viewer that we're moving on to the next subject, 279 00:15:11.110 --> 00:15:13.312 but you don't want to use them too many. 280 00:15:13.312 --> 00:15:17.049 It's time has come only after three and a half years, it's upgrade time. 281 00:15:17.049 --> 00:15:18.717 See that's a weird sentence, yuck. 282 00:15:19.418 --> 00:15:23.155 Not only do we have the worst price to performance ratio out of all of our rigs. 283 00:15:23.222 --> 00:15:24.790 There's a link to a Google Docs sheet. 284 00:15:24.823 --> 00:15:27.860 I will say the most embarrassing thing about this was not looking at my script; 285 00:15:27.860 --> 00:15:31.196 it was going back and looking at my spreadsheet. 286 00:15:31.363 --> 00:15:32.932 Adam: Awful, awful. 287 00:15:33.365 --> 00:15:35.200 Adam: I wasn't sure if I was gonna show it to them, 288 00:15:35.200 --> 00:15:38.771 but I realized that for this kind of script I need to show them something 289 00:15:38.771 --> 00:15:41.040 or else I'm just kind of like yelling numbers at a page; 290 00:15:41.040 --> 00:15:46.912 and I wanted to show them that I also know how to do some graphing as well as like, parse data, 291 00:15:46.912 --> 00:15:52.818 but I kind of only made the spreadsheet for me, and I did not have enough time to fix it, 292 00:15:52.851 --> 00:15:55.020 to make it like really nice and presentable; 293 00:15:55.020 --> 00:15:57.890 so I kind of just tacked it in at the end there, which might not have been the smartest move. 294 00:15:57.957 --> 00:16:01.660 I'm still- I still got hired, but I'm just- Maybe I would have gotten hired sooner. 295 00:16:01.694 --> 00:16:02.728 Sammy: Hahahahaha. 296 00:16:03.095 --> 00:16:06.999 Adam: When it comes to this- This has the worst price to performance ratio of all of our rigs; 297 00:16:07.466 --> 00:16:08.300 but when it comes to that- 298 00:16:08.300 --> 00:16:11.537 When it comes to this system, our non overclockable CPU is starting to feel the heat; 299 00:16:11.537 --> 00:16:14.840 so we are going to upgrade that too, which means we need to upgrade our motherboard. 300 00:16:14.840 --> 00:16:18.577 Oh no, this means a lot of money that we saved going budget back in 2013 301 00:16:18.577 --> 00:16:22.915 is going to have to be spent on components that don't provide a meaningful uplift in performance. 302 00:16:23.382 --> 00:16:26.018 Maybe we aren't saving as much as we thought we were. 303 00:16:26.018 --> 00:16:29.421 So with our remaining budget we upgraded the mobo to a newer model, 304 00:16:29.421 --> 00:16:35.894 got a new kit of RAM and upgraded to a Ryzen 1500X and a GTX 1060, just barely squeezing into our budget. 305 00:16:35.928 --> 00:16:38.564 I think this is a good paragraph now. 306 00:16:38.564 --> 00:16:40.032 I mean the- Yeah, I'd fix some things, 307 00:16:40.065 --> 00:16:40.432 Sammy: Yeah. 308 00:16:40.466 --> 00:16:43.002 Adam: but like yeah, pretty much. 309 00:16:43.002 --> 00:16:45.104 It's just like okay here's the point, here's what it is. 310 00:16:45.104 --> 00:16:49.942 It's interesting, because now overclocking just doesn't matter; but back then overclocking was huge. 311 00:16:49.942 --> 00:16:58.117 I remember the system I had that I built in 2013 had a i7-2600K, 312 00:16:58.117 --> 00:17:03.355 and I think the boo- the base boost was like 3.8 gigahertz or something? 313 00:17:03.355 --> 00:17:06.158 But I overclocked it to 5 gigahertz. 314 00:17:06.892 --> 00:17:11.797 Like stable all core, because that's just what you could do back then? It was wild. 315 00:17:11.830 --> 00:17:14.500 Our mid-range build is still getting the job done in 2016, 316 00:17:14.533 --> 00:17:17.870 but we have some spare cash for performance uplift, so let's just upgrade the GPU. 317 00:17:17.870 --> 00:17:20.139 We can spend some good money on a new card 318 00:17:20.139 --> 00:17:23.709 and still be spending less than our big spender did over there in 2013. 319 00:17:23.709 --> 00:17:25.744 That- I just added the \"in 2013\"; 320 00:17:25.778 --> 00:17:27.846 Sammy: Yeah. Adam: because that clarifies that sentence. 321 00:17:27.946 --> 00:17:32.851 We'll keep this CPU and upgrade to a fancy new GTX 1070, and see what kind of pep this puts in our step. 322 00:17:32.851 --> 00:17:35.721 Oh and look at that, we still have about $50 left in our budget; 323 00:17:35.754 --> 00:17:37.890 $50 we could spend at LTTStore.com. 324 00:17:37.890 --> 00:17:40.092 Adam: I, my comment on it is, this is really funny; 325 00:17:40.092 --> 00:17:42.061 my comment says \"Ooh baby, merch integration\". 326 00:17:42.094 --> 00:17:43.162 Sammy: Hahahahaha. 327 00:17:43.195 --> 00:17:45.330 Adam: Oh, this one is f****ing embarrassing. 328 00:17:45.330 --> 00:17:47.766 This sentence just shouldn't be there. 329 00:17:47.766 --> 00:17:52.805 For 2020, games we can see that out budget PC, is basically out of the running; 330 00:17:53.705 --> 00:17:55.340 unable to get playable frame rates. 331 00:17:55.407 --> 00:17:59.445 There's a needless comma at the start, when I should- \"for 2020\" comma, 332 00:17:59.445 --> 00:18:03.882 \"games that we can see that out\", it should be \"our\" budget PC; 333 00:18:03.882 --> 00:18:06.051 \"is basically out of the running\" and another comma splice... 334 00:18:06.985 --> 00:18:09.121 \"unable to get playable frame rates\", no period. 335 00:18:09.121 --> 00:18:10.355 Feels like I just was about to start up; 336 00:18:10.422 --> 00:18:13.125 and then I go \"as we can see from our price to performance charts, It's a bit of a blowout\". 337 00:18:13.158 --> 00:18:16.728 I just didn't- I think I just needed to mention the 2020 games. 338 00:18:16.762 --> 00:18:18.797 I know here I also would have clarified, 339 00:18:18.797 --> 00:18:21.733 that I would remind the viewer that we are not upgrading the high-end PC; 340 00:18:21.733 --> 00:18:23.469 because we've used all of our budget in 2013. 341 00:18:23.469 --> 00:18:25.404 I'm just more like, I can't believe I submitted that. 342 00:18:25.437 --> 00:18:26.004 Sammy: Hahahaha. 343 00:18:26.038 --> 00:18:28.907 Adam: I remember being incredibly busy when I had to write this. 344 00:18:29.241 --> 00:18:29.808 Sammy: Mmm. 345 00:18:29.875 --> 00:18:33.979 Adam: And so like, I think I wrote most of this in like a couple of nights. 346 00:18:33.979 --> 00:18:37.783 As we can see from our price to performance charts, it is a bit of a blowout. 347 00:18:37.816 --> 00:18:41.553 Splurging all at once isn't worth it, and neither is trying to do a dirt-cheap budget build. 348 00:18:41.553 --> 00:18:47.126 In fact, they're almost performing exactly identical in terms of price to performance, post upgrade. 349 00:18:47.626 --> 00:18:50.729 If you're trying to save money in the long term the best course of action 350 00:18:50.729 --> 00:18:54.867 appears to be spending a bit more on your CPU to get a chip that will last you a long time for gaming; 351 00:18:54.867 --> 00:18:59.138 while holding back on your initial GPU purchase so that you can upgrade later down the line. 352 00:18:59.204 --> 00:19:03.275 While the budget build may seem appealing, the cost of upgrading so many components more frequently 353 00:19:03.275 --> 00:19:07.045 ends up being a bigger burden on your budget... fun alliteration, 354 00:19:07.045 --> 00:19:12.050 over the course of time and you spend more time with lackluster performance than a mid-range build. 355 00:19:12.050 --> 00:19:13.919 Well, none of these builds will compare to new- 356 00:19:13.919 --> 00:19:16.822 So that's an okay sentence, I would say that my problem with is 357 00:19:16.822 --> 00:19:20.058 that we don't acknowledge, the angle that sometimes people- 358 00:19:20.058 --> 00:19:23.762 A lot of people who are buying budget systems that's just all they can afford. 359 00:19:24.496 --> 00:19:26.532 For a lot of people, like especially if it's a computer; 360 00:19:26.532 --> 00:19:30.936 maybe not for a gaming computer, but for a lot of people that they can't wait to buy a computer, 361 00:19:30.936 --> 00:19:32.037 they have to buy a computer now. 362 00:19:32.037 --> 00:19:34.439 But I think that like the advice still kind of holds; 363 00:19:34.439 --> 00:19:37.075 if you're a gamer and you're going to buy a computer, 364 00:19:37.075 --> 00:19:40.712 and you want to not upgrade it for a long time? buy a good CPU. 365 00:19:40.712 --> 00:19:44.616 Funny enough, we didn't even know this but like, AM4 was around for forever; 366 00:19:44.616 --> 00:19:48.620 so if you moved to this, you could have been in a- On an AM4 socket computer 367 00:19:48.620 --> 00:19:52.291 and then continue to not have to upgrade your motherboard for another five. 368 00:19:52.324 --> 00:19:54.960 Well, you still wouldn't have to upgrade it; you could just get a new CPU. 369 00:19:55.527 --> 00:19:58.664 But we didn't- No one knew that back in 2020. 370 00:19:58.730 --> 00:20:01.133 While none of these builds will compare to a newer systems, 371 00:20:01.133 --> 00:20:05.470 using the massive leap in performance that the new Ryzen CPUs and 2020 GPUs have given us; 372 00:20:05.470 --> 00:20:08.006 \"shown us\", it should be like \"given us\", \"have provided us\"? I don't know. 373 00:20:08.040 --> 00:20:12.945 The mid-range computer's now looking like the only computer out of our three that doesn't need an upgrade. 374 00:20:13.378 --> 00:20:15.847 Hopefully this video provided you with a bit more insight into your next upgrades, 375 00:20:15.847 --> 00:20:17.216 and as a final note think about this. 376 00:20:17.216 --> 00:20:21.019 As we go into the new console generation consider taking that mid-rate- the mid-range route; 377 00:20:21.019 --> 00:20:25.090 and plan on a one GPU upgrade, but don't spend the bread just yet. 378 00:20:25.090 --> 00:20:27.926 We still don't know how intensive these next-gen games are going to be; 379 00:20:27.926 --> 00:20:31.997 so my advice is while this may be a great year to upgrade, hold off. 380 00:20:32.030 --> 00:20:36.768 Remember, knowledge is power; don't pre-order anything, wait to see reviews 381 00:20:36.768 --> 00:20:39.338 and real-world benchmarks before buying stuff. 382 00:20:40.205 --> 00:20:44.209 Just be patient, at least until our 6000 series coverage comes out. 383 00:20:44.209 --> 00:20:47.846 Speaking of waiting, you know you shouldn't- Don't wait to check out our sponsor. 384 00:20:48.113 --> 00:20:49.548 It's not good enough to be a video. 385 00:20:49.748 --> 00:20:52.484 It just is- Frankly at this point to me it feels unfinished. 386 00:20:52.551 --> 00:20:53.051 Sammy: Mhmm. 387 00:20:53.252 --> 00:20:56.021 Adam: There's not- We barely do any discussion; 388 00:20:56.021 --> 00:20:58.724 I basically just read you the results and then go, peace. 389 00:20:58.857 --> 00:20:59.358 Sammy: Haha. 390 00:20:59.391 --> 00:21:01.960 Adam: I don't help you, like I don't provide extra learnables; 391 00:21:01.960 --> 00:21:06.865 I also don't spend enough time talking about caveats with methodology or... 392 00:21:06.865 --> 00:21:10.002 Nothing's guaranteed, like I didn't reinforce the point that like 393 00:21:10.002 --> 00:21:14.973 this is just looking back, this is not a predictor of how things will go in the future. 394 00:21:14.973 --> 00:21:17.576 When a lot of people bought like 20 series cards or 10 series cards, 395 00:21:17.576 --> 00:21:20.078 nobody knew that the 30 series would be such a huge jump. 396 00:21:20.212 --> 00:21:22.447 So if you bought a 20 series card, you got screwed. 397 00:21:23.382 --> 00:21:26.551 But at the time it wouldn't have been the worst choice. 398 00:21:26.551 --> 00:21:30.222 This is like, like one of the big things about this is it's like- 399 00:21:30.222 --> 00:21:35.360 In general some of the rules that I have here, in terms of like thinking about your upgrades, 400 00:21:35.360 --> 00:21:40.465 going for mid-range CPUs so that you can last a little bit longer and plan on one GPU upgrade. 401 00:21:40.465 --> 00:21:46.238 Is a- is smart, you really don't actually know. 402 00:21:46.238 --> 00:21:49.274 It's not like, it's not super applicable. 403 00:21:49.641 --> 00:21:51.977 I think I wrote it in about two nights. 404 00:21:51.977 --> 00:21:54.713 Probably most of it on the same night knowing how I was back then. 405 00:21:54.813 --> 00:21:59.318 It would take me a lot longer now; because one, half the- 406 00:21:59.318 --> 00:22:02.054 like, there's like no guidance for like 80% of the script; 407 00:22:02.054 --> 00:22:04.990 two the script would be a little bit long, it would need to be more fleshed out. 408 00:22:04.990 --> 00:22:07.759 But I think I was also aiming for a word count, 409 00:22:07.759 --> 00:22:11.496 and I think the word count that they had for the scripts was slightly lower than the word count for a video. 410 00:22:11.530 --> 00:22:13.999 Sammy: Yeah, I heard it was a thousand? 411 00:22:14.366 --> 00:22:18.837 Adam: Yeah, so I have like, just from quickly highlighting, I have like 1100 words. 412 00:22:18.837 --> 00:22:22.374 So I think that like, for our videos we usually aim for like 1500. 413 00:22:22.374 --> 00:22:26.912 That's like the length, so I would have had more words to cover. 414 00:22:26.912 --> 00:22:30.449 A lot of this was also like I just pulled numbers from websites, 415 00:22:30.482 --> 00:22:32.718 and benchmarking takes a really long time. 416 00:22:32.718 --> 00:22:35.854 I probably could have spit this out in a similar pace, but I probably would be a little bit slower 417 00:22:35.854 --> 00:22:36.788 but it would be much better. 418 00:22:36.788 --> 00:22:39.191 Yeah, I think that um, 419 00:22:39.191 --> 00:22:43.495 the strongest thing is I think I really did kind of nail the tone. 420 00:22:43.495 --> 00:22:46.164 I think I sounded like a- It sounded like an LTT script. 421 00:22:46.198 --> 00:22:46.665 Sammy: Yeah. 422 00:22:46.698 --> 00:22:50.235 Adam: In terms of like, kind of like asking questions out loud, 423 00:22:50.235 --> 00:22:53.372 some sort of fun kind of sentences in there, probably not enough. 424 00:22:53.372 --> 00:22:55.774 I would have more jokes in at this, at this point. 425 00:22:55.774 --> 00:23:00.946 But yeah, I think I think I really nailed the tone; which is what I was going for. 426 00:23:00.946 --> 00:23:04.950 I think the worst thing is that I just it just lacks discussion, 427 00:23:04.950 --> 00:23:11.890 and honestly probably, the first paragraph discussing half the results is just a mess. 428 00:23:11.923 --> 00:23:12.691 Sammy: Hahahahaha. 429 00:23:12.691 --> 00:23:15.560 Adam: That's probably the worst part, is that it's just like, huh? What? Who? 430 00:23:15.560 --> 00:23:18.864 It's important to be able tell a story and have a good flow, 431 00:23:19.531 --> 00:23:21.500 then it is to know a lot about hardware. 432 00:23:22.100 --> 00:23:24.536 But really yeah, really what it comes down to is 433 00:23:25.137 --> 00:23:33.078 understand your voice and your position, and let that in influence everything, every part of the script. 434 00:23:33.178 --> 00:23:39.851 If a sentence in there is only facts, then think about how that sentence could be turned in to have, 435 00:23:39.851 --> 00:23:42.587 to have some sort of slant to it; 436 00:23:43.188 --> 00:23:46.057 something that, how that sentence influences your story. 437 00:23:46.057 --> 00:23:48.126 And make it fun, yeah You just have to have fun. 438 00:23:48.126 --> 00:23:50.629 Like it can be tough when you're doing like a job application, 439 00:23:50.629 --> 00:23:54.900 but if you aren't having fun writing your script or don't have fun with it, 440 00:23:55.467 --> 00:23:57.135 we're not gonna have fun reading it. 441 00:23:57.135 --> 00:24:00.972 And probably the most important thing about LTT is that we want to be fun. 442 00:24:01.006 --> 00:24:06.545 We want to be fun and educational so- But the fun comes before the word educational. 443 00:24:06.578 --> 00:24:08.713 Thanks for watching and subscribing to Floatplane. 444 00:24:08.713 --> 00:24:12.150 If you like this one, why don't you watch? Well, one of the other ones in this series. 445 00:24:12.150 --> 00:24:14.886 I don't know who's out right now, but you can go do it. 446 00:24:14.886 --> 00:24:16.588 Or you could watch my Meet the Team. 447 00:24:17.255 --> 00:24:19.424 How come we don't do Meet the Teams anymore, Sammy?","speaker":null,"is_sponsor":0}],"full_text":"Adam: Hello I'm Adam, I've been a writer at Linus Media Group for about two? 2 00:00:05.472 --> 00:00:07.474 Almost three years. three years in November. 3 00:00:07.674 --> 00:00:09.275 So I actually applied twice, 4 00:00:09.275 --> 00:00:13.880 the first time I applied was probably in 2018 or 2019. 5 00:00:13.880 --> 00:00:16.816 And I remember at the time I was working at an escape room. 6 00:00:16.883 --> 00:00:20.153 As well- Part-time at an escape room, 7 00:00:20.153 --> 00:00:24.024 and part-time doing business to business sales in grocery stores. 8 00:00:24.024 --> 00:00:26.626 And I was just kind of doing writing stuff on the side, 9 00:00:26.626 --> 00:00:28.428 as well as doing a bunch of improv at the time. 10 00:00:28.428 --> 00:00:30.230 The first time I applied, I basically I got an interview. 11 00:00:30.230 --> 00:00:31.664 I basically bombed the interview. 12 00:00:31.698 --> 00:00:32.665 Sammy: *Laughs* 13 00:00:32.966 --> 00:00:36.302 Adam: Yeah, I think I talk about why if you go to my Meet the Team video, 14 00:00:36.302 --> 00:00:38.104 from like a year and a bit ago. 15 00:00:38.104 --> 00:00:41.041 Basically long story short is that I bombed the interview; 16 00:00:41.041 --> 00:00:46.279 but then six months later, they bought that script off of me, used it for a TechQuickie. 17 00:00:46.279 --> 00:00:49.616 But since that one was made into a video, I'm not going to check out that script today, 18 00:00:49.616 --> 00:00:52.152 because you can just watch the video on TechQuickie. 19 00:00:52.152 --> 00:00:55.922 I will however do the script from the second time I applied. 20 00:00:56.489 --> 00:01:00.560 Well outside of like doing writing in an academic setting for like university, 21 00:01:00.560 --> 00:01:02.595 I did not have a ton of writing experience. 22 00:01:02.595 --> 00:01:06.933 It was something I had a knack for, but not something I ever actually really tried to pursue professionally. 23 00:01:06.933 --> 00:01:11.871 At the times that I applied I had like a music blog, 24 00:01:11.871 --> 00:01:16.242 that I was kind of updating very infrequent, relatively infrequently 25 00:01:16.242 --> 00:01:17.944 a lot of the times when I was looking for writing jobs. 26 00:01:17.944 --> 00:01:19.946 I've just been in a creative field for a long time. 27 00:01:19.946 --> 00:01:22.449 I was a theater kid in high school and stuff like that; 28 00:01:22.449 --> 00:01:26.319 so I've always kind of wanted to- Liked creating stuff. 29 00:01:26.553 --> 00:01:31.491 Adam: I mean like, I guess it's tough to gauge; because definitely a lot of interest in tech. 30 00:01:31.491 --> 00:01:34.494 I had built my own computers and built computers for friends at that point. 31 00:01:34.494 --> 00:01:37.497 but I was just an enthusiast and a generalist, 32 00:01:37.497 --> 00:01:43.470 and I think also like I just had a deep passion for the tech side of things; 33 00:01:43.470 --> 00:01:47.474 as well as I think- I like to think I'm a quick learner. 34 00:01:48.441 --> 00:01:50.710 I think one of the things that I bring, 35 00:01:50.777 --> 00:01:52.846 that I was bringing to the table is that I have a background, 36 00:01:52.846 --> 00:01:58.218 I went to school for neuroscience; so I have a Bachelor of Science in neuroscience. 37 00:01:58.218 --> 00:02:04.424 And that kind of gave me a very like, human centric look at um, 38 00:02:04.457 --> 00:02:07.060 like thinking about tech and how it affects us. 39 00:02:07.894 --> 00:02:10.730 That was always a big part of it for me that made it me really interested. 40 00:02:10.730 --> 00:02:12.298 Adam: Oh, yeah, I'd been watching for a while, 41 00:02:12.332 --> 00:02:15.435 the reason I applied was because they put out a video for writers. 42 00:02:15.435 --> 00:02:18.671 The first time I applied, I think that's how they found writers. 43 00:02:18.671 --> 00:02:21.508 They didn't like do job postings; they like, put out a video. 44 00:02:21.508 --> 00:02:25.812 No, both- So the first script was um... yeah, it was my own prompt 45 00:02:25.812 --> 00:02:29.415 and I remember Linus being like this is more of a TechQuickie, and I was like, I know. 46 00:02:29.516 --> 00:02:30.383 Sammy: Hahahahaha 47 00:02:30.416 --> 00:02:30.550 Sammy: \"I know\". 48 00:02:30.550 --> 00:02:31.885 Sammy: It looks like your own prompt, It's- 49 00:02:31.918 --> 00:02:32.552 Adam: Yeah. 50 00:02:32.585 --> 00:02:33.386 Sammy: And now it's time to upgrade. 51 00:02:33.686 --> 00:02:37.090 Adam: And then the most- then this one that at the time was also my own prompt was like, 52 00:02:37.090 --> 00:02:39.292 I was more interested in answering a different question; 53 00:02:39.292 --> 00:02:42.662 and I wanted to show in my application that I was like, not- 54 00:02:42.662 --> 00:02:45.431 I didn't want to just write a review because like I think, honestly 55 00:02:45.431 --> 00:02:48.434 it's very easy to write a review; because you don't have to think of an idea, 56 00:02:48.434 --> 00:02:50.203 you just talk about a product. 57 00:02:50.203 --> 00:02:53.640 Easy is not the word, I think that there's a trap that you can fall into with writing reviews; 58 00:02:53.640 --> 00:02:56.643 where you just talk about a product, and 59 00:02:56.676 --> 00:03:02.382 It's important especially as like a new writer to be coming in with your angle, 60 00:03:02.415 --> 00:03:05.818 and finding your idea about the product, you don't just want to talk about like- 61 00:03:05.818 --> 00:03:09.355 It's a useful resource to just do a review that just talks about a product, 62 00:03:09.355 --> 00:03:11.824 that goes through all the features, and it's very specific; 63 00:03:11.858 --> 00:03:15.662 but it's important, that you also have to have an angle 64 00:03:15.695 --> 00:03:18.531 and you're telling a story at the same time with a review. 65 00:03:18.531 --> 00:03:21.100 which is why like there's kind of a difference between say, 66 00:03:21.100 --> 00:03:24.737 like how we've done CPU reviews, which are far more focused on being like 67 00:03:24.737 --> 00:03:28.141 here's the details about this specific product; 68 00:03:28.141 --> 00:03:31.544 and say a review that we do on like a new TV, 69 00:03:31.544 --> 00:03:35.448 Where we want to tell more about the story, or the coverage to CPUs 70 00:03:35.448 --> 00:03:38.785 versus the coverage we give To a TV, is a little bit different; 71 00:03:38.785 --> 00:03:42.755 because a TV is something that we can find an angle and a story with 72 00:03:42.755 --> 00:03:47.527 a bit easier than a CPU, and a CPU is also something that the audience wants to just know, 73 00:03:48.094 --> 00:03:49.629 like how does it do? 74 00:03:49.696 --> 00:03:52.966 I didn't want to do a review, also I was broke as hell; 75 00:03:52.999 --> 00:03:54.667 so I didn't have any products to review. 76 00:03:54.667 --> 00:03:57.604 Sammy: I think Eli had the same prompt as you, or he made the same prompt as you. 77 00:03:57.604 --> 00:03:59.472 Adam: Yeah, his was pretty similar, but I did it better. 78 00:03:59.472 --> 00:04:00.840 Sammy: Hahahahahaha! Adam: *Laughs* 79 00:04:01.341 --> 00:04:03.309 Adam: I mean, so part of it was an interesting discussion. 80 00:04:03.309 --> 00:04:05.645 For me a part of it was answering a question that I had, 81 00:04:05.645 --> 00:04:09.983 which was like is there a way to tell-? Basically who's gonna get ripped off? Is my question; 82 00:04:09.983 --> 00:04:13.186 is it the person who has to buy the cheap- who can only afford the cheapest thing at any given point? 83 00:04:13.486 --> 00:04:17.090 And has to upgrade more times? Is it the person who can buy the middle-of-the-road thing? 84 00:04:17.090 --> 00:04:20.226 And upgrade once every five years? Or is it the guy who bought the super best computer, 85 00:04:20.226 --> 00:04:23.263 the most expensive computer at the time; and only upgrades once every 10 years? 86 00:04:23.263 --> 00:04:28.635 There's a lot of places in life where being poor, or not being able to afford stuff 87 00:04:28.635 --> 00:04:30.570 ends up being more expensive in the long run. 88 00:04:30.570 --> 00:04:34.474 It's like if you buy, if you can only afford for like $20 or $40 shoes, 89 00:04:34.474 --> 00:04:39.012 you're gonna spend up more money over the course of 10 years buying shoes to replace them, 90 00:04:39.012 --> 00:04:43.149 because you have to replace a pair every 10 years; than if you bought like a solid pair of $200 boots. 91 00:04:43.149 --> 00:04:45.985 I wondered if that kind of applied to computers. 92 00:04:45.985 --> 00:04:48.888 When making a big purchase timing can be everything. 93 00:04:48.888 --> 00:04:52.458 The last thing you want to be is someone who purchased a 2080 Ti in May of this year 94 00:04:52.458 --> 00:04:55.261 only to find out you could have received the same performance for half the price 95 00:04:55.261 --> 00:04:56.996 if you had just waited another six months. 96 00:04:56.996 --> 00:05:01.467 But you also don't want to be the guy whose sluggish machine can barely play today's biggest titles. 97 00:05:01.467 --> 00:05:04.070 So is there an upgrade strategy that works best? 98 00:05:04.270 --> 00:05:05.772 Should we do cheap and frequent upgrades? 99 00:05:05.772 --> 00:05:09.142 Or buy big now and be happy with a beastly rig for the next few years? 100 00:05:09.609 --> 00:05:12.812 Well to answer this we've built three rigs that reflect the types of machines 101 00:05:12.812 --> 00:05:15.014 different people would have bought way back in 2013 102 00:05:15.014 --> 00:05:17.917 to find out if there is an upgrade strategy that works best. 103 00:05:17.917 --> 00:05:21.120 Speaking of an upgrade, upgrade your life with our sponsor. 104 00:05:21.120 --> 00:05:22.488 Honestly, it's not bad. 105 00:05:23.423 --> 00:05:25.124 It cuts straight to the point. 106 00:05:25.124 --> 00:05:30.530 I think the first sentence would be changed a lot, in terms of just kind of getting to the point. 107 00:05:30.530 --> 00:05:34.901 Being more specific sooner, you I could just cut out the first sentence, I could just say 108 00:05:34.901 --> 00:05:38.504 the last thing you want to be is somebody who purchased a 2080Ti in May of this year 109 00:05:38.504 --> 00:05:41.974 only to find out you could have received the same performance for half the price just six months later. 110 00:05:42.041 --> 00:05:45.545 Honestly, I dunno, this is like a pretty solid intro. 111 00:05:45.611 --> 00:05:46.913 Adam: It would be a little bit of just trimming the fat; 112 00:05:46.913 --> 00:05:50.316 but I think it gets to the point, we tell it we get the premise of the video, you're immediately hooked. 113 00:05:50.316 --> 00:05:53.419 There could be massage and improved, but I got to the point of it. 114 00:05:53.453 --> 00:05:57.557 I'd rate it like a 6 or a 7; I think it's solid but, 115 00:05:57.557 --> 00:06:00.893 it needs to be finessed to really get it to the last kind of like 8 or 9. 116 00:06:00.893 --> 00:06:03.496 Like I would just, I just like watched several LTT- 117 00:06:03.496 --> 00:06:07.100 I'd like remember writing this, and I was like how do LTT videos start? 118 00:06:07.100 --> 00:06:11.671 And I watched like 20 and 30 of them, where I just watched the first like minute. 119 00:06:11.671 --> 00:06:14.173 And that's basically I just was like, okay this is how they do it; 120 00:06:14.173 --> 00:06:17.877 so I'm gonna like try and make sure that my intro's formulated like that. 121 00:06:17.877 --> 00:06:21.614 Adam: So why 2013 you may ask? Now that consoles have such a massive place in the market; 122 00:06:21.614 --> 00:06:26.386 it is rare to see any games that made by AAA studios that are specifically for PC. 123 00:06:26.386 --> 00:06:31.758 This has got me thinking that the best time to upgrade is near, or shortly after a console launch; 124 00:06:31.758 --> 00:06:36.496 because game studios will now be creating releases that are targeting this year's console hardware 125 00:06:36.496 --> 00:06:39.999 for the next several years; which lends to the idea that if you buy a current computer hardware, 126 00:06:39.999 --> 00:06:43.503 you should be set for the next, most of the next console generation, 127 00:06:43.503 --> 00:06:47.273 assuming you don't mind console-like performance in your video games. 128 00:06:47.273 --> 00:06:49.008 That's a clunky sentence at the end. 129 00:06:49.041 --> 00:06:50.076 Sammy: Hahahaha. 130 00:06:50.343 --> 00:06:52.512 Adam: To test this we've set a budget of $1400 131 00:06:52.512 --> 00:06:55.882 to be spent over seven years spanning this console generation. 132 00:06:55.882 --> 00:06:59.318 The budget will be spent in three ways; a budget system with frequent upgrades, 133 00:06:59.318 --> 00:07:02.054 a mid-range system that has infrequent but more significant upgrades, 134 00:07:02.054 --> 00:07:05.491 and an all-out high-end PC that is still running unchanged today. 135 00:07:05.658 --> 00:07:10.329 I chose this budget, because I could use my own computer 136 00:07:10.730 --> 00:07:11.497 Sammy: hahahaha. 137 00:07:11.531 --> 00:07:15.101 Adam: to test, because that's how much I spent on my computer in 2013. 138 00:07:15.101 --> 00:07:20.606 And so then I did do an upgrade, it like, I ended up being the mid-range guy for this; 139 00:07:20.606 --> 00:07:22.708 so I could actually do some benchmarking for it. 140 00:07:22.809 --> 00:07:26.979 Funny enough, for the rest of the results I had to use UserBenchmark. 141 00:07:27.113 --> 00:07:32.618 Which is a, has a pretty bad reputation these days, but it was a practice not an actual- 142 00:07:32.618 --> 00:07:35.288 It was, the point of it was practicing, I couldn't- 143 00:07:35.288 --> 00:07:37.490 I didn't have hardware to test, let's keep going. 144 00:07:37.690 --> 00:07:41.027 Each of these systems will be benchmarked against games that released from their day, 145 00:07:41.027 --> 00:07:46.065 games from around 2016 to 2017 and... oh yeah, this is a weird sentence. 146 00:07:46.065 --> 00:07:49.469 Each of these systems will be benchmarks to games from their day, 147 00:07:49.469 --> 00:07:54.006 games from 2016 or 2017, right around the time of the PS4 Pro and Xbox One X releases, 148 00:07:54.006 --> 00:07:57.777 and games from this very year to see how their performance holds up. 149 00:07:57.777 --> 00:08:00.680 \"This year\" would have been 2020. 150 00:08:00.680 --> 00:08:04.684 So place your bets, who will end up on top financially? The high-end but patient enthusiast? 151 00:08:04.684 --> 00:08:07.887 The mindfully priced mid-ranger? Or the Bargain-seeking budget build? 152 00:08:07.887 --> 00:08:10.356 Here I see an issue where it's like, that's a great sentence; 153 00:08:10.356 --> 00:08:12.191 that could have been tossed up at the intro. 154 00:08:12.191 --> 00:08:13.159 So, and I have guidance; 155 00:08:13.192 --> 00:08:16.662 Linus will jump and turn on the spot, as a wipe comes across the screen, 156 00:08:16.662 --> 00:08:19.332 he'll be wearing his old \"Professional Unboxer\" shirt. 157 00:08:19.332 --> 00:08:21.968 I wanted Linus to look like he was from a 2013 video. 158 00:08:21.968 --> 00:08:28.641 Our first PC is the 2013 budget gamer, featuring an Intel Core i5-4430 Quad-Core locked at 3 gigahertz, 159 00:08:28.641 --> 00:08:34.914 8 GB of Patriot Signature RAM, and an NVIDIA 650 Ti graphics card. Clocking in at about $650. 160 00:08:34.914 --> 00:08:40.953 The second PC is the Mid-Range Gamer, with an Intel Core i5-4670k running at 3.4 gigahertz, 161 00:08:40.953 --> 00:08:46.859 16 gigs of Corsair Vengeance RAM, and an AMD R9 280x, totaling at $950 big ones. 162 00:08:46.926 --> 00:08:52.698 Our third PC is a high-end beast from 2013, with a top-of-the-line Intel Core i7-4470K- 163 00:08:52.698 --> 00:08:55.268 That's, probably not the CPU it should be... 164 00:08:55.468 --> 00:08:58.037 Adam: That should probably be like a 4770k. 165 00:08:58.037 --> 00:08:58.571 Sammy: I love how you're... 166 00:08:58.571 --> 00:09:00.473 Adam: Yeah, sorry, I don't why I edited it. 167 00:09:00.506 --> 00:09:02.408 Adam: You know, it's not as bad as I thought it was gonna be. 168 00:09:02.408 --> 00:09:03.743 There's a lot of things I would change, 169 00:09:03.743 --> 00:09:06.679 but I think it's got the bones of something that's good and makes sense. 170 00:09:06.679 --> 00:09:11.284 Like I wouldn't have slammed all of these specs back to back. 171 00:09:11.284 --> 00:09:14.020 And I think one thing that I've learned as I've written 172 00:09:14.020 --> 00:09:17.456 is that a lot of the stuff that I'm saying right now, can be shown on screen. 173 00:09:17.456 --> 00:09:20.893 I could be like, we have three gaming systems, 174 00:09:21.594 --> 00:09:25.631 one featuring an Intel Core and an NVIDIA 650 Ti graphics card. 175 00:09:25.631 --> 00:09:29.101 I could've just had like two pieces of hardware; the CPU and the GPU, 176 00:09:29.101 --> 00:09:32.138 then shown the rest of the parts; which is what I did. 177 00:09:32.138 --> 00:09:34.173 And it was like, kudos to me... 178 00:09:34.240 --> 00:09:40.446 I did specifically only choose the Processor, RAM, and GPU to talk about; 179 00:09:40.446 --> 00:09:41.781 because those would be the most relevant, 180 00:09:41.781 --> 00:09:43.916 I didn't bother talking about the motherboard or anything like that; 181 00:09:43.916 --> 00:09:47.520 so like, good that I had a knack for like what's actually important. 182 00:09:47.520 --> 00:09:50.456 It's just have to like be like bam bam bam, with so many specs. 183 00:09:50.456 --> 00:09:52.858 I would try and probably massage and space that out. 184 00:09:52.858 --> 00:09:56.262 That I would probably maybe move and talk about the results from one. 185 00:09:56.262 --> 00:09:57.930 I would go like, here's the budget gamer, 186 00:09:57.930 --> 00:10:00.967 how does it hold up in the games from 2013? Bring that in. 187 00:10:00.967 --> 00:10:04.270 Then I would introduce the mid-ranger, do the results in 2013; 188 00:10:04.270 --> 00:10:06.772 then I would introduce the high-end beast, that would make it less like 189 00:10:06.772 --> 00:10:09.208 oh my god, he's yelling numbers and words at me. 190 00:10:09.208 --> 00:10:11.010 And then we would go into just being like, 191 00:10:11.010 --> 00:10:16.182 okay and then how do they all do in the middle of the decade games. 192 00:10:16.182 --> 00:10:19.251 Also, this is the other kind of stuff that we would cut out nowadays. 193 00:10:19.485 --> 00:10:22.488 Now that we know what hardware we're dealing with, let's take a look at how they run; 194 00:10:22.488 --> 00:10:23.689 it's like shut up, just do that. 195 00:10:23.923 --> 00:10:27.860 We can and then you can see the variance in performance across these systems already in games like 196 00:10:27.860 --> 00:10:29.195 Tomb Raider and Bioshock Infinite, 197 00:10:29.962 --> 00:10:31.597 and I just have benchmarking graphs. 198 00:10:31.597 --> 00:10:32.732 So like this took a long time to write, 199 00:10:32.732 --> 00:10:36.402 because I had to find hardware that was also all like from the same source. 200 00:10:36.402 --> 00:10:38.804 So I could steal their numbers and write something that's relatively true, 201 00:10:38.804 --> 00:10:42.708 because I wanted to show that I had like the abilities to analyze data and talk about it. 202 00:10:42.708 --> 00:10:45.878 Our high-end system absolutely destroys these benchmarks at 1080p, 203 00:10:45.878 --> 00:10:48.881 and really stretches its legs at 1440p with the 780 Ti 204 00:10:48.881 --> 00:10:53.519 pulling out an impressive 71 FPS in infinite and at 1440p. 205 00:10:53.519 --> 00:10:55.221 Yeah, see this is now I'm jumbling; 206 00:10:55.254 --> 00:10:59.325 talking about 1080p and then talking about 1440p, and it's already confusing. 207 00:10:59.325 --> 00:11:03.162 So I really- I would have sectioned this off as, we're gonna talk about 1080p, 208 00:11:03.162 --> 00:11:04.563 then we're gonna talk about 1440p. 209 00:11:04.597 --> 00:11:09.135 The 650 Ti is already struggling to pull a steady 30 FPS and Ultra settings, 210 00:11:09.135 --> 00:11:13.572 but jumping down to medium and lowering anti-aliasing nets us a respectable 63 FPS average. 211 00:11:13.606 --> 00:11:16.709 Remember this card was made to be driven at 1080p. 212 00:11:16.709 --> 00:11:21.380 The 280x is doing a good job pulling 50 FPS, we see similar performance from these cards 213 00:11:21.380 --> 00:11:27.787 and we take a look at Tomb Raider where the 780 Ti and 1080p runs at a blistering 146 FPS. 214 00:11:27.787 --> 00:11:34.427 The mid-range system scores 105 FPS, and our budget system pulls out a solid 75 FPS. 215 00:11:34.427 --> 00:11:37.563 Again, this is one of those things where it's like now that I know how to- 216 00:11:37.563 --> 00:11:40.366 Especially after writing several reviews, I know that we're highlight- 217 00:11:40.366 --> 00:11:43.602 It's more like, it's less about talking about everything in the graph, 218 00:11:43.602 --> 00:11:50.309 and it's more about writing about what is the story that's being told in those graphs? 219 00:11:50.342 --> 00:11:52.178 Like that's where the whole point is, that the viewer can pause; 220 00:11:52.211 --> 00:11:56.782 so we don't feel the need in our videos to talk about every single point on the graph. 221 00:11:56.782 --> 00:11:59.285 We want to be like, here's the most important things to note; 222 00:11:59.785 --> 00:12:02.488 and this is what weaves the story. 223 00:12:02.488 --> 00:12:04.824 And so what I'm doing here is I'm just like reading out the graph, 224 00:12:04.824 --> 00:12:08.427 which is like what's the point of showing the graph if I'm just gonna read it out; 225 00:12:08.427 --> 00:12:12.498 but I do cut right to the chase, because I go, now let's jump ahead a few years 226 00:12:12.498 --> 00:12:15.401 and see how these systems are holding up around three and a half years later; 227 00:12:15.401 --> 00:12:20.439 when the PS4 Pro and Xbox One X launched, and I said launch, it's a typo right there. 228 00:12:20.439 --> 00:12:25.010 Here we're gonna benchmark our systems using Hitman 2016, Rise of the Tomb Raider, and Doom 2016. 229 00:12:25.544 --> 00:12:26.946 As we can see from our benchmarks, 230 00:12:26.946 --> 00:12:30.382 the budget system is already in dire straits with these more demanding titles; 231 00:12:30.382 --> 00:12:33.753 barely getting 20 FPS in our Hitman 2016 benchmark, 232 00:12:33.753 --> 00:12:38.190 and it isn't until we dial back the graphics to medium that we are getting 30 to 40 FPS, 233 00:12:38.691 --> 00:12:41.327 which is the cutoff to what we would call playable. 234 00:12:42.394 --> 00:12:44.497 It's kind of looking like a good time to upgrade. 235 00:12:44.497 --> 00:12:48.467 Our 2020 games clearly show those, our systems' deficiencies. 236 00:12:48.467 --> 00:12:52.638 So here again, I've just- I've changed the order of how we're talking about it, 237 00:12:52.705 --> 00:12:54.073 Are we talking 1080p? Are we talking resolution? 238 00:12:54.106 --> 00:12:56.509 Are we talking all of the things at the same resolution? 239 00:12:56.542 --> 00:13:04.850 Is the scenario for this video going system by system? Or Is it going year by year? 240 00:13:04.850 --> 00:13:10.422 And I've kind of mixed, like I've pivoted to talking about one system through multiple years, 241 00:13:10.589 --> 00:13:11.757 and that's what's gonna be confusing. 242 00:13:12.258 --> 00:13:15.027 Our 2020 games clearly show our systems' deficiencies. 243 00:13:15.027 --> 00:13:17.596 The budget system basically can't play modern titles, 244 00:13:17.596 --> 00:13:21.033 and the mid-range build is starting to struggl- Oh really I just- 245 00:13:21.033 --> 00:13:24.470 Okay no, now I'm getting it; it seems like I just kind of only talk about the mid-range... 246 00:13:24.470 --> 00:13:31.243 The budget system? I guess I was showing the graphs at the time; 247 00:13:31.243 --> 00:13:33.145 so I would have only been talking about certain things. 248 00:13:33.145 --> 00:13:36.882 One thing I will notice, I will note is that there's like no guidance in here; 249 00:13:36.882 --> 00:13:41.387 so much of this would be Linus just talking at a camera, I should have done way more guidance. 250 00:13:41.387 --> 00:13:45.124 Now we like to, we use coverage to site sources; 251 00:13:45.124 --> 00:13:46.859 to be like, yeah we said this thing, 252 00:13:46.859 --> 00:13:49.895 then this thing's backed up from this website that we got that information from, 253 00:13:49.895 --> 00:13:51.897 as well as to just add visual interest; 254 00:13:51.897 --> 00:13:55.701 but my brain didn't think like that, my brain was in a, I write things as text mode; 255 00:13:55.701 --> 00:13:57.670 because that's all I had done for most of my life. 256 00:13:57.670 --> 00:13:59.505 Sammy: I mean, I think that's what I thought, that they probably cared about 257 00:13:59.505 --> 00:14:02.808 is like how well you can write, and they can probably teach you how to like, 258 00:14:02.808 --> 00:14:04.476 just have more visuals, I guess. 259 00:14:04.476 --> 00:14:08.848 Adam: Yeah, and a big part of it, that they care a lot about just having the fundamentals there. 260 00:14:08.848 --> 00:14:11.750 Our 2020 games clearly show our systems deficiencies; 261 00:14:11.750 --> 00:14:13.886 the budget system basically can't play modern titles 262 00:14:13.886 --> 00:14:16.689 and the mid-range build is starting to struggle with games like Death Stranding. 263 00:14:16.689 --> 00:14:20.459 The high-end Build however is still giving us stable frame rates on intense games; 264 00:14:20.459 --> 00:14:24.096 but we're not really doing anything better than a console can put out right now. 265 00:14:24.096 --> 00:14:28.100 So let's imagine if we decided to upgrade our systems in 2016, 266 00:14:28.100 --> 00:14:30.870 to keep up- In 2016 to keep up with the console refreshes. 267 00:14:30.870 --> 00:14:33.105 Sammy: You have 15 \"so's\" in the script. 268 00:14:33.105 --> 00:14:34.607 Sammy: Hahahaha. Adam: Yeah, I realize, yeah. 269 00:14:34.607 --> 00:14:39.378 Adam: That's actually funny, that's a rule that I honestly disagree with on some occasions with Linus. 270 00:14:39.378 --> 00:14:43.082 So the \"so\" is banned thing, makes a lot more sense when you're doing a vlog. 271 00:14:43.115 --> 00:14:43.549 Sammy: Mmmm. 272 00:14:43.549 --> 00:14:48.320 Adam: Because a lot of people will start saying \"so\", as a preamble to the rest of their sentence; 273 00:14:48.320 --> 00:14:51.423 and when you cut a bunch of sentences together, it gets really obnoxious. 274 00:14:51.423 --> 00:14:55.060 When you're- In a script, saying the word \"so\" is a little bit better, 275 00:14:55.060 --> 00:14:59.164 but I do say so two sentences in a row, and one I don't need it. 276 00:14:59.198 --> 00:15:03.435 Going like, \"so let's imagine we decided to upgrade our systems in 2016\"; 277 00:15:03.435 --> 00:15:07.139 Is a fine usage of the word \"so\", because it kind of helps it ebb and flow, 278 00:15:07.172 --> 00:15:10.643 and it indicates to the viewer that we're moving on to the next subject, 279 00:15:11.110 --> 00:15:13.312 but you don't want to use them too many. 280 00:15:13.312 --> 00:15:17.049 It's time has come only after three and a half years, it's upgrade time. 281 00:15:17.049 --> 00:15:18.717 See that's a weird sentence, yuck. 282 00:15:19.418 --> 00:15:23.155 Not only do we have the worst price to performance ratio out of all of our rigs. 283 00:15:23.222 --> 00:15:24.790 There's a link to a Google Docs sheet. 284 00:15:24.823 --> 00:15:27.860 I will say the most embarrassing thing about this was not looking at my script; 285 00:15:27.860 --> 00:15:31.196 it was going back and looking at my spreadsheet. 286 00:15:31.363 --> 00:15:32.932 Adam: Awful, awful. 287 00:15:33.365 --> 00:15:35.200 Adam: I wasn't sure if I was gonna show it to them, 288 00:15:35.200 --> 00:15:38.771 but I realized that for this kind of script I need to show them something 289 00:15:38.771 --> 00:15:41.040 or else I'm just kind of like yelling numbers at a page; 290 00:15:41.040 --> 00:15:46.912 and I wanted to show them that I also know how to do some graphing as well as like, parse data, 291 00:15:46.912 --> 00:15:52.818 but I kind of only made the spreadsheet for me, and I did not have enough time to fix it, 292 00:15:52.851 --> 00:15:55.020 to make it like really nice and presentable; 293 00:15:55.020 --> 00:15:57.890 so I kind of just tacked it in at the end there, which might not have been the smartest move. 294 00:15:57.957 --> 00:16:01.660 I'm still- I still got hired, but I'm just- Maybe I would have gotten hired sooner. 295 00:16:01.694 --> 00:16:02.728 Sammy: Hahahahaha. 296 00:16:03.095 --> 00:16:06.999 Adam: When it comes to this- This has the worst price to performance ratio of all of our rigs; 297 00:16:07.466 --> 00:16:08.300 but when it comes to that- 298 00:16:08.300 --> 00:16:11.537 When it comes to this system, our non overclockable CPU is starting to feel the heat; 299 00:16:11.537 --> 00:16:14.840 so we are going to upgrade that too, which means we need to upgrade our motherboard. 300 00:16:14.840 --> 00:16:18.577 Oh no, this means a lot of money that we saved going budget back in 2013 301 00:16:18.577 --> 00:16:22.915 is going to have to be spent on components that don't provide a meaningful uplift in performance. 302 00:16:23.382 --> 00:16:26.018 Maybe we aren't saving as much as we thought we were. 303 00:16:26.018 --> 00:16:29.421 So with our remaining budget we upgraded the mobo to a newer model, 304 00:16:29.421 --> 00:16:35.894 got a new kit of RAM and upgraded to a Ryzen 1500X and a GTX 1060, just barely squeezing into our budget. 305 00:16:35.928 --> 00:16:38.564 I think this is a good paragraph now. 306 00:16:38.564 --> 00:16:40.032 I mean the- Yeah, I'd fix some things, 307 00:16:40.065 --> 00:16:40.432 Sammy: Yeah. 308 00:16:40.466 --> 00:16:43.002 Adam: but like yeah, pretty much. 309 00:16:43.002 --> 00:16:45.104 It's just like okay here's the point, here's what it is. 310 00:16:45.104 --> 00:16:49.942 It's interesting, because now overclocking just doesn't matter; but back then overclocking was huge. 311 00:16:49.942 --> 00:16:58.117 I remember the system I had that I built in 2013 had a i7-2600K, 312 00:16:58.117 --> 00:17:03.355 and I think the boo- the base boost was like 3.8 gigahertz or something? 313 00:17:03.355 --> 00:17:06.158 But I overclocked it to 5 gigahertz. 314 00:17:06.892 --> 00:17:11.797 Like stable all core, because that's just what you could do back then? It was wild. 315 00:17:11.830 --> 00:17:14.500 Our mid-range build is still getting the job done in 2016, 316 00:17:14.533 --> 00:17:17.870 but we have some spare cash for performance uplift, so let's just upgrade the GPU. 317 00:17:17.870 --> 00:17:20.139 We can spend some good money on a new card 318 00:17:20.139 --> 00:17:23.709 and still be spending less than our big spender did over there in 2013. 319 00:17:23.709 --> 00:17:25.744 That- I just added the \"in 2013\"; 320 00:17:25.778 --> 00:17:27.846 Sammy: Yeah. Adam: because that clarifies that sentence. 321 00:17:27.946 --> 00:17:32.851 We'll keep this CPU and upgrade to a fancy new GTX 1070, and see what kind of pep this puts in our step. 322 00:17:32.851 --> 00:17:35.721 Oh and look at that, we still have about $50 left in our budget; 323 00:17:35.754 --> 00:17:37.890 $50 we could spend at LTTStore.com. 324 00:17:37.890 --> 00:17:40.092 Adam: I, my comment on it is, this is really funny; 325 00:17:40.092 --> 00:17:42.061 my comment says \"Ooh baby, merch integration\". 326 00:17:42.094 --> 00:17:43.162 Sammy: Hahahahaha. 327 00:17:43.195 --> 00:17:45.330 Adam: Oh, this one is f****ing embarrassing. 328 00:17:45.330 --> 00:17:47.766 This sentence just shouldn't be there. 329 00:17:47.766 --> 00:17:52.805 For 2020, games we can see that out budget PC, is basically out of the running; 330 00:17:53.705 --> 00:17:55.340 unable to get playable frame rates. 331 00:17:55.407 --> 00:17:59.445 There's a needless comma at the start, when I should- \"for 2020\" comma, 332 00:17:59.445 --> 00:18:03.882 \"games that we can see that out\", it should be \"our\" budget PC; 333 00:18:03.882 --> 00:18:06.051 \"is basically out of the running\" and another comma splice... 334 00:18:06.985 --> 00:18:09.121 \"unable to get playable frame rates\", no period. 335 00:18:09.121 --> 00:18:10.355 Feels like I just was about to start up; 336 00:18:10.422 --> 00:18:13.125 and then I go \"as we can see from our price to performance charts, It's a bit of a blowout\". 337 00:18:13.158 --> 00:18:16.728 I just didn't- I think I just needed to mention the 2020 games. 338 00:18:16.762 --> 00:18:18.797 I know here I also would have clarified, 339 00:18:18.797 --> 00:18:21.733 that I would remind the viewer that we are not upgrading the high-end PC; 340 00:18:21.733 --> 00:18:23.469 because we've used all of our budget in 2013. 341 00:18:23.469 --> 00:18:25.404 I'm just more like, I can't believe I submitted that. 342 00:18:25.437 --> 00:18:26.004 Sammy: Hahahaha. 343 00:18:26.038 --> 00:18:28.907 Adam: I remember being incredibly busy when I had to write this. 344 00:18:29.241 --> 00:18:29.808 Sammy: Mmm. 345 00:18:29.875 --> 00:18:33.979 Adam: And so like, I think I wrote most of this in like a couple of nights. 346 00:18:33.979 --> 00:18:37.783 As we can see from our price to performance charts, it is a bit of a blowout. 347 00:18:37.816 --> 00:18:41.553 Splurging all at once isn't worth it, and neither is trying to do a dirt-cheap budget build. 348 00:18:41.553 --> 00:18:47.126 In fact, they're almost performing exactly identical in terms of price to performance, post upgrade. 349 00:18:47.626 --> 00:18:50.729 If you're trying to save money in the long term the best course of action 350 00:18:50.729 --> 00:18:54.867 appears to be spending a bit more on your CPU to get a chip that will last you a long time for gaming; 351 00:18:54.867 --> 00:18:59.138 while holding back on your initial GPU purchase so that you can upgrade later down the line. 352 00:18:59.204 --> 00:19:03.275 While the budget build may seem appealing, the cost of upgrading so many components more frequently 353 00:19:03.275 --> 00:19:07.045 ends up being a bigger burden on your budget... fun alliteration, 354 00:19:07.045 --> 00:19:12.050 over the course of time and you spend more time with lackluster performance than a mid-range build. 355 00:19:12.050 --> 00:19:13.919 Well, none of these builds will compare to new- 356 00:19:13.919 --> 00:19:16.822 So that's an okay sentence, I would say that my problem with is 357 00:19:16.822 --> 00:19:20.058 that we don't acknowledge, the angle that sometimes people- 358 00:19:20.058 --> 00:19:23.762 A lot of people who are buying budget systems that's just all they can afford. 359 00:19:24.496 --> 00:19:26.532 For a lot of people, like especially if it's a computer; 360 00:19:26.532 --> 00:19:30.936 maybe not for a gaming computer, but for a lot of people that they can't wait to buy a computer, 361 00:19:30.936 --> 00:19:32.037 they have to buy a computer now. 362 00:19:32.037 --> 00:19:34.439 But I think that like the advice still kind of holds; 363 00:19:34.439 --> 00:19:37.075 if you're a gamer and you're going to buy a computer, 364 00:19:37.075 --> 00:19:40.712 and you want to not upgrade it for a long time? buy a good CPU. 365 00:19:40.712 --> 00:19:44.616 Funny enough, we didn't even know this but like, AM4 was around for forever; 366 00:19:44.616 --> 00:19:48.620 so if you moved to this, you could have been in a- On an AM4 socket computer 367 00:19:48.620 --> 00:19:52.291 and then continue to not have to upgrade your motherboard for another five. 368 00:19:52.324 --> 00:19:54.960 Well, you still wouldn't have to upgrade it; you could just get a new CPU. 369 00:19:55.527 --> 00:19:58.664 But we didn't- No one knew that back in 2020. 370 00:19:58.730 --> 00:20:01.133 While none of these builds will compare to a newer systems, 371 00:20:01.133 --> 00:20:05.470 using the massive leap in performance that the new Ryzen CPUs and 2020 GPUs have given us; 372 00:20:05.470 --> 00:20:08.006 \"shown us\", it should be like \"given us\", \"have provided us\"? I don't know. 373 00:20:08.040 --> 00:20:12.945 The mid-range computer's now looking like the only computer out of our three that doesn't need an upgrade. 374 00:20:13.378 --> 00:20:15.847 Hopefully this video provided you with a bit more insight into your next upgrades, 375 00:20:15.847 --> 00:20:17.216 and as a final note think about this. 376 00:20:17.216 --> 00:20:21.019 As we go into the new console generation consider taking that mid-rate- the mid-range route; 377 00:20:21.019 --> 00:20:25.090 and plan on a one GPU upgrade, but don't spend the bread just yet. 378 00:20:25.090 --> 00:20:27.926 We still don't know how intensive these next-gen games are going to be; 379 00:20:27.926 --> 00:20:31.997 so my advice is while this may be a great year to upgrade, hold off. 380 00:20:32.030 --> 00:20:36.768 Remember, knowledge is power; don't pre-order anything, wait to see reviews 381 00:20:36.768 --> 00:20:39.338 and real-world benchmarks before buying stuff. 382 00:20:40.205 --> 00:20:44.209 Just be patient, at least until our 6000 series coverage comes out. 383 00:20:44.209 --> 00:20:47.846 Speaking of waiting, you know you shouldn't- Don't wait to check out our sponsor. 384 00:20:48.113 --> 00:20:49.548 It's not good enough to be a video. 385 00:20:49.748 --> 00:20:52.484 It just is- Frankly at this point to me it feels unfinished. 386 00:20:52.551 --> 00:20:53.051 Sammy: Mhmm. 387 00:20:53.252 --> 00:20:56.021 Adam: There's not- We barely do any discussion; 388 00:20:56.021 --> 00:20:58.724 I basically just read you the results and then go, peace. 389 00:20:58.857 --> 00:20:59.358 Sammy: Haha. 390 00:20:59.391 --> 00:21:01.960 Adam: I don't help you, like I don't provide extra learnables; 391 00:21:01.960 --> 00:21:06.865 I also don't spend enough time talking about caveats with methodology or... 392 00:21:06.865 --> 00:21:10.002 Nothing's guaranteed, like I didn't reinforce the point that like 393 00:21:10.002 --> 00:21:14.973 this is just looking back, this is not a predictor of how things will go in the future. 394 00:21:14.973 --> 00:21:17.576 When a lot of people bought like 20 series cards or 10 series cards, 395 00:21:17.576 --> 00:21:20.078 nobody knew that the 30 series would be such a huge jump. 396 00:21:20.212 --> 00:21:22.447 So if you bought a 20 series card, you got screwed. 397 00:21:23.382 --> 00:21:26.551 But at the time it wouldn't have been the worst choice. 398 00:21:26.551 --> 00:21:30.222 This is like, like one of the big things about this is it's like- 399 00:21:30.222 --> 00:21:35.360 In general some of the rules that I have here, in terms of like thinking about your upgrades, 400 00:21:35.360 --> 00:21:40.465 going for mid-range CPUs so that you can last a little bit longer and plan on one GPU upgrade. 401 00:21:40.465 --> 00:21:46.238 Is a- is smart, you really don't actually know. 402 00:21:46.238 --> 00:21:49.274 It's not like, it's not super applicable. 403 00:21:49.641 --> 00:21:51.977 I think I wrote it in about two nights. 404 00:21:51.977 --> 00:21:54.713 Probably most of it on the same night knowing how I was back then. 405 00:21:54.813 --> 00:21:59.318 It would take me a lot longer now; because one, half the- 406 00:21:59.318 --> 00:22:02.054 like, there's like no guidance for like 80% of the script; 407 00:22:02.054 --> 00:22:04.990 two the script would be a little bit long, it would need to be more fleshed out. 408 00:22:04.990 --> 00:22:07.759 But I think I was also aiming for a word count, 409 00:22:07.759 --> 00:22:11.496 and I think the word count that they had for the scripts was slightly lower than the word count for a video. 410 00:22:11.530 --> 00:22:13.999 Sammy: Yeah, I heard it was a thousand? 411 00:22:14.366 --> 00:22:18.837 Adam: Yeah, so I have like, just from quickly highlighting, I have like 1100 words. 412 00:22:18.837 --> 00:22:22.374 So I think that like, for our videos we usually aim for like 1500. 413 00:22:22.374 --> 00:22:26.912 That's like the length, so I would have had more words to cover. 414 00:22:26.912 --> 00:22:30.449 A lot of this was also like I just pulled numbers from websites, 415 00:22:30.482 --> 00:22:32.718 and benchmarking takes a really long time. 416 00:22:32.718 --> 00:22:35.854 I probably could have spit this out in a similar pace, but I probably would be a little bit slower 417 00:22:35.854 --> 00:22:36.788 but it would be much better. 418 00:22:36.788 --> 00:22:39.191 Yeah, I think that um, 419 00:22:39.191 --> 00:22:43.495 the strongest thing is I think I really did kind of nail the tone. 420 00:22:43.495 --> 00:22:46.164 I think I sounded like a- It sounded like an LTT script. 421 00:22:46.198 --> 00:22:46.665 Sammy: Yeah. 422 00:22:46.698 --> 00:22:50.235 Adam: In terms of like, kind of like asking questions out loud, 423 00:22:50.235 --> 00:22:53.372 some sort of fun kind of sentences in there, probably not enough. 424 00:22:53.372 --> 00:22:55.774 I would have more jokes in at this, at this point. 425 00:22:55.774 --> 00:23:00.946 But yeah, I think I think I really nailed the tone; which is what I was going for. 426 00:23:00.946 --> 00:23:04.950 I think the worst thing is that I just it just lacks discussion, 427 00:23:04.950 --> 00:23:11.890 and honestly probably, the first paragraph discussing half the results is just a mess. 428 00:23:11.923 --> 00:23:12.691 Sammy: Hahahahaha. 429 00:23:12.691 --> 00:23:15.560 Adam: That's probably the worst part, is that it's just like, huh? What? Who? 430 00:23:15.560 --> 00:23:18.864 It's important to be able tell a story and have a good flow, 431 00:23:19.531 --> 00:23:21.500 then it is to know a lot about hardware. 432 00:23:22.100 --> 00:23:24.536 But really yeah, really what it comes down to is 433 00:23:25.137 --> 00:23:33.078 understand your voice and your position, and let that in influence everything, every part of the script. 434 00:23:33.178 --> 00:23:39.851 If a sentence in there is only facts, then think about how that sentence could be turned in to have, 435 00:23:39.851 --> 00:23:42.587 to have some sort of slant to it; 436 00:23:43.188 --> 00:23:46.057 something that, how that sentence influences your story. 437 00:23:46.057 --> 00:23:48.126 And make it fun, yeah You just have to have fun. 438 00:23:48.126 --> 00:23:50.629 Like it can be tough when you're doing like a job application, 439 00:23:50.629 --> 00:23:54.900 but if you aren't having fun writing your script or don't have fun with it, 440 00:23:55.467 --> 00:23:57.135 we're not gonna have fun reading it. 441 00:23:57.135 --> 00:24:00.972 And probably the most important thing about LTT is that we want to be fun. 442 00:24:01.006 --> 00:24:06.545 We want to be fun and educational so- But the fun comes before the word educational. 443 00:24:06.578 --> 00:24:08.713 Thanks for watching and subscribing to Floatplane. 444 00:24:08.713 --> 00:24:12.150 If you like this one, why don't you watch? Well, one of the other ones in this series. 445 00:24:12.150 --> 00:24:14.886 I don't know who's out right now, but you can go do it. 446 00:24:14.886 --> 00:24:16.588 Or you could watch my Meet the Team. 447 00:24:17.255 --> 00:24:19.424 How come we don't do Meet the Teams anymore, Sammy?"}