Hey, this is Brett, and this 2019 Ram 3500 Crew Cab, Long Box, Dual Rear Wheel, Big Horn Level 1 Sport Appearance Package is stock number 13942Z. I am here at Summit Automotive in Fond du Lac, Wisconsin, your new and used heavy-duty truck and Ram headquarters. This 2019 Ram 3500 has the 6.7 liter high output. Cummins diesel engine puts out 400 horsepower, 1,000 foot-pounds of torque, and it's paired up with the ICE in heavy-duty 6-speed automatic transmission. This truck can tow an amazing 32,781 pounds and has a max payload of 5,433 pounds. I found those numbers on Ram's TOWLGuide website. I'll link those in the description below. This truck has been fully-safetyed and inspected by Alra Service Shop per the state of Wisconsin inspection process. It has a fresh oil and filter change. All the fluids have been checked and topped off and it is 100% ready to go. That being said, I'm going to go all the way around in this video inside underneath, start it up, and take a look under the hood to give you the most accurate representation possible. Diamond black pro-coats color. I shoot all my videos in 4K, and if you like the video, you can subscribe to my YouTube channel, which is youtube.com. Click the bell notifications to get updates on the videos I do each and every day, as well as having access to one of the largest catalogs of vehicle and truck walk-arounds on YouTube. This one comes with the 17-inch polished aluminum wheels, and it has Michelin LTX AT tires. These are LT 235 ADR 17s. I would say they have probably about 80% to 90% of the tread left on them. Frame and underbody is exceptionally clean on this truck. This is a one-owner clean title history, clean car facts, no accidents out of Kentucky. Headlight lenses are nice and clear. You get the factory fog lights. Painted bumper is part of that sport appearance group. No major dents or dings on that front bumper. You get the front bumper parking sensors as well. Blacked-out grille, also part of that sport appearance group. The hood is in fantastic condition, and you do get the cab lights up top. Passengers side front fender, no major dents or dings on there. And the passenger side front wheel, no major scuffs or scrapes on there. Diamond black, one of my favorite blacks of any manufacturer. It's got a lot of gold flake in it. So when it's out in the sun, it really sparkles gold a lot. Really a cool color. And as you go down this side of this 2019 Ram 3500, take note of how clean that body is, how reflective and mirror-like that paint is. I take these HD videos so if you are far away or even if you're close by and you just cannot make the trip down but you're still interested in purchasing the truck, you can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's absolutely no surprises, and you can make a smart and informed buying decision from wherever you're at. If this video helps you make that buying decision, let your salesmen know that you saw the video, that it was helpful, that Brett sent you. This one does have the 3M rock guard on the front of the Dually tub, and it's doing a nice job. I didn't see any major dents or chips or anything like that. Back wheels are like new, very nice wheels on this truck, and the back tires have just as much tread as the front tires. Frame and underbody is exceptionally clean. It's like that all the way underneath, and it has all the remaining factory exhaust, so it hasn't been altered in any way. Dually tub rests the way down. Didn't see any major dents or dings on there. Looks really good. Coming around to the back, the rear bumper is in pretty nice shape, and the only thing that I really saw in the entire truck is there is a ding on that rear bumper, but do not worry, it does not affect the performance of the truck. Back up parking sensors, full towing package with receiver H4 pin and 7 pin wiring. Tailgate is in fantastic condition. It does have the locking tailgate, spring and bed liner, gooseneck hitch, you get 7 pin wiring back here. You also get LED bed lighting, which go on like that, and you can see you get some side box tie downs. That spring and bed liner goes on to the tailgate, which is really nice. This one also comes with a trifecta 2.0 truck hero soft tonneau cover. I didn't see any major rips or tears on there. I believe it's a fold up tonneau cover. And as you go down the driver's side, just as clean as that passenger side, no major dents or dings on there, looks really good. Once again, very few to know rock chips on there, and for full disclosure, this back wheel is in fantastic condition as well. Driver's side doors and cab, all very, very nice. See just how reflective that paint is, very nice truck. Heated fold up tow mirrors, built in directional signals. They fold up like so, they fold in like that.  No rips, no tears on the seats. Power driver's seat with a lumbar, factory all-weather floor mats. Auto headlamps, power pedals, power windows locks, mirrors. You get the cloth bolsters and the wood grain trim. You also get the power folding mirrors. I always like showing both sides so that you know that both sides are working properly. And this truck is super clean in the front. It is also super clean in the back. No rips or tears on the back seats. You also get the latch child safety system for any child car seats you may have. Fixed glass rear window, that headliner is in fantastic condition. These seats fold up for extra storage. You get a load floor back here, which is really nice. You've got muddy boots or tools. Put them on there. You're not going to get your seats dirty. Or if you've got pets, put both sides down. They get a nice flat place to lay or sit. And once again, they're not going to get your seats dirty. Receiver hitch reducer and storage under there. You get in-floor storage with removable bins for easy cleaning. You can put ice and drinks in there. It's like you have too many coolers wherever you go, or if you're not in Wisconsin, just extra storage. Sides curtain airbags, child safety locks on the back doors. And the inside and bottoms of the doors are in fantastic condition. We'll hop inside in just a second. I'll show you the VIN sticker as well as the tire and loading information sticker. Once again, this one can haul 32,781 pounds and has a max payload of 5,433 pounds. Hop inside here, check out the miles, radio, and everything that this truck has to offer on the interior. You can see this one has 28,469 miles. The instrument cluster is very nice and clean. You do get the digital speedometer, leather-wrapped steering wheel, cruise controls and gear selector on the right, Bluetooth and information center controls on the left. You also get audio controls on the back of the steering wheel. Your six-speed automatic transmission, ICEN transmission, there's your gear selector right there on the steering wheel. Push-button four-wheel drive, you get the 8.4 4C radio. It gives you AM, FM, and series XM radio capabilities. You also have your apps on here, including your cargo cam and your backup cam. You can see just how nice and clear those are. They made them HD in the new Rams. And you get your cargo cam there, which if you didn't have the tonneau cover on, you can see what's going on in the bed. And you can zoom in on that receiver hitch to get hooked up to your boat camper or trailer the first time, every time. This one also has Android Auto and Apple CarPlay capabilities. So you can project your phone to the screen. If you've got Waze or Google Maps on your cell phone, project it right to the screen. And it's like you have nav on the screen. So that's a really neat system. We actually did a demo on Android Auto to show you how that works. That's in the upper right-hand part of the screen if you want to check that out. Volume and tune controls, climb controls, factory brake controller, factory exhaust brake, tow haul mode, and front and rear parking sensors. You also get two USBs, two USB-Cs and an Augstjack keyless entry with remote start. And that's in nice condition as well. Smells very clean inside this truck. I don't think it's ever been smoked in. Passengers side format and seat are in fantastic condition. And once again, that headliner is like new. You do get map lights right there. Home link buttons for your garage door security systems and lane systems and auto dimming mirror. We'll start it up and take a look under the hood. Starts right up. No check engine lights or anything like that. We will be putting some fuel in this truck after this video. I would personally like to thank you for checking out the video today. And hopefully from this HD video, you've been able to verify the quality, condition, options, and of course, cleanliness of this truck all the way around. All those lights are working fantastically under the hood. We have the 6.7 liter high output Cummins diesel. 400 horsepower, 1000 foot-pounds of torque. Engine bay is very clean, runs very smooth. Once again, this truck has been fully safe and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. There is the emission sticker. And this truck is 100% ready to go. I would highly recommend it from a quality and condition standpoint and other than that little ding in the bumper. This thing is just about perfect. I would ship this one to New York, Texas, California, Florida, whoever is going to get this truck is going to love it. And to see more pictures of this truck or one of our other 550 new and used cars, trucks, SUVs, minivans, wranglers, half-tons, three-quarter-tons, one-tons. You name it, we've got to go to that website there. Summitauto.com. Full pictures and descriptions of every single vehicle all at summitauto.com. If you'd like to check out more HD videos, you can go to youtube.com. Click the bell notifications. You'll get updates on the videos I do each and every day as well as having access to one of the largest catalogs of vehicle and truck walk-arounds on YouTube. In fact, in a second, you will see a link to subscribe in my YouTube channel in the upper left. A link to more Ram 3500 truck videos are done in the upper right. A link to this vehicle on our website in the lower left. And a link to one of our latest YouTube videos in the lower right. Click those, check us out. We're super excited to help you with this Ultra Clean 2019 Ram 3500 Crew Cab Long Box Dually. Bighorn Level 1 Sport Appearance Package with the Hyo Put Cummins Diesel in Diamond Black Braille. Thanks again for checking out today. Remember to like, subscribe, and share on the YouTube channel. I really appreciate it. Thanks again.


