Hi guys so here's another kit from my friends in China now this is a this is a kit I know it works because I've already built one and that's always nice to know isn't it, so we're going to get work and we've got ourselves a circuit diagram for anybody at home that might want to just sit and build the room and these are all the parts and everything's put in there so and here we go with this okay well you know to be easy it's gonna be easier I think just to just to look at the board but it's all pretty much yep it's all pretty much easy enough to see what goes where so we know we've got a tip 41 in there which probably does that's the IRF 530 tip 41 a couple of these heat sinks you've got some nice brass standoffs set it off the ground this is for our primary turns as that looks like it's probably all there I don't see why they won't be we've got two 10k's, two 2k's, tip 41, a couple of 3 mil LEDs swap them out with a different color but just remember that these reds take less voltage than others and we've got a 350 turn end up to coil there and JT that's just the connection isn't it and then we've got our M3 times 10 4's four of them we also have 105 which is in that's Puff because it's capacitor we've got a one micro farad two to three turns for our primary DC input M3 times six oh we've got six screws five screws one our six screws in because we've got two for these uh two for these heat sinks uh 25 by 23 to one of that is all right but to be honest with you there doesn't seem to be anything missing from the other one oh and there's this is where you get a little neon light a little neon okay so let's put it together now like with all these kits always go with the smallest pieces first so we know we've got two why don't we've got two 2k's and two 10k's so i'm gonna be going to see the difference but there's only four resistors and these are two of these are together so we just got to figure out what one of these is now i'm gonna say this one is a 10k let's have a look meter this will do it a little bit of resistance sorry there's loads of i do like these you can buy these pretty cheap on ebay you can buy very expensively on amazon uh you're in the uk but you can buy them very cheaply and anyway there we go so we've got our 10k there i'm gonna just just check these just make sure that they're so it's supposed to be 2k 2k right 2k okay 2k is okay right so let's do these two in first then and then they're gonna have r3 and r5 there's that 2k one bomb we've got r3 here 2k nice and easy well when you bend these uh well to be honest with you i'd never come across a problem of bending them i suppose you should always just be careful because you're going to damage the compound but i guess you're probably neither anyway and we've got to be up here r3 and r5 so r5 is there just makes it a lot easier for me anyway just to do like this put them on and then um just solve it up i'm not going to change anything and it's not a bad little circuit actually i mean this is just like a standard uh it does a circuit but you can use audio now i must admit when i tried using audio uh with my little my little samsung s3 here because it's got a uh got a headphone jack in it it just switches off the movie player the music player sorry you know just turns it off doesn't allow any output and my i've got a samsung s21 and of course they went the after taking the mickey out of apple they went the apple way anyway which was to get rid of the microphone here the headphone socket and uh which is a pity because i liked the headphone socket before and the samsung but there you go i suppose it's for our the best for our safety or something like uh so we've got this one last this one last 10k whatever is left there's only one hole left so it's gonna go in there uh if i can find it do you think you might fit me always not i can't see the wood for the trees yeah so it'll be interesting to see if this one actually plays i don't i mean i could try it with my computer but i don't really want to plug this into my computer we've got a capacitor there we've got that where's this coming through i suppose you know we are you know i don't know enough i've already killed one music player playing not with these circuits but playing around i made my own and uh if i'm not my own it was a copy of the circuit and you know i just could see it did actually work a little bit but then blew the part blew the little uh uvio u o o i or u aio player that's quite a bother go mind right so we've got leds now uh anode cathode to the shorter one or if you can see inside it the bit with the biggest metal plate or it looks like a metal plate but the bit with the biggest amount of material inside is the negative and the longer lead if you have it as a new one is the um is the anode so the anode is the bottom of the triangle the cathode is the the marking across it the line across the top of the triangle so now these i'd be careful with when you're doing these because sometimes these leds uh can be a little bit a little bit um delicate so i'd just be careful when you're doing that i mean i don't know the other ones i'd put it all the way down to the board near enough but these i leave a little bit of a space there because i'm just trying to keep it out of the way so again you know the longer lead down the bottom and the cathode lead the shorter one at the top there i'm gonna add a little capacitor what's this not very big at all is it i mean physically it's not very big at all which i see is made by reckons it's uh one micro farad 50 volts made by sw so on this one you can see on on here there's our c1 one micro farad and the positive side there is a got a little positive thing in there and all this side is white and that will go with the the lighter side of the capacitor so i'll just put that in and again the positive look it's got the longer lead shorter lead on the arm negative side okay and there we go a little yeah 105 yeah it's even five puff it's got to be a micro farad or something there all right so we can just quickly sort that up i mean i suppose we could if we wanted to we could what i do with these is i'm not gonna bother putting any paste on then the coupling to this should be that should be enough for what they'll be doing but if it does need to have paste for any reason it seems like it's not coupling enough let's say the uh the transistor itself or the MOSFET is getting way too hot and the case isn't the heat sink isn't then you know couple it up with some thermal coupling paste but just for this i'm not gonna i'm worried about it too much i just find it easier like this to put these on first because then when you come through the whole you know how high you know more low the leads need to be i'm pretty clustered on but get it done all right so this is our tip 41 tip 41c i know it's gonna face inwards just like on the diagram i'm just trying to shade the fins of the heat sink i'll just fit into those three holes as long as it's legs uh those leads are uh are good and then we're just gonna poke it through ready to solder up we'll just do the same with the next one same thing applies if we look down there we're like that then we just flip it flip it and then we're gonna solder it flip it and solder it right just need some power over there so yeah there's our uh standoffs and sit that on um we're gonna put these on even though you know yeah we're gonna put them on just put like now this one could be a bit tricky what we're gonna do is know which one's the top bit and which one's the bottom and i'm gonna say this bit's the top bit and the reason i'm gonna say that is because we want the long bit on the top yeah because as this like has that little bit of uh a breakout on it um it's gonna burn the metal then this will get wear away it will go wear away so if you have it this short of it there you're not gonna have that much but i suppose you can always keep pulling a bit out just keep taking take off a turn if you need to but i'd have to check the other so your orientation of it because we need to get that correctly around that's easy enough i mean whichever way we put it on if it doesn't work then we'll just rewind this the other way the way it is and solder it down again it should work and then once we've got it you know working um we can then tune this let's say or make it look neater depends how yeah how you like these things let me show you what i mean it's like i did this one like this and you know it maybe works a bit better different maybe an extra turn or uh maybe it does work better but as far as i'm concerned that looks okay and it works and so yeah well good did these some of these coils i must admit there's a couple of nicks on these coils i'm just a little bit worried but we're just a little bit like that and hopefully we don't have any damage well this one looks okay looks good looks good looks good all right the soldering on should be ready i stick this on because i just think it's good practice for me as i do quite a bit of soldering and that just sucks out for you yeah then the soldered and yeah because i don't really like breathing it in i mean smells really nice but you're not supposed to breathe in it um right what's that gonna mean right look i'm just screwing on that whoa go back a bit i can't see me getting any better angle or anything i'm sorry about that if you wanted that but right so it's gonna go basically i'm i'm just gonna solder whatever pins are exposed to me making sure that i spend as minimal time on it as possible because we're just gonna do a little bit of a quick snippy of the ones that i can see that i've done these can be quite uh oh i need to stop drinking don't i see my hands i can only get over where i want to um yeah these can be quite dangerous you know when you're clipping away with your clickers because you can just ping all over the place and you know you're lucky you might not stick you in the eye i've got a couple of cats and so i try not to get anything on the ground because like when they come in they're running around like lunatics i don't want them to like you know get anything stuck in their paws so i tend to just like put my finger over the end of it before i blink it and then blink it just means that i got it and it doesn't shoot up anywhere else and it's just easy enough for me to chuck into my uh chuck into my little bowl that i keep on here so the thing is with these sort of things you know when you're really doing anything like this just take your time take your time there's no big um no big rush to anything any more lightly it's not making a mistake like you know leave a pin or cut a pin before you've actually uh breathing those cats see with this better no it just looks a little bit better alright i'll do it all right so now i suppose the easiest thing i'm gonna do i'm gonna hot glue all i'm gonna do is i'm just gonna put some hot glue down in here and then just place the quill but before i do that i've got to decide i'm supposed this is gonna come down into it here and what i'm gonna need to do is because this is a mammal so you need to take off some of this enamel i'm probably gonna just use a sharp knife um oh you can see actually there is a little bit that's already been taken off by the looks of it so if i just there it is look yep i don't think you can see that can you see that it looks like a little bit it's been taken off again don't know there you go like might be able to just see it there that's okay you don't really need to do that then i've done it for you already i've done it for me done it for us very kind very thoughtful i've got no chance of doing this with my eyes i need somebody else's eyes help me so i'm gonna cheat on it i don't have to bring this down so is it interfere with the camera that doesn't mean i didn't realize that i thought it was like my other one but it kept making the camera have lines go through it she can be quite right i think what i'm gonna do is yeah that's where it's gonna go i'm gonna pull it all the way to this side and then pop it through like that but i'm gonna get the get the heat the hot glue on the go because we don't need some hot glue my guys here so we've got the hot glue in and what we want to do is we want to see this dribbling out the end uh before we're gonna use it otherwise it's just not hot enough i know that's uh sat out in there slightly that's because i i helped it out so that's just about it would be nice it just like just drizzles out slightly you know it's nice and warm that should be okay all right let's just get this in here yeah hopefully that should be okay not too much not too little bit on it just to build up on the inside a little tiny bit let's get this don't worry if you don't get it exactly around the the circle in the circle i don't suppose it's gonna matter too much let's go up this piece of wire now a little hole there you go beautiful not gonna be sticking out of there just gonna chuck a chuck a little solder on that so that's nicely put in there all right and this of course will be sticking up uh we need to take that off in an element it's not very straight is it never winds i mean i've only put minimal solder on it really because uh in some ways i like to keep these things you can think sometimes what you pay for these things go up and the heat seems to probably cost about a minute so we can just pull this off nice and gently really careful so don't damage anything pop that up in here that's where we're gonna get a little bit of crown rough uh now the next thing we want to do is our coil now now now let's just take a little poof and wonder at this one because that went round that way let's have a look so our coil this coil is well to be honest with you it's on sort of anti-clockwise uh let's look from the top on this one to be just not true yep they both are going around this way like if you're looking at them like this anti-clockwise which means then which means that we want to go the other way with our primary where this you always take pull this off a bit the only one that we're doing let's look at the one we're doing let's keep on this one um it goes around this way so the other one yeah we want to start it off here and bring it around the other way or finish it off in there just like I did with this one here so you put them in the opposite way yeah the opposite way so let's uh let's kind of release a wire set up for that the old uh they do you plan on your wire don't they and this is solid core as well so don't throw it because you might want to use this as like hook-up wire you know i'm going to go uh breadboards you know psychic boards pretty tight i don't know if you can actually say it's pretty tight on the board but anyway so yeah so we want to go um the bottom we're going to go into here and then we're going to go round and round like this and then that one is going to go into this side here all right now it looks a bit messy but it seems i pulled this off the end and do it let's see what i mean i'd say you get a bit of solid core wire here so i'm trying to twist it together there's only one in there let's just hold that through there just give a little bit of a little bit of salt on it nobody's still see that okay they're all in salt i don't tend to mess around with a wet sponge with my soldier i prefer the like the brass wall don't bother with that steel that steel wall that's like rubbish doing the sorting it just ends up breaking down and one of your turns neatly, if you can, the actual insulation on this should be enough for your distance between you. That is something you'll have to play with actually and I think I might, I think what I might do with this is just for the sake of it, put all this wire on and see what the difference is going to be by just having three turns and let's say whatever the max of this is, just for the output, both of them, on a standard supply, let's say, what they reckon would 24 volts, doesn't it? So let's not do that, we don't want to just burn out the top real quick. Oh look at that look. I mean look at the difference on how much you've got to have in there to go to there. With a bit of hot it's not keeping this in place. We got ourselves six turns I think, one, two, three, about six turns, yeah six and a half turns. That's pretty good, so all we're going to do now is get this off without just yanking the whole thing off. So I'm going to very carefully bend that off, bend that around and push that through. Yeah I could probably turn that down a bit later actually, can I? So it's a bit more just directly into that. I wish I'd left the hot snuck going on now. So I'm going to pinch a bit off, just got to be careful when you do this because if you cut too far into it now, what you'll end up doing, snipping it too short and then you won't be able to get those extra turns on. But we're just going to see what happens because there we go. I was mainly trying not to pull the coil off more so than anything else. So you know that can just stay like that for now, okay? We get to play around with that and see what the difference is. We've got the other one done there and we can see what the difference is on power output. It's more how that be fine. That will be fine, right. Okay, so now we can just pop in the standoffs. Let's see where we go with that. A little thing up, right. We need the soldering iron anymore. So we'll just stick a bit of clean off the tip, a nice bit of solder on the end just to keep it nicely tinned up. Just while it carry on sucking that away. I'll just push my, if I can get my hands around the bottom. Just push the screw in and do this up.  No, everything's going over. Let me just turn that off. That up. It makes a bit of extra noise in here but I'll tell you what, you know, I don't know, I'll keep the leg fumes down. When you're doing, you know, boards with quite a few components, it's really nice to be able to do that unless you've got a bit of fresh air thing going on but unfortunately people are quite noisy outside. That's why sometimes I like leaving it to later in the evening to do my videos but now I tend to talk a lot quieter just because it's later in the evening, I suppose. And it's generally pretty quiet here anyway. So I tend to have a, everything a bit quieter. Apart from in the morning, sometimes I want to go and listen on a Sunday morning to some music.  Some of those sort of bands from the old days, 60s and I love that sort of music because it's just really nice to listen to. It's got something to it, you know, some content, some hearts and soul. Okay, so we've got this little neon light and that doesn't actually go anywhere. I think this is just for us to hold and it will glow up a little bit when this is working. So let's give ourselves another bit of power. Now if I remember the centre of this is, what does that say? That goes from 15 volts to 24 volts, right? So we'll put it on 15 volts now. The centre of this is positive. And this one, this one, it's with a stripe on it. The positive, okay, a little power for here because it's already connected over there. It's just going into a cheap ebay supply. What we're looking for off the end of that is any, oh, there we've got a little bit of discharge. That's nice. Oh, and our little neon light lights. Look at that. That's what it looks like about these. I think this comes on and off when there's music going through it, but you can see where it's. I'm going to turn that volume up a little bit by volume on the voltage. So this is now on 15 volts. Okay, that's quite a bit and you can see the corona just a little tiny bit there. I'll take that to the side, maybe, behind there. And it says up to 24, so let's go to 20 volts. I'll be more powerful as I get in. Oh, that's quite good. Good intro, eh? Intro or so. So let's put on some of the 24 volts. And we're only using, right, now it's gone up to 300 milliamps. That's 24 exactly on there, which is probably not the rate as the 24. I want it to jump. So you can see there the corona, but you can just imagine as well, that's going to reach through that pretty quickly. But we get about an inch and a half there when it comes on. Now I'm just going to pack it up a little tiny bit just so it saves. I'll back it down to 14 volts. It does work with 14 volts. And you can still do the little, you know, this. Let's be honest with you, you don't really lose that much distance.  And you've got to go in that far. But anyway, I mean, it goes to show. I do wish I had another cable now. I know I've got one somewhere. Back out, pal. Intro was pretty good for me. There we go, that's enough for that. We know it works. Okay, well, we know that one works. Okay, so we can see that works. That's pretty good. A bit of audio out of it. I don't know why I put it up on this. I just saw it would be easier. Very hot. A little bit warm. A little bit warm. I can put up just a little shower to put a little bit more. What else can we do with this? Oh, we've got this. The good old plain and the fluorescent tubes, of course, that's always good for these things. A little party trick. I could also probably stick an LED on one of those coils and get a bit of transfer over one of these, because we're not really on that. I don't have to play around with that another time. I just wanted to show these little kits, at least some stuff. This is from eBay, these kits. I think I bought four of these, three and a half pound each. I'll put it up on the screen, actually, so you can see where I got them from. You wanted to get some yourselves.  Okay, so we'll ask that. That's the little test with that. That works. That works fine. It works through on the audio. I don't know why the other one wasn't doing what I expected to do, but I'll try to look over that and see what's going on there. But that certainly does work, so there we go. That's enough of that. I'll catch you in the next one.


