Microplastic pollution of our waterways may not just represent a threat to marine ecosystems, but also to human health. It's evident we're exposed to microplastic pollutants in seafood, which may create a food safety risk. But is there some seafood less contaminated than others? The first published study looked at mollusks, eating an average serving of mollusks. You consume about 90 plastic particles, whereas an average serving of oysters may contain only around 50. As a result, the annual dietary exposure for European shellfish consumers can amount to 11,000 swallowed microplastics per year, though we don't yet know what kind of risk this would carry. Of course, due to their persistent nature, microplastic abundance is only going to get worse. It's inevitable that humans eating seafood will ingest at least some microplastics, particularly when the entire creature is consumed, such as mussels, oysters, and small fish, so what, like sardines? Oh, we didn't know until now. Contamination of microplastics and mesoplastics, which are like little pieces of plastic larger than a millimeter, they looked at 20 brands of canned sardines from 13 countries over four continents, and only found plastic particles in about one in five. They suggested that disparity may have been due to improper gutting in the contaminated samples, but in mammals at least, ingested microplastics can get through the gut wall and circulate throughout the body and even cross the placental barrier. So do microplastics actually make it into the muscles of the fish, like a fish fillet? Let's find out. If you compare the level of microplastics in eviscerated flesh versus the organs, surprisingly, sometimes the flesh actually contained higher microplastic loads than the excised organs, which highlights that evisceration does not necessarily eliminate the risk of microplastic intake by consumers. Microplastics of all colors, shapes, and sizes were detected in all investigative fish muscle samples, so they do actually get into the flesh. So the average intake of microplastics from eating flathead grouper shrimp scat or barracuda may be in the hundreds per 300 grams serving or just in the dozens of plastic particles in a two ounce child serving. Besides the plastic itself, the particles may release absorbed pollutants like PCBs and also release plastics chemical additives like BPA, which collectively may cause hormone disruption, and cancer risk and DNA damage. Hence, although there's no standard, like tolerable dose for microplastics ingestion, as well as information on exact toxicity of different plastic types in the human body, taking weekly servings of these kind of fish may threaten the health of consumers, especially vulnerable groups, including pregnant and breastfeeding women and children. In the U.S., anthropogenic debris, meaning man-made materials, were found in a quarter of individual fish and in two-thirds of all fish species tested, and also about a third of individual shellfish samples, demonstrating that man-made debris has infiltrated the aquatic food chain up to the level of humans via seafood. Because this debris is associated with a cocktail of pollutants, this validates the concern that the debris may be transferring these chemicals to humans via diets containing fish or shellfish, raising important questions regarding the bioaccumulation and magnification of chemicals and consequences for human health. Now, this study also included non-plastic debris, like foams, film, and fibers, but we know now that the ingestion of microplastics appears to be a widespread and pervasive phenomenon across a number of commercially important mollusks, crustaceans, and fish. So, the potential for humans as top predators to consume microplastics as contaminants in seafood is very real, and its implications for health needs to be considered. Despite the existence of considerable uncertainties and unknowns, there may already be a compelling case for urgent actions to identify control and, wherever possible, eliminate key sources of microplastics before they ever make it into our oceans.