Hey guys, this week in the rundown, applications are being accepted for the Advanced Education Voucher Program. We have an interview with Mikpon on SAPR, and E-9 active duty board results are out. TAYLORS E7 through E-9, who are looking for an opportunity to earn a bachelor's or master's degree, are encouraged to submit applications for the Fiscal Year 16 Advanced Education Voucher or AEV program. To be eligible, you must pursue a degree relevant to the Navy such as Strategic Foreign Languages, Construction Management, or Human Resources, being E-7 with no more than 17 years of service, an E-8 with no more than 19 years of service, or E-9 with no more than 23 years of service. Applications must include endorsements from both their CEOs and Command Master Chiefs. Deadline for submission to Instic is May 27. Check out navadmin092-16 to read all the details of the AEV program. This week, we talk with Mikpon Stevens as we wrap up Sexual Assault Awareness and Prevention Month, or SAPLM. Mikpon spoke on the importance of using our command resources and preventing sexual assault year-round and not just during SAPLM. Here's some of that interview. What's most important is that we remember to treat each other with dignity and respect. You know, if we just treat each other with dignity and respect that we and others deserve, then in many ways this problem, this significant challenge that we have with sexual assault, just goes away. So let's remember to treat each other with dignity and respect. Check out the full blog and interview on Navy Life. E-9 results are out and congratulations to all those selected. Check out the navadmin on NPC to get the full list of those selected. Well, that's all for this week. For any questions, send us a message at usnpeople at gmo.com. For the Chief of Naval Personnel, I'm Institute L.J. Burleson. Thanks for watching.


What's up everybody, it's Jason here for jasperjasecasebreaks.com 21-22 Pinini Spectrum Basketball 4 box half case break picketing number 6 just sold out and I believe this is the second half number 5 and 6 were from the same case we did have to do an R&B which we did for these teams here in the list and let me quickly show you that list right there so we have Cleveland, Orlando, Brooklyn, Sacramento New York, NY, Miami and Phoenix there's those customer names there and everybody else bought in straight up let me adjust this really quick Jeremy, is that the dude from your Pacers? Alright, cool yo and again, Joe X them so let's take another from the same case 4 boxes that's no bueno I think that's actually just stuck on here on the top that was a little weird but a Jalen Green though you can probably wipe that off with a microfiber cloth Rockets, that is going to straight up Ryan PG and a little LeBron James variation then we got a Rudy Gay full spectrum, that's the Raptors which is Nicholas straight up and then Jazz which is straight up as well so that'll be randomizer there 74-99 so we'll randomize that at the end I mean I don't know if you really want this card to have this on there but probably better to take it off now before it gets even more stuck 10 out of 99, Christian Wood for the Rockets PG, Aaron Wiggins and it's a 99 Jaden Springer little patch auto that's Philly you want Philly, Philly? Wayne with the 76ers my King's bouncing back beating the the Toronto Maple Leafs 4-2 John Collins 75th for the Hawks Sean with that one Ogyon Novi, John Morant and I bought a little Moises Moody to 99 22 out of 99 Golden State Ward is going to Shawn Matic last one here, we'll go to the next box a little young Kevin Garnett number 10 out of 49 that's for the T-Wolves which is Ryan Albert and St. Gunn that's the 25 Radiant Autograph for the Rockets that is Houston Rockets, Ryan alright, next box does anybody even remember what was hidden the first half of this? Herb Jones for the Pellows to 99 Stephen Curry, Jimmy Butler Austin Reeves to 149 with a patch auto for the Lakers Ryan with that one didn't see a Carl Calf well let's just hope nothing's super crazy so that way we can pull some crazy stuff here alright Fin Pack, I think we got a redemption Zyger Williams for the Grizzlies alright and let's check on this here Rookie Jersey Autographs interstellar part number 206 Zyger Williams I don't know what interstellar is out of let's see if we can take a look though but that's going to go to the Memphis Grizzlies though and Nicholas Rookie Jersey Autographs interstellars out of 49 alright next one nice one there, Malcolm Brogdon 11-35 and a Kobe White that's number to 75 nice Davion Mitchell for the Sacramento King that's our first hit for the random number block at least numbered ones 47, it's about 7 going to Robert Runkel so again all the non-numbered ones will be randomized to the group but I think that was our first numbered card though how about the Admiral to 49 for the Spurs Kaishawn with that one catalyst 35 out of 49 solid, solid ooh good me in Vegas Chris Duarte alright they've got JT Thor to 75 a little patch auto that is for the Charlotte Hornets and Brian Wofford D'Angelo Russell to 99 and Karis Lavert to 25 that's our own card as well Cleveland part of the random number block in the zone 8 out of 25, that is Robert Runkel alright well technically I technically worked those days probably going to be able to go out there my wedding anniversary though is on the 17 so I think I might be working that day but I'll probably be celebrating on our days off Desmond Bay or actually sorry on the 16th I have a poster on the 17th and Jared Butler to 10 9 out of 10 Radiant Gold Gold Utah Houston Rockets dinner shoulder well wizards 49 in the zone wizards going to Shea alright down to the last box maybe we did hit some monster stuff I don't know see what this last box is holding and hiding alright let me change it to the World Series game now no the Kingswong Oregon wong Kingswong today alright let's see ooh 5-0 Houston now does Philly have a comeback though I don't think so right imagine if Philly were to come back 2 nights in a row down 5-0 that would be ridiculous Tobias Harris and then we got a Wendell Carter Jr that's 21 out of 49 full spectrum and again that's Bulls which is Jeffery and then Orlando is part of the random number block so again whoever wins that randomizer Bulls gets it straight up it's Orlando is going to go to spot 1 which would be Kev we'll do the randomizer 2 as well Tyler here over the heat that's part of the random number block 7 out of 25 spot 7 is Robbie Ronkel I think Robbie got all the hits so far ooh that little brunt spot a short brunt probably not but actually still a nice one to sleeve and Bill Lambier Icons 43 out of 49 that's Nicholas with the Detroit Pistons come on baby let's go with something nice right here and Bo Nicks man he's definitely played a lot better in Georgia and a beautiful Josh Giddy good lord that is 14 out of 35 and straight up Andrew with the Thunder to 99 Devin Vaso for the Spurs catch on with that one 38 out of 99 man alright we must hit something monstrous in the first half then we're about to get a 1 on 1 right now let's see last character guys we got Laurie Markinin Cavs 97 out of 99 that's actually part of the random number block 7 another one for Robbie Ronkel which was a variation for Sacramento here we go out of 49 Jaylen Green radiant autographs so maybe there was some nice stuff we ended it off nice here though that is 12 out of 49 for the Houston Rockets which is Ryan straight up there you go nice way to end it right there though and there you go folks so again all the non numbered base for the R&B will be randomized a lot and it's only for those teams in the R&B if there isn't any well then obviously don't get anything everything numbered should went to their numbers and then of course really quickly quick little recap nice giddy there that would be our Bradley Beale Goldger Butler JT Thor Robinson Coby White Zyra Williams Reeves, Sengun, Moody, Jayden Springer not the worst but first half maybe alright then two randomizes here that will be Raptors, Utah Jazz and then of course Bulls, Orlando Magic switch scenes get a dice roll list list list alright so there you go Raptors, Jazz, Magic Bulls here we go roll one and a two three times good luck here we go one two and it's gonna go to the Raptors after three times or sorry no Jazz, sorry three times I guess it's moved right to the last second for number three so Jazz actually get that so there you go alright I'm not tripping alright one two three Jazz, yeah alright now three times here for this one one two three times three three Magic so Magic win that that means it's gonna go to the random number spot one which is Kev alright so there you go so I appreciate it folks there you go guys again don't know if we have any more spectra but if we do it'll be from our fresh case we'll post them up jazbyzcasebricks.com