Safety experts were busy answering all kinds of questions during the 12th annual Northern Minnesota Safety Conference today. Josh Peterson was there and found that new safety issues have come to the forefront. Creating safer and healthier workplaces was the objective for the day-long Northern Minnesota Safety Conference. This joint effort put together by the Minnesota Safety Council in Optivation provided valuable tools to local companies and businesses. It's a gathering of safety directors, HR directors, safety supervisors, folks who work in safety and their companies in the Bemidji area, along with a whole bunch of vendors to sit down and think a little bit, talk a little bit, learn a little bit about safety, try to refocus. Vendors such as Minnesota Base 3M shared how the safety products that they develop come from the needs of local businesses. They suggest something like we need a really robust anti-fog coating. We go back to the lab working with our engineers and chemists and scientists, develop those products based on feedback from our customers. The conference not only addressed basic workplace safety but trending issues such as alcohol and drug abuse as well as efforts to prevent violence in the workplace. People think that the only consequence to workplace violence is police or enforcement action is not. So it could mean better trained employees. It could be early recognition when people have problems. With issues of drug abuse and workplace violence becoming mainstream, speakers had the opportunity to talk about procedures and strategies that could be implemented in any sized workplace. Talk about the importance of how we need to come to work feeling well because my work affects my coworkers. People that are under the influence are 33% less productive. Through conferences like this, the hope is that employers learn to become more proactive and be prepared for any situation. In Bemidji, Josh Peterson, Lakeland News. The Minnesota Safety Council will host its largest safety and health conference at the Minneapolis Convention Center May 16th through the 18th. If you've enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland Public Television.