You and McNeil, I'm the convener for the MINICONF, and we're going to get started now. Our first speaker is Javier, who's going to talk to us about configuration management, a love story. Okay, welcome everybody. My name is Javier. I'm here to talk about configuration management and about love. It's really tough to go after the keynote, so please take it easy with me. So what's the story with this story? I think the first time I heard about configuration management was in another great Linux conference for them. It was 2010, and I fell in love with the topic, then followed all the streams about DevOps, and it happened that I moved to live to Australia. I started working for a company, a REA group that managed realestate.com.edu, and I've been doing a lot of configuration management since then. The story behind this presentation was that we had the Puppet Labs guys coming one day to our office and asked this awkward question, configuration management, what are you doing about it? We're like, oh, that's a long story. Started sketching in the whiteboard, and then a few days later, one of my colleagues, David Lutz, asked me, oh, we have a slot in one of the meet-ups I'm running, which is Infacoders, and said, can you put together a presentation for that? I said, well, this could be a good story. When is the meet-up? And he said, tomorrow. I said, OK, I'll try to do that. So I thought, what is going to be the fastest way to get a presentation together? So I had this idea of just writing in a whiteboard and taking pictures of the different things that we are doing. So that's what I'm going to be doing. So we are going to go through four stories. Hopefully I have enough time for the four of them. I'm going to try to be quick. So let's start with the first one. Hands up who has been in love at any time. Excellent. Hands up who is doing something about configuration management. Cool, a few of you. Hands up who has ever hated configuration management. We have a few as well. So the first love, everything is going to be perfect. She is the one. She is the one. Has everything that you need is the one. So here we go with the story. So up in the top left we have a calendar, which is kind of rough days about when things were happening in the company. You can imagine it was a smaller company than it is today. Probably it had only one data center. It had a small dev team. It had a small ops team, typical. So a few servers. The deployments were done manually. And configuration was done via SSH. So someone will SSH into one of the servers and craft the configuration. Then the dev team over time keeps growing, growing, growing. Requirements makes you want another data center for DR for running active, active. So things keep growing and the number of ops slowly grows with it. But the dev team really wants to deploy. Deploy fast. And then we want more features. We want more business value deliver. So what can we do? So our brave ops go and add your service. Start deploying into the data centers as fast as they can. Until they hit a problem and we got an incident. Oh, slow down, slow down. We start to get that tension between the two groups that we all know about. Everybody is hungry. Nobody is happy with what's happening. So suddenly someone goes to a conference and comes back and say, like, oh, I heard about this tool. Got in love with this tool. It's called Puppet. And it's great. It's going to solve all our problems. So the team goes and starts implementing it. It's a good team. So they start crafting a few pieces of code, put it together. They push it to Git. Then we have a Jenkins job to push it into two Puppet masters, one in the data center. And then we had a lot of servers that are running Puppet in demo mode. And it starts pulling that configuration. And the configuration gets pulled. And everything is fantastic. End of the story. Hooray. We're winning. But then things started to be complicated and tried to represent that with the number of code, the number of pieces of code that we had in that repository. And we tried to make abstractions. And we tried to use classes in different places. And we tried to reuse code all over the place. So what happens is you try to push a piece of code. And not only breaks the server that you were deploying to, breaks a lot of other servers that are related to that piece of configuration. So then the ops team starts with a typical talk about, oh, it's an incident. We want to meet over 99.99999, whatever. This is not going to happen again. We need to do this manually. This cannot happen. We cannot break a lot of servers at once. So, well, when the team comes again and says deploy, please, then the ops team only had one way. It was removing the puppet daemon from the servers and do the deployments manually. What could possibly go wrong? So the ops team will go and put everything in Gith. It gets pushed into Jenkins. That goes to the two data centers. And then someone SSH into a box and applies that. OK, that's all right. But when you haven't done that for a long time, then it's when you have started to have problems. Because maybe you have updated a lot of times in the same server. But there's a few of them that you never update. So whenever you want to try to update those, you find that you have 72 changes to apply. And three of them are errors. So what do they do now? I need to deploy. I need to deploy now. So what could I do? So someone had a great idea. I will SSH into the box. And I'll make my change. And then I'll copy that into configuration management. What a great idea. Yep. Commit. It's already done. So you can imagine this over time and over time and over time. It's into a really, really difficult situation. Really difficult to manage. Lots of confidence and lots of problems. So we had some configuration management, but it was done probably incorrectly. So there comes the next story, which is the other. So now you're having troubles with your partner. And you start seeing other people around. And I don't start hanging out with someone else. And let's see what's out there. And then you start to have other ideas. So let's first present the problem. So we had our increasing development team that wants to deploy. But as we were having a lot of trouble with our deployments, then they want to have a staging environment where they can deploy and they can check things before going to production. Great idea. So the ops team goes, provision a bunch of things where they can deploy and then we have a great staging environment. But when you have tens or hundreds of developers that want to deploy, then there's a lot of contention into that environment. So they come and say, can I have two staging environments? And you're like, oh, well, we'll have to go to whatever is your hardware provider and then buy more team. They deploy the team to the data center and everything. So that was not ideal. We had a lot of people waiting. So we are into agile. So we provide user stories. We provide requirements. So as a dev, I want to test my changes in a product-like environment as early in the process as possible. And I don't want to be waiting for other people. So someone had a great idea. We created a team called Gandalf. Gandalf came to the Shire and said, I'm going to solve all these problems. You just need to hold this ring and I'll come back later. So Gandalf was a project that was put together. We had some people from the ops team. We have some people from the dev team and we have some consultant coming. So a mix of everything and what's going to solve the problem. So he came with new powers and new ideas. We were, why don't we use the cloud? Cloud is infinite. You can use as much as you want, as much as you can pay. And it's not going to be contentious because we can create environments for all over developers. So the idea was, why not? Each developer can have its own environment. So it can test any changes that they want. And then they say, like, well, to make that easier, why don't we write some tooling? And then with this tooling, we are able to deploy easily into that environment. So you just can type REA deploy and then say, I want this environment that has only the front end or has only the back end or has everything. So it could go from a couple of servers to probably 30 different kinds of servers and databases. And then the last great idea was, why don't we implement it in Chef? Because we've seen that Puppet is not working. So we have this other idea because why don't we bring another tool and that will solve all our problems. So Gandalf weighs his one. And we created a VPC into Amazon EC2. And then people were able to write their own Chef recipes to define all those services that we wanted to use. And then using the tooling, they could deploy into an environment, for example. That's one there. They had everything that they needed in a smaller size than in production. And they could do all the changes. This is great for hack days.   That was great. And then another team wants to deploy. Or even an individual wants to have a full environment. I want to have everything they want to test and could do it. Oh, great. We're winning. OK. Now we test it. We can do stuff. Now let's go to prod. Let's see what happens. Then the ops team, because nobody thought about prod, goes and says, OK, I'll replicate the changes you want in my puppet and deploy it into the servers. And yeah, that always works. Can you guess why? Mm, prod like. Well, I forgot about a few things here and there. So cloud versus data centers. They're not the same environment. There's a lot of things that can't change. Puppet versus Chef. We are not keeping consistency between the two configuration management systems. Debian versus centers. Oh, why are we going to deploy in the same operating system? That's nonsense. Not the same deployment mechanism. Well, you can guess what kind of problems we're emerging from there. So yeah, that worked for a long time. That was kind of the strategy. We were finding problems. At least we could have as many staging environments as we wanted, and that problem went away. But many others came with that. So we thought, oh, we need to standardize. We need to go with one way of doing things. We want to get engaged. So the first thing that we should tell here is how the company changed over that period of time. So we no longer had ops team. We were following agile practices and DevOps principles. So what we did is we organized the company in different line of business that align to different business objectives. And inside those line of business, we have different teams that will be composed of people from different practices. So for example, in the LOBX Team 1, we have an iteration manager. We have a QA. We have developers. And we have one ops. So they have everything that they need to be able to deploy a full project and to create a full project without depending on other teams, which was great and is working really well at the moment. In the other side, we had a platform team, which his duty was to maintain the data center structure, the cloud structure, and some of the services that these teams were using. But we were drawing the line at the operating system. So everything about the operating system in terms of keeping security patches or deploying the application and managing everything was done by those teams removing handover between different teams. At the same time, we started to have our first EC2 production environment in which the first thing that we deployed and was really successful was the images of the site. So you can imagine at real estate sites, 90% of the site is the images. You can see the pictures. There's no point of having that kind of site. And we deployed move from the net up into EC2 and we started to have a farm of resizing service in there, which was working really well and gave the business the confidence that we could move our workloads from the data center into the cloud. So more confidence on having things in the cloud going forward. So what the platform team did was why don't we provide an environment that everybody can use even if it's in EC2 or is in the data center that has everything installed in that operating system that is normally required by all the teams. These are things like, for example, LDAP. These are things, for example, like NFS configuration. This is things like New Relic or Splank configuration. So everything that is a base and that all the teams are using will be pre-configured and installed in an image that you can deploy in both environments. That reduces the amount of configuration management that you need to do on top of that when you want to deploy a service which makes it really easy. So what we did is we brought up a bunch of puppets that we chunked in Git and then we have a Jenkins job again that creates an MI and a BMD key image and then we are able to test that before sending it to production. Whenever we are happy with that then the team will promote it to stable and then everybody can start using that for their deployment. So it's a tested image that is consistent between all the teams that I talked before about having different environments where people were deploying. So the process of deploying for these teams is we write in our code, we push it to Git, then we have a Jenkins job or a bamboo job and that packages everything into an RPM that can be deployed on top of that platform image. Again, that reduces the amount of things that need to be done in the configuration management layer to make it as simple as possible. So a deployment looks like something like that. We have an RPM with the application and then we have the platform image. We put them together and then we push it into prod using some automation. When we are happy, we push it first to test and then when we are happy, we push it to prod which makes sense. So there's one small bit that is not there. So you have different environments so you may want to have different configuration variables in those environments. So the thing that we were using, similar to what other environments like Heroku does is to inject those into the service before booting the services and then having them consume. For that we build what we call a config service which is just a REST API that you can consume from and it will give you all the information that you need that is related to that environment that is not going to be packaged in the RPM. That way we can deploy the image and the same application into dev and into prod and the only thing is it's going to change those small pieces of configuration. At the moment there wasn't anything that we like. Probably if we rebuild this we will use some of the products that are out there like HERA or HCD There are many options for that but at that point let's build our own. It probably wasn't a good idea. So you put all that together and then you can deploy and remove some of the problems that you will normally have in your deployments. That's the full thing put together. We have the platform image the app deployed as an RPM and the configuration. Finally, we are getting closer to today. We have this idea of you have different teams and the teams are independent between each other. Why they have to marry the same girl? They can make their own choices. We are seeing that a lot with other technologies for example languages. People are starting not to use the same language for everything so they choose the programming language that is more adapted to the application that they are creating and the same thing with databases and persistent storage. You don't use the same kind of database for everything. The same deployment mechanism for everything. What we have again the infrastructure environment has evolved a little bit more. At this time we are 2014 we had Amazon creating the region in Sydney so we started to have the opportunity to connect the Amazon region into our data center using DirectConnect so we had a tiny connection directly from the cloud into our data center and that helped us to migrate the applications really easy which in the long term maybe was the best idea because when you want to move to the cloud you want to rearchitect your applications to be more cloud like and that connection sometimes was something that it was making the engineers not to think about how to move stuff and how to decouple things between the old way of doing things and the new way of doing things. At the same time we created this circle and what we did before is as a team you have the autonomy to decide what are the best options for you in terms of technology and you have the autonomy to make your own choices so everything gets together and decides what technologies they want to use and that brings back the accountability that means that every system that you build you're going to have to maintain it so you're going to have to think before if you want to use this technology or that technology that you can empower to do whatever is needed to build your services then there's all this conversation about economic scale or well if everybody's using different services and it's using different technologies then how do we share like as a company if someone moves from team A to team B it's going to have to learn all the stuff that this team is using and also if we employ people it's going to have to come from different environments and sometimes there's this view of the teams are doing the same thing they are reinventing the world because we have probably 10 different ways of deploying and the idea was well we really fancy more the first option which is having the teams accountable and autonomous than having the economies of the scales so we decided we know that there's a little bit of ways of doing it this way so we're going to continue doing it in that way so some ways that you can try to solve that problem are the guilds and the open source model so we proud ourselves to be a sharing culture company where like everybody is happy to help someone else and everybody's happy to teach other people and there's a continuous conversation going on so we have this thing called guilds that other companies are doing as well where like people will get together and what a surprise so you will come there and there's different guilds so we have around one which is called the ops dojo where we get together and we practice operational skills and people learn about operations but there are many other guilds including things like a happiness guild or a public presentation guild or anything the other part that we try to use to bridge that gap of having teams doing their own thing and trying to follow something like the open source model this is the idea of world in the open source world everybody can start a project and everybody can decide what kind of project are they building and then there's a community that is built around that and then there's a supporting community and then like for example if there are two projects that are trying to attend the same thing eventually they will come to agreement and use one now if they are successful both of them they will continue doing their own thing but that's only if they are happy with that if not they can switch so the idea is that through all that sharing and all those guilds we have the opportunity to broadcast what we are doing and then we have the idea that the best projects will win and then people will start to adopt those instead of having a top down approach where we were pushing the teams to use the technology that we think is better so again coming back to the autonomy the teams are happy to see what other people are doing and to embrace tools and practices that other teams are doing so for example what we've seen a lot is now that we are using more and more amazon web services cloud formation is becoming the base that we use to build our infrastructure so before in the data center in the data center model we couldn't really decide and we couldn't really change a lot of topology and we couldn't change a lot of things in there now the teams in cloud formation they can decide what they do and how they build well, I need a BBC, I need a load balancer I need this kind of databases and they can work independently which is great and it's replacing somehow some of the configuration management tools that we had before because it's allowing us to shape the infrastructure that we need so it covers the deployment process and some things will use the platform image to do the deployment and to again shorten that gap to minimize the amount of configuration management required but other teams say like, you know what in that platform image there's a lot of things that I don't use I don't need all that stuff and that is making my boot time really slow and I can't cover that easily with my own configuration management they decided to stop using the platform image and move to an amazon AMI that's totally fine, we're happy with that is that maybe it will be more work for them but they can get better results and then again they can choose whatever deployment mechanism that they want some people choose Ansible for example what they will do is our infrastructure in cloud formation so this number of load balancers this number of servers, these auto scaling groups these databases, whatever and then when it comes to the deployment mechanism we normally will have a CI server that is running a deployment process and that will use the configuration management to deploy the final steps of the configuration of that server for that, continuing in the team 1 some teams are using the amazon CLI to do the deployment but all the teams for example the team 3 have decided to build their own tool again coming back to the kind of times where they decided that they can build something better than the CLI and that is more adapted to what they need to do and what they want to do so some things have created that Kool-Aid some teams are moving into docker so the teams that are moving at the moment into docker, they are building their own tool to wrap around docker to make it work the way that we like our deployments required to be done in this case for example they are using the Ruby SDK instead of using the CLI that is totally fine again and they decided that the platform image is a really good idea for them so they continue using it and they say like oh, you know what I'm not doing an RPM I'm not doing anything else it's so easy for me that the only thing I do is just just bash and say deploy this RPM so yeah again, different choices which I may agree with or not Questions So we have about 5 minutes for questions I was faster than I expected From the I think 2013 you're talking about having images with I think everything in install that might possibly be needed that seems so weird to me do you mean that every system had an LDAP server installed, every system had a Oh no no So what we have is the client so for example we have an LDAP server in the data center and then when you deploy new servers they may be using that LDAP server for authentication so what they have is the client configured to go to that LDAP server whenever anyone wants to log in so in the platform image we're only putting the client of the LDAP Does it make sense? Yes, but is it really so hard to just configure it in a configuration management system? So here I see if it is so difficult to do it in the configuration management system and I think that it relates back to the first story where we try to do everything in configuration management and we try to create classes that apply to every single system and then when someone wanted to modify those they were really scared because it was touching every single system that we had so we decided not to try to do that and it was really difficult to test so it can be done uncompletely Yes, that's fine and you can do it that way but we Yes, that's fine but you can do it these other ways so this is an alternative that we use to minimize that we had at that point but yeah, there's different ways to tackle the problem I think the main idea behind the conference is the talk is that there are many different ways of doing things but we have tried some of them some of them have been successful for us some of them failed but yeah, we had that same problem that you mentioned about having an image where they tried to install everything so we had another team that was taking care of the Windows deployments and the idea was well what about if I put everything that can be needed I have an SQL server I have everything that I need so the deployment is really easy and can be used for everyone but our image was much more lean it was really really small only had the things that really we thought that 90% of the teams will be using that's analytics and that's logging and authentication on just a little bit of our own customization Yeah, hi how do you manage things or secure things like database credentials configuration files? so it depends there are many ways that we are doing that one of the ways that we used to do it it was through the configuration server so every environment will be able to ping that configuration service and ask for credentials and those will be injected only into authorized boxes to then be able to access other systems where is the okay this one is going to be the last question Hi, one of the problems I see with this kind of approach is that you've now gone from supporting one or two different technology stacks to now supporting 10 or 20 or 30 and when those development teams leave or recycle in about six months or a year's time you know you've now got this huge legacy that you're having to carry and you'll have one person and one team saying why the hell did they use Ansible why don't they use Sol and suddenly it becomes a real burden on the company because there's all of these multiple technologies that are now involved the way that we tackle that normally I said it's up to the team to decide but normally there's a bigger unit which is normally the line of business which is like that business oriented that will have different streams and will have different teams so the ownership of the systems are normally given to that line of business so they try to do some reuse of technologies and they try to so they have the opportunity to do some of those economies of scale and they know that so they know that they're going to have to support the system over time so they try to minimize the number of technologies that they use and they try to find the right people for doing that some of that inside the smaller circles but we thought that the unit shouldn't be the company itself because when you make decisions at a company level then you're making them for some kind of cases and will not work for everything but yeah, that's true this approach comes with some problems that can be moving people between teams and having legacy that you have to support over time but that comes with the accountability part so we're giving you the autonomy to choose whatever you want better you have a plan to maintain that over time ok, that's all the time we have for questions please join me in thanking Havia for his talk


Okay, morning everyone. Good morning to the students online as well. Hope you're doing well Okay, so let's do do a quick review. What what we did last week, right? So last week we looked at Sharing the gospel in five minutes. We looked at sharing the gospel in two minutes we look at the four spiritual laws and And and so it's very important that we use these guidelines, right? They just guidelines for us to share the gospel right now Doesn't mean that you know, I have to use it this way I have to say from Genesis to revelations or I have to give the salvation experience you see what works for you and You share the gospel, right? So we looked at Experience what was your need before and how the Lord met your need and then we looked at very importantly the work of the Holy Spirit While ministering the gospel Now we must understand that it's not our work, right? Is it our work? Is it our work to speak into people's hearts? Yes or no Our work is to share the gospel and The gospel the power of God the Holy Spirit will speak into people's lives, right? So that's very important we must understand that and Especially when we're sharing teaching preaching Everything must be anointed from the Holy Spirit I was teaching the other class we were talking about why the anointing is important right We can do many things in Ministry, right? But if it's not anointed of God, it's not going to touch people's lives Yes Right because the anointing of God the Holy Spirit's anointing will only touch and change people's lives We can preach We can lead worship We can do everything Out of the flesh also And if there's no anointing of the Holy Spirit, it is not going to touch people's lives It'll only go here You won't go here Right, so whatever we are doing in ministry, right? It should be anointed of God Right, so that should be our prayer God I'm leading 10 minutes of worship now or 20 minutes.  You know Holy Spirit. No He's there inside you Even right so everything that we do must be anointed of God Right, so let's look at the next chapter next chapter We're going to be talking about ministering the gospel in power and love everyone say power and love Now they are like oxymorons know meaning they are They are This power there's love power talks about authority and there's love Now Jesus ministered in power But he also ministered in love Now we must develop this ability to do that Is power important? Yes or no Power is important. Why do we need the power of God students online? Why do we need the power of God to Manifest his gifts. Okay. Why do we need God's power? He convicts. Okay Why do we need the power of God? Can't we just you know this do ministry? Why do we need God's power? Sorry To be an effective witness. What do you say? To impact others. Okay. Who else? Why do you need? What is power in Hindi? Shakti. Yeah, Samarth. Why do you need that? We must ask ourselves. Why do I need the power of God? Is it simply because God is saying I'm powerful. So I also want to be powerful. Why do you want the power of God? To bring down strong holds. Okay People believe What do you say? Okay. Jesus Apostle Paul says my ministry was not only in word but in demonstration and power Right. There was demonstration. Right. So Jesus ministered with power When the Lord Jesus went about preaching and teaching Healing and delivering and working out miracles. He did it with power But he combined it with compassion Now, usually if you see a powerful man Very unlikely they are compassionate Right These powerful rich men and women that you may see around us Very unlikely that they are compassionate They're very authoritarian by nature Right. Jesus had thousands of people following him But what happened after that? He had the power. Right. He was telling the blind people. Hey, I'll make you see. He was healing people He was just changing the course of events happening there But he did all of this because of his love He didn't do it because he wanted to become famous He didn't do it because he wanted people to know. Okay, that, you know Even though I'm a carpenter son, I'm able to do these great things He didn't do it just to show the Pharisees and Sadducees that, you know, I'm greater than you. I know more than you He didn't do it for that He didn't do it for that Jesus ministered in power and in love Love of Christ, the love of God the Father Pushed him to do all of this Now, this is very important for all of us We all want to do a powerful ministry, right We all want to do a good worship We want to teach the word of God powerfully We must remember that we must love the people that we are ministering to It could be one person. It could be thousands of people We got to love them We must be in a place to care for them by saying that, okay These are people that need to hear the gospel They need to understand Christ. They need to understand the word of God And when you minister out of love, it's already power there So let's look at a few examples here Matthew chapter 9 and verse 36 Anyone of us can read Matthew 9 and verse 36 Matthew chapter 9 and verse 36 And maybe someone else can take Matthew 14-14 as well When he saw the people he was What does it say there? Moved with compassion The Greek for moved was he was stirred up with compassion So Jesus was moved with compassion when he saw the people Jesus didn't say, okay, why have you come here again? How many times to tell you the same thing? Why do you keep following me? What does he say? He was moved with compassion. Why? Because there were people who are just there lost without a shepherd, without a leader They don't know what they're doing Many of them had sicknesses, diseases Failures in their life He was moved with compassion Matthew 14-14 Great Again, he saw a great multitude and he was moved with compassion What is this that we must learn in this? Very simple point When we are ministering to people They may be people from other faiths It's very easy to bring condemnation What you're doing is wrong What you're doing is wrong What you're doing is wrong But Jesus here, he didn't say what you're doing is wrong He was moved with compassion The love of God Was the source of all that he did So it's very important for each one of us To be moved with compassion When we see people Who are struggling And we get this opportunity to minister to them Do it Now, here's the thing Very important point To be moved with compassion Does not mean you agree to everything what people say Yes or no What did Jesus say? Many places he rebuked the leaders Did he rebuked the leaders? Yeah But did he not love them? Or did he love them? Love them Right So when we are ministering We minister with compassion Next one We minister with the power of God Let's read John 14 Now this is a big verse But maybe one of us can read this John 14 1 to 13 John John 14 I will go to the place of him I will come again and receive myself Let's hear from him Here he comes And here I go to know and to read him Thomas said to me Lord, if you do not know Where you are going And how can you move the way Jesus said to me I will be the truth and the life No one comes to the Father Accept it to me The Father If you had named me You would have known my mother also And from now on you know me And have seen me Please accept it Lord, show us the Father And if it's sufficient Or as Jesus said to me Have I been with you so long And yet you have not known me Please He who has been with me has been with the Father So How can you say Show us the Father Do you not believe that I am with the Father And the Father in me The words that I speak to I promote to speak on my own authority But the Father who dwells with me Does not want Believe me that I am with the Father in me Or else believe me For the sake of the words themselves So this is John 14, 1 to 13 Right? 1 to 13 13 Most I have said to you He who believes in me The words that I have written to God And greater words than the days He will do Because I have put my Father And will never be fast in my name That I will do That the Father may think he will be fast If you ask I think he may believe I will do it How does this focus on that One verse, right? What does it say there? Greater things than I do I did, you will do Right? Now in the Greek When we look at it Jesus is not talking about The essence of the miracle Right? So I hope you are getting what I am saying I am not talking about When he says greater things It's not about the essence Right? Now Jesus walked on water Doesn't mean we can say Okay, Jesus walked greater things Than, you know He did, I will do Go to the nearest swimming pool And try to walk on water You will need help Right? You can't do it You can't take Yes or no Or one plate of food And say, okay, all of us are going to pray No, he is talking about the essence It's not the essence of the miracles But greater in terms of volume Right? The Apostle, sorry Jesus did his miracles For three and a half years Jesus is saying As believers You will continue this ministry Doing greater means volumes Much more than what I did I did only for three and a half years But you will do greater More Right? So what Jesus did in three and a half years As believers, you will do much more than that And is it true or not? Yes All across the world, globally When we see now What's happening? Thousands and thousands and thousands of miracles Now how is that happening? That verse goes on later Because the power of God will be in you Right? It's not happening on our own ability But it's happening because of the power of God So it's very important to remember the essence Of that verse Greater works Than what I did, you will do So the greater in the Greek Simply means bigger More In terms of volume I'm saying what I'm saying Because there's many times This can be used And put into a wrong understanding Greater works So even I will do Even I will try to turn water into wine Or I will also try to Feed people Or I will also try to go and do something No Yes, God may call us to Do supernatural works But we have to be led by the Holy Spirit See the Lord Jesus He was tempted He came back after he was tempted He was led by the Holy Spirit In every way So when he went to the wedding at Kena He was led First what did he say? What did Jesus say? My time has not yet come But the next verse, what does he say? Go fill the water pots What happened there? A moment The Holy Spirit would have told him Start Now is the time You launch your ministry But before that he said So you see That the Lord Jesus was being led by the Holy Spirit So there will be times You will be led by God To say things To do things You do it boldly But remember Empower and love Right? Let's look at the next example Luke 24, 46 to 49 Anybody can read Luke 24, 46 to 49 This is interesting Let me give you a context What's happening here Jesus is resurrected He's come and he's meeting his believers Even in the book of John He sees the disciples What does he say? He blows on them The Holy Spirit Can we find that verse? John 2022 Somebody read that Okay Now Jesus is resurrected He's meeting the disciples John 2022 He breathed on them And said to them Receive the Holy Spirit So they received the Holy Spirit But what does he say after that? Go and tarry Which means go and wait For the Holy Spirit to come What's the difference here? Jesus already blew No, the Holy Spirit Why is he saying go and wait? Then it happened in Acts The day of Pentecost Why were they waiting? He already blew on them the Holy Spirit It says there That when you receive the Holy Spirit When you wait and receive You will receive the power Of the Holy Spirit You see Let's read that verse again John, sorry Luke 24 I think it's verse 49 Endured with power So what is Jesus trying to say?  Acts chapter one verse eight Let's read Acts one eight We all know this verse Acts one eight Amen So now Acts chapter one verse eight 120 people are praying Where are the thousands of people?  They received the power To be a witness You know the Greek word for witness It means martyr What is martyr in Hindi To help the students in Hindi What is martyr? Anybody knows the meaning of martyr? Martyr means somebody who's willing To die for Jesus Like Apostle Paul Right All the disciples Those who are killed For the sake of Jesus Are called martyrs Did you understand? Right in Hindi Did you understand? Right So those who are killed For the sake of the Gospel Are called martyrs So the Greek there is You will receive power To be a martyr For Christ Now Jesus knows That we cannot do ministry Without the power of the Holy Spirit What is the best example? Where was Peter When Jesus was crucified on the cross? Where was he? Crying somewhere? Where was he? He was not there, no Was he at the cross over Jesus? No He was not there He denied Jesus Forget about At least not being there He denied Jesus He said, no I don't know this person Okay Why out of fear obviously That he saw what's happening to Jesus They were beating him He was scourged And the people were saying Hey, you're Jesus's disciple When they may catch him And beat him also So he said, I don't know Right What was their fear?  Have you thought of it? Where's that fear? Just maybe one month back He was afraid Where's the fear gone? There was no fear And the Bible says When you read in the book of Acts They saw that these two were unschooled But they had the power of God They could not do anything to them Later on they arrested Peter What happened? What did Peter say for that? Was Peter fearful? Did he say, oh no Please don't arrest me I will not preach He said, okay It didn't matter to him Why? Because the Holy Spirit has empowered him Now you and I must understand That we need the power of the Holy Spirit To minister to people We can't do it on our own The legs will be shaking If you try to do it on your own Especially in a time like we are living in now With all the things that are happening around We need the power of the Holy Spirit You cannot go and minister to people On your own ability You cannot do it Jesus is telling the disciples here Even though I was with you For three and a half years You saw all of it All the miracles You walked with me Yet you still need the power Of the Holy Spirit The baptism of the Holy Spirit How much more you and I need it? Do we need it or not? Whether we are called to start a ministry Whether we are called to be in the workplace We are called to be a witness But we cannot do it on our own ability We will fail Because I'm not discouraging you But what I'm saying is You need the Holy Spirit For everything You need the power of the Holy Spirit And this is the best example Peter is the best example They were all fearful They were all running away Next thing you know Peter is bored and he is standing there Unafraid He didn't say Oh my wife is at home Can you choose somebody else? John is not married You choose him No It doesn't matter The blind, the lame man was there Peter and John goes to the temple The lame man is begging there They would have gone through that steps Hundreds and thousands of times Yes or no The steps to the temple But they saw that lame man there He's asking for money What does Peter do? He says hey listen Sin word and gold I don't have But what I have I'll give you In the name of Jesus Christ Rise up and walk Now tell me The same Peter Hundreds of times he's walked through that temple He's not done it But when the power of God is in our life Nothing can stop us But we must also learn We'll learn in the next chapters How to walk in wisdom Just because we have power Which shouldn't be like We do whatever we feel like Walk in wisdom We'll talk about that later Okay acts 532 Let's read Acts 532 right Great Sorry can you read that again?  Now Peter and John After they are Arrested The angel comes And they are Loosed from their chains They walk out of prison And they testify this And then later on Also in the book of Acts There's so many testimonies Right? Picture this Paul is in the island of Malta He's He's trying to put the You know Fire together A snake gets caught in his hand He shakes off that snake He's preaching the gospel Everyone are falling asleep Teaching teaching the whole night He's not stopping It was not a one hour session It was not being recorded But he's teaching teaching teaching Young boy is sitting near the window I don't know why he chose the window But he shows the window He's sitting there He fell asleep He fell off and he died What did Paul do? Let's start 21 days fasting prayer What did Paul do? Don't worry Pray and raise them up Right? So They were able to testify Of God's power Right? Nowhere was it in a way that It was only talk No They were able to testify And so here We see that When we walk in the power of God We'll be able to testify Of his power And we had testimony time Right? All of us shared our testimony We may not have had this big testimony Who You know Suddenly Angel came and Said something and went We may not have those kind of testimonies But even the smallest testimony Is a testimony of God's power In our life Yes Right? Because the enemy has so many ways To distract us The very fact that he has Called us Into his kingdom To be his children Is the power of God It's God's work in our lives Right? Next one Hebrews chapter 2 Verse 3 and 4 Hebrews 2 3 and 4 Amen God testified it With signs, miracles and wonders What does it go say after that? And gifts of the Holy Spirit Signs Everyone say the signs Miracles Wonders And the gifts of the Holy Spirit Why do you have Supernatural hour every day? Time pass What? I hope it's not time pass Why do you have Supernatural hour every day? Because Come on Why do you have Supernatural hour every day? I think we should Tell you why you have Supernatural hour Students Why do you Online students Why do you pray And ask God for You know Pray and read the word every day Why do you take all that effort? Why do you have Supernatural hour every day? Why do you have Supernatural hour every day? Because it's called Supernatural hour Okay So what happens to the Supernatural hour? There should be The work of the Holy Spirit Sorry Yeah Yeah So it's not only that Okay, I want to flow in all the gifts That's good Right But we want to see Ourselves growing closer to God There should be A sense of Okay, God I want to I want to go closer to you Right I want to know the Holy Spirit And the Holy Spirit begins to work in our lives Through science, miracles and wonders Some of us may say How come I've been praying for so many years? I don't see science I don't see miracles I don't see anything in my life Right I don't see You know, I'm not speaking in tongues I don't know the prophetic I don't know word of knowledge I'm not flowing in these gifts But it's been two, three years that I am You know Praying for it I want to encourage you Don't give up Right Continue to pray Because this is not a man-made effort Right Of receiving the gift God gives it to us The Holy Spirit inside us He gives it to us Right But we must desire it Everyone say desire Right Like how you are desiring for this class to get over Desire For the gifts of the Holy Spirit When you desire something, you are passionate about it Right When you desire for Friday Friday comes on Saturday, Sunday Leave You don't feel that? You love very holy people Sometimes, you know, I desire for Friday Friday Saturday You know When I was in Bible college I would go and visit my parents When you visit your parents after one week You just have to sit Everything will come to you Food, snacks, everything Because you are going after one week So I desire for Friday Saturday morning, go visit my parents So we desire so many things in life We desire to become a worship leader We desire to preach We desire to start a ministry Same way, we must desire To flow in the supernatural We must desire the gifts of the Spirit And when we desire it There will be signs, miracles and wonders And here is the verse that we just read God testifies it Testifies what we speak And preach with signs, wonders and miracles And that's what we want to achieve in the supernatural hour as well What you are doing It should be a place where You begin to release the gifts of the Spirit Begin to pray in the Spirit Begin to flow in the gifts of the Spirit It's not going to happen overnight It's not going to happen because I said it It's going to happen today No, if it does good But remember that you can do it Because God is saying here I will testify it I will testify that the Holy Spirit is inside you With signs, miracles and wonders Now the important point is Understand, do you have the Holy Spirit inside you? Are you sure? All of us are sure? And testify it With signs, miracles and wonders Let people see Now you are not doing it for a show But what is the meaning of testify To show an outward appearance of it We can't see the Holy Spirit But we can see His working in and through us Amen? That's what we are called for Expect miracles, signs and wonders Wherever and whenever we minister Right? You may be in a college You may be in ministering it on the street You may be in a friend's house You may be visiting another friend Or somebody may have invited you to share A topic which is maybe not even about the gospel But be willing to minister Be willing to see signs, wonders and miracles There are many instances where we used to go to colleges Across Bangalore, we used to go And we used to have these one hour of worship Word and prayer But they used to say don't say too much of Jesus Because there's a lot of people from other religions Don't say too much of Jesus You can use God but don't say too much of Jesus So we agreed to it But we would use Jesus every now and then But we taught scriptures And many a times It was so nice, it was so wonderful to see There were times we were just teaching Or just sharing something And many lives were touched It's not about the preacher It's not about the person who's teaching But it's about God's word touching them And ministering to them We were in Mangalore for about four years APC Mangalore I used to go to this college And when I used to go to this college We used to take scripture classes And there was this boy here It was for 11th and 12th So they call it PUC There was this boy, he was very disruptive Very very disruptive guy When he would come to class He would start walking there He would start disturbing everyone He would start throwing chits on people And he would start poking fun He would look at his phone He would start yawning He would stretch himself Very distracting guy And he would disrupt the whole class He would do something with the whole class To touch their lives But half the time it was This guy would disturb the class It would start from the beginning He would start the class with something The whole class would be So their mood would have just changed So I thought, I used to pray I said, God, this fellow is a troublemaker How do I get him out? I thought, let me chase him away from the class Let me tell him, okay, out But if I do that How is he going to be ministered to? He'll happily go Nothing for him But how will he be ministered to? I'm sure there's something about this fellow So I kept praying every day Every day the same problem One day he's come with a bow and arrow I don't know from where he gets these things One day he'll come Just very disruptive Suddenly he will tell him Sir, I don't think I need God for now Very disruptive guy One day I was just praying I said, God, I don't want the class to be disruptive Because it's one fellow Should I send him out of class?   Did she hang herself? He said, yes So you're angry with God You don't want anything to do with God because of this And you want to just be You have plans to just leave And you want to spoil your entire life Because of this, yeah She is an innocent girl Good girl But she committed suicide And I don't know why And then I had to share It took a lot of effort A lot of time Because I had to share with him About Jesus How can I say God loves you I can't say God loves you Don't worry He said quietly in class I can't do that There's a deep hurt inside him I began to talk to him every week Every week And all of them In the end of that whole semester He came forward And testified Of what God did in his life Because he was a changed boy Completely changed Right And so We are not to You know Look at people and Eventually make their You know Just say You are like this Give God the time Give God a way to minister in their lives Trust in God To work miracles Right Amen We gotta trust in God New ministering to people Don't Come to a place where We can write off people Don't write off people Give them time Because God can work in their lives And when we look at Apostle Paul He did great miracles He went to Athens He went to Galatia He went to Ephesus In Rome Everywhere he went His ministry was back With signs, wonders and miracles Why do you think We are talking about it now Thousands of years later Why are we talking about The church in Rome One church in Colosse A small church that is It's one small town Why are we talking about it? Because these are works that God is testifying It was all born out of the spirit Something that is born of the spirit Will last Something's born of the flesh It's going to die away What's the proof in the scriptures? Remember there was a guy I think it's In the book of Acts One guy he came and said Okay, you know He started a new doctrine And there were many new doctrines He started But they didn't last What did the high priest say When they called Jesus They said the high priest said See, many people have come And said they are the messiah And all If it's not If he's not the messiah It will fade away Leave him alone Right So that which is born of the spirit Will birth the spirit's work Right We must minister with compassion And also with power Let's read 2 Corinthians 5 14 and 15 2 Corinthians 5 14 and 15 I like that first part of the verse The love of Christ compels us Some of the verses say The love of Christ Constraineth me Right What I'm doing Paul is trying to tell the believers You're in current What I'm doing is Because of the love of Christ That compels me to do it Do you think it's fun To go from place to place Being beaten up People are trying to kill me People are I don't have proper food I don't have proper clothing Do you think it's fun He's saying no He's saying The love of Christ compels me Now the background of this is In current Most of us have read the letter of Corinthians Right What's happening there The believers are saying I like Paul I like Apollos I like Cephas I like Jesus So now there's division Paul is saying Hello Listen It's not about Paul It's not about Apollos It's not about Cephas What is this division The reason all three of us Or all of us are doing ministry Is because the love of Christ compels us to do it We could have been sitting In our home And relaxing And doing whatever we want to do But we've come here Because the love of Christ For each one of you Is compelling us It pushes us forward To do the work of the ministry Right Let's read First Thessalonians chapter 2 That's a little long Verse 1 to 8 First Thessalonians 2 1 to 8 The church in Thessalonica Was a church which had very little Right It is a small town But this is the church Where Paul is writing and saying Whatever you This was the church that blessed Paul Materially When he was doing ministry And he's saying to them That you Whatever you're doing Is you're doing it for the ministry Because we did it for the ministry You're doing it for the ministry Because we did not come to you In our own words In our own thoughts In our own abilities But we came to you in love And because of love And because of the love of Christ That is why you are reciprocating That love to us By your generosity You know the love of God Is stronger than the hate That we see in the world Right The love of God is stronger Than the hate we see in the world Look around There's so much of hatred Jealousy, anger Anger and There's so much that the enemy is doing The love of God is able to break through All of that Right So Jesus As Christ He set an example to us As the Messiah As our God He set an example When we are ministering to people Minister out of power and authority But let the foundation be love Right Let the foundation be love And build on that foundation Amen So let's keep this in our heart Right Whatever we're doing The power of God The authority and power of God That we do The love of Christ Shall we pray? All right Let's pray Father, we thank you for this beautiful time We thank you for What you have taught us today, Lord I pray that you will teach us You will lead us and guide us, O God As your children That we will continue in the things of God Everything that we do We will glorify your name And give you praise in our life, O God May our lives be pleasing in your sight We give you all the praise We give you all the glory and honor In Jesus' name we pray Amen Amen God bless you all Thank you, everyone online Have a great week ahead See you next week