I want you to see how Rational National kind of responds to this guy and the kind of admiration, the kind of, and this is what, this is the left. This is who we're dealing with in terms of economics, in terms of morality, in terms of everything, and you know it's, let's take a look at this. So I'm going to be commenting on Rational Nationals. What's his name? Somebody you know his name? I couldn't find his name. It has to be somewhere here. But anyway, we're going to be commenting on his response to this Richard Wolfe guy as well. Here we go.  Mark's an economist, Professor Richard Wolfe. Now before we get to that, did you notice just the, the sneering, the attitude, the disgust with which this guy talks about you and your job and, and I mean, it's just, just this condescending, creepy, you'll see this over and over again.   All right. Was that left form 2019 where he discussed four issues with capitalism? David Bell. No. It was about 20 minutes long, but I'm going to pull three different clips out of it to showcase to you just how brilliant Richard Wolfe is. He's really able to. Okay. Keep in mind, brilliant. This guy is brilliant. Richard Wolfe is brilliant. So keep that in mind as we go through this.  So I'm going to show you, I'm going to show you two of them.  To break down the, the inherent issues with capitalism and make it digestible to the average person. So let's get to the first clip. You know that in the private sector, which is where most of us work, the overwhelming majority. By the way, everything he says from now on is basically true of the public sector as well of any sector of the nonprofit sector of any sector. You know, we'll talk about that, but, but it's basically true of, of every sector produces some good or some service and sells it into the market. And that employer is never ever going to hire you for $20 an hour, unless the following sentence is true. During each hour that you work, you add more to the value of what your employer sells than the $20 he's going to pay you. Or to say it in real simple English, you produce more than you get paid. Now notice, he presents this as some kind of revelation. This is a deep point. This is, wow.  You work to them, in other words, more than $50,000. Now this is, this is what Marxism is about. This is a key point within Marxism. This is the whole basis of this idea of exploitation. But note the disdain and the wonder in which he says this, ooh, I am such a smart guy.  Now why is that just a truism? Indeed, that has to be the case. And indeed, that is true of every, every trade, every trade. When I buy an iPhone, when I buy an iPhone, I mean, it's horrible. I pay $1,000 for the iPhone, but you know what? The iPhone is actually worth more than $1,000 to me. I'm actually underpaying for the iPhone. I mean, if I paid the full worth of what the iPhone is worth to me to Apple, Apple would have a lot more money. It's not fair. And you know, what else? When Apple sells it to me, it's because they value the $1,000 more than they value the iPhone. They make money off of it.  The essence of trade is that basically we pay for something less than what it's worth to us so that we are better off as a consequence. And we sell something for more than what it is worth to us. And therefore, we also benefit. That's what makes trade fundamentally win-win. Now let's apply this to labor. The business, the evil corporation, evil in quotes, corporation, pays you $50,000 a year, $100,000 a year, whatever the amount is, $100,000 a year, because you can produce for them more than that. That is, you're worth more than $100,000. That's why they're willing to pay it for you, otherwise they'd keep the money. So the value you add to the business is worth more, I have mentioned iPhones, I've mentioned it, is worth more than the amount they give up, again, the essence of trade. And you know what's amazing about that is, is that the worker accepts the $100,000 a year because what? Because that is worth to him more than the time he's going to invest in working for this company. So of course, I always tell students in my talks, you are going to be paid less than what you're worth to the company, but more than what you can get anywhere else or more than what you value your time at. That's why it's a win-win. You're better off because you're getting more than your alternatives. And I'm assuming here that it's not just about wages, it's also about the environment, it's about the whole package benefits, whatever, the whole package that the employment involves. And the employer is going to get more than what they're paying for. It's exactly the same as buying an iPhone. And yet the Marxists present it, and Wolf is not unique here, this is the whole basis of exploitation theory, we'll get to that as he moves forward. Is that this is some kind of revelation?   All right, let's keep going. So notice, okay, so you're getting paid less than what you produce. So if you've said to yourself, have you heard some proud person say, I will never work for anyone who doesn't pay me what I'm worth, you're talking to a person who doesn't understand how the system works. Notice, he equivocates between what you are worth economically, of course, and what you produce in the context of a corporation. Note that if you could produce that as an independent and make that 100,000, let's say, I don't know, let's say you write code for Apple, and they pay you $100,000, plus the benefits or whatever, if you could write the code and sell the product by yourself to get $100,000, or let's say $110,000, because you're actually producing code worth $110,000, because you're producing more than what they pay you. If you could do that independently of Apple, then you wouldn't go to work for Apple. You'd do it independently. But the fact is, you cannot do it independently. So your work is actually worth zero independent of Apple, or Google, or some employer employing you, you know, unless you've got some new idea for some new product, and then you can go become an entrepreneur. But your work that you're doing for Apple is not relevant to anything else. It can't, it doesn't stand on its own. And therefore your worth is your worth to whom? It's not, you don't have an intrinsic worth, and your ability to produce is ability to produce for whom? Now, if you want to produce for yourself and be an entrepreneur, that's a different career track. Good for you. But we can't all do that, partially because we, most of us don't have what it takes to be entrepreneurs. Most of us don't have good ideas. Most of us, some of us are not disciplined enough to be entrepreneurs and to work for ourselves. We don't know how to sell what we would make. We have no idea how to do it, and then we would have to hire people to do the marketing. I mean, what Richard Wolfe is doing as he's rejecting specialization, rejecting again, another basic idea, basic concept in economics, and he's rejecting his rejecting the whole idea that you are worth to someone. There's no intrinsic worth. You produce for someone.  And then you get exactly what the value is that you produce. But even then, what is the price at which you get the potatoes for? Well, what the market is willing to bear? In a sense, the market is going to determine your worth. Who else is going to determine your worth? Your worth economically is what people are willing to pay you based on how much you produce and based on the fact that they make that job available to you. Now, we'll get to the role of the capitalist and the role of the entrepreneur in all of this and why there's a whole lot of dimension of ignorance here. I mean, these people have no clue how business is created, how business runs, how business produces. They just think it just happens. They're just jobs. There's just a place for you.  There's just innovation. There's just stuff. I said this the other day when I talked about about, no, I forget his name. Anyway, the guy I talked about two days ago, who did I talk about two days ago? Man, I'm getting old. The whole assumption of the Marxism and the whole assumption under most leftist economics and unfortunately, the whole assumption under most every economics with exception of some Austrians is that stuff is just there. I spoke about Cornell West. Thank you, Jennifer. Cornell West makes the same mistake. The stuff is just there. And the whole view in economics, the whole view in economics, that economics is the study of the allocation of resources under under scarcity. No, that's not what economics is about at all. scarcity is irrelevant. There are no scarce resources. What's interesting about economics is the creation of resources. It's how resources created, how wealth is created, how stuff is created, not how stuff that somehow miraculously appears gets distributed. That's not economics. That's not economics. When Marxists do it, and it's not economics when classical economists do it. The whole point of economics is to study two things. Economics properly is the study of production and trade. How resources come into existence, how values, material values come into existence. How stuff is produced and created. And then how it's traded, the principles by which that occurs. That's economics. And none of these guys, none of these guys, you know, understand, or none of these conventional mainstream or Marxist economists have any clue about what economics is really about. Never mind about economics themselves. Understand this guy, Richard Wolf is going to debate Gene Epstein. I mean, we'll see how Gene does with him. I wonder, I think Gene just like when he debated me on selfishness will will stick on some small point and won't address the bigger philosophical issues, the bigger fundamental issues that make everything this guy says, basically complete and utter nonsense. All right, here we go. You were never paid what you were worth. Yes, all of you were paid what you were worth. And if you think you could be paid more, that is, if you think you are worth more, can be worth more than switch jobs. But there is no worth that is external, that is somehow intrinsic to what the market, what people will pay you for whatever service or product or job that you produce.  Even if you think it, it's worth more. Your worth is determined in a sense by others. And you cannot and will not be in a capitalist system. Why? Because the difference between what your labor adds to the value that your employer sells. And what he pays you is his profit. Well, that's why he's in business. That's true. But no, there's the sneering. Notice the profit disgusting stuff like that. And yes, that's why he's in business. And of course, the difference between what you produce, it's not. And what he sells it at is not all profit. Other people are producing. He produces the CEO, the people who run the shop produce. And only when you deduct all of them, of course, he's got expenses, there's materials, there's marketing, there's advertising, there's a million other expenses associated with it. And only then the difference is the profit. Only then is there a profit. But all of that other stuff doesn't count. Because again, the Marxists are all about physical labor. Only labor adds value. They are intellectuals who negate the intellect. And if you don't generate that profit for him, he's got no use for you. That's right. What use do you have? Why would I pay somebody money? If they're not going to add value to me. If they're not going to make my life in some way better. And for business that some way better is profit. For nonprofit, it might be measured differently, but I'm still paying somebody, paying somebody less than what they produce, less than what they really want to me. Because I have to get value from that relationship. There has to be a profit. Otherwise, why transact? So, you know, this is again, this is just basic stuff. And the way he says it, the sneering, the, it's just disgusting. So for the American people, the vast majority of whom come home every day with a vague sense of having been ripped off. Is that true? The most Americans come home every day with a vague sense that they have been ripped off? Really? Ripped off? I mean, people might think I should be paid more and they might not be happy with a job. But really, a majority of Americans come home with a sense that they're being ripped off. Now, the truth is that if you tell the American people often enough, that they should have the feeling that they've been ripped off, that indeed they have been ripped off. Then you will create that feeling. And that I think is a lot of the frustration of working Americans of the of the what's called the working class, the middle, the lower middle class, with the jobs because they be told that their wages haven't increased, even though that's not true. They'd be told the standard of living hasn't gotten better, even though that's not true. They'd be told that inequality is a real economic problem that's holding them back. Even though that's not true. They'd be told that they're being exploited by corporations, even though that's not true. And they told us over and over and over again and nobody stands up and says, That's not true. None of that is true. Indeed, 184,000 people watch this video.  And that doesn't include the other millions of people who watch some of these horrific ideas about economics clueless about what really how economics really works. The job, they're exactly right. It's now what happens. I wonder what happens how these people view when a company loses money, and still pays its employees. And when the shareholders get really upset because the shipwrecks went down, and they lost money, and employees still get paid. It eat most businesses who start out, start out losing money. For years sometimes, the entrepreneur, the capitalist financial markets, pay the employees and they still get paid, even though they're producing no profit. Think about a biotech company that my employee at a startup, my employee, 10 scientists, real, you know, 10 scientists, pay them a salary every month for years. And for years, there'd be no profit. And yet those scientists, including the non scientists, the janitors, the secretaries, the everybody gets paid every month. And the venture capitalists keep pouring money into it. And they lose money every month. And yet, these people paid get paid every month, the workers get paid, who's exploiting hooten here. And then maybe 10 years out. Boom, there's a new drug or a new invention and they start making money. And all those years, it was the workers who got paid. And the capitalist who lost. Nobody cares. Nobody cares. It doesn't matter. What is the, because they add nothing. Just they haven't had the course yet to be able to understand why they feel that way. And why they ought to the course on uneconomics, non economics, anti economics, the closest we get to pardon me, pardon me, me for those of you who've heard me do this joke before, the closest we get as a culture to recognizing it is that peculiar tradition we have of the name we give for the two hours immediately at the end of the workday. The two hours that are advertised in that window we pass on the way home from the job, which tells us if we come inside, we can have a happy hour, underscoring how different it is from the previous hours. Is that true? The people in America hate their jobs so much that happy hour represents the distinction from being at work. The people resent their jobs that much. And if that's true, that's very sad. And that's a real problem. And the problem is that they shouldn't be at the job that they're at, that they're not being selfish enough. They haven't thought about what they really should be doing with their life and how to do it. I mean, if people at that dissatisfied, but I don't think happy hour, happy hour is not happy because it's the end of the day. I don't know. Or maybe happy hour is associated with alcohol, because that's what our culture views as happiness is getting drunk. Well, if happiness is getting drunk, then yeah, working is no good. But that's so perverse. It's not a joke. That's sad. And think about what they were doing before they had work. That is what human beings do. Before they went to work. Well, they got up with the rise of the sun.   And then they go to bed when the sun sets. That's life. That is life. Whoops, what did I just do? I don't want to do that. That's life under a pre capitalist, a pre you have a job world. Right. And that's, that's what he's arguing for. Let's go back to, let's go back to subsistence farming. How was that for those people? How was that for anybody? Even Marx understood that that was wrong. That that was bad, that that was no good. And yet that's the only option he presents here. The only option he presents. What we need today, what I call the new intellectual would be any man or woman who is willing to think, meaning any man or woman who knows that man's life must be guided by reason, by the intellect, not by feelings, wishes, wins or mystic revelations. Any man or woman who values his life, and who does not want to give in to today's cult of the stare, cynicism and impotence, and does not intend to give up the world to the dark ages, and to the role of the collectivist roads.