Dwi'n cerddad yn ogoith dwych, dwi'n ymlachio, dwi'r hydd y meddwl am yr hyffyddol. Trees are the root of all life. Dwi'n meddwl, tyfys i ddyn ni, yn nabod be oedd y coed yn ddyn mor hwyd. The tree I love is this copperbeach and it's been there for 150 years. It's so spectacular, it's such a beautiful shape and it's always full of birds and wildlife. It's a really special tree. Mae'r coed wycoedd yn arbennig i mi, chos mae'na ennaid mewn coedwych. Mae'na ennaid yn asyn cysylltu chi'n ôl i'r coed wycoedd celtau ddglaw yn yr ardal. Yr hen blannigion, yr hen ffordd y fyw, ym mynd i hel, a dyfnyddio blannigion o'r coedwych ar gyfer y carff neu iddyta. Dwi'n wrthymod, wrthymod. I don't think anyone would argue that it's the prettiest tree in the world, but it's so important to us. We'd miss it terribly if we didn't have any trees on our street. They have a huge role in boosting mental health, lowering our anxiety, and I reckon they got loads to teach us about just slowing down in our lives and feeling calmer. Dwi'n meddwl bod y rafod dwi'n forma mor bwysig i mi, oherwydd bod y rafod yn ymlu bro ac yn canu trwy'r coed. Tach hyn, cedda trwy'r coed yma cais gata am i liad. Mi glwch i'r rafod yn siwrwtwr canhina. The tree that's special for me represents the first tree of 70,000 trees that were planted over the next four years. It represents the 70th anniversary of Cwmbran as a new-tone, and it's part of the first wave in the fight against climate change. One word for trees I would use is joy. Bwnn vrygus. I think they make me feel excited. Important. Inmate.


Excellent, right. Thank you very much for coming back from lunch, nice and promptly. I do realise I'm tearing you away from food. My name is Daniel Jones, and I'm the CTO of Engineer Better, a UK Cloud Foundry consultancy. In the last few years, I've been working with Cloud Foundry for a variety of different organisations, and more recently, one of them was a global wealth management enterprise. Now, if you've worked with the financial services, you know there can be a little bit antsy about the information that is leaked about them, especially if that's not from one of their own members of staff. So, this talk is grounded in the experience of operating Cloud Foundry at a global wealth management enterprise. Unfortunately, I can't give you really specific details, because I'll be breaking NDAs and all sorts. So, we'll just have to be a little bit more abstract. When I'm talking about a global wealth management enterprise, what does that look like? Billions of dollars. There are billions of dollars at stake. If you include parent companies, then we're actually talking trillions of dollars, but again, I don't want to give too much information away. Because the stakes are so high, security is of paramount concern, right? So, there's going to be lots of policies in place to make sure that people's money is safe. Because the stakes are high, there will be multiple data centres. This is something that we're seeing more and more certainly in the UK, with financial organisations adopting Cloud Foundry, that they have their own physical TIN data centres, and they want to be operating Cloud Foundry in each of them. As well as having multiple data centres, they're going to have multiple Cloud Foundry instances in each data centre. So, in terms of architecture, we're talking about multiple data centres with a big enterprise load balancer at the top. I'm sure you can guess what kind of brand. And then Cloud Foundry instances in those with local traffic managers rooting traffic to them. Got a production Cloud Foundry in each data centre that is serving traffic to end users, so customers of the business. And then non-production Cloud Foundry instances as well, which from a PaaS operations team's point of view are still production, right? Because your app development teams are going to be pretty cross with you if your Cloud Foundry goes down whilst they're trying to develop their apps. As we go through this talk, I've got the privilege of being a Cloud Foundry ambassador at the summit.  Before I go any further, can you hear the squeaking through the microphone? Should I stop wondering about? Because this floor is really squeaky. No? OK, shout at me. Heck, I'll throw something if it gets too squeaky for your liking. So, we defined, you know, the kind of organisation we're talking about. We've briefly touched on the architecture. So, what is the advice that I would give you? If you're going to integrate Cloud Foundry into an organisation like this, or any organisation, really, it's really important to define success. What is it you're trying to achieve by adopting PaaS in this organisation? Are you trying to allow people to develop the apps they've always been developing and get them into production quicker? Are you just trying to reduce time to market? Have you got a load of monoliths on TIN that you're trying to migrate, turn into cloud-native microservices and deploy onto a PaaS? Or maybe you're doing something closer to innovation accounting, where you're trying to enable new types of application that didn't exist before, new types of things the company couldn't do before that are now possible. All of those things are going to require focus in different areas. And if you're not clear about what it is you're trying to achieve, then where do you focus your operations resources? This isn't just something for CIOs and CTOs who are spending their money on Cloud Foundry. This is relevant for the operations team as well. If you're doing a migration from monoliths on TIN to cloud-native microservices, friction is going to be your enemy. The app teams are not going to want to move from their comfortable world of change control requests and putting things on pet servers if there's friction in the way. However, if you're trying to enable new types of application, then functionality features are going to be much more important. You're going to want to have new data services, for example, maybe stick a Cassandra in there that they're not used to. Be clear about what it is you're trying to achieve, measure it, continually improve against it. If you're bringing Cloud Foundry into an existing organization with some heritage and some legacy, there's going to be an existing context, right? Before you came along with your hips to PaaS, they will have been getting along just fine with bureaucracy and rules that they've had in place for years. Those policies were created at a time when they didn't have a PaaS, right? So they're obviously not going to fit anymore. However, the people that you're talking to, the app development teams, for example, will still think that they apply. An example of this was an app development team that we were working with who insisted that they could not use Cloud Foundry, they could not use the PaaS offering in this organization because their developers weren't allowed to push stuff into production, right? So the whole cell service thing went out the window. For DevOps people, that's crazy, right? Because we want to go from ideation to production and looking after the whole thing all in the same team. But if you don't have all of the assumptions that go with DevOps and continuous delivery and CI and all those sorts of things, then actually you can understand why this might be a bit scary, the idea of having some cowboy coder sneaking a backdoor into a financial system and sticking it straight onto a production server. So we were talking to the app development team trying to get them to onboard onto the PaaS, insisted that, no, we can't do that. There's this policy over here. It's been etched into a stone tablet. We can't possibly change it. We went to the security and the compliance folks. We asked them about the regulations that informed that policy. Why do we have this policy in the first place? How can we change it? How can we work around it? How can we have a new policy? What if we insist that all of their code is under source control? Everything is delivered via CI. What if we have static analysis as part of that? What if we lock down all of their production spaces so that humans can't log into them but only automated systems can? What happens if we use a tool like IBM's Urban Deploy? I don't know if you've used Urban Deploy. It's got a big, horrible, enterprise-y GUI, but it serves some really useful purposes in the context of Cloud Foundry. It's got really granular user permissions, much more so than Cloud Foundry itself. Everything's audited, including all the binaries that it pushes. So not a temporary cache like you find inside Cloud Foundry, but actually archiving every binary push to every environment. And more importantly than all of those, it served as one place that we could do secret injection. So the PaaS operations team wrote some tooling to interplay properties that Urban Deploy, the tool, knew about into manifests, which it would then push into the production spaces. We took that to the security and compliance folks. They matched it against the regulations. They were like, yeah, this makes sense. We can do that. We went back to the app development team and said, yes, yes, you can use Cloud Foundry. That policy now doesn't apply to you. You're going to find these policies resist when people try and insist that they still apply, even though they don't. Reinterpret the regulations, come up with new policies appropriate for the time. The kind of policies that you will encounter are likely to involve some amount of manual approval, right? Why do enterprises like manual approval? Well, for lots of reasons, one of them being that they like to have someone to blame. They like someone to be responsible for making a decision. Also, you will find that in large enterprises, the IT organization and the app development organization could be completely separate legal entities, right? And it's the IT organization's responsibility to gatekeep, to make sure that things are done sensibly, that all the rules are applied and things like firewall rules are correct and match up to what they should do. Having those manual processes in the critical path of what your app teams are trying to do is going to prevent your PaaS from being self-service. If your PaaS is not self-service, then it is platform as a service, okay? There should be two Ss in PaaS. Make sure that you've got the right S and not the wrong one. An example of this was in an organization where they had this idea that they wanted a declaration of everything that should be configured for an app team to use Cloud Foundry, and this was actually quite a good idea, right? So all of the spaces they wanted, all of the users, all of the roles for those users, user-provided services, the IP addresses and ports of things they were connecting to, all in one place. That one place did happen to be an Excel spreadsheet, which wasn't ideal, but it was raised through a change control ticket to the PaaS operations team who, you know, tap away on the CFCLI and make it all happen. That meant that there was a stop in the process. It couldn't be self-service. People had to raise a change control request, wait for it to be implemented. That introduced friction. So when you're trying to convince people to start using your PaaS because it's a sensible thing to do, you're taking them out of their comfort zone, but you're not really making their life that much easier. Resist any temptation to have manual processes in the critical path of getting apps onto your PaaS. As well as manual processes for the critical path of users of your PaaS, so manual processes in the workflow of your customers, it's really important to not have manual processes in the critical workflow of the PaaS operations team itself. I mean, the keynote yesterday, it was talking about automation taking over the world. Really important, right? If you have loads of slow manual processes, sooner or later, someone is going to come along and disrupt your company and do everything much more efficiently and more productively than you. That's probably why you were using Cloud Foundry in the first place, right, to protect yourself against that. The problem with manual processes is that they take time.  You get stuck in a trap. You can't get back out of it again. The book in the background there, Scarcity, is how people get stuck in traps when they don't have enough of something. There are psychological effects that have been proven and demonstrated when you don't have enough of a resource and when you're aware that you don't have enough of a resource, be it money, be it time. You can only focus on the task right in front of you. Your ability to plan into the future, your executive control is inhibited. You are less able to do abstract problem-solving and dig your way out of that hole. Don't get yourself into this trap in the first place.  Everybody that I talked to when I was going back and creating this presentation and the different teams that I've worked with over the years really wanted me to make this point to you. Don't get yourselves into that trap. So why isn't there more automation end prizes? Why is it not the default state of things, everything automated already? Well, one reason is that bureaucracy is yesterday's automation. And I'm sure that in 50 years' time, people will be looking at all the automation that we've put in and complaining about it just as much as we do as rules and policies, right? That was the better alternative than chaos and anarchy. Another reason is that when people that practice continuous delivery talk about automation, we're actually talking about automation. In the Toyota production system, which inspired Lean and the Kanban Development Methodology, Taichi Ono talked about automation being automation with the human touch. And that human touch was common sense. It was error checking, right? It was making sure that a machine wouldn't rampantly do the wrong thing, that if pieces came out the wrong shape or size or whatever, that the system would shut down. Of course, as DevOps folks, we're not going to deploy something without smoke testing it. We're not going to deploy something without blue-greening it. When you're dealing with trying to bring automation into an enterprise, sooner or later you're hit upon that person who tells you the war story of, ah, well, we automated this thing a few years ago and it rampantly went out of control and it was a disaster and it spanned up VMs everywhere and we're never doing that again. They don't realize that we're thinking about automation and we probably don't realize that either. When you come up against hostility for automation, demonstrate your automation, show them the smoke tests, show them the safety checks that mean that it's not going to rampantly go out of control and do bad things. The other thing about manual processes is that they're soft, right? They're squishy. They're fuzzy around the edges. They don't have hard edges like an API. If I send a request to the cloud controller and I get it wrong, I'm going to get told very quickly that I did the wrong thing, right? I get an error message. I get some pain delivered to me.  That pain is information. That informs me that I need to do things differently. The information I'm receiving in this picture, by the way, was that I should do what the men on top of me were telling me to. You want to be like an API and pass on that pain to your users, right? Anecdote about this. Remember that spreadsheet I was telling you about with all the user provided services and the IP addresses and the ports and things like that? We had 46 user provided services for one app because it's a large enterprise. They've got lots of heritage off-pads databases. 46 user provided services with lots of different IPs and ports for each one of them. Day before a production release, they realized they've got connectivity problems and they want us to debug into it. We say, we'll send us your spreadsheet so we can look at the canonical list of all the things you want to connect to. I'm afraid we can't do that. What had been happening? We've seen sending change control requests in without the appropriate information and then phoning their friends in the Power's Operations team who was trying to do the right thing. He was trying to help out fellow workers. He knew that they were under pressure. He knew they were under deadlines. When the request comes in of, I know we haven't put the spreadsheet on, but can you just add this rule? I know we haven't put the spreadsheet on. Can you just take that rule out? Can you just change this port to that? Before long, it had diverged completely. It was to go through every cloud boundary on every data sensor down to the list of all the use-provided services, all the security groups, and all the firewall rules from the SDM and try and collate that list of them. Our answer? No. We're not going to do that. You're going to miss your production deadline because you've not done the right thing. Now, that sounds really harsh, right? It is harsh, but it's fair. If you absorb that slack, then information gets lost. The whole machine continues to be inefficient. If I was an API, if the PaaS operations team was an API, they would not be able to get away with that. If you're going to move your users towards automation, you need to train them that they can't get away with those sorts of things. You need to re-educate them and their behavior.  I know I didn't type that, but that's not what I meant. Train them to use automated systems. Pass on pain, be like an API. We can't be all stick and no carrot, right? That would be bad. If we carried on like that with every single request, then nobody is going to use our platform. We want to help people be successful. We're passing on that pain and educating them for the sake of making them more successful. So we need to understand their context more, right? This, when I read this, I nearly fell off my chair and then I wanted to print it out, frame it, and stick it up on the wall in my office. Unfortunately, if I did, I'd be breaking my NDA. So this came about where the PaaS operations team wrote a bit of tooling, which, if you're running Cloud Foundry, and especially a commercial distribution of it, is quite a good idea. It swept through all of the non-production spaces and turned off apps at the end of that unit's working day. If you're an enterprise, chances are you're running Java. If you're using Java, you're running Hello World in anything less than half a gigabyte of RAM. It's true, Spring Boot, the wonderful as it is, you can't get much done without much RAM. You will also have a load of apps called manifest.yaml that you probably don't need to be running, that will be using all the RAM on your Cloud Foundry. So this swept through and turned them off. Product owner emailed his engineers, saying, look, I realize that restarting our apps is scary, but it's part of the brave new world of Cloud Native. I had never thought that restarting apps could be scary. It just totally blew my mind. I didn't even think that this would be a concern of theirs. So why was it a concern of theirs? Enterprise IT is awesome at what it does, but it has a slow rate of change. So they develop an app, or at the end of a long-gant chart, put it on a pet TIN server that never changes, doesn't move, and it stays there for two years without being restarted. It just runs. Now, we're telling them to restart them all the time, so they're not used to it. That made me realize how much of a gap there can be between those... If you're involved in PaaS operations, hopefully you get things like DevOps and continuous delivery, but your customers probably don't, and we need to bridge that gulf. We need to make sure that we understand the context of where they're coming from. If Cloud Foundry is a new thing to your users, then it's going to get blamed for things, right? If there's a problem, it's going to be the new thing. It's not my code, it's that new thing you're making me use. I've run out of the lost count of times that I received phone calls or emails, something along the lines of, well, my application works perfectly fine on my machine, but when I push it to your Cloud Foundry, it doesn't work, so I think you've got a problem with your PaaS. At which point, right, you've got two choices. You can do the enterprise thing. You can throw away hundreds of thousands of years of human evolution where we evolve to be social beings that work well together and have emotional responses to each other's faces and things like that and send a passive-aggressive email. Well, I've looked at the other apps and I've looked at the monitoring. It all looks fine to me. It must be your problem, mate. Go back and fix it. Or you can do something else. You can find out where they sit and if they are in the same building as you, you can sneak up on them without them seeing you. Sit yourself down. Right, I hear you've got a problem with your app on Cloud Foundry. Let's work through it together. Plug in a keyboard and we'll work through this one together. You can turn people around from people that hostile, scared of your platform into advocates through pairing with them. You can educate them, show them all the tips and tricks of how you debug things, explain how the internals of the PaaS work. If you just send people passive-aggressive emails, they're not going to get all of those benefits. Whilst I'm talking about pairing, if in your PaaS operations team you are not pairing, you should be doing it now. Pairing is not just for programming, okay?  You want another brain to help contribute towards that problem. What's more important than all of that though is that you're debugging and the exposure of knowledge. When you send an email out that says that, oh, well, there was this problem and these were the symptoms and I did this to fix it, that's declarative semantic knowledge, right? That's like remembering facts for a multiple-choice quiz. I don't know about you. Most people don't remember that kind of information very well. When you're on a journey with someone, debugging, problem-solving constantly, then it's using your episodic memory. You remember journeys. You remember experiences much better than any point of fact. Pair with people in order to expose that learning. Make them remember things. So even if you start bridging that golf and establishing a lot of context with people, you will get people that break the rules. When I talk about breaking rules, I really do mean rules because there's likely a service contract between the operations team and the app development teams. One organization I was in, the service contract was Thou shalt write 12-factor apps. Thou shalt not put monoliths on Cloud Foundry. No, no, no. Unfortunately, one team insisted on writing their session states locally. So whenever users logged in, got written into this Cloud Foundry here, these didn't know about it. If we needed to upgrade this Cloud Foundry, then the users would be moved over here and logged out and lose work in progress. What could we do about that? Not a lot. We're a PaaS operations team. We don't have the levers to be able to go and chastise people. Hell, we'd even got them to sign up and said they wouldn't do it. Used the Simeon Army approach. We wrote some tooling that was run on a CI server that would talk to the global load balancer using its REST API and switch off traffic to production Cloud Foundries during production hours randomly. We told them that we were going to do this. We gave them lots of notice. We were very kind to them, but they knew now that it was going to happen. It wasn't a remote possibility in their heads. It was a forcing function. They knew for the better to make more resilient systems. If you've got people that are new to writing cloud-native apps and are struggling with the idea of designing for failure, check out a project called Chaos Galago. It's a service broker that will restart apps at a random interval. You give it a probability and a duration and it will randomly restart apps. That might help people on that journey. That keeps the app developers honest. What about the PaaS operations team? If you don't take anything else away from this talk, I want it to be this. Continuously acceptance test your platform every minute of every day. What do I mean by acceptance tests? In your favorite BDD framework, whether it's RSpec, GoMega, Lambda, Behave and Java, test that exercise the functionality of your platform from the user's point of view. Low-level infrastructure monitoring is great, knowing that a server has had a problem. If a server falls down in the middle of the woods and there's no user there to notice it, does anybody care? Well, probably, but not at 4 o'clock in the morning when they get paged out of bed. Don't get distracted by low-level monitoring and data metrics. Use acceptance tests to find out whether you've got a real problem. An example of an acceptance test that we were running, a CF push test. It would check out a fixture. It would push that app. It would hit that app. It would check the response. It would stop the app. It would remap the route for the app. It would hit it again. It would stop it again. It would delete it. We did that every two minutes on every cloud foundry and every data center, which also low-tested our platform to a certain extent. But we did the same thing for our data service as well. Rabbit, MQ, Redis, those sorts of things. That meant we had great confidence that the system was working. It was on a CI server, so we had a great wall board with red and green boxes. Published that to the app teams. Published it to your stakeholders. Everyone will know how well your platform is performing. That works well for the day-to-day running of your PaaS. What about when you need to do upgrades? I've talked about having multiple cloud foundries, which is a really great pattern for insulating yourself from failure. Despite all the cool things that Pivotal Ops Manager and Bosch can do, you can still irrecoverably balk a cloud foundry in the course of an upgrade. You need to be able to divert traffic to other cloud foundries if that happens. When you're doing upgrades, you need to check that your apps are still working. Why would I need to do that? You ask me, there's a perfect abstraction between PaaS and app. Unfortunately, it's not that simple, especially when it comes to build packs. Long story short, open SSL issues, lots of upgrades, upgraded our cloud foundry, picked up a new build pack, apps were using the new build pack, asked the app development team, can you test your app still works on this non-prod cloud foundry? Well, we don't have any automated tests. It's an enterprise. They plan things three months in advance on a Gantt chart. The offshore testing team is busy doing something else. So they didn't really give it a thorough test. We upgrade all the production cloud foundries. Next thing you know, somebody is debugging byte arrays in Hex for a week, finding a bug in Kerberos and the OpenJDK. Make sure that your apps have automated tests, that you've got to hook into their CIS system if they do, that you can trigger tests against your upgraded cloud foundry. If not, have a contract with them that they will expose an endpoint that you can hit that does a dummy transaction, something meaningful with all the behavior of their application. If you're going to have multiple cloud foundries, have a development cloud foundry. You should be writing some automation and some tooling, which is changing the state of your cloud foundry. Make sure you're not using the same one that your users are, like the app development teams. Some numpty once wrote a piece of code that was creating some users. That's safe. We're only creating users. And of course, you should have realistic test data, right? So people understand the purpose of your code. The only problem was that the realistic test data was admin user. Have we all recognized that? That looks realistic. And we need to tear down the data we create in the tests. Ah, yeah, don't do that. Have a development cloud foundry. If you're using Windows, apologies to any Microsoft folks in the room. If you're using Windows and you're trying to develop Ruby on cloud foundry, you're going to have a bad time. You will lose weeks to various issues with things like knock-a-girian compilation. If you can use Linux or OS X, that's what the rest of the ecosystem uses. You will be more productive because you can leverage more things that the community has made. If you are using Windows, or you find yourself in an enterprise that's using Windows, you can be pretty productive with MinGW, which is minimum GNU tools for Windows, which gives you bash and con emu, which is a bit like iTerm, but with completely different keyboard shortcuts. Use that in the past worked really well. I was going to tell you about a load of bash scripts that we wrote to make targeting multiple cloud foundries easier. And then we did some stuff to print out CF home to our bash prompts, and we always knew which one we were targeting. Instead, I'm going to tell you about CFplex, which we've written and is a simple shim that will allow you to manage multiple cloud foundries and run one command against all of them. Still works with all your favorite plugins. It optionally fails fast, so if you're deleting something maybe you can use it on others, it will cope with that. What's more exciting than that, though, is CF Converger, which I've been hacking on while I've been over in Santa Clara. This is a system that will take a YAML file, and it will make your cloud foundry look like you described in that YAML file. So, hands up quickly if you use Bosch. Cool, enough people. With Bosch, we know that snowflakes are bad. We say, make the world look like this Bosch, and it goes and does it. With a cloud foundry, though, we all think it's fine. You just fiddle with your state and change this and change that, and it will be fine. Someone will back it up. Converger will take a YAML file, create orgs, spaces, users, user provided services, and that can be run against multiple cloud foundries. So, if you have to make a cloud foundry look a certain way, or set up an app across multiple cloud foundries, this will help you. Another tool that is handy if you've used a software defined network made by some friends of mine. It's called Virgil. It will sweep through Bosch, look at where your Diego cells are, and will dump out a load of JSON describing firewall rules based on your security groups. And so, hopefully I've given you some useful links to tools. Talked about some lessons that I've learned, hopefully you can apply. Let's move away from the challenges and look at some of the successes. This is something that I tweeted about last year. OpenSSL issues had lots of upgrades to be done. This work involved a pair in the PaaS operations team occasionally leaning over, going to ops manager, next, and then carrying on with their work. So, it took a couple of days, but minutes of people's time rather than hours. The folks that were there were embedded in this enterprise estimated two years of scheduled weekend maintenance, every weekend for two years. This is several orders of magnitude better than the status quo, right? That is why you're all here. That is why we are here, because Cloud Foundry gives people that orders of magnitude better improvement in their productivity. I really wish I could share with you the story of this. This is from a product owner who emailed out to his engineering team, to the IT directors, the PaaS operations team. This product release took us weeks instead of months, because we're using PaaS instead of physical TIN servers. Again, that is why we're here, not because it's a bit better, because it's a lot better. Define success. Make sure you're clear on what your objectives are. Measure them and continuously improve against them. Reinterpret regulations rather than reapplying existing policies. If it's not self-service, then it's platform as a service. Demonstrate automation when you find hostility to automation. Do like an API. At the same time, build empathy through pairing. Understand their contacts. Educate them. Help them learn. Shake out rule breakers by using the chaos monkey approach. How testing contracts. So you can make sure you can upgrade your Cloud Foundries in a timely fashion. And most importantly of all, do continuous acceptance testing against your platforms all the time, so you have great confidence that they're working. I'm Daniel Jones from Engineer Better. If you have any UK Cloud Foundry requirements, please talk to me. If you want to ask any questions about Cloud Foundry generally, I'm an ambassador and I'm more than happy to help. Do we have time for questions? Yes, yes we do. It's about 10 minutes until the next people are in. So if there are any questions, please stroll up to the mic. Tumbleweed. OK, well thank you very much then.


Hey guys, it's Nate, A.K. The Foot Account, and welcome back to the channel. It is a start of a brand new week and another Monday on FIFA 22, which means a very popular SBC is expiring, but also hopefully refreshing today in FIFA 22. Now, the same SBC is the same SBC we've been talking about on Mondays for like the past month now, hoping that it would be unlimited, repeatable. And yes, it is the 85 times 10 that we are talking about, but in a different sense today, because we've been able to do this SBC for three times per day for the past week. Does making this SBC unlimited, repeatable, if they go ahead and do that today, is that enough hype to save FIFA 22? Because right now, right now in this preseason promo, it is a little bit bleak, I can't lie. There is stuff to do, but again, we talked about in yesterday's video. This is the problem right here. The squad that has impacts preseason batch number one with these cards still impacts, that's the problem right now. So I wanna talk about that a little bit today and even will the 85 times 10 actually be unlimited, repeatable because we've been hoping that it would be for like the past literally four weeks and it still has not been yet. So I'm gonna talk about that. Of course, all the other content, we finally had a Renato Sanchez SBC. Also today's a big day for summer swap tokens. The rewards are expiring. So make sure that you get those sent out of your club and interned in for something at the very least if you have any leftover tokens or if you have kind of paused your grind for whatever, make sure you do go ahead and remember that. So we're gonna take a look at all that more and look at market a little bit because that Renato Sanchez did move the market a decent amount.  Let's start off by talking about this 85 times 10 because like I said, does this SBC or like I posed the question, does this SBC released as unlimited repeatable? Does that make you want to grind the menus any more than you currently can? And for me, the answer to that question is no because I'm not even doing this three times a day. The way that it is because it's not even possible to craft this really 82 plus player picks are too expensive and not good value for how cheap SBC fodder is. We don't have a 75 times five upgrade to go out and get those done. And to get gold rares and maybe 83s, 84s, 85s that you would use to turn into the 85 times 10 with other higher rates that you may have. There's a common gold upgrade, but it just kind of feels like it's not worth it. And I think that's where a lot of people are in this stage of the game. The 85 times 10 is even losing its height because again, like I mentioned, it's the cards that are in packs right now. Pre-season batch one, only a hundred players. The special drop rate in these, I've seen people get nine golds, eight golds in 85 times 10, and it's not that uncommon. So that's, you know, Mondays we've been getting excited for the 85 times 10 and now we're just at a point where it's like EA, you messed up. If this SBC was really gonna be at its peak hype, unlimited repeatable, that was two weeks ago during footies. The last batch of footies with 200 cards in packs, that's when this SBC needed to be unlimited repeatable. I feel like EA have missed the boat and they've kind of just, you know, they've lost the plot almost with the 85 times 10. So I do think that it's gonna get re-released today. Hopefully it's the exact same requirements because let's be honest, this is still technically a good value SBC. 87 squad team is these and requirements have not changed since it's been released. And if it is unlimited repeatable today, there will be some people that will be happy for it because if you're still going after Renato, Rutiger, any of these footies SBCs that are still here, if you're trying to crap them last minute before they go away, well I guess Mendy's the only one that's going away very soon, you know, it is another option for you and it is possible to craft these and to get good value cards SBC fodder wise from this. But it's again, like I said, the hype I feel like has just worn out because we didn't get this like two weeks ago when we really needed it, okay? That's just again, that's the thought process. So again, like I mentioned, it's just kind of hard to craft and the hype is going away anyway. So that's the problem with that SBC for me today. Now let's talk a little bit more about Monday content because that's a big piece of content. Again, not super crazy hype, but we do have one more transfer SBC that we have not seen yet and we have a leaked Diego Carlos Villa card that is not out in the game just as of yet and as we currently look at the leaks, wow, I can't even type this guy's name, Diego Carlos. You guys know who he is. I'm not gonna find him on the market. He doesn't have any special cards, at least recent ones. That would be a really nice center back card that could drop today. I mean, we just had the Rudiger SBC, of course, which a lot of people went out and did, but a Diego Carlos could arrival him as a Brazilian center back with Premier League links instead of La Liga. And I know the Real Madrid links are very, very nice and very, very popular, but a Diego Carlos with the Prem Brazil links could be very popular as well today. All depends on the price. All depends on the stats. I don't exactly know if that's getting dropped today. I should rephrase that. It could be later on this week inside of the middle of the week and instead of last week where we didn't have anything in the middle of the week, maybe this week they'll give us an SBC or two, player-wise. We've already had Rudiger, we had Renato Sanchez yesterday. We'll talk about that in a second. And the transfer SBCs keep rolling, but that's the only one that we have leaked right now is Diego Carlos. So we will see if that's today or later on. But for the rest of the Monday content, I mean, I'm not expecting more swap tokens today. Obviously, in fact, the objectives are going away for the summer swaps one, two, or was it three and four that we have left. These are both expiring today because like I mentioned, inside of the SBC section, if you go to the swaps tab, this is the last few hours that you have to turn in your swap token. So maybe if you have a couple laying around in the club that you didn't know that you had or maybe you're finishing up some objectives to get your bannietter, to get a player pick, to get your fodder packs, whatever it may be, make sure that you don't leave any of these sitting around in the club because after today, these tokens will have literally zero use. So whatever you're grinding for, make sure you kind of complete that grind and get that done if possible and then turn those tokens in for something if you have any left because those are going away today. Now let's talk about a Renato Sanchez SBC it was dropped yesterday. Again, this was the SBC we were waiting for for so long. And I think it's a little bit of a bummer. I'm gonna be honest, five star skills, four star weak foot, it is a very nice boost. And I think EA also priced this card at the upgrade that they gave him, 150,000 coins to get this Renato Sanchez done, which is gonna be such an easy price point to craft. And you could say with the 85 times 10 being unlimited repeatable, another reason why it doesn't even need to be unlimited repeatable, you can literally do like two 85 times 10s and basically get this guy done by going and buying the rest of the fodder that you need, it's two squads. So that means you're easy getting it done with an 85 times 10. So they did introduce some very unique requirements with this SBC that I do wanna talk about here in a second. But the upgrade of this card is nice. I think we would have really loved 90 defense and we really would have loved the five star, five star. But again, 150K, they're making it this cheap. The upgrade's not as great. We finally got the Renato though. A lot of people are going out and doing it. 1,900 up votes to 347 down votes. So very popular card, very meta in game, very OP. And a lot of people are doing this SBC. I'm probably gonna get it done myself. Now, here's what I wanna point out. In these SBCs, it's an 87 rated squad, but they make you turn in a certain number of players that are a certain rating or above. You see this here in both of the segments, 89 or higher overall players, minimum two, 90 or higher overall players, minimum one for an 88 rated squad. So they're making you put in a certain number of players that are above that threshold rating, which technically in my opinion does nothing because if you think about an 88 rated squad, how are you gonna get an 88? Unless you do like 296 or 95 rated cards with the rest being 86s or something like that. I mean, if you're doing an 88 rated squad, you're probably gonna end up having three cards that are 89 or above, and one of those being 90 or above doing the SBC anyway at this stage of the game. So I feel like this doesn't mean much for now, but it could mean something later down the road. Maybe in FIFA 23, they'll put out some specific SBC requirements that we will have to use specific player ratings. That would be very interesting. So this was like the first time I think that I've ever seen something like this in FIFA. We'll see if it translate forward into FIFA 23, or if we see this again in the near future in FIFA 22. Now, speaking of fodder and SBCs, of course, let's take a look at that SBC fodder because I have a couple things to speak about and get a couple of ideas, I guess you could say, about fodder as the hype is maybe detracting a little bit from this promo. Yes, we do have some great SBCs that are still being released that a lot of people are going and doing. You still had some fluctuation on fodder cards yesterday. Thomas Lamar went from down to under 2,000 coins back up to 2.8, 2.9K for a 83-rated card. 84s are below 3,000 coins. This is crazy. I mean, I do think that some of these cards are probably a little bit too low and they're probably gonna have their daily spikes, especially with an 85 times 10, potentially being repeatable today. But again, I feel like with the hype falling away from this game, that's gonna make the SBC fodder bounces maybe a little bit less and a little bit less often and basically a little bit less profit. That's kind of what it boils down to with fodder in my opinion. Although you're still seeing these cards move up and down at price because again, like I said, there are still SBCs that people are going out and doing. So if you're still trying to trade, make some coins or just be market conscious, buying these cards before content is 100% a play. I would watch these cards today on Monday. Again, you have some weekly rewards being paid out today. That could be some supply for a few of these cards. Again, it's the same story that we've been talking about for literally like in the last month, right? You buy fodder in the nighttime or the early morning and it goes up after content for an hour. You sell it or you do an SBC for cheaper right away. Then you buy it again the next day. Same situation every single day. Again, like I said, the 85 times 10 unlimited, it's only 47K to do an 8510 right now, which is crazy, crazy how cheap that is, which does make it even a little bit better of good value, but also your fodder in general is just down so much that it's also making sense to why that SBC has gotten a lot cheaper and the value levels are maybe a little bit less there since it's really cheap to do. And you have 90 rated cards or excuse me, you have 94 rated cards that are 13K crazy, right? Crazy with the value of fodder at this stage. So that's kind of what's going on with SBC fodder at the moment. Again, you can do your daily stock on the low tier. I think it will go up today with the release of whatever content that we do get. Now yesterday we also had the 93 plus moments player pick. No nation specific one though, like we were maybe expecting. We had the Brazil, Dutch and France one from last week that was not re-released unfortunately. So yesterday it was just the 93 plus and the Renato Sanchez SBC. Now also with this Renato, just to point out for a bit, some of those PSG cards, especially your rare PSG cards, like this messy team of the year. I mean, these, wow, he just literally sold for 820,000 coins and now there's a 790. Like this guy's price, and I'm gonna show you his footprint graph because it's even crazier to see the footprint graph for some of these PSG guys. But these price fluctuations were mad on some of the PSG cards, just with how much hype the Renato has for sure. I might even buy this messy. I'm not even lying. I might buy this. 730 is what he was a bit ago. Look at this man, 700K. He went all the way, he was at 900K. Like this guy was up over 100,000 coins. We have sales 850, 835, 850, 857, some high 800 sales for a lot of the time there yesterday. So if I can get this one on bid here like 730, then I might go for it. But some of your messy cards, the messy shape shift, there's over 2 million coins now. After he was like 1,7 I think? Yeah, maybe not quite 1,7, but let's see, Saturday he was 1,88. He just kind of kept rising. The longer that Renato was delayed, he just kept rising because people knew that, again the hype was going down and that makes the card more rare and messy, he's not in packs. And that just meant that Renato was coming sooner or later. So there were a couple of cards that went down, like the 96 rated Sergio Ramos card. That was a card that went down of course, because you had another midfielder released. So we went from 180 down to 120. He did go back up though to about 160, 170,000 coins where he is right now on the market. But that's honestly just because he's got PSG links, man. And he's a pretty rare card. I don't even believe he might not be in packs right now. I'm kind of losing track on who's in packs. Actually you know what? He might be in packs with this batch one of pre-season, but I'm kind of losing track of what cards are in packs because that's just where we're at with this pre-season promo. Again, the hype is just dwindling down. Now for me again this week, what I'm grinding right now is I gotta get that 50K pack secured. 50K pack has to be secured from the Kickstart objective. Pre-season cup, nice W, nothing super insane there. Get some extra packs and some shapes of the player picks and the warm-up objective as well. Might as well get these done because they're super-duper easy to do. But it's for this Kickstart pack here that is such a key grind. I'm gonna say it like every single video this week, that's what you gotta be doing right now in FIFA 22 to get yourself set up for FIFA 23 Ultimate Team. So start of a brand new week today on Monday. Again, not a whole lot going on. We'll see if the 85x10 gets re-released repeatable. Again, it's just, it's kind of the story of a little bit too, not enough and it's too late. That's the problem. So I honestly just can't wait until these cards go out of packs, give us something new EA Sports, get 200 cards back in packs, that'll revive a little bit of hype left for the end game of FIFA 22 in my opinion. So comment down below what you guys are feeling right now with this game, what you're grinding, how you feel about Renato and everything related to that. But if you did enjoy today's video, smash the thumbs up on it and subscribe if you are new. It's been Nate, The Photo Count, and I'll catch you guys later. Peace.


Studying Remy and Juliet by William Shakespeare. Let's do some word-level analysis beginning with the prologue. Now the prologue at the beginning is important because it basically foreshadows what will happen to Remy and Juliet in the play. This is zero here. It's really important in setting the scene for us. The assonance of eye emphasises similarity between the Montes and the Capulet. The noun Verona tells us that this takes place in Italy. The words grudge, mutiny and blood belong to the semantic field of violence telling us that it was violence that will cause them to lose their life. Also the literation of F here shows that this play will be a tragedy, something bad will happen. The reference to star-crossed lovers lest your imagery showing that Remy and Juliet were destined to be together. The oxymoron life and death shows that from something really bad good things will happen. They will bury the anger. The contrast between death and love shows how ill-fated the love was. The alliteration of T in two in traffic creates an excitement within us as the audience as we now realise this play is about to begin. The whole chorus is written in iron bit pentameter which means 10 syllables, one stress and one in stress five times.