Today there is a guy called creationist on footer and he wrote the basic library that not uses for the movie now. He wrote the same thing using you all today and twice as fast. It's not the JS part that is the great thing about it. It's the whole async wave programming that is the strength. So what do you mean by async? In any programming language, in any program where you write, you are going to have a pandas sequence and the execution is going to happen sequence. So you will be able to have a statement and once that statement gets completed, the execution goes to the second statement and goes on. Right from assembly language to any language in any high-level language, whatever you are going to write, it's all going to follow the same current term. But there are other event-based systems apart from Node.js. For example, I think if you take Python, I think we have this. For Ruby, there is another framework which does that and for C, there is this event clip, which basically is not used to give you an event-based model. So the major difference between an event-based model and the normal programming parameter is that. So in normal, you have lines, say, print or something. So everything can sequence. So first you print it and then you are going to get an input from the user. So assuming that it's a command line, maybe it's like waiting for the user to write something on the console. So what happens now is, like, this multiple statement, when the control reaches here, it's going to wait. It's going to wait for any high-level operations to be going to happen. User input is one high-level. So there could be other high-levels, like maybe you could probably query the data, or probably you want to read from a file. There could be so many ways by which you can do input and output. And for all these, that particular statement is going to wait. And the statement after that is not going to get executed. So that's the traditional programming parameter, which is almost like most of the languages problem. So here what will happen is, if you are going to do any operation, especially an input or output operation, what it's going to do is it's not going to wait for the execution to stop to come back to the next step. So what you're going to have here is something called a callback. So if, for example, we're going to have the same thing here, so it's going to be something like, say, we're going to have a callback here, which is not for anything. And then you're going to continue. So what's going to happen is, let's assume that this particular function is going to take input from the user. So what happens is, as soon as the control comes to the statement, it sets up the even, and then it's those sets of the callback function, and then the control immediately goes to the other statement, and then it starts exhibiting here. And so here we are waiting for the user input, or whatever, or whatever it's going to do, or what the operation is going to do, maybe we're going to wait for a file, or we're waiting for a database to return back and all that. So once that happens, this even gets triggered, and this callback gets called. So here it's giving an anonymous function to it. To be an anonymous function, now it would probably be a function under the word. So that gets invoked, and this is putting the code getting executed. So if you look at the and there's a thing that if there are a lot of other statements here, this also gets executed. This gets executed here as the control code. But here what happens? We don't have this statement, nothing is executed to this statement. So this is the basic algorithm changed in Node.js. And now we'll come to the second part, Node.js part, the JavaScript. So most of you I assume would have done some kind of JavaScript. What happens in JavaScript? Any event, by itself we use the event model. You have an event listener, which has a program. So the JavaScript language itself has capabilities for doing event based operations. So that was one of the reasons why this entire node or the entire sync concept was implemented in JavaScript. I guess I read it sometimes, I'm not sure how authentic this information is. When the person who was behind Node, Node.js, when he actually wanted to do something like this, he started off with the event loop in C. And at the end of the particular point, he felt that it's very difficult to have callbacks in the sync. And I think later he considered Root and then there were some issues with that. Then after that he saw JavaScript and JavaScript since by the language implementation of the language feature itself had supported all this callbacks and all that. So it became a perfect match. So the author, Ryan Dal, he tried doing this a couple of years back also, but it wasn't working out because JavaScript was fine, but it didn't have a good implementation. Then Chrome came up and the V8 engine came up and JavaScript became insanely fast. And that's why he ported this. Otherwise this wouldn't have happened. They wouldn't have been in Node.js, it would have been Node.lu or something. It happened because of V8. That's the other part, right? So this is the concept and this is the sync part, this is the JavaScript part and then how we are currently it's implemented. So the implementation was your Chrome when it became a source project, they had this JavaScript engine called V8. So in a root sense you can compare it to a compiler which can take any JavaScript program, compile it and then run it. Compiler press probably an interpreter. Compiler may not be the correct one. Just in time compilation. I'm just like saying I'm not talking about V8 but I was trying to give an analogy of JavaScript, V8 and maybe C and GC. It's quite similar to how people work in Java world. So it's more like an interpreter plus compiler that you can think of. So what happens is it basically when you give a JavaScript program to it, it compiles it or it's not compiling it, it interprets it and it's going to run it, right? And V8 is exceptionally agile and because of that and one more important feature of V8 is that it's very clever. So instead of Chrome code base if you look, the V8 engine is like, you know, is separate from the other Chrome code, the other Chrome code part, just to display the windows and stuff like that. So what it was, it took the V8 code base and then wrapped it out around the event lib library of C. So essentially what happens is you write your code in JavaScript which gets run by this V8 engine, right? Not on the browser context as a separate process. So that's how your node code is going to run. Node, the JavaScript part and the implementation. First of all, like how string works. Like here the callback function may take some time, right? It's like if the file upload function under something like that if it resorts under. So that will be pushed to callback function so that will take care of that. So finally at the end of that we need to communicate again to browsers. So you are talking about a web server or any server when you upload the file from a website. So it will go to node there and then it will process it and the callback function will return a message to the browser. So how do you treat that? So I understood your question. The thing is node here is not just a web server. So that's what I'm trying to check. My question is like how stringing works. So stringing it has to return the client idea or something. Like two websites, so two websites. So from one page I am uploading the file. So that has to return which browser has the product. So let me come to that. Before that Node.js is not just a web server. So you can write a web server on Node.js. So if you typically take any web programming combination like you have in a patchy server, you have a PHP scripting language or probably you have a Python with some framework and all that. So Node.js is going to actually have the entire stack. So even the web server is going to be on top of Node.js. So you are actually writing a web server, not just the application program on top of it. So to come to your point. So what happens is when you are implementing a web server every time there is a request count, that itself would be a call count. That itself would be a separate process. So what happens is let's take the same example. So this is so getting good. This is like when a client request comes. So there is a caller which gets assigned to it. And then the web server is free to accept calls again. It goes out of it. And the control is inside. This gets executed. This is done. It gives a response back to the client. So the main advantage here is that you can... So the actual thread of the actual process is that I mean the client request, right? Instead of doing a point one, it can still process other client. So there would be team happening finally. Every client would probably get a call. That's a major advantage of when you implement a server. So ideally there are a lot of implementation for web servers. Even XMPT servers. So is your question that how do you retain... When a call back comes, how do you retain the previous information on how to relate it back, right? That's what the question is. Do you understand... Yeah, so do you have a program in Python? So you understand Jojo's? What happens is when a request comes before you actually send the request for processing you can extract out a client ID from session or whatever and that variable will be available when the call back is called. So you can just say, okay, this ID is available because it's bound in a closure. You can say, okay, this ID is handed back this information. So the information gets bound in a closure. That's the whole point. So even here, right? This callback will have access to the... So there's going to be a closure in one. So here's the question. We're assuming that this callback gets called in the same request, right? If you're calling it back in another request then obviously you're not getting any context when the callback happens. No, the context is in the callback. That's all you said, right? No, I understand that. We're assuming that the callback, the event was fired within the same history we request because if it came in a different history request then the whole stack has been cleared by then. Basically you can have something in the static map somewhere that's saying this client ID, this is the output. By default, it's to keep it down. When the processing is done, put it in the output back in there. When he refreshes the page or something, you can get the same client ID session. You can send him back in there. You can use session... There's another way. You can map the client's session ID, something with... There's something called... Someone sent events now using web sockets and all. So you can actually send... Even to the client saying that the work is done, you can pick that up now. So you don't actually have to wait for the next refresh. You can actually map a web socket to a client ID. Okay, that's pretty cool. Yeah, that happens if you're going to do web sockets. But if you're just thinking about traditional web servers and all. In a traditional web server, apart from sessions, if there are going to be multiple requests from the same client over a period of time, all of those requests are technically not related. They are required because of the response. That's it, too. Actually, having some kind of an ID, if you don't know a session, you have some ID in the URL. How does it happen in a traditional web server where it's either a response of multiple processes or multi-processing? No. Have you used Apache? Yeah. Have you used any of those? Yeah. You must actually know graphs, right? Apache, increasing, engineering, response, etc. So what happens is when you use Apache, every request spawns a new process. It depends on the idea you're using. The whole idea is spawn something. And it asks for some allocations for memory and all of it. When you're using engineering, there's a huge fat pipe somewhere, maintained by the OS. When a request comes, you just say, okay, look, this is a request, this is a response. Just take the two handles, keep it together, and delegate the work to somebody else. When the work is done, that comes up, picks up the request and the response, done with all the manipulations, writes the response and it's done with it. So the whole part of the main process is just take the request and the response, and put it in the fat pipe. That's exactly what happens in Node.js also. When the request and response, you get them and you call, you say, fire the callback and then you're done. Essentially, doing the same thing.  It says, okay, now I have the request and response like a manipulator. It's not like Apache where you have to spawn and date till the whole process is done and then you kill the thread and spawn a new thread. That doesn't happen there. So there's no cost of spawning processes, more threads, additional VMs, nothing. That's why it's fast. That's the basic programming kind of shift. So it's not the first async framework out there. I mean, Nginx has been waiting for quite some time for the same reasons. The whole benefit that it brought to this, since you code in JS and a lot of people already code for the browser, it can also code for the server right now. That's the best thing. You have one language across the platform. That's one of the best benefits of this thing. Actually, Nginx and this thing are different. Because Nginx, you're basically spawning things. Here what you have is a single thread. No, Nginx, you define how many workers you have and then each worker, so the main process takes a request and response, puts it in the pack file and the workers process and then operate on the request and response. But it doesn't spawn any additional workers. You can specify initially how many workers you have. For example, you can put Nginx in front of it. So, I mean, it's the back end that's just a curve over there. The blocking part is not happening. Exactly. So that doesn't happen in Nginx also. Let's say you're serving a static file. It has to read the file from the file system. That's not blocking. What happens is it uses the libEvent itself and when the request comes, it puts it in the hard file and says, hey OS, take up this file reading part. Whenever you're done with the file reading, give me back the file response and tell me about what the request and response objects are. And there's a callback that says, okay, just respond this request and this is the file system file that I've got. Just write it back. So Nginx works quite similar. The only difference is Nginx is completely written in C. So you can't really do a lot with it. You can't hack around with it much. This on the other hand is very much easier to hack around with. You can start writing TCP servers and you get big applications. The scale of doing things is quite wild in Node.js. That's the whole point. Also, just to clarify, Node.js as such is not a server. Node.js as such is not a server. It's just a runtime. So right now what he's saying is he's comparing Nginx with a web server written in Node.js. Or a web server written in Node.js using the event that I own. So Node.js is, what is it? It's a runtime environment built on VAs. So VAs is a VM and Node.js is just an extra APIs. IO APIs are not good. VAs is pure JS. VAs is just like a GDM and Node.js would probably be... J2E kind of extra APIs. Probably called a framework. No, it's a runtime. Just like J2E has extra APIs. Confusion about Node.js, especially when people talk about the advantages because people generally compare it with other servers so they probably start thinking that it's a web server. But as such, Node.js is not a web server. You can write. Node.js is like a platform where you can write web servers. You do that because benefit of using Node.js is only when you're doing IO. That's the biggest thing. If you're not doing IO-based application, it's just another platform. It's just another tool. Nothing beneficial about it. The whole benefit is on asking IO. If your application doesn't require IO, it's just another tool. You better write it or anything else. You're familiar with it. So one of the biggest disadvantages is you cannot have concurrency. The whole thing runs in one single process. You cannot sponsor it. There's work going on. You cannot have multi-threaded applications. So for high-scaled websites, people have this very vague definition of what high-scalability is. You don't need to sponsor threads to be scalable. Even model-scales amazingly. You don't need threads at all. Threads make sense when you want to do parallel computing. Then it makes sense. So you don't write really computing. What does Facebook act more like a threat? Actually, the OS spawns the threads. OS is responsible for managing all this. For your application, there is no thread. Everything runs. So there's a saying, as Ryan said, in Node.js, everything runs in a separate thread except your code. Everything is multi-threaded except your code. Your code is one single thread. So when you do a parallel... There's some processing in Node.js. In that case, I had four different... I tried to call the call function, possibly four different take-time-consuming jobs. In that case, how the whole thing works? So let's say you are hitting IHDT API. That's actually the call. Let's say I'm processing an image in Node.js. So you should spawn a new process and do it there. That's the thing. You should never write blocking code otherwise you're defeating your purpose or something like that. No, but if I make a sync call, say yes, call back. Then again, you have to write an application that takes a sync call. You can either read the binary data and run loops over it and process it and all, but then it will be blocking. Or you can create a separate process or you can use a module that creates separate process for you and let it... But you can't do some kind of call back which is... So what if I say this is a function and this is a call back, which returns the process image. In that case, I'm giving an image path. This function takes something and then processes it. That's the implementation of that function. If the function implements it outside the VM kind of... Let's say you're talking about video processing in VM impact. You can spawn a separate process saying this is the input file. I have impact taken output the generated file and let me know. So you can do that. In that case, since you're spawning and you process completely, it will be our sync. And you will be blocking. But let's say you started doing all that FFF does in your code itself. Then it will be blocking. But that happens as a call back. No, not always. You can let sync code also. No, no. Can that be written as a call back? So everything can be written. So if you write this function in your code only, it will be a sync code. You just say function A, execute something, and it will suddenly value to function B. And function A, let's say it's outside somewhere. Let's say mode or a module. It might be a sync. But if you write it inline somewhere down there, then it will be a sync. It will just jump to that function and start executing because it's part of your code. If you want it to be separate code, you spawn a separate process. You can write a sync thing in the same part. You can. But not in the same file itself. The moment you write it in the same application, it becomes sync by default. It's like a separate application and then call it. You can spawn a child process, give it an input, get an output back from it. So the spawning process is done by mode or you have to use some... You can actually call OS methods too. You can call the OS methods. You can ask node to create for you also. So there's something called... V8 isolates. It's a V8 that the JavaScript engine has been using. Right now it's like one huge VM in a process. That's it. What... In V8 3.1 or something, I think they have come up with many VMs in the single process. So after that, you don't have to create a process of anyone. Probably nodes 0.6, you'll have the same VM, with the same process with multiple VMs. So it'll be much faster. The cost of... Instancing a process won't be there. VMs are already there. You just start using them. It's like the benefit of engineering. It already has a working thing. But it's not even... It's not even multi-processed. It's a single process multi-stated. And you can pass messages around, like it's an active model and all. You just... Immutable messages. You pass the messages. It's got a pass and drag message. That kind of thing. So you can do all that. Probably in some more time. Writing a sync code in your application itself, in some more time. Right now, if you want a sync code, you have to extract it out into a separate binding. Separate code. Either binding or your own code will be fine. You can have... You can just probably put it as... Yeah. Node 100.js calls... responds node to learn.js. But you can have a callback inside the callback. Right? You can... We'll write a sync code inside. The whole idea of a sync is not just callbacks. The whole idea of a sync is the function your calling itself... should not be consuming your current thread. It should be spawning its own thread working as a returning battery. That's all I get. Just because there's a callback doesn't mean that it will be a sync. Yes. Please. Please don't. Are we true? That was... One more thing to add to this. Okay. So if you want to pull some external web servers past that... all those things, Node.js would be easy. Easy as one. There are a couple of libraries like DOM, JS DOM, or different. Where... You know, using jQuery, scrapping data is one simple thing. But when you... When the same thing can be implemented on the server, hopefully it will be awesome. We like scraping data already. If you like scraping data. You do it. For example, an application with Node.js is not booted yet. An application with Node.js is not booted yet. Are you using a web counter? Have you guys ever seen a web counter with so many visitors? Okay. Let's say if you are running a very high... high-graphy website, this counter has to be safe against... It has to be locked, right? On every implement. Let's say if it's on 20 and two people simultaneously come, how would you manage the concurrency problem? So the concurrency problem is there. You cannot write concurrent applications in Node.js. You can attempt, but you probably won't be able to do that. No, but again, if you're writing a very simple counter, it will work. Problem will start happening if you spawn like four instances, and you share this variable across. Problem is, we cannot write multi-sided applications, which can be concurrent. That's why concurrency is still not there. People have tried to concurrency. The internal is a fork. We have it. Yahoo has concurrency, but it's highly debatable that if it works or not. We cannot write highly concurrent applications. That's the whole idea. So it's not good for writing enterprise business-oriented applications, which have transactions and so on. Unless there is a good reason for Node.js to be used, probably not use Node.js. It is the only good tool if you want a high-level base application. So probably most websites will be fine with whatever. You can write a... So if you're writing PHP code, continue with it. The only benefit you can have from Node is, you upload a file and it has to be processed. You have to know. You won't be spawning multiple processes in a row. You can create a message queue. It's great for creating message queues. Anything which they're saying will do. Exactly. It has one purpose and it's great at that. So if you're writing an application, you could use essentially a Python in front of Node.js. Yeah. I think there is a Node.js for WCI. So you can use it as a front-end. Instead of engine, it's our project. This works. In case no one knows it yet, JS for website is in Node.js. Yeah, completely in Node.js. It's got no good reason to be in Node.js. It's completely in Node.js. Yeah. And after three weeks, it actually crashed yesterday for the first time. It's running single process. No issues, nothing. Was it traffic like? Not that great, but it crashed because the persisting IRC logs to a remote server. So there was some network glitch and it failed. And I haven't handled that either. It was a typical number. I'm sure it's getting more than 1000 inch. Probably not. You can look at the stats. It's not that big. We have not actually publicized the JS for website so far. The people who have seen it are those who accidentally walked and found the site. So, I guess once you fix up the last few things today, we'll start. Actually, remember, you are allowed to be built. Go and have a look at it. Okay, so I guess you are done. He won't say hello. Hello. So. Yeah, let me see. Yeah, I'd like to break the idea.