Hello and welcome to the session. In this session we discuss the following question which says, solve the following differential equation dy by dx plus y is equal to cos x minus sin x. Let's see the solution now. The given differential equation is dy by dx plus y is equal to cos x minus sin x. This given differential equation is a linear differential equation. Consider the linear differential equation of the form dy by dx plus py is equal to q. Now comparing these two differential equations we get p is equal to 1 and q is equal to cos x minus sin x. Now the integrating factor that is if is equal to e to the power integral p dx that is equal to e to the power integral 1 into dx. Or you can say this is equal to e to the power x that is we have the integrating factor if is equal to e to the power x. So we have the required solution of the differential equation y into the integrating factor is equal to integral q into integrating factor dx plus c. Now substituting the values for integrating factor q we get this is further equal to y into e to the power x is equal to integral q that is cos x minus sin x. This whole multiplied by e to the power x dx plus c where the c is the constant of integration. This further gives y into e to the power x is equal to integral cos x into e to the power x dx minus integral sin x into e to the power x dx plus c. So further we get y into e to the power x is equal to now let's solve this integral by parts. So we take this as the first function and this as the second function. So this is equal to first function that is cos x into integral of the second function that is e to the power x dx minus integral of differential of the first function that is cos x. Which would be minus sin x into integral of the second function that is e to the power x which is e to the power x into dx minus integral of sin x into e to the power x dx that is this term remains as it is plus c. So this further gives us y into e to the power x is equal to cos x into now integral of e to the power x dx is e to the power x plus integral of sin x into e to the power x dx minus integral of sin x into e to the power x dx plus c. Now this term cancels with this term and so we get y into e to the power x is equal to cos x into e to the power x plus c or you can say we get y is equal to cos x plus c into e to the power minus x. So this is the solution of the given differential equation. So this completes the session hope you have understood the solution of this question.


please subscribe to this youtube channel mentor talk can do press bell button for notifications there is a little bit of social commentary that's coming from me and i wanted to address the topic around china is china the new nazi germany that we had seen back in uh 1918 the first world war and then up to 1945 the second world war where the world had to come together to take nazi germany down and what comes to question really is that um the aggression that has happened at the lac which is against india in argolan ladakh region uh le ladakh region you would wonder that india being the most popular democracy in the world today has the most populous communist nation trying to aggressively um uh trying to merge it in the wrong direction and you know these are the world's civilizations so one would one would have thought that they'd get along and the the exact opposite has happened now that puts a question to our minds is that ideologies come to play here and when you have communist china it is now aggressively waging some sort of a war against democratic nations so india is the most populous democracy you have united states is the oldest democracy and you have recently seen that when it comes to india and also they're having you huge issues around commercial aspects of the 5g uh technology that is coming in from china one question that i uh came to me was that is china behaving like the nazi germany uh of world war days will the democratic nations come together uh more from a humanitarian aspect to become a communist china so will india be the beginning of the end of the communist party of china so the ccp to say so to say and this is coming at a point where we already have a pandemic uh looming large on all of us which is uh known and reportedly come out of Wuhan which is the city of china and there have been many questions that have come around being asked of china to explain why did they did not share the details of the pandemic that had happened first in their city and uh because of the lack of information that came in from the communist party of china is why the other countries could not take steps uh timely if that had happened they would have been less spread of this disease and probably less among the kids please subscribe to this youtube channel mentor talk and do press bell button for notifications


Hi, everyone. This is Winnie from Spark, and I'm going to teach you how to get to the Review Proposals page from your email or the website. So first, you should have received an email that said Invitation to Review Proposals, and in that email should be a link, a button that takes you to the C-Vent page to review proposals. Let's go ahead and open that up. So it should look like this. If you didn't receive the email, or you just can't find it, you can also access this page by going to Call for Proposals and clicking on Submit Proposal. It will take you to the exact same page. Now, regardless of that, you're going to need to log in. If you haven't created an account, you're going to need to create an account with the email we sent this invitation to. Using that, you're going to go ahead and log in. OK, so you'll have a My Submissions tab, and then you'll have a My Reviews tab. Your review should already be assigned to you within your Review tab. And there is a sample proposal for you to get used to the system with. You can go ahead and click Review, which will open up the proposal. Section A is all the proposal information. This is what the author has written. This is what you will review, and B will start the review criteria. So this is how you will score each proposal and what your overall recommendation will be and any additional comments you want to leave. The Save and Submit button will help you save or submit the proposal for review.


All we're going to do start by the mannequins going wide. Now Bull now needs to be taken beyond the 18 yard line. Two recovering, us three going in. Let's go. All defended son. Safe, no risk, Bull's out in the danger zone. That's better, that's better. Dead, dead, outside the box dead. I'm going to make one adjustment. There'll be two to start with to defend, two recovering and there'll be three attackers and the principle will be that the ball will start with the attackers and it will be served still to a wide player and it's about how those defenders two three recover as an individual and as a unit in relation to not only the ball now and the danger areas that we're trying to protect but where the opposition player is going to go as well. Great delivery. Dan, Dan, hold on for the benefit of defenders. If you're a defender now you might not need to do what so much. You ain't got to smash it. All you've got to do is what? Use the pace on the ball. Present the surface to get it out of the danger area. Okay we're going to add another defender in there. So three out of four, take it in turns, just rotate around. That's it. The three of you now have got to start between the mannequins. All right nice and tight. So we're three on three to start with. All right there's no overload like before but the ball's going out wide and it's coming in quick. There you go. Hold on. Attitude to recover. Magnificent. Trouble was you all recovered where? Dead straight. Dead straight line. Straight in the middle area of the goal. If one of them gets in front of you you can score and as what happened they ended up hitting the ball over the top of you and not one of the three could get anywhere near the challenge. Make sense? So lines of recovery very very important. So what have I done to the first man? So you might find that in a game. All right so you've got to be aware that if that first man gets blocked off now the two of you have got to readjust. What you'll see you know if I go in there sometimes it's either to paint a very clear picture about what is needed, what needs correcting, what is good practice and I'll also show one or two different scenarios maybe where attackers are quite crafty and bend the rules slightly with regard to how they use their body, how they step across people when they're recovering and see if they can solve that problem. So you might see me step in there, you might not but I like to throw the odd one in just so that they don't think well we've only got to recover along this line, we've only got to recover along that line.


Today we're talking top-notch shipping tips for your online store here on The Journey. Look, you put a lot of effort into making sure that the customer experience is a great one, that they're happy.  And with some thought and some planning, you can give yourself some time back, some well deserved time back.  Shipping both the logistics and the pricing can stress even the most seasoned entrepreneurs out. And we get it, shipping is hard. It can be complicated and messy. But hey, don't worry, small business shipping doesn't have to be a struggle. Running the operations of an e-commerce business takes a considerable amount of effort, especially if you're doing it alone. And that's why it's so important to map out a defined shipping strategy. Since the world of shipping and fulfillment can seem complex, when you're not that familiar with it, we're here, M&I, to take the agony out of shipping with shipping tips and strategies to move your e-commerce efforts forward. Starting with, hey, take advantage of free shipping supplies. Hello, environmentally friendly. Most shipping companies offer free shipping materials, which definitely helps reduce the stress of it all and the overhead. You can choose from boxes, envelopes, padded envelope pouches, you name it, you can order it. And UPS, USPS, FedEx are some of the most common shipping providers with free shipping material options. And your customers will appreciate having the full information about their final charges, especially if you alert them of shipping charges early on during the order placement and checkout process. Surprising your shoppers with the extra charges adds a block to their purchasing flow, causing a not so nice experience. So not sure what shipping options to offer? Let's take a look at some of the pros and cons to each of the options. So starting with free shipping. On average, 55% of shoppers abandon their shopping cart due to unexpected added costs during checkout. Guilty. Increase the cost of your store's items to help offset the cost of shipping. Just make sure if you're going to do that, increase the cost of the store's items. If you're going to do that, make sure it isn't just this drastic increase as significantly higher costs will throw customers off. Another shipping option you have at your disposal is flat rate shipping. This allows you to customize shipping rates to the dimensions of flat rate boxes, which can help keep costs in check. On the customer's end, they'll appreciate that there is no major surprise when it comes to checkout provided you prominently advertise the flat rate. And you'll need to do some number crunching to determine your average per package shipping cost. So you can identify an appropriate flat rate. And this is critical because it helps you land a number that makes sure that you don't underestimate and have to overpay and don't overestimate. So the customer has to overpay and consider pairing flat rates with free shipping. You can do this by charging a flat rate for smaller purchase totals and offering free shipping above a certain total, thus enjoying the best of both worlds. And it might entice that user to spend an extra $10 to get free shipping on their entire order. Another shipping option is carrier calculated shipping. Now how this works under this model, your customer pays the same rate for shipping and handling that you, your company would pay if you shouldered the bill. Now these rates vary depending on the carrier, of course, what's being shipped, its size, its weight, and where it's being shipped, the location. Now you would need to utilize shopping cart function that provides these up to date shipping quotes from various carriers. Now the obvious perk of this model is that your business passes on the cost of shipping to consumers. So these costs don't eat into your margins. This shipping strategy tends to work best for companies that aren't competing heavily on price. So experiment with those surchargers and discounts. And if you want your customers to pay for packaging and other fulfillment costs, then consider adding a surcharge to carriers projected shipping rates. You want to stand out from your competitors, consider offering a discount, perhaps on qualifying orders again on the carriers rates. All right, that's a great segue nearly. Now we want to talk about offering free shipping on promotions. I love these. So if you don't want to commit to fully free shipping for your online store, that's cool, I get it. The shipping promotions is another way to go. If you choose to offer free shipping, make sure you advertise it. That always catches my eye when I'm doing some online shopping. And so advertise it. You can do this on your social media channels and it will help to increase conversion rates. Now to maximize your profitability, you could offer free shipping once the order reaches a total amount. This gets me every time with Sephora. I go on there just to get a little bit more, I don't know, shampoo or some brow stuff. And then I notice the shipping costs and then they let me know how much more to spend. What do you think I'm going to do? I'm going to spend more so I get the free shipping. So this free shipping threshold will encourage buyers to add another item or in my case, four more items. And in the case that the minimum price is not met yet, you can select a fallback that is charged. And hey, we've all been there. The shirt doesn't fit or you wanted lime green and not alligator green or they sent you the wrong brow stuff. You never know. Put yourself in the customer's shoes and make sure that you've spelled out a clear return policy. So their mind is at ease in the event that they have to return a product. The rule here is to prepare for the worst case scenario by outlining expectations ahead of time so that those customers understand your policies clearly. Those policies will serve as a helpful playbook and can even be a chance for you to wow your customers and just help them understand that in the event that something doesn't go right, it probably won't. But if it does, I've got your back. And don't forget to include return labels. Scan based return labels are a special kind of return label that you're not charged for unless the customer uses it. So think of it as a pay one shift. And this option adds a few cents to your upfront label cost and it makes it a much better experience for your customers. So just consider including return labels for that. See, shipping is not so scary.  I think I'm going to update my LinkedIn profile and make myself my professional title a power shipper. But anyways, saving all of those hours and dollars opens up a world of possibility to focus on other key aspects of your business. All right, Neil, I'm going to check your LinkedIn later, but for now that's a wrap. You just learned top not shipping tips for your online store. Be sure to like this video, comment below with your favorite tip. Hey, make sure you subscribe to this channel and ring that bell so you get these episodes first. This is The Journey and we'll see you next time.


I am standing on Wyoming Highway 70 that crosses the Sierra Madre Mountains between encampment and bags.  When you hear the word landslide, your thoughts probably go to California's coast where million dollar homes are swept away every year. Wyoming's cold, semi-arid landscape probably doesn't immediately flash into your mind. However, with the right conditions, landslides are a very real possibility right here in the Cowboy State. In fact, landslides are one of the most common geologic hazards in Wyoming with some of the highest landslide densities in the country found within the state. The Wyoming Department of Transportation estimates that the approximate yearly cost to remove landslides from roads, maintain landslide damage roads, and to study or stabilize landslides is one million dollars per year. This year, the mountains experienced exceptional levels of snowpack and spring precipitation that saturated the soil. This combined with steep slopes, underlying bedrock, and limited vegetation to stabilize the slopes creates the perfect recipe for massive landslides such as the one you see here. In the battle of road versus landslide, the landslide usually wins by moving millions of tons of soil, rock, and vegetation. From the University of Wyoming Cooperative Extension Service, I'm Mae Smith, Exploring the Nature of Wyoming.


Good morning. So my name is Wesley, as he said. I go by GMS online. So that's what you'll find me on Twitter and GitHub and that sort of thing. And I call myself the hacker laureate of Heroku. I don't know if anybody else actually calls me that, but it's my story and I'm sticking to it. So to give you a little background, some of you maybe have never heard of this library. It's a library in Ruby that provides client interactions with a bunch of different cloud services. So this is kind of one of my biggest introductions to the world of APIs because it turns out if you want to interact with, you know, I think it's something like 20 or 30 different cloud services, you interact with a lot of different APIs and a lot of different ideas of what a good API might or might not be and, you know, kind of everything in between. And so this was actually the second or third thing that I ended up working on right in a row where I was interacting, like writing a lot of clients, interacting with a lot of APIs. So coming out of that, I was in the position where I was able to get a job with Heroku. And so when I first started actually kind of continuing with that theme was working on the command line tool, what we now call the tool belt, which again, yet another API clients, which gave me the opportunity to actually become pretty intimately familiar with the API that we had at Heroku at the time. Before I then transitioned onto the actual API team and undertook to perhaps fix what I perceived as many flaws in the API that was there when I joined. So it didn't take long to sort of realize that consuming and producing were quite distinct, even though people were like, oh, well you know all kinds of stuff about APIs, you use them all the time. And it's like, yeah, but using them and actually making them is a pretty different thing. Consuming I think is a lot simpler in most cases, although it can sometimes be really frustrating because some APIs are not awesome. So I think maybe the saving grace and some capacity is I sort of have this philosophy that in a lot of ways it's not really what it looks like that's gonna matter with the design of an API in particular, it's how it feels to actually interact with it, like what it is like for a user. And so having interacted with a lot of them, I at least have my gut reactions to fall back on. So when we're talking about a new API design or something, I can often say that doesn't feel right to me, it gives me the heebie-jeebies, I'm concerned about that, even though it's taken me quite a while after that to necessarily be able to work backwards and say, well, I don't think that this is necessarily a good idea because of X, Y, and Z, like turning that gut feeling into concrete reasons was difficult. So about the feels, so I think it's really important that the user should feel empowered and in order to better do that, I think it's really important that we borrow from things like user experience design and information design, because ultimately that's what we're trying to do is provide a good user experience for the user, the client that's interacting with their API. It should be relatively simple for them to get on board and get started. I also pull a lot, I think, from the philosophy of Ruby, which has been very influential for me, so I think it's important to think about things like the principle of least surprise that people talk about, although people sometimes jokingly call it the principle of Matt's least surprise within the Ruby context, but this idea that if you already have some knowledge about how something works and you're going in and working on something that ought to be pretty similar so far as you can understand, it shouldn't work in a completely different surprising way. If it does, then you have a problem because now you basically have to apply yourself to that learning curve every time you're going to do a new thing instead of the curve being perhaps a bit steep at first and then leveling off, which is what you hope for and something that's more consistent and less surprising. So that being said, working at Heroku on this big, important API is actually the first API that I've ever really produced, which, you know, it's no pressure, not a big deal. You know, what's the worst that could happen? I still am at this job after a couple of years, so I guess I haven't done anything too horrific, but some of my colleagues might disagree with that at times. So let me tell you a little bit about this API that I sort of inherited. What we had was, I would say, it was organic, which because it was organic, it was somewhat inconsistent, and it was also private, and I think all of these things have a tendency to go together. So for us, the only real consumers that we had concerned ourselves with of this API were the command line tool and the webpage that we operated. Since we controlled both sides of the whole equation, in some ways it didn't matter a ton what the API actually looked like as long as it got the job done. And so what we'd had over time is that when people needed to add something new to the API, they would just add sort of whatever was, you know, sort of necessary even if it wasn't sufficient, right? Like as long as it did the job, that's what mattered. And it was a different person adding the new API almost every time. They weren't too worried about going back and reviewing the existing API to see if it fit in. They just wanted to get the job done. In the world we came from that totally made sense, but I found that I wanted something that was more carefully crafted, that was more coherent throughout, that from going from one resource to another, as I mentioned, was not surprising, that it made sense because I'd written a lot of these clients. I'd even worked against this particular API and it was really frustrating for me that half the time when I was working on the tool belt, I'd actually need to open up the API code base and read through code to even understand what a particular resource did because it would be so different from the resource right next to it. And also then I wanted it to be public and for it to be public and for it to be something that I was willing to stand behind and sort of put my name on and be proud of, I thought it was really important that it needed to be more carefully brought together. So the way that this ended up working is this sort of divide and conquer thing of like I started working through the API and started building out a new version of the API that had the same resources, but in this more consistent format by trying to extract some of the common patterns and destroy all of this sort of like beautiful and unique snowflakes that were within the system because that's not really what we wanted. We wanted things that were relatively uniform and then just sort of repeating that process over and over again. As it turns out, this is incredibly tedious, especially with something that has the large surface area that the Heroku API has. We ended up kind of doing it in this checklist driven way, which is actually pretty helpful for something like this where there were basically this set of steps of like, does this resource endpoint provide these things? Is it in this particular format and this order and so on and so forth? So it helped me to be more consistent than I would be if I was just doing it off the top of my head and I would probably forget things. But I did not love this process by any means. It was not exciting particularly. I thought it was important, so I kind of trudged through it, but it quickly became clear that, you know, we were in this process of growing the API as we were going to be adding more and more endpoints, things were gonna be moving faster and faster and that ultimately it wasn't something that I was going to continue to be able to really do independently that I was gonna need help, right? So I needed to like recruit other people to be more involved in this process, but up to this point, the vast majority of this process had been basically in my head, right? It was a process that I had, it was working, I was making progress, but it wasn't something that I could easily bring other people into. You know, I couldn't invite people into it. Other people within the company were not going to feel particularly empowered to work on this API. So from there, we started working on some different tools and documentation to make hopefully this process of API design and implementation more approachable. So I wanted to walk through some of those tools now, hopefully because they might also be useful or interesting to you guys as you approach your own API concerns. So the first one is the HTTP API design guide. We have an organization called Interagent that we decided to create on GitHub to kind of house these different API design tools and patterns just because basically the Heroku org has a bunch of open source projects on it and we felt that if we just threw all of these additional things on there, they just get lost in the noise. So by having one organization, we hope it's a place that we can kind of consolidate and keep all of the things that are closely related to this area. So some of you maybe don't know what 12 factor is, but so I'll just describe that very briefly. It's something that came from the original CTO of Heroku. It talks about the 12 factor app that kind of gives 12 like first principles that are good for like web scale type apps, right? It kind of describes in a lot of ways what the ethos of Heroku was in terms of what an app is and how you should run one in the modern context. So it's like this great set of first principles. It doesn't really say like you should use Rails. It's more like, you know, you should use environment variables to set temporary configuration. You should have development and production systems be as similar to one another as possible. Like these other, you know, top level kind of principles. So my hope was that I would do something similar in the API space where I talked about best practices and the things that were working for us and why they were working as much as possible. The explain part is definitely still sort of work in progress and that people tell me all the time that I've not done a good job of explaining why some of these things are. It's sort of like I was describing of this sort of like, I have the gut feeling that this is the right thing. I can't quite put my finger on why that is, but I'm pretty sure it is the case that we should do that. So I've been trying to go back through and explain some of this better, but it's an ongoing process. And the big thing I think that's important to realize there is that it's more about patterns than necessarily solutions. And I think that's how I try to do a lot of my job too. You don't really want to solve this particular problem once. Ideally you want to try to solve that sort of class of problems because inevitably that same sort of problem is gonna come up again and again and again as you work with more and different people and more and different resources. And so if you have just a pattern that you can say, well actually in that case we use this pattern. Use this pattern in the way that makes sense for this particular thing. It's a lot more powerful than saying, well maybe this time we should do it this way and maybe next time we'll do it a little bit different way because that's how you get back to this sort of organic and consistent and ultimately private state because it's so unusable that people publicly aren't gonna use it even if they can access it. So that being said it was important for us to have an easy way to actually describe the APIs that we were working on, right? Like actually just trying to like write out an API from scratch is like everybody kind of does it a little bit differently, they leave things out. So we wanted to have something that was human-writeable but also machine-readable because we felt that having it be machine-readable would bias a lot of capabilities because if it's machine-readable we can write programs around it, we can automate things related to it. So there are a number of different formats in this space and I'd be happy to have a discussion with people about the different ones and pros and cons but I'm not gonna do it right now. We settled on JSON schema and JSON hyper schema which are both in the RFC world of things. There are RFCs that describe both of them. There are ways to basically have a JSON document that describes an API and JSON hyper schema basically adds links to what would otherwise just be a description of JSON blobs to let you describe the whole basically surface area of your API which this gives us a lot of traction because now when somebody's proposing a new endpoint they can actually write a schema and you can very concretely see exactly what they mean. It's not sort of like well, I thought it would be kind of like the app's resource except for this other part which would be kind of like the user's resource and it's like I have no idea what that means. Please just point to a schema that actually spells it out so that we know that we're on the same page and we're actually discussing the same thing. The one thing that I would say that is maybe different is that we actually use YAML to write the JSON schemas because at least most of the people on the team don't wanna actually have to hand write JSON for obvious reasons. So a little bit of an optimization there which I would recommend because it does make it a lot nicer to actually work with. So I'm gonna get one sip of water. I don't know if people have any idea what this is but I will explain in a second. So this is my sort of inside baseball for you today of why the thing that I'm about to describe is named what it is. This is a pyramid scheme. I don't know if you guys are familiar with pyramid schemes. There's a very famous one recently with Bernie Madoff, right? He got all these people to give him all this money. Supposedly that they were gonna get all of these returns and then he like disappeared basically. So we have this tool called pyramid that I basically named in effect because I wanted to sort of remind myself to remain somewhat skeptical and that the schema is very powerful but it's not the sort of be all and all. I don't think it will solve every problem ever but it is very helpful. Anyway, it's shortened so people usually don't realize what it actually is supposed to be because it's PRMD but it's supposed to be pyramid. So this is a command line tool that provides a lot of how we actually get work done with these schemas. So there are generators. So when you're creating a new resource from scratch, it turns out there's just a certain amount of boiler plate that you're gonna end up with pretty much every time especially with resources that have CRUD. Well, CRUD looks pretty similar on most resources. You don't need to specify a lot of unique stuff. So you have a generator that will spit out that file for you. We have verifiers that will take one of these files and check to see if it actually matches with our expectations or not until you when things are broken. If you look at the documentation for the Heroku API it actually all is just automatically generated from our schema which helps us hopefully at least keep things more in line. Like if we have a schema that we agree upon and we're pretty sure our implementation matches it then the docs ought to match everything else too because it all comes from the same place. We also have stubbing capabilities there. So you can actually basically spin up a server that will pretend to be your API that you can do client work against or just play with to like do curl commands and make sure that it's doing kind of what you think it ought to do. So anyway, super useful tool. If you're getting into the world of JSON schema I think there's still a lot of work we can do here to improve this tool but it's already been really helpful to us in terms of breaking things down and making it easier to actually work with these things. Basically like empowering people that don't want to use JSON schema to use it more easily because the learning curve can be a little bit steep on it. All right, so we were still in this sort of situation. All right, there's this sort of idea of like you know on this side we have basically a JSON schema or something on this side we have a fully formed API, right? Not super helpful for people that haven't done this before there's still a pretty big gap between these things, right? Like just having a schema that describes the API and actually implementing and operating an API are quite different things. So in order to kind of narrow that gap at least we have a couple additional tools. So the first one is called Pliny and in simplest terms I would say it's kind of like how Rails is this sort of big opinionated framework that makes it really easy to make front end like web pages, right? Pliny is intended to be sort of a somewhat smaller but still very opinionated framework for making APIs specifically. It doesn't really have any notion of views. It doesn't do things with templates or whatever. It's all just about doing APIs. And a lot of the patterns that are in here are basically extracted from our API code base that we haven't done like a grand rewrite to make it all beyond Pliny. It's still like a mix of all of this crazy old legacy stuff but there are certain patterns that as we worked on it we found to be incredibly helpful to make designing and implementing these APIs easier. And so when we're making new APIs within the company now which we do on a somewhat regular basis which I'll touch on in a minute we usually start with Pliny as our foundation and it makes it again it just lowers that learning curve. It empowers people to build and deploy their first API because there aren't all of these crazy things you have to figure out to start with. And one of the things that's like at the core of that that you can use independently and that we do use in our existing API is something called committee which is a rack middleware that can take these JSON schemas and do things with them. So there's a couple important things that committee can do that are very powerful. The first is you can use it for input validation. So inside of your schema you actually say when somebody creates one of these objects these parameters are required. This parameter needs to be in this particular format. So for instance like an email address, right? You can say this email address needs to match this regular expression or it's not an email address. And committee can actually take the incoming request compare it to the schema and return valid like validation errors directly. So it can say this is 422 unprocessable and see the thing that you pass that's supposed to be an email address clearly not an email address. And it lets you, it sort of alleviates needing to do all of that over again by rewriting basically the same thing that you put into the schema into your code base. Should you still have it in your code base somewhere? Probably because I don't know, trust but verify but it should actually handle it and in a lot of cases I think does a great job of it. On the output side it's also able to basically look at all of the responses and check the responses to make sure that they're also valid format but you wouldn't want to raise an error in that case because it would be bad for the user. So in that case we usually would look at grabbing that error and sending it up to like an error reporting surface. So like a roll bar or airplane or one of those kinds of things would get these errors that say, hey, you have this response that really doesn't match with the schema you have so you should probably either fix the response which is probably actually the wrong thing to do because you'd be breaking the API you'd be changing the behavior of it. You should probably actually fix the schema in that case and make sure that your docs have been regenerated then to match this actual schema and the actual reality of things. Okay, so umbrella. So the new thing that we've started doing a lot within the context of Heroku is something that we refer to as the umbrella. And the idea with this is that as we've continued to grow and the surface area of the API has continued to grow it has not seemed like a good idea to continue piling new endpoints onto the monolith. So more and more often as we add a new resource that's relatively independent from the existing resources we'll actually have a team inside of the company that is concerned with that particular thing spin up a brand new API service using Pliny and then we'll basically just attach it to the existing API via sort of like a proxy infrastructure. So that's the umbrella part where we have this umbrella that covers all of the things underneath and kind of hides away from people that it's actually a bunch of disparate parts. So we found that this has been really powerful and the Pliny stuff has been a big enabler for us to do that. So we are creating these sort of net new APIs but we're just making an effort to not make that be obvious to external users because you don't care, right? And if you had to use a different host name to get to every different endpoint in the API you would quickly pull all your hair out probably. So in terms of actually consuming APIs then we also commonly fall back to Xcon which is something that a long time ago I basically extracted out of Fog and this is a sort of low level HTTP library that in particular I optimized in a lot of ways to support usage as an API client because the use case of an API client is not quite the same as the use case of a general like net HTTP or whatever. You can certainly use this in that general way but this is kind of geared towards like using one connection for many requests, having persistent connections and also just like being crazy fast like as much as possible I tried to make it very fast and it tends to be quite a bit more performant than especially like net HTTP which is pretty slow for I could go on for longer than you wanna care to hear about why that is but anyway it's kind of slow. So we use this as one of the main ways that we communicate between these internal services. So the umbrella uses Xcon clients usually to talk to these backing services and get the responses for the end users. So I wanted to talk a little bit about some particular lessons that we've learned and hopefully to give you a bit of clear idea of some of my philosophy of this as well as like how we concretely have created some of these patterns because hopefully that will kind of drive home what we actually do with these tools and how some of these pieces fit together. So one of the first ones that we've kind of gone back and forth on this but I feel relatively confident. I have like a varying confidence level on all of these things. Like I don't know that I'm certain on anything which is disconcerting to say the least but it's this pretty common pattern you'll see of like these deeply nested things. I think this comes from Rails. I don't know what version of Rails or whatever it's this DHHism maybe but we had these like really deep nestings pretty commonly and it comes up a lot in the Heroku context because at least historically almost everything belonged to an app. So you'd have app slash whatever slash some other things slash whatever maybe slash some other things slash whatever to infinity, right? Because everything belongs to an app so let's just nest everything. Well, I find over time that I did not really like this at all and that really we ought to I think be minimizing the nesting wherever possible. So basically just avoid going to a depth greater than this, right? And so there's like some implications of this though which is that like that child now probably needs to have the parent foreign key serialized on it because before the parent foreign key was implied by the path that you were going to but now you have no reference to it and so you probably actually need to know which parent it refers to but this has stronger information sent which maybe also makes no sense to anyone that hasn't studied information foraging stuff but the idea being that if you are foraging and looking for food and you get no sense that there's any food in an area after a short amount of time you'll give up and you'll go and look somewhere else in the context of an API especially if you have competitors in the space you don't want somebody to come in and try to figure out how to use your API for a little while not find any sense in how to do that and just leave and go somewhere else to find the same thing. So by having everything be nested at the same level it makes it easier and more consistent for people to figure out because they're like oh well I wanna interact with this resource where do I interact with it at? Well in a nested world it's like well does this thing nest? Is it a child object or is it one of the Uber parent objects? Well you have to figure that out on each individual resource versus a world where everything's unnested and you can just assume that everything is always at the top level you don't need to think about it it's much more consistent that way. That being said I can still see maybe a case for having a nesting like this just for the case of asking for a list of children that is scoped more narrowly but there are other mechanisms by which you can do scoping so I'm not sure that doing it in the path even makes sense I think maybe just having a single level of nesting is sufficient just about every case so anyway that's one concrete example that I think is helpful another one that we find has been really helpful is sometimes within the context of a REST API there are things that don't concretely fit in the sort of like create read update delete world in a lot of cases there are basically things that I think you could map to like state machine transitions and so we needed a way to sometimes represent that a concrete example within the context of Heroku would be dinos where you sometimes wanna like restart a dyno or stop a dyno and it's not clear that you should just like set the state of the dyno to restarting like because then it actually causes other things to happen so we wanted to have a way to like more distinctly call that out so in a lot of cases in other APIs you'll sometimes see something like this and over time I found that I didn't like that because it was another place where there was some inconsistency because normally and granted if you're in a denested world this is less true but normally you see things that have this certain cadence of basically resource identifier resource identifier and this has two identifiers in a row which is certainly it does not seem consistent and it's not really clear what that final one is other than through perhaps maybe some convention you know that people would get used to it but I don't want people to have to get used to stuff I'd like it to be relatively obvious to them so we ended up actually implementing this basically where we kind of treat actions as a collection that actually belongs to the resource and within that we want to call the particular action and we found this to be really helpful and to be a nice pattern that we can reuse anytime we have these actions and make it clear exactly what this thing actually is it's basically a state machine transition it's one of these actions it's more complex so call it in this other way the other maybe less obvious application of this is I think in order to get it to work if you need to do it at the collection level which doesn't happen very often and actually in the cases where we've ended up doing it I've been dissatisfied that maybe it's a bad idea but I think you would probably end up nesting it this way again this allows you to have the same like consistent style of nesting in order to show that you're actually operating on the whole resources collection another one that's come up is the Singleton pattern like it's not that uncommon that people would have like slash account slash whatever as one of the URLs like one of the account things basically you're operating on the current user and we found that that was really not great because more and more often we have cases where admins either in an organization or within Heroku need to modify a particular user in some way and in order for this to work you have to use impersonation right you have to pretend to be this person in order to have account mean them even though you're you and then that makes auditing awkward so we've actually settled on using this instead where tilde means sort of the default value so users tilde is the current user and in other contexts I think tilde might mean other things although I don't think we've used it anywhere but the user context so far so some things that were good patterns I think as we shoot for IO parity so for the vast majority of cases the style of JSON blob that you pass in to create something and the style of JSON blob that you get back from that same resource should be very similar that's not always the case in a lot of APIs and I think that there's a lot to be gained from having that similarity that makes it easier to reason about we use UIDs throughout I think that also simplifies some things and makes it more consistent and hopefully more scalable but we also provide friendly IDs that you can use so like for app you can either address it by UID or its name and having both gives you a lot of flexibility we also use request IDs since we have this complex like service oriented architecture when a request is coming in you can provide a request ID or even if you don't we'll provide one for you and anytime we're making calls back through this network of backing services that request ID has passed along which actually provides us a way to trace its route through the entire system which can be very valuable so we still have some development woes though like I said there's still a steep ish learning curve I think some of these tools and stuff help there's also this sort of idea of this seductiveness of specialization a lot of people would love to see an API that did just the thing that they wanted even though it might not be useful to anyone else in the entire world but we're not really in a place where we can manage to make tons and tons of special APIs we need to make a more generic one in order to serve everyone hopefully the other thing that's super challenging is change management right so we do this via stability right now at least this is how we say that we're doing it we've never really changed anything in a breaking way so we haven't actually had to put this into practice but our plan anyway is that we have these stabilities that are at a per resource level if it's prototype stability we basically say we'll give you a week's notice if we're gonna make a breaking change in development we give you a month's notice and production we give you a year's notice I think something like this is maybe reasonable but we've already found some places where it's like this is kind of hard that it's at the per resource level that the whole endpoint basically has this same stability contract but I'm not sure what to do about this I think it might be that we just need to try to find easier ways to version because since versioning is hard we are reticent to make changes because we don't wanna have to support multiple versions at once versioning by the way, super hard one thing I would recommend if you're making a green field API is to not have a default version I think that's an anti-pattern one that we're stuck with because of legacy reasons but that's another surprising thing right because if the default's version two now and you release a version three and you'd like to make it the default suddenly you will break it for a ton of people that never even realize that they're sort of opting into that behavior I think it's a lot better to ask them to explicitly specify which version they'd like to be locked into there's also the complexity within the context of versioning of like if I have version three now and I wanna release version four do I have to rewrite every endpoint to be version four can I just say this endpoint is version four and this is the only endpoint that's available in version four or do I say this version four endpoint is different so you can access it and if you say that you want version four and access an existing other old endpoint it will fall back to version three's behavior it's probably also bad there's a lot of trade-offs there supporting multiple versions also just has a lot of operational overhead like operating in effect like multiple apps for your API instead of a single one I don't have a great answer here it's something that we're still trying to figure out so kind of bringing that all together so what is my conclusion from all of this I think my conclusion is basically that I still feel like I have no idea what I'm doing for the most part I mean there's some things that like I said varying levels of confidence but I think that honestly this is kind of where almost everyone that's doing this kind of stuff is and we don't necessarily have an open discussion about it because who wants to like go up and stage in front of a bunch of people and admit they have no idea what they're doing but I think that it's valuable for us to have these broader discussions and talk about these tools and these patterns and what's working and what's not working so that we can move the industry forward so I would really welcome you to consider being a part of this and coming and joining me and being lost we have a lot of great discussions on some of the different interagent projects of the things that are working the things that aren't working a lot of discussions about the feels and where I try to explain why I actually have some of these feelings or APIs I've interacted with in the past that I didn't like and why I didn't like them or whatever that might be and so I hope that some of that will be helpful you can certainly find the various projects on Energy Agent you can find me at Jemus and that is a link to this slide deck should you want to pull it up to find these links or that sort of thing so I think that's it I don't know that I have very much time for your questions I'll be around all day though so thank you


What Dell says about the latitude 1494 30 is that it offers a non-compromise CEO level laptop experience But you know that we're not that naive and we won't believe anything unless it's proven in our laboratory So let's go This laptop is on the top of the food chain in Dell's pyramid. So we expect no nonsense when it comes to everything on On the outside we find a sleek aluminum shell with a glossy finish on the sides and a matte finish on the lid It weighs just 1.27 kilograms and has a thickness of up to 13.91 millimeters Up top you can see the full HD webcam and the accompanying sensors which include an IR sensor and proximity sensors for quicker logins There's also an electronic privacy shutter activated with the F9 key And pressing the F9 key feels pretty good In fact the entire keyboard is a treat to type on thanks to the decent key travel and the tactile feedback It also features a backlight, but doesn't say anything about spill resistance Which is a minus when compared to Lenovo's notebooks It still sports a fingerprint reader inside the power button As for the touchpad you can't ask for more as the glass surface is super smooth while the responsiveness and accuracy are great Going to the ports most of them are on the left with an HDMI 2.0 port two Thunderbolt 4 ports a micro SD card reader and a 3.5 millimeters audio jack On the right there's a lonely USB type a 3.2 generation 1 port as well as a big vent for cooling With a premium business laptop you get some of the best available displays Here this means a 16 to 10 full HD IPS panel with excellent viewing angles and a peak brightness of 533 nits The contrast ratio is very high as well, which means deep blacks and great colors The 96 percent sRGB coverage contributes to that as well So you can certainly use the device for any type of color grading be it images or videos It's almost mandatory to get our design and gaming profile Which improves the accuracy of the color significantly from a Delta E value of 2.9 to 1.1 To put things into perspective anything below 2 is considered accurate with the human eye being unable to distinguish values below 1 We'll link our display profiles in the description below We almost forgot to mention the front firing speakers, which flanked the keyboard on the left and right They deliver pretty good audio with no significant deviations across the entire frequency range as well as a high maximum volume Which is the weakness of most laptops Only 2 per 100 people watching this video are subscribers if you decide to just start following us We'll be able to reinvest more in our laboratory thus making even more helpful videos for you. Thank you. You're awesome In terms of performance, you can choose between the core i5-1245U and the core i7-1265U 2 10 core chips with 12 threads and 12 megabytes of cache We tested the core i7, but all in all both chips are very similar The laptop does perform well even reaching the levels of the ThinkPad X1 Carbon G10 Which has a more powerful p-series CPU inside It's able to do this thanks to a beefy cooling setup, which has two heat pipes and one fan It might not sound like much, but it helps the core i7-1265U maintain 43 watts in the first 30 seconds of our test as well as 28 watts for more than 15 minutes Which is everything that you might want from a laptop like this one Also during the stress test the laptop didn't get uncomfortably loud or worn with a hot spot of only 38 degrees Celsius What we feel is even more important for a business machine is efficiency So you can effortlessly get through a whole day of meetings and emails The 59.6 watt hours unit inside the latitude 14 lasts for 15 hours and 29 minutes of web browsing Or 12 hours and 34 minutes of video playback Lastly, getting inside the laptop is relatively easy However, there's not much to do as the RAM is soldered with up to 32 gigabytes of LPDDR5 memory clocked at 5,200 MHz Storage-wise, there's one 30mm M.2 slot for generation for SSDs We'll have our teardown video down below, which gives you a detailed explanation of how to upgrade the laptop The Dell Latitude 149430 is a premium laptop with a premium price tag However, it does offer a lot to make it all worth it in the end The build is excellent The keyboard and display have no faults and the laptop runs cool and quiet even during the heaviest of stress tests All the while being very efficient We're probably forgetting something since the laptop has so many good qualities So why don't you swing by our website and check out the full in-death review with more benchmarks and tests? It's linked down below