Pressure is something that can affect all of us individually each in our own way Some people in their response to pressure. They can excel. They can exceed expectations They can do more than what anybody thought that they would possibly do and then other people crumble Other people get scared Other people get intimidated other people just they can't handle it And when that pressure is put on They fall So if you're in a job Where you have a results driven job a results driven career What are you gonna do when that pressure is put on you and That leads us to the the topic of this video today on which Ravens player has the most pressure on Them this season Now you can look all up and down the roster and you can be like, huh? Well, it's this guy. Well, no, it's just no is this guy But we're gonna take a look at some different positions and some different guys who it could be First guys is one of the most obvious ones Lamar Jackson Why does Lamar Jackson have the most pressure on him this season? Is it because of the media? Say, oh, well, okay. Now we got two years of film on you now. We'll definitely get you figured out Could be people could look at it that way Is it because oh man Running quarterbacks. They don't last long. He gonna fall off soon Could be but in my opinion, I think that Lamar Jackson has the most pressure on him for two reasons follow up Follow up Two reasons two words first reason first follow up You adjust the MVP of the league last year How do you follow that up? What comes next what happens now because you took a team and you had them 14 and 2 Y'all won 14 games 12 games in a row only lost two games How do you follow that up you threw 36 touchdowns and only what six interceptions last year How do you follow that up the official the efficiency was incredible last year? How do you follow that up? But then that's one But two another follow-up What will you do despite what happens in a regular season? Even if you get another MVP if you have another phenomenal year What happens in the playoffs now, what do you do when everything counts the most? Lamar Jackson all eyes on you Pressure so that's why I feel like Lamar Jackson could be an easy candidate to go with For him having the most pressure on him heading into this season But we also know that even though a lot of pressure may be on Lamar He's fine with that. He puts the pressure on himself But let's move on Somebody else that has a lot of pressure on them this season Is a running back and This running back. He came on to the team a lot of people really didn't know what to expect from him They knew that he could put up some numbers and he could contribute But they didn't know exactly what the Ravens were gonna get out of but what did they get they got over a thousand yards Got a good amount of touchdowns got just a great amount of leadership And that would be Mark Ingram and Mark Ingram he definitely has some pressure on him Why? Would Mark Ingram be safe? I mean, he's on a low deal. It's a three year 15 million dollar deal This is the second year of that deal. I mean you see these running backs getting paid all this crazy money Mark Ingram's not so Raven should be cool with that deal well insert JK Dobbins Insert JK Dobbins Now Mark Ingram he was productive this past year and We appreciated him a lot still do appreciate him. Mark Ingram was a spokesperson for this team He let his voice be heard. He was repping his team hard But then the Ravens went turn around. They still got Gus Edwards still got justice. He'll they went in they got JK Dobbins and all around back that can do everything that all the running backs on the Ravens roster can do and You would think that okay JK Dobbins. That's that's their future. I Think that's quite clear but anyway Mark Ingram has a lot of pressure on him because Leadership it doesn't keep you around Leadership is a night a great great quality to have an underrated quality to have but it does not mean that you will remain with the team Look at Tony Jefferson Look at Eric Weddle It's not like either one of those two guys their contracts ran out. No, they were released They were released Then you look at guys like CJ Mosie and Terrell sucks Who the Ravens they tried to re-sign them but both of them But the Ravens they didn't want to pay them higher and Terrell sucks say you know He didn't want to feel like he was taking money from the Ravens Go So with Mark Ingram I feel like there's pressure on Mark Ingram simply because you have somebody that's young and Mark Ingram knows the business He's been part of the business but you have somebody that's young and somebody that's You know they're gonna be getting their fair share of touches because the Ravens invested in that guy So Mark Ingram has a lot of pressure on him as well Another player that has a lot of pressure on him going into this season Based off of history Based off of last year Miles Boykin Miles Boykin has a lot of pressure on him because We've known Ravens to not be patient with their wide receivers, especially if you're not a first-round draft pick First-round draft pick you'll get some leeway But anything after that besides Tory Smith If you don't make an immediate impact You can find yourself on the outside looking in fast fast So with Miles Boykin, even though we are under Eric Dacosta, so he may do things different than they did with Ozzy Newsom But it's still to be determined But we do know that Eric Dacosta is a no-nonsense guy He is a no-nonsense GM He is cutthroat So with Miles Boykin there is an immense amount of pressure on him to perform He has to step it up and again, that's just as much on him as it is Lamar Jackson too Because he can't throw the ball to himself But Miles Boykin going into his second year. He got to step it up. I Think another part of the pressure. That's all Miles Boykin has presented himself through one Hollywood Brown And this is not a bad thing None of these are bad pressures They're pressures that can get the most out of these guys I'm sure they want to get the most out of themselves already But Hollywood Brown has presented a pressure on Miles Boykin because Hollywood He was never healthy last year and this guy did his thing He didn't put up these old these crazy numbers anything like that, but he's still produced And he was the most productive Ravens receiver Albeit injured as well So with Miles Boykin he could look at that and be like man, I was healthy last year I'm bigger. I'm fast. I can catch So I wasn't that me And of course, I'm sure he's been hearing all the talk about him. He's been seeing all the videos reports articles about him He's like, huh? Okay But him himself as a competitor as a wide receiver. I'm sure he has it in a way He's like, okay, I gotta make this happen. I gotta do this. I'm sure he's putting enough pressure on himself So we'll see how it goes But you already know we were we ruined for We certainly are Now some more pressure That also comes on the offense is not one particular player because we don't know who is gonna be yet But whoever steps into that right guard spot The pressure is there Because whoever steps into that right guard spot you are following up a legend You're following up a Hall of Famer. You're following up one of the best cars to ever do it Because again one key word that we would use to describe Marsha Yanda is consistency This guy was so consistent You could line him up on any position on the offensive line and he would be just fine I mean, he's played every position on the offensive line and he did just fine But as that right guard whoever steps into that role People gonna be watching you they're gonna be waiting and the expectations are going to be set high because of what came before you and that's not your fault But you still got to deal with that pressure How you respond to that pressure who you all that respond to that pressure whoever that player ends up being They still got that pressure on We'll see how it goes Another person that has some pressure on them Ferg Jalen Ferguson Now it's not as much pressure as the previous three guys, but it is some pressure nonetheless And I think that he has a lot of pressure on him simply because of what's in front of him You got a Kalaeus Campbell. You got a pranel McPhee. You got two guys that have held it down They've had a lot of success in the NFL careers But they could be taken off of your plate So you are going to have a limited amount of opportunities to do what you do because of them and That's not a bad thing for the team and you of course don't want to look at it selfishly But you got to be straight up. Hey, they taking snaps from you So now That pressure is on for you to step your game up and show these Ravens like a You could count on me. I know we got some vets in front of me, but hey, I'm a young stud and I'm gonna make this thing happen Another young guy who has some pressure on him to make some stuff happen It's Tyus Bowser Tyus Bowser's in a quiet contract year. Nobody's talking about Tyus Bowser's contract year Because everybody's talking about Jude on of course because he's 16 mil everybody's talking about Ronnie Stanley We even got Marlon Humphrey coming up, too But nobody's talking about Tyus Bowser So there's some pressure on him as well And that pressure that's on him is to really make the most of his opportunities because him and Jude on play the same position You know Jude on is obviously dead guy Tyus Bowser. He gonna get on the field now But again, just like Jaylen Ferguson. He's getting on the field in a limited amount of snaps And since he's gonna be on the field for a limited amount of snaps. He's got to again make the most of his opportunity If you don't make the most of your opportunity You go I Mean, I think he's gonna be going regardless, but in order for him to maximize his earning potential When you're on that field this year you have an immense amount of pressure on you because You get seldom opportunities So with Tyus Bowser, it's time to put up man It's time to put up Last year John Hall ball called both Tyus Bowser and Tim Williams out call both of them out and now only one remains Everybody can't take the pressure It's not for everybody. Everybody ain't built the same So who's gonna take the pressure this year? Team keep it clean. I love y'all. I appreciate y'all We out


Okay, so we will kick off. It's again a pleasure to introduce a colleague of mine, David Kennedy. David has done some fabulous work that we'll be sharing with you here today. On what's most certainly in my opinion a silver lining to the clouds that was COVID is all of the work that David's after creating and hopefully we'll be bringing forward into non-COVID times. So David, what I'll do is you have 20 minutes. I'll give you a 15-minute slot that will allow five minutes for questions. So I'll give you a two-minute warning if that's okay. Excellent, excellent Mark and thanks very much for having me. Okay, so the floor is yours whenever you're ready to start. Excellent, thanks Mark. I suppose just in brief what I'm aiming to do with you today really is to tell you a story really about the movement from a synchronous face-to-face teaching module to basically a wholly asynchronous module. And the key learnings for me was the importance in which the tools that were made available on Moodle, which is branded as a loop in our university, really helped to accommodate and make this reality possible. So just a bit of general information, I suppose a frame, I suppose background to what I'm about to tell you is that the module in question is from the Bachelor of Education Honours Degree Programme in DCU, which is, folks, it's really it's an initial teacher training program for primary education in Ireland. And the module that I'm going to tell you about is ED201118 Religious Education and the Child. The class size is 405 students and I'm the sole lecturer on the course. It's a five-threaded module and it was with second year and it ran over the course of one semester. Now prior to COVID, the module was run in a very traditional fashion. It was synchronous face-to-face teaching with weekly plenary lectures with the 400 group and then bi-weekly seminars where we broke down that 400 group to about 30 students per seminar session. Traditionally even the assessment method again was very much a traditional academic assignment to 2000 words and all the readings and assessment information was all made available via Moodle. But in a very, I suppose, uncoordinated fashion in the sense that you can see here from the screenshot of the old page, all the material is just kind of listed there. It's kind of dumped there really. Whilst we have the use of the headings, you know, per lecture topics, there's still a very kind of disheveled look to the page for make kind of challenge for students to, I suppose, make their way through it. But that was perfectly fine really and Moodle managed to meet the needs of students really in that totally face-to-face setting because again, this was merely a point of reference as opposed to being the central learning environment for where all the learning took place. So when COVID came along, we had to move the entire module to a completely asynchronous environment and there was this, I suppose you could say there was a sense of hopelessness in one regard when you were there looking at the screen and the panic sets in that it's already challenging enough to try and manage a module with 405 students in a face-to-face synchronous environment, let alone to having to move the module completely to an asynchronous module. Now, the complete move to complete asynchronous module was, I suppose, in part really the main reason why we had to go totally asynchronous was because of timetable changes and all of this trying to meet the needs with COVID in the university. So when I got really started off the journey of thinking how I could recreate this module and how Moodle and Loop could really take effect is that I wanted to take what I was doing really well in a synchronous context and reimagine it in this asynchronous context. So it was really, really important to take what was being done well in that face-to-face setting and try and replicate it in an asynchronous environment and at the heart particularly as well because of the module that it's in religious education and then because of the wider context of COVID and just I suppose the general philosophy of education that we try to embody within the religious education department is that we really sought to ensure that the human person was at the center of the module in a very holistic sense and UDL, the Universal Design for Learning, played a really strong role in making an inclusive relational and dynamic and inviting meaningful experience for students and I suppose the main thing that I wanted to achieve was that I wanted students to learn something and not to merely complete something and that was about finding that balance in that asynchronous environment to try and create a meaningful learning experience. So to assist me and kind of I suppose showing you the tools in which I use to maybe try my best and humbly really try my best to make achieve that goal. We're going to look at the importance of clarity and consistency, so looking at tools like Moodle Books, Communication and just the outline of assessment briefs, etc. The creation of presence and absence so really was in this paradoxical space because it was an asynchronous module that you really wanted to have some teacher presence there and that they didn't feel completely isolated and run their own within that learning environment. And then the big challenge that we had, as I mentioned previously, we had bi-weekly seminars in the face-to-face context and it was in these seminars that the real teaching happened in the sense of that the teachers got to engage with the curriculum and the various programs in a very hands-on way to learn how to teach and how to manage a classroom within the subject area. So we had to try and reimagine this in an asynchronous environment and this is where H5P came in really important and the use of embedded videos and student forums and just a caveat at the end was that the benefit that happened through those seminars was that there was far more usage of discussion forums than I previously experienced. So the clarity and consistency dimension then in terms of communication was really important. So earlier on in this presentation already I flagged the page of how it looked prior to COVID and I very much felt it a bit like a Ron Burgundy moment, hey everyone come and see how good I look when I finished redesigning my loop page in light of the CPD that I had participated in over the summer months and you can see already immediately from the start was that you have already a module handbook for students where they find all their lecture topics, learning outcomes, assessment details, recommended readings and then a clear communication procedure as well as support resources. Their submission boxes for assessment are there very clearly as well and then you can see here that when it comes to lecture topics each lecture topic had its own individual loop book and they had the same structure and content across every lecture in the sense of that in each book you found a pre-recorded lecture, you found readings, a reading list and you found a study task be it a loop quiz or a H5P interactive session. So when it came to the module handbook and as I mentioned this was previously a face-to-face module, we really had to try and I suppose convert students over to an asynchronous learning environment in a very short period of time and this is where the Thomas Aquinas's quote really stood out in my mind of to convert somebody go and take them by the hand and guide them. So the big lesson I learned was straight away from day one you cannot be clear enough and pragmatic enough in terms of communication and layout of the module for the students and what they're going to take up and what they're hoping they will learn and how they can achieve successfully achieve and learn in this module. So this is where the module loop book really became useful. So within that loop book when you clicked in the first thing you had was a description of the course and an embedded video. As you can see there I had Irish language students in the module so all video content had to be interpreted by ISL interpreters. You see very clear assessment brief for the rubric and everything presented but each section had corresponding video input explaining what they had to do so they had a choice of reading or watching. Clear expectations outlined for them again you have the video input and the same again when it comes to the reading list and what was really important within the within this asynchronous environment and the use of loop for me in particular was I wanted the students to have everything at one click away so if it's a reading it had to be one click away if it was for a book it was one click away so their whole reading list as you can see here were all hyperlinked immediately to the documents they didn't have to go and try and find something else somewhere else. So in terms of the lectures then this is where each lecture topic had a loop book you had your lecture inside which are embedded video and then and also a PDF copy of the slides then you had your assigned readings for your for your lecture and then you had your interactive study task or just a study quiz using loop quizzes and this is accessible all via hyperlink but it was very clear and coordinated in how the students were guided by the hand through the module. One of the big things that I learned in my CPT around asynchronous learning as well was the importance of presence and creating this presence and absence and more importantly to not be a walley you need you don't need to be have to be found and sought out by the student you should be very clearly there so when it came to any kind of communication to students be it in an announcement forum I tried my best where possible to give video communication as well. The same then for each lecture topic each lecture topic had an introductory background video of like 30 seconds outline on what they were going to find in the lecture what we're going to look at and the same then again for each lecture topic. So in each part of the module in its layout there was a corresponding visual presence and communication from myself what was kind of funny over the period was it was nearly like a beard growing montage over the course of COVID through to the videos as the module progressed but I suppose the key challenge for us the real challenge within the already team was how do we recreate these very engaged and pragmatic seminars in an asynchronous context so to assist us with this the normal layout of a seminar would have consisted of a very brief presentation PowerPoint presentation and then some activity in some regard so we kept the topics the same but we really reimagined them we came together as a team and had a group conversation around the topic and recorded and then provided ISL interpretation so students watched this video initially and then they participated in an interactive H5P activity which got them to engage with the curricular documents and programs and got them to really I suppose embed and consolidate any learning that they had but not only in the seminar but also throughout the lecture content and the big unexpected finding for us through developing the module in this way and the seminars in this way was that at the end of each seminar they had a task we wanted to hear what the students were were doing where how they were finding things both informally outside of a formative assessment so each seminar session ended with a student task where they had to go away and look at the curriculum or look at the program documents and then feedback to the students of discussion forum and this was really really an active space over the course of the semester students really posted a lot of information and one of the things that they noted in in in a consultation that I've had with students after the module running was that by addressing what they've uploaded in the forums be it by the embedded videos for the seminars or by email or in the forum itself it really also enhanced this sense of presence that was there for the students over the course of the module um but if you're interested in finding more out I suppose in more detail about uh I suppose uh I suppose the other aspects of the course and killing the assessment method we moved from a traditional assessment to loop reflect how did how did that come about um engaged with uh building up the professional community practice by engaging with professionals out there working in the field by having video podcast conversations with uh with teachers at different stages in their career patrons and chairs of boards of management and those so basically those involved in the provision of governance of education in Ireland and those involved at the chalkboard you'll find more information here on a podcast I've done with DCU on the module and on a case study that's available on the teaching enhancement website so on that thanks for listening and uh I hope I can answer any questions that you may have as a bit of a speed run through it but I suppose I said I try and get as much in free as I could


Okay, my name's Rob. Our last name is spelled F-A-U-X, which if you know French means foe or fake. Therefore, we are the genuine fake farm. Our farm is 14 acres, and we are surrounded by corn and soybeans in northeast Iowa.  Now, since I'm representing the farm, I have to put on my uniform, excuse me. I am now at work, all right. This is actually my Sunday go-to-meeting hat. It's the nice one. If you saw me out at the farm, it would not look nearly so red or beautiful. But it's what I'm supposed to wear. Just to give you a real brief idea, one of the things that my wife and I are very interested in is trying to grow mixed or inter-crop vegetables to try and help each of the plants survive and do well without chemicals and without other techniques. We are a certified organic farm. We have five acres of vegetables on the farm, and we started it. Do we need to increase the volume of my voice? Okay. We started this with just one lawn tractor and one walk-behind tiller. And you can guess how much fun it would be to till about one acre behind a walk-behind tiller that likes to break down every so often. So that gives you some background. We came from basically a large garden, and now we are a small produce farm, and we sell using a farm-shared CSA. We have about 120 families in the CSA, and we grow all kinds of vegetables from asparagus to zucchini. So that kind of gives you an idea of what we do. And the idea here was we were raring ourselves into the ground trying to keep all the weeds out, trying to handle all the production. We have to find ways so that we can actually maintain these five acres of vegetables, get a good quality product out to people, and maintain the variety that we're known for. And then you add certified organic to the whole mess, and this adds a few more dynamics to it. So here's the motivation for this.  The other motivation is we used to just run a tiller. We got in a tiller attachment for the lawn tractor. And the other motivation was that thing was not meant for five acres of tilling. After a few years, the tines were gone and everything was breaking up on it. So we needed to scale up our operation, but we did not want to give up the companion planting or intercropping. So there's your motivation. We all there with me now? I'd like to still scale up and maintain this method. So here's what we did. We said let's take our old spacing methods when we had the small tillers, and that's all we had, and compare them to some different spacing methods with the tractor so we could take advantage of it, especially for cultivation. So here we go. Here's the first thing. What we did is we selected certain crops that we like to do companion planting with, and we took the fields that we grew them in and split them in half. So the south half would be our old style spacing. The north half would be the new style spacing. And we made mirror images. So that meant the same vegetables were closest to the center, and then you'd work your way out in the field. And each of these plots, if you look at it, this is a 200-foot plot. And the width is 60, so each, the treatment and the control are 30-foot wide. So this would be the tilled area is the 30-foot, and then you see some greenery in the middle. That's where we hadn't planted yet. That would be the center of the field. Here's what we did before. We would have basically tiller widths, and we would have a walking space in between each. If you're a gardener, this all sounds familiar, right? You'd till it, and you'd have a walking space on each side, and what happens? You have lots of space that you have to keep weeds out of, or you mulch or whatever. So we'd do things like we'd have double rows of onions, and then we would have a single row of broccoli and then some more onions, call a flower over here, and then we'd usually have flowers on the edge of the field. That was our standard approach. And of course, what you would do is you'd try to have the double row of onions, and you'd try to make sure that they were wide enough apart that you could actually run some cultivation in between. We used something called a wheel hoe for that. So if you've seen a wheel hoe, you'll see one later in the operation. This is what we used to do. And here's what we tried to do. What we said is, okay, we've got this little 48N tractor. It's about 60 inches to the edges of the wheels. The center is going to be about 40-inch bed, allowing for slop, because if you're not a particularly good tractor driver or you're not used to it, you're going to kind of slide around a little bit so you don't want to plant too close to the edge of the bed or you'll destroy your crop. And of course, if you're going to use any kind of tillage behind the tractor, it's going to have some play to it, so it's going to slide around. So when you're thinking about having the bed, you want to make sure that you're pretty sure that 40 inches is clean so that you're not going to destroy what you're trying to save. That was my biggest nightmare, by the way. If you're going to go ahead and increase your production to get a bigger piece of equipment, my biggest nightmare was driving for 100 feet, looking back and seeing my entire crop rolled over, and the weeds still standing there going, haha, I win. So we had to try and think about this real hard. Now here's the thing. Remember, we're still a small farm with not a lot of tools. The tractor is new to us, and we don't have a lot of things that go with it. So we're still doing the butt scooch down the row and planting in the plants. But we do have a 40-inch bed, which is wider than our tiller before, so here we're trying something new. We're doing onions on both sides and Kohlrabi down the middle. Kind of makes some sense, doesn't it? I mean, Kohlrabi gets done in about 40 to 50 days, so it's pulled out, and the onions can go a little bit longer. So it made sense on a piece of paper to do this, and we tried to put three in one row and away we went. And the idea here is then we could use mechanical tillage for the wider paths, and we wouldn't have to do that all by hand. So that's the plan. We also said, you know what? We don't know this tractor spacing is going to work perfect, so we also modified our regular spacing and said, you know, instead of always having a walking path between each tiller, let's just cram two of them up close to each other and have a walking path on either side, which certainly makes sense. Why didn't I think of this before? Well, it's because I had no motivation to think of it before. So we did that as well, and now you can, by the way, this is Barty. Barty's our tiller. He's a BCS. He's a good-looking little tiller. And here's what we're trying to do. On our farm, we do all kinds of intercropping, and we decided to focus on two of them for the Sare Grant. The first one is the brassca and allium. So that would be broccoli and onions, for example, would be an example from each family. And the other one that we do is the potatoes and beans. And I'll just summarize this very quickly for you.  We are thoroughly convinced that if you have allium crops like garlic, like leeks, like onions next to brassca, you will have less of that pest in your brassca crops, okay? If you grew 200 by 60-foot solid of broccoli and you do nothing to control for those cabbage butterflies, you will have a big white sea of them. I can guarantee you that. So if we break this up with some diversity, we believe this controls for the problem. So that's one of the ones we were interested in with the potatoes and beans. We're really worried about the Colorado potato beetle. That thing's nasty. And we know this works because we had problems a couple years ago with getting green beans to germinate. They wouldn't. Guess what happened to our potatoes? They also were destroyed because the Colorado potato moved in, potato beetle moved in and took all the foliage away. So we lost both crops that year. So we're pretty convinced these are two good companion plants or intercropping techniques. So now we're going to try and make them work so that Rob doesn't have to walk behind the walk behind tiller every day as long as he did. So here we are in the brassca and allium crops when we're planting. And here is our tractor spacing here. My lovely bride is there doing a little bit of hand weeding right next to the plants real early in the process. And notice we're doing two rows of brassca in one bed. And we're trying to keep them about six to eight inches from the edge of that 40 inch bed. That's approximately what we're doing. This is our standard technique using the two tiller beds right next to each other. And that's the same planting technique we've always done. And here's the potato beans. I tried to put some lines in here for you so you can kind of see where they're at. They're just planted in, of course, bean seed potatoes and seed bean at this time. You don't see anything. But here's the problem that you probably are wondering about. A lot of you like to put potatoes in early and then green beans go in later. If you're going to do this and you're going to mechanize, you almost have to keep them within a similar window for planting time. Because it's going to be difficult to plant your potatoes and then come through and prepare in these same tractor beds and plant your beans later. So that was a restriction we had as they had to go in at about the same time. So here we go. This is an example of some of our green crops with that second tractor or the second no tractor method. Here's what the broccoli and onions look like in June. So they're growing and there's plenty of weeds because that's the way it is. And here's the potatoes and beans. And this is the tractor spacing. And I wanted to get to this because you start seeing something here quickly. We have potatoes here, we have beans here. We have potatoes here, we have beans there. This is the tractor spacing. They're growing right into and right next to each other. They're excellent companions because you've got the potatoes underneath the ground, the root system's a little bit different than the root system for the beans and they both are very tolerant of each other. It doesn't matter if they kind of lean to the side apart from each other and make a crown. The other advantage is, is once they fill in here, you've got a canopy between them. So you have a chance when they're young to run through with a wheel hoe and knock down the weeds young. And then you've got canopy that helps prevent more weed germination later on. So it was kind of nice in that respect. And then as they lean over, the canopy spreads out further into the space between the rows. So that was fairly nice. Here's what it looks like with no tractor. And what we did is we'd have a single row of potatoes and then we'd have double rows of beans. So that's what we're trying to do here. Now remember, one of the things we want is we want control of Colorado potato beetle. So we're trying to find a way to make sure the beans are close enough to the potatoes to have some effect. So this is where some of the spacing comes from. And here is the center between those two. You're gonna notice that we've got the tractor spacing here and this is the non-tractor spacing here. I took the first two pictures thinking, gosh, I want to show people how beautiful both sides of our field look. And then I thought, well, okay, truth in advertising, here's where we didn't get to the weeding in row yet. With the larger cultivation pieces, you can get the paths cleaned up pretty easy, but you still have to go through regardless of the spacing you pick and pull out the weeds in the row. Whether it's a hand tool by hand or with a wheel hoe. Okay, here's the brass canalium in July. We've managed actually in this picture to stay up pretty well with the weeds. It looks pretty darn good. I'm not so worried by the way about this stretch right here with weeds in it, because there's nothing there right now. So that doesn't bother me so much, I can run through and knock it all down. But here we've got a double row of onions right here and right here we've got ourselves a row of abrasica. And you'll notice that we've put drip line in because in Iowa, we also had a drought problem. It's just kind of like having a relative that you don't really want around. The drought was like that this year for everybody. It's like, could you please go away? And it didn't. So we started running a lot more drip line. And here's what it looked like on the tractor side. Notice we've got a single row of onions here and a single row of brassica here, and they're fairly close to each other. Want you to take note of that because it's going to be important later on. Okay, another thing to notice is after harvest. This was pock choy, this was kohlrabi here. Both of them are fairly short season. And the reason I took this picture is because you could kind of see that we still had some weeds in these rows. But because they were mature crops ready to pull out, you don't waste your labor going through and pulling these weeds now.  So truth in advertising again, we were not perfectly clean with the weeds. We still had them. Okay, here's July. Potatoes and beans in July, the tractor spacing. Potatoes here, beans here. We always had the beans on the north and the potatoes on the south for every single one of them. And I can tell you this much right now, that looks darn good. Looks pretty nice. And here's the no tractor spacing. We've got a double row of beans here, single row of potatoes, double row of beans, and you'll notice there's a little bit more of the button weed and a few other things in these rows. So it's just a little bit more weedy and we've had to attack both of them at about the same rate. And if you look real carefully, you'll see a couple people back here. We're trying to clean it up and I said, heck, I'm taking the picture anyway. Plus I'm showing you that we do work, all right? Then we had a diversion from the season. We are an organic vegetable farm and we got sprayed. Happily not on that part of the farm, but our west half of the farm got sprayed. So now I can tell you why we didn't get a whole lot of pictures in August of those fields. We were a little busy. But here is one picture in August and you'll notice that not only did we get just a tad bit of rain in August, which was really welcome, we were a little diverted, so we didn't get out there and get the weeds. So now you're not seeing the pictures as well. But what I want you to notice here is this is broccoli and our broccoli was getting to be pretty darn good size because we got the irrigation out there in time and we had some good fertility. Our onions are supposed to be here and here. But we had a nice wind a couple of times and it rolled over the broccoli plants and the cauliflower plants.  So they're fine, well the onions were not so fine. They were pretty well covered, let's just put it that way. So now they're not getting the sun, the competition of the brassica is winning and the onions are not so happy, okay? So what ended up happening in the tractor spacing is we lost a lot of our onions. They didn't bulb out because they didn't have the chance to do so. And part of that was they were just too close, all right? So the tractor spacing probably loses for the brassica and the onions. And then here's a October picture where we still have the brussel sprouts in here, we've pulled out a number of the onions that were still there. And to be truthful, our onion crop on the south side wasn't great, partly because it was so dry, but that's where we got our onions. Was the south side where we did our traditional spacing. We got very little, next to none, out of the tractor spacing. So no, I'm kind of saying, okay, we're gonna have to do something different if we're gonna do that tractor spacing. Here's one of our favorite tools, this is called the wheel hoe. This is how we do a lot of our hand weeding. And it's kind of turned upside down right now, but we've got the long handles and we have a saddle hoe connection down there. And what it does is it uses more of your bigger muscles. So you're spending less time with your shoulder muscles, hands, arms, and more of your legs and upper body working together. So the wheel hoe is a good way if you have a little bit longer rows to work larger areas. And then here is where we started mechanizing. This is the Ford 8N tractor. And this is a standard toolbar. We initially, when we did the serigrant, had written it up to try and get a brand new made for vegetable production cultivator. Which can be fairly expensive on the order of $1,000 to $1,700 if you want a new one. And finding a used one's nearly impossible. So we went to an old farm auction and found this toolbar that was about 14 foot long initially that had gangs of S times, so an S time looks like an S. And they're on these different gangs that can be removed from the toolbar. And we cut the 14 footer in half and had two seven footers. And now what you can do is if you want to cultivate the whole thing, you leave all the gangs on.  And this cost me $250. 250, 1250, I think I'll take the 250, thank you very much. So this works fairly well for us right here. And here's an example of using this S time. In this case, I ran it with all the tines on it. And this is a field that we just, we put fallow for the year. We have one of our fields fallow in the crop rotation. And I wanted to kind of pick up the trash. And what that means is I have all these weeds growing, they were about this tall. And I said, okay, here's what I'm gonna do. I'm gonna just drop it down to the surface of the soil and drive the tractor. It grabbed the weeds and pulled them to the end. And now I have a pile of weeds at the end. It wasn't so bad, okay? It worked pretty good. One of the things that I did learn, however, is it catches trash so prolifically that if you have tall weeds, even if you mow them down, anything that's longer than a foot, these things are gonna grab and clog the machine up.  And it'll pull things up out of the ground, too. You know, if you've got stuff that you've broken in, it'll pull that up and clog it up, too. So you have to make sure you don't let things get up too high.  Here's another option that we started looking at. We started looking at paper mulch because you noticed back before, we had the rows where there was weeding still to do in row. So we did a trial with paper mulch, and that's because we were able to save money on that cultivator. Instead of spending 12.50 on a made for vegetable cultivation thing, we could spend some here. And here is the used mulch layer that we got. It's a flat bed mulch layer, and I was able to get this for a few hundred dollars as well, and it works pretty well. This is a drip tape roll up here. I just put a bar across the top, and I could find a way to run the drip tape down underneath. And what happens is you put a roll right down here of that paper mulch. And what happens is this disc digs a little bit of a trench, sorry. And then the paper rolls down underneath this wheel, and the wheel pushes it down. And then there's two more discs on the back that throw the dirt back over it. So now the edges of the paper mulch are covered to prevent it from blowing away. It would work for plastic as well, but we have a philosophical difference with plastic, so we don't use it. The other thing that we had to do is irrigation. And what we found with the irrigation is the tractor spacing was a win. Because you could run one row of drip tape for the bean and the potato row, just one. But if you used our old spacing, you had to run one for each row of potatoes in each bean. So in one of those, we could have 14 tractor spaced beds and have 14 strips of drip tape. With the old method, I would have had to run 22 strips. And if you're paying money for materials that probably won't make it through more than one year, I have yet to find anybody who can reuse drip tape well because this stuff breaks down. You're gonna throw that much away and buy it again next year if you need it. So I wanted to cut down on that. So the tractor spacings are in here. And then of course we did the potato harvest and we were able to get ourselves a little, this is an old horse drawn potato digger that we put a three point hitch on. And we can use that to try and dig the potatoes. It beats using a fork or a broad fork or a shovel. And then we were able to run that down. Notice the beans are done, so this is the other thing. You have to make sure you're done with your bean harvest. Then you can run the tractor and you can go ahead and harvest the potatoes. So that's another restriction with a companion planning, but frankly that's okay, as far as what we do. And we were able to run that. Basically the potatoes all get dug up mostly on top of the soil or at least the soil's loose and then we run through and pick them up, throw them in containers and away we go. Here's where it gets interesting. You remember in the non tractor spacing, I had double rows of green beans. And in the tractor spacing I had a single row of green beans next to the potatoes. We're worried about yield here, right? Are we at least getting the same thing as we were before? So here's the deal. We ran provider green beans as one of our trials. Providers a very standard green bean, a lot of people will grow this thing. Okay, and so tractor we had 193 pounds and no tractor we had 235 pounds of green beans for the season. That's not bad. These are 200 foot rows, folks. And I'm getting about a pound per row foot, which is about what you would like to get, okay? So that's good. But here's the thing. Providers here in the south, in the no tractor, those are double rows. So I've actually got 400 seed foot. I've dropped twice as much seed and I'm not getting twice as much production for the providers. So I actually wasted seed in that double row with the provider, okay? That's the first thing you should notice. The second thing you should notice is for Jade, look at that. That's just about double. This is the double row. This is the single row. Jade didn't care. It said it's okay if you run me into double row. I'll give you about double production. So its seed foot has the same ratio. Its row foot is approximately double. And in both cases, they weren't affected for their production by the potatoes they were next to. Okay? So that means I can have a win either way, but I probably should change my ideas about putting providers in a double row. Cuz I'm not gonna get more out of that double row than I got out of a single row. That was by the way not one of the questions we were asking, but it was cool to find out, okay? So that's the first thing. And here's the other thing. We did the potatoes. By the way, that's bullwinkle the potato. We ended up pulling a potato out that looked a lot like bullwinkle and of course we brought it to the market and everybody was having fun with it. But here's what we learned with some of our potatoes. Real grande is this type over here and it's a russet type. And you'll notice that with no tractor and tractor spacing, the tractor spacing was down a fair amount, okay? And that's the one where the beans are next door, like right next door. And with the non tractor, they're a little further away. There's possibility here, although it's not statistically significant that those potatoes were affected by the beans. On the other hand, the purple majesties are right about the same. So they didn't appear to be affected at all, whether the potatoes were next door or not next door to the beans, okay? So this could be very much a variety, independent or dependent. I don't know which right now, I would have to study it more. But this is telling me that that tractor spacing can work. Now here's the other thing that was interesting about it. I don't have a slide for it. We found that the potato beetles that we found in the field were always on the edges in both cases. So the ends of the rows, okay? So what does that tell me? That tells me it looks like the companion planning or intercropping worked. Because whenever I found the pests, they were not where the rows were next to each other. They were on the ends. So this is a good thing. And that is my quick summary of what we ended up doing, which means I'd like to get questions from you if you have them. Yeah. Kind of at this point, you know, between gardening and mechanization, and one guy that I was talking to was saying that if you plant by hand versus planting off of a tractor or off of a bar spacing, it makes it very hard to cultivate with a tractor because it's hard to get your uniform row spaced and what was your experience with that? Okay. The question or the observation has to do with planting by hand versus planting mechanically. And the issue, if you plant by hand, if you saw the butt scooch picture way back at the beginning with people planting, you noticed the onion rows did this nice little sneaky thing and none of them were exactly the same distance apart because no matter how hard we tried, we couldn't get them straight, all right? And then when you do the mechanical cultivation, that's an issue. And that's entirely true, entirely true. It is very hard to take hand planting and combine it with mechanized cultivation. So what we ended up having to do or what you have to do in this case is we tried to make sure that the outsides where those paths were, where the wheel tracks were, that's where the mechanized cultivation came in. I did not try mechanized cultivation in between the companions. That ended up being the wheel hoe anyway. So the net result, though, is I didn't save the labor I was hoping to save with the tractor planting because it wasn't straight. So here's the next part. We're looking at maybe a waterwheel transplanter in the future and that will force, if it's not a perfectly straight row, it's a tractor non-straight row or it's a gentle curve instead of, and the spacing between them is the same. And here's the second part to that answer. The paper mulch can come pre-punched. And if they have pre-punched holes, then they're always the same spacing, but you're also not cultivating in between. So those are our two possible approaches right there. Good question, yes? It's easy to get a crooked row with mechanical, with tractors planting and then you come right with the six row cultivator and you rip up just as much. But how did your paper mulch work out? Okay, there's an observation about it. It's easy to handle crookedness when you're working with the tractor. Yes. It was real easy to make a mess with the tractor. And make a mess with it all at the same time, yeah. In fact, when we did the potato digging, I had it shift on me a couple of times and of course now you gotta go back and get those areas again. But the issue was the question about the paper mulch. How did it work? The first thing that I noticed about the paper mulch is it actually lasted longer than I thought it would. I was prepared to maybe throw a mulch on top of the paper mulch after a while, but that's probably because it was so dry. If we add the moisture, I think it would break down faster. I did notice that as far as what I liked about is the fact that when it did rain, the rain was taken advantage of because it would go through the paper mulch, okay? I also noticed because I've seen and worked with people who've used plastic that it laid no worse. It laid just as well with this flatbed mulcher as plastic. It maybe would make you nervous as it would intend to maybe tear, you would think, or wrinkle, but it handled it fine. We did get the heavier mulch. We didn't get the light paper mulch. So that might have been part of the deals we got the heavier mulch and we were intending on it. But I was pleased enough. We only bought a couple of rolls to try it. I'm going to do a much bigger trial next year. It was that good. I'll be around out here and back if anybody wants to talk.