I think. All right. Let me move this chair. Okay, so I have a short tutorial on writing and contributing back easy config files. I'm not going to explain it in length how to write an easy config file, but I'm going to focus on some of the important points, which will hopefully be helpful. The slides are there. They're also linked on the event page. So you can certainly find them again if I'm going a bit quick.  Just letting us know that stuff doesn't work or that you're unhappy with something. Reporting bugs, mailing lists, Slack, EasyBuild, Comfort Call. So it does know what you have to be code that you contribute back. So we're happy with pretty much everything you send us back in any way. Certainly also documentation. What we're looking at now is adding support for additional software in EasyBuild. It could be an update of something that's already there or a totally new software package. Basically for every installation EasyBuild does, there has to be a corresponding easy config file. The easy config file defines is basically key value definition. So for a bunch of easy config parameters to specify to EasyBuild what it should use, and you can certainly use the big stack of existing easy config files we have, especially when you're doing software updates, you basically you usually take an existing easy config file in one way or another and you update it to whatever or you try to update it to make it install the version you need. You can do this manually or you can do it using the try options that the EB command has. Certainly for version updates or toolchain updates, they are quite good. And especially in the latest version of EasyBuild, try toolchain works very well together with dash dash robot. So it's a toolchain aware to mention that so it will pick up on things a lot better than it has before. So if you've tried it before, you wouldn't be really happy with it. So definitely try it again. It has improved a lot, mostly thanks to Alan who has worked on this. The basics of writing easy config files is well covered in the documentation, I think. And I think we have a detailed example as well for Worf, as I remember correctly. For most installations, and I don't have the numbers here, but I think there's about 20% of the installations need a specific easy block because the software is just so complicated to it's maybe even less than 20%. But for everything else, we use a handful of easy blocks which we call generic easy blocks. So for installing a Python package, we have one easy block, one Python script that knows how to install a Python package. And for every Python package, you can just tell EasyBuild to use this rather than re-implementing the same logic over and over. We have one for, yeah, have a list of the most common ones on the next slide. If you, if it gets really complex or you're hacking around too much, trying to convince EasyBuild to use a generic easy block in a hacky way, that's probably a sign that you actually need a dedicated easy block for it. But there's a thin line there. It's not exactly clear when to use what. So writing easy config files, again, set of key value definitions for the easy config parameters. The order in which you define things doesn't matter. What we try to keep things in a certain order just so it's easy to compare easy config files next to each other. Or when you see an easy config file, it has name, version, toolchain in a certain order that just helps a bit, certainly for people new to EasyBuild to get started or to easily recognize an easy config file. A couple of them are strictly required. So name, version, and toolchain, that's not a surprise. We also always require you to give a homepage and a description just to have some metadata that we throw into the module file that is generated. So that helps people who pick up on the module to actually tell what kind of software it is. Other commonly used easy config parameters are these. Most of them speak for themselves. You can specify an easy block which EasyBuild should use. It's not mandatory because by default we will look for an easy block that matches the software name. And if we can't find it only then, are you required to specify a particular easy block? So like for Zlib, for example, you have to tell easy block equals configure make and then EasyBuild will use this configure make easy block to install Zlib. If you don't do this, there has to be a software specific easy block that corresponds to the software. Source URLs and sources, just a list of sources that EasyBuild can grab from these URLs if it can auto download them. Version suffix maybe to indicate certain variants of builds like certain configure options or maybe a different version of Python it was installed for. You can list dependencies and you can get control over which configure options, which options for the build commands, for example make that you can pass down to EasyBuild and same for the install command you get options that go after the install command so make install something something. But you can also put stuff before the command and that helps a bit sometimes to hack around to convince EasyBuild to first do something else before running make install. That helps a bit with making the general or the generic easy blocks to be used a bit more. Extensions list this is for Python packages, R libraries, so the stuff that John was talking about with EasyUpdate go in here and then sanity check parts. This is a list of files and directories that are supposed to be there when the installation is done. So pretty early on in EasyBuild we noticed that even if make exits with zero and everything looks fine based on exit codes, things may have gone horribly wrong. So what we started doing pretty quickly is if you're installing Zlib we expect a lib slash libz.a to be there. If it's not there something went horribly wrong and then we fail the installation we don't generate the module file. So these are just a couple of simple checks that EasyBuild does for certain files and directories to be there. And then the module class is the categorization like bio modules, chemistry modules. We try to keep track of that as well. So all of this is thrown into the easy config file. An important one of course is the easy block that you can use or that EasyBuild should use. So we have an auto updated list of generic easy blocks in the documentation. For every EasyBuild release this is updated with a script so it's always it always matches the latest EasyBuild release. And the most common ones are listed here so configure make is still very common just want configure make make install and through config opts you can add specific configure options that you need to enable or disable certain features. By default EasyBuild will do configure dash dash prefix equals install directory and anything else that it finds in config opts it will add there as well. Build opts goes to make and install opt goes to make install and so on. Then cmake make is very similar but rather than running configure we run cmake with a bunch of options to specify the prefix but also to specify the C compiler to use the C++ compiler to use and recently also to disable fancy features of cmake like looking onto the system locations first for boost we really don't want it to do that because usually if boost is required it's included as a dependency and it should pick up on that one and not the system one. So we have to tell cmake like don't consider the system parts for boost and it has a dedicated option for system parts for boost. Python package speaks for itself how to install a Python package you can either do Python setup.py install which is what the default is now or you can tell it to do pip install which we hope to switch to with EasyBuild 4 but I'm not entirely sure anymore after fighting with pip for half a day last week. I'm less convinced now that's a good idea. Python bundle is basically to install a whole bunch of Python packages together in a single installation directory so sometimes a Python package needs three other Python packages that in their turn need two other Python packages and rather than having all separate easy config files and all separate modules for them you can just pack them all in a single installation directory quite easily. Make CP this is used a lot for bioinformatics software it doesn't have a configuration step just has a make file and when the make is done the binary floats around somewhere in the build directory and then they're happy because they have the binary and they don't really care. While in EasyBuild you want to do the build and then have a proper installation directory bin with all the tools in it so you can list which files and directories have to be copied into the installation directory. Darball it just unpacks the sources and copies everything so this is for like a bundle of Perl scripts or something like this and binary can be used to run a binary installer where you can install the or specify the installation command to use so this is typically for commercial software if it's not an interactive installer because then you're stuck to writing a custom easy block for it. So there's a thin line between easy config files and easy blocks sometimes you can get away with quite a lot by leveraging a generic easy block and specifying configure options, build options, install options sometimes with being a bit creative like I won't try and find an example but in the pre-config opts you can specify a command to run and then do a .coma and EasyBuild will glue the .configure command after that or you can do a double ampersand to glue the commands together so you can get away with quite a lot in an easy config file that uses a generic easy block but sometimes people get a bit too creative and they start rather than gluing commands together through pre-config opts they specify some command and they add a hash at the end so they're basically commenting out the part that EasyBuild adds as a configure command. If you're doing this then it's really a sign that you're just hacking around and some people are happy while the check guy is already gone but they seem to be quite happy but yeah it works and I'm done right if you're lazy then you can get around it stuff like this or get away with stuff like this but in the central repository we will not accept an easy config file like this so this may be a sign that you have to implement maybe a very simple but you will have to implement an easy block that does whatever you need it to do or you may be using the wrong generic easy block that may be a better one that's more suited for that particular installation procedure so some of the reasons here so if you have some easy config parameters that are really important to get right that may be a sign that you need an easy block typically that is something connected to the tool chains if you have to do have to use a different configure command when building with gcc another one we're building with intel another one we're building with pgi you can't put this in an easy config file but you'll have to get it right every time you change the tool chain and with options like try to chain try to change will only change the tool chain and nothing else so if the configure options have to follow it's actually easy to just implement that logic once in an easy block and then forget about it because the easy block can react to the tool chain and use the proper configure option based on that so it's a bit of an effort certainly if you don't know python it can be a bit of an effort to do it but you do it once or somebody does it once and then you forget about it that's the idea now some people disagree with this so it's not like at css they mentioned that they rather have an easy config file that stand alone and it's not um yeah you can go both ways i guess tool chain specific things that you have to get right are to me a good sign of writing an easy block interactive commands so if you have an installation script or an installer that starts asking you questions and you have to pick a number from a list and this is what the this is goes what beyond an easy config file can can handle so then you really need an easy block uh configure options for certain dependencies a bit similar to connect it to tool chains maybe a good sign as well so the the goal is really to have an easy config file that just specify what is needed version dependency dependency versions tool chain um if it if it goes beyond just some regular configure options maybe it's better to use an easy block for it yeah i think we used the interactive commands for plume d you know plume d there because you probably used that in the easy block for gromax but for the interactive reply it worked also in the easy config using the python syntax with the i think the the minor signs so it was taking the option yeah so sometimes that there are yeah there's like a silent configuration way you can convince the script not to ask you questions but to give the answers up front if you can do that then sure you can use an easy config file but not all interactive installers have this option and then if it doesn't then you're really stuck the tensorflow is a good example as well tensorflow has the configure script is a python script that calls something else that starts asking you questions and if you go into the script you can actually find environment variables that you can define if it finds those it will not ask you the questions so if you know about them you can use them but this is not documented anywhere so you have to dive into the script yourself and and figure it out so yeah and anyway for tensorflow all hope is lost to do it only in an easy config file forget about it ask Guillermo yeah well he's not here anymore um you can probably get get around to making it work but you'll be hacking quite a lot and the easy config file will grow a lot and if you change the version you may have to go back in and see why you did certain things in the configure options and yeah it gets hairy and don't get me wrong the easy block for tensorflow is not easy either it's pretty complex because of the way they do things but at least we do it once and there have been several recent tensorflow updates where we just bump the version and it just works so there was a lot of effort initially to implement an easy block for tensorflow but then it becomes a lot easier okay so when you're writing easy config files and you're considering considering to contribute and back there's two very handy features in easy build that are fairly recent it has an inject checksums option and you can just give it a list of easy config files to consider it will post the easy config file figure out which source files and patch files are needed it will compute the shell 256 checksums for those and it will add them back into the easy config file so rather than having to do shell some manually and copy pasting that easy build can do all of that for you so that's quite handy and we have a hard requirement now for any pull requests in the last year or so that the checksums are there for all sources and patch files if one is missing the test will fail and we will not merge the pull request so this is very useful to have and slightly related to that we have a check contrib option that you can run on easy config files it will do some checks to try and make sure that the easy config file is ready to contribute back so it does a pre-check of some things we check for the checksums is one part of it another part is we check for code style issues so no tab characters in the easy config file yeah some silly I forgot which ones pop up sometimes but there's some some yeah we try to have some strict ish formatting in easy config files to make it easy for people to jump from one to the other and if you don't do this you can still make the contribution but the test will fail anyway so it's good to do it manually up front and just quickly run the the check yourself before you do the contribution so suppose you have composed an easy config file it worked for you or maybe a set of easy config files that work together you need a couple of dependencies so how do you contribute this back so we will this is also well covered in the documentation in full detail so the intention is that you open a pull request to the develop branch of the central easy config repository on github we like that you keep the PRs limited in size so just to make it easy to review and test them if you have a hundred easy config files in there and first of all you that costs like one or two hours just to take a look at all of them and do some reviewing but then we may get back to you and say for these 10 please make this change and then you make the change it just makes the process really long so we like to keep them limited to let's say 10 easy config files touching 10 easy config files is a good rule of thumb but usually it's like one or two or three that are back together in the PR once you've opened your pull request we like that people submit a test report and I'll show you how to do that to to basically show that the easy config files work for you and on what kind of system it was tested centOS or your boot to which python version which easy build version which easy build configuration so that is all fully automated you can easily easily do that after a bit of initial setup and then so we have a bunch of small checks that run automatically when you open the pull request these are things like for an easy config file can I find other easy config files for all the dependencies that are listed is the toolchain unknown toolchain all of these things are checked are you not introducing any conflicts in the module three so you can actually load the module and it's built so these things are checked pretty quickly in a matter of minutes but it's not actually doing the actual installation so that doesn't happen on Travis and then one of the reviewers one of the maintainers usually you know other people can review pull requests as well there's a visual check of the easy config file and maybe asked for a couple of modifications and we have a good way of doing visual checks I'll show this as well so you may have to make some changes based on both of these and you also may have to be a bit patient as I showed you this morning we get 1600 PRs for easy conflicts that's like six or seven per working day on the yearly basis that's quite a lot so we won't jump on the pull request minutes after we've opened it it may take us a while hopefully somebody will look at it and if it gets forgotten definitely bring it up somewhere in the Slack channel or hopefully we're not overlooking your contribution and hopefully it gets merged in the end and then your easy config is included in the next easy book release and you get eternal glory from that so one thing you need to know a bit is git like to open a pull request to to github you need to create a brand well a git branch you need to add stage or easy config file in the right location of the easy configs repository do a git commit do get push out to github login to github click around a bit and because most of the easy build users are not software developers people were running into trouble because of that or were getting frustrated because they didn't know git well enough or even github well enough to make contributions so that was annoying so basically first of all you need to make sure you have a github account like some people don't yet you may have to create it you have to fork the easy configs repository so you you sort of take a copy of it under your own name and then you dive into the terminal you clone either your git repository or the central one so you can do both and depending on that you may have to change your workflow a bit and then you start running git commands you create a funny branch name that you're going to add the easy config file in you put the easy config file in the right location so we have this organization easy build easy configs the first letter of the software name slash software name slash all the easy configs we have to put it there with the right naming you stage it with git add you commit to with the descriptive message or the easy config file then you push it to this is probably your fork of the easy configs repository that's part one then you log into github if you're quick enough you get this button here to open the pull request or you may have to find your branch and then open the pull request a couple of details there so this is a window like this a couple of details there is we want you to target the develop branch not the master branch so master always corresponds to the latest release develop branch is what we're preparing for the next release ideally we'd like you to have a sensible title for the PR so we we have this standard format module class toolchain software name software version and maybe some common dependencies like python just to have a when we look at the list of pull request that we have an idea of what's in there and having this standard format helps us a lot maybe you need a small description for your work you better double check how many changed files are in your branch because maybe you added something by accident that you actually don't want to contribute so be a bit careful and then if you're sure you can create the pull request and then we're not done yet so once your pull request is open travis will do the quick checks on it and hopefully everything passes there one of the maintenance will review your pull request if you're not sending a test report yourself somebody else will test it probably the guy who's reviewing the pull request so you he submits a test report for it and the test report is a hard requirement we will not merge any easy complex pull request unless there's a working test report so if you're not doing it we like you to but if you don't that's okay then we will do it ourselves you may get some requested changes and if you do you'll have to get back to the get dance and figure things out so how do i get back to that pull request and make any changes and you may need to do the cycle a couple of times so say you get a remark for your contribution you remember the branch name that was corresponding to your pull request you use vim what else would you use to change the files you commit the changes if you commit all changes you better make sure you don't have anything else in there and you push the branch again to your repository to update it so this is try explaining this to somebody who doesn't know get or get help it's like okay i don't want to contribute anymore right too much work too much manual steps too much things you have to know develop branch easy config file name where it goes i need to get all these tests right and you have code style policy and ah no i'm done and that's assuming you don't screw up with git anywhere which is not that hard to do you can easily shoot yourself on the foot and either add too much changes in the branch or suddenly blow away what you have and then you can't find it anymore so yeah people were not very happy with that together with this situation we saw that this was back in 2015 in the years before we were getting about 500 easy conflict PRs of which a big part were our own so they are part of this for sure but in 2015 it started exploding a bit we're getting lots of contributions from people who are familiar with git and this whole procedure but some other people were letting us know like i want to contribute but this git thing i would have to learn git to contribute to easy build and it's too much for me i don't have time for this so here i give you a tarble with all my easy config files and you can add them yourself which is yeah not the situation we were very happy with and it also clashes with the idea that easy build is used for automating things but then you have to do all this manual work to contribute back so that's not okay so at some point i think it was christmas 2015 i was fed up with this started hacking a bit i started working on this github integration stuff so the idea was to try and automate the contribution workflow so rather than having all these steps manually having something probably easy build doing it for you and even second goal was to try avoid direct interaction with git and github so you don't have to actually have to know any git or github everything is done under the covers so that's what we did we added support in easy build for opening new pull requests updating existing pull requests downloading easy config files from a pull request you can easily test them without having to copy the easy config files manually you can just ask easy build i know there's a pull request for a new version of cmake i want to use it so you from pr you give it the number of the pull request and easy build pulls in the easy config file and builds it and also for uploading test reports we wanted to have a standard way of doing that that gives us all the information we need in the nice format so it looks all standard and we don't have to figure out for every contributor what they did exactly or how for now it's still limited to easy config files but the concept can actually also work for easy blocks or even for framework so we can let you hopefully in the future hack something in framework make a change that you need to fix a bug and just tell easy build figure out what i changed and open the pull request for it that's still not there but in principle we could make it work under the covers this features uses uses git python which is a python library to talk to git which actually sucks i actually want to get rid of it probably an easy build for rather than using talking to git python we'll just straight up run git commands because there's no real value in using git python at least not in my view maybe i'm missing something but i don't really like it too much we're talking to the the github rest api which is very nice and very well documented and that avoids that you we make you click around on github to open a pull request once you get a github token so like a way that you can talk in an authenticated way with github we can actually automate all the clicks that you have to do to open a pull request which is quite nice and that includes things like targeting develop branch all these all these things you have to remember and then we use the key ring python package which is also a bit of a hassle but haven't found a better alternative to securely store your github token so easy build can load it whatever it needs to talk to github so how does this work so first of all there's a bit of configuration you have to do for all of this to work um you have to tell easy build what your github username is so we have configuration options for all of these things or most of these things you have to give it your github token so we have a command line option where i think it's install github token um you can copy paste the the token in a secure way so you won't actually see it on the on the screen and hit enter and easy build will make sure it's actually a valid github token so you'll test it it will do some simple interactions with github to make sure it's a token for your user which is the case here it will check for the git command because it needs it to run git it will check for git python currently and make sure it's a sufficiently recent version it will check whether this token gives push access to your fork of the repository and whether this fork actually exists and we also use this github gist to for the test report so we make sure we can create gist as well so you can you can create a token that has certain limitations on it so that's why you have to check these things separately and then this is actually less of a less of an issue you can make sure that the commands i will show work a bit faster by telling it where where you have a clone of the easy complex repository already in your process so it doesn't have to download the whole thing yeah okay who is joining the brewery visit the second one most people are okay well i can probably stop here because the stuff that's coming have to do it all at once pretty much but we can interrupt here yeah and continue how long does the tour take 30 minutes yeah so let's let's do that yeah does that work Alan yeah okay so we're gonna that's fine we'll stop the session here because there's a a brewery visit so for the people on the stream the people that are in the room are going out for beers so i will be talking to the walls if i continue so we'll interrupt here and we'll continue in about 45 minutes yeah so say five p.m we'll start again with the rest of this tutorial


And so then generally what I eat are either beef sticks, something like that, high protein beef sticks. I'll also eat tin fish, and so tin fish is obviously just a little bit more expensive. That's between like a 12 to maybe $18 price point, but it's a tremendous amount of protein. Pretty delicious if you're into tin fish, a lot of healthy fats, some good vitamins also. When you sent me your product a while back, like that.


So you want to know how Stable Diffusion stacks up against Dali. Not a problem. For this video I will be comparing the official Stable Diffusion website with the official Dali website, which has now gone public and no longer requires a waitlist to sign up. So when I do a software comparison I always do it strictly from the end user perspective and generally users care about six things. Ease of access, affordability, quality, speed, intuitiveness and policy. Both of them are easy to access. You just make an account and within a single minute you can start typing away and generate images. So they're both basically even there. As far as affordability goes Stable Diffusion gives you about a hundred five twelve by five twelve images for free and then when you're out you have to pay ten bucks for about a thousand more images. Dali gives you fifty credits for free and one credit gives you four images. Fifty times four is two hundred free initial images. However for the rest of your life Dali also gives you fifteen credits for free each month. The biggest difference is Dali's images are ten twenty four by ten twenty four. So they're four times larger than the images you get in Stable Diffusion.  I didn't do the exact calculations but you get like ten. This would have been a close match if Stable Diffusion gave you free images every month or took the mid-journey approach and charged you thirty four monthly subscription and unlimited usage. But as it stands right now Dali definitely gives you more for your money especially when you consider the size of the images. As far as quality goes I'll have another video explaining this in detail but for now Dali does a much better job at photorealistic images. Stable Diffusion on the other hand is much better at doing artistic style paintings however it is much better at generating beautiful faces. This is largely due to the fact that Dali handles policy bans in a way that sabotages its own AI. So if you're a character designer definitely go with Stable Diffusion. But if you're going for photorealism Dali has the advantage on that right now. For speed I'd actually go ahead and give it to Stable Diffusion. Here is raw footage of how long it takes for Dali to generate images for you. I think the average is about somewhere in between ten to twenty seconds. Sometimes a little shorter or sometimes a little longer. I think in this particular example took me like twelve to fifteen seconds. Now here is the raw footage of me generating nine images on Stable Diffusion's website. As you can tell it's way faster. Took like what five seconds. And if you reduce the steps it takes even less time. That was like what two seconds? So if you need speed Stable Diffusion is definitely the way to go. Intuitiveness is honestly about the same. I'm going to give it to Dali simply because their image editor works in both Google and Firefox and doesn't glitch out every time you accidentally draw outside the canvas. And last comes down to policy. Both of them give you commercial license to your work. But Dali also gives you commercial ownership over your prompts. Stable Diffusion on the other hand only gives you commercial license to the images. So that is something to consider. Both websites have censorship. The difference is Dali won't let you search for things that are on the ban list. While Stable Diffusion will let you search for whatever you want but will blur out images it deems inappropriate. But it seems like even if the image is blurred you still paid for it. So that's very unfortunate and disappointing. When I'm working on beautiful fantasy characters I'd say about twenty percent of the time my images come out blurred. I think the fact that you still pay for blurred images is why I'm going to say it's a little bit worse than Dali. Apparently there used to be a way for paying members to turn censorship off but it looks like they've removed that option which I believe to be a big mistake. Now as someone who's rooting for Stable Diffusion this is kind of frustrating because this should have been an easy win for Stable Diffusion. Especially when Google Party gets released it's going to be really hard for people like me to recommend Stable Diffusion over Google if they have the same policy and they're both censored but Google just has better quality. So give people the option to disable Safe Mode. It will probably be your biggest and only advantage when Party is finally released. And for everyone else watching this is why Crayon in my opinion is the underdog that we should all be rooting for because out of all the image generating websites out there that are free and available for everyone to use with the commercial license included Crayon is the only one that has zero filters but hopefully Stable Diffusion will follow soon. Seriously bring back the option to disable the Safe Mode. If you want keep it on the $10 tier but trust me when I say you guys are going to need that option to stay on top of the game and be the people's choice. But anyway those are the main differences. All that helps and as always hope you have a fantastic day and I'll see you around.


Welcome to 50 Days of Keynote, 50 things you can create for the classroom. Today's topic, how to use Keynote to create great posters. Why Keynote and not any other poster generator out there? Well, with Keynote you have full control over the design tools. You can add elements, move them around in any place without any constraints. Here students are also encouraged to think about effective design elements rather than just replicating things on a template. It's then their own artwork so they don't have to copy from anybody else. It can be easily exported. There's no login required to an online platform and they have the added advantage of being able to collaborate with others if the possibility with Apple ID is given. The design tools are the same as anywhere else. We have images, fonts, colors and shapes. What I'd like to do when I teach students how to create great posters is to have them really understand these basic rules. So posters should have clarity. It should be legible. There should be a good contrast. There should be a harmony between the elements on the page. There should have something, a real eye-catcher. It should be a really good and well-chosen color scheme to evoke a certain mood. And the composition, all things how they go together should be really effective because that is what a poster does and what a poster is. A poster communicates a message and that's what effective posters do. They stand out when they're next to other posters. They deliver their message and they say something about the messenger. So what are some lesson examples? Here I have a few for you. Travel posters, a show or exhibition and protest posters. So with a travel poster you can have students research online to see what posters there are. They can choose the elements. They think that are relevant to this topic and then they can choose a city or country and showcase the place with their own design. With the exhibition, students also can use online tools to research what great historical posters there are. For example, on the World Fair or Bar House or Woodstock or World War II. Then they can either design something similar for an upcoming exhibition at school or they can create a poster for a past show. Here they should also again reflect on what they've done and what really makes the design effective. A very good topic these days is climate change or the climate change process. So here is a really great opportunity to have students create a poster to communicate their message on climate change. They can again research online, choose a motif, choose a slogan and create a poster to reflect this. How can this be done in Keynote? Let me show you. So in Keynote what you should do is you should change the document format to click on slide size, choose portrait 3 to 4, change the background color in this case to black, add a circle for the earth. You want to add the continents as well, change them to green and then place them over each other to get a real earth and added drawings or your text. When you're finished export to PDF or image and there you have it. That was already day three. Join us on our journey, follow us. You can find all the videos here and all the Keynote files here. See you tomorrow.


Do you ever feel like something is off about your relationship? Does it seem like they're trying to take advantage of you while looking well-meaning or wise? Manipulators are naturals at getting you to question your own sanity or perception of reality. And depending on who it is, it can be tough to spot, especially if the aggressor is among your close friends and family. So to help you be more aware of these behaviors, here are seven common phrases manipulators use to trick their victims. 1.  To any outburst from your end, they may retort with, oh so you're mad, even if I'm mistakenly accused by you? You do know you're the one who's hurting me, right? This is a common manipulation tactic where they try to rewrite the narrative and get you to empathize with them, even when they're the ones at fault. They're denying the hurt feelings you have for them to get their own way. For empaths and timid people, this manipulative performance can sadly be quite effective. 2. I seriously don't want to argue When a manipulator says I seriously don't want to argue, it usually just means that they want you to stop attacking them to keep their reign of dominance intact. They want to cut off any healthy and honest communication lines, to keep you from stepping out of the line in the dynamic that works so well for them. What makes matters worse is when you use the same phrase, they throw in their excuses saying it's not their fault and that you're the one being delusional, to keep them in power. Their attempts to avoid any and all arguments may be their way to self-enrich themselves and to keep you at bay. A healthy person would at least try to lend an opening ear, so it's a good idea to be aware of the difference. 3. Stop exaggerating everything Do you know someone who constantly tries to downplay a situation? It can feel exhausting when you're upset at a manipulative person, since they're often too prideful to empathize, understand, and work with you to help solve the problem. Instead, they may use underhanded techniques to dismantle your argument. Stop exaggerating everything is one of the phrases they may say as an attempt to diffuse situations, control the narrative, and keep you from lashing out at them, even if it's clearly warranted. In cases like this, recognizing their patterns is always the first step to rising above them. If it persists, then it's always best to look after yourself no matter what the cost, even if that means removing yourself from the situation entirely. 4. They're crazy Listen to me. Imagine you've reached out to your friend to talk about your relationship problems, and they tell you that your partner is actually very manipulative. When you bring this up to your partner, instead of keeping an open mind, they may defend themselves by putting down the other person. They may say that your friends are the ones who are crazy and that they are the only person who is right and who you should listen to. The worst part is that some manipulators can be charismatic enough to convince you. This can be severe enough to the point that they force you to stick with them at all times, which can isolate you from the people who might go against them. 5. Look, you clearly don't understand. Have they tried undermining your arguments? Manipulators are great at confusing people and making them hesitant. Sometimes they might even act like a brick wall so there's no room to communicate at all. No matter how you feel emotionally or how much you try to argue, they may never make any sort of attempt to empathize or understand you. In this way, they evade any form of accountability. 6. No, no, you're being delusional.  Manipulators like to shift the blame away from them and paint you in a bad light. They're not in the relationship for a healthy two-way dynamic. They're in it so they can make themselves feel better at your expense. Suffice to say, it's not healthy. Manipulators love it when you're nice and kind to them but they're ready to discard all of that in case it's not needed anymore. It's a good idea to ask for insight from other people or professionals about the situation or set clear boundaries from here on out. 7. Now, why would I do that? You know I love you. Manipulators know how to skirt around romance and get you to fall for their good side. They may show their vulnerability during first impressions but reveal their darker side once they've caught your attention. The most frightening part for empaths and people who fall victim to manipulators is that it's so hard to turn off the switch and remove the manipulator from their lives forever. After all, the experiences, the good times that I love use can all seem incredibly real but manipulators know this too and may use it to manipulate you further. If they really cared and loved you they wouldn't constantly dismiss your feelings but have an honest conversation about them with you. Instead, they're normalizing in action, mind games and dismissive emotional patterns which is not something a healthy person would resort to. So has anyone ever used these phrases against you? Let us know in the comments below. If you found this video helpful be sure to like, subscribe and share this video with those who might benefit from it. And don't forget to hit the notification bell icon to get notified whenever Psych2Go posts a new video. The references and studies used in this video are added in the description below. Thanks so much for watching and see you in our next video.


I'm excited to see what kinds of products Americans are using in the next 50 years. In 1972, the drafters of our statute couldn't have possibly foreseen the number of products that we're, the type of products that we're dealing with right now. I'm excited to see where this goes.


With the AudioKey 2 app, you can control your RONDO 3 settings.  All from your phone, but first you need to pair it. Let's see how you do it. If you are using AudioKey 2 with RONDO 3 for the first time, make sure that you have Bluetooth enabled on your phone. Restart your RONDO 3 and position it close by. Open the AudioKey 2 app. The pairing screen should automatically appear. Then select the Direct Connection option and tap Next. If the pairing screen does not appear automatically, navigate to your profile and under Audio Processor, tap Pair Now. Turn RONDO 3 off and then on again. Then select the Direct Connection option. And tap Next. AudioKey 2 will automatically pair with your device. Once your audio processor is paired, tap Next. Assign a user to the audio processor. If it is your audio processor, select your account and tap Next. If the audio processor belongs to your child or someone you look after, then select the corresponding user from the list. Tap Create New User, then Next. Enter their name and tap Create. Your audio processor is now paired with AudioKey 2. Now your audio processor is paired with AudioKey 2. For more details about what you can do with AudioKey 2, visit go.meta.com slash AudioKey 2.


Fel ydych chi'n gweithio i'r gwaith, a ffwrdd i'r drwy'r edrych a'r gweithio am y gwaith ddylch yn ymddangosol. Felly, mae'n ddweud ei wneud yn ymdweud i'n ddweud i'r gweithio i'r comfor i'r Michael a i'r Kathy a'i'n gweithio i'r gymhag i dda i gael yma i gael i'r gweithio i'r gweithio i'r gymhag. As you know, the first one was held in Dublin, the second one was Llymrack, now in Cork, there's nowhere else to go so we'd probably move back up the country again. But since Llymrack, we've been continuing to work actively in a number of areas. Our next, we've done April, June, September for the education and development events and the next one will be in February, which will tie in with our first annual conference. The article writing forum has gone very well and has resulted in the fact that we have a number of articles which will now be incorporating into our first bulletin, which will be coming out at the end of the year, beginning of next year. February is the month for, as I said, the annual conference. We'll tell you more about that near the time. We'll, of course, be looking for speakers, so you're more than welcome to put in a vote for that. The Digital ELT Conference, we've been working alongside the Learning Technology SIG from IA Teffel and also MEI in helping to put that together, and that will take place in November, as it has done over the last couple of years. I think most of you already are receiving our fortnightly newsletter with updates about what's going on, keeping everybody in touch. As usual, we've got our Chinwag, which takes place on Twitter every second Monday. In addition to that, we said at the last event that we were now an affiliate of IA Teffel, and we were following up on that and working closely with some of the other associates and affiliates in different parts of the world. Peter attended the IA Teffel Poland Conference. They hosted him, and we'll be doing that and hosting one of their members when we have our annual conference in February. I recently met their president of ELTA in Albania, and we'll be doing the same type of thing. So, yes, we're growing in Ireland, but we're also growing outside of Ireland as well.


What's up everybody Jason for Jasper's case breaks calm little pack filler to win five spots in opulence basketball with this 1920 penini Chronicles NBA fat pack break number 749. So again 30 total spots This is a high-risk, high reward type of break guys So first we do the break randomize the customer names and teams distribute the hits out of the one fat pack Then at the end of the break we'll randomize all 30 customer names in a separate dice roller randomizer And the top five names will win a spot in this break here Which is a $300 a spot Right, so you can win a spot for as low as 53 bucks. So top five get in I'll post up another way to do two more plus eight spots straight up to knock off that opulence tonight guys So let's do the break first guys dice roller from the names and teams We got a two and a six or two and a four six times. Good luck one two three four five six Nick Nick down to Daniel. All right six times one two three four five six And you got the pelicans Down to the Rockets Alright, so quick little glance at what you got just stick with what you got so pelicans up there with Nick We have the Lakers here with Nicoba grizzlies down here with James All the way down here to the bottom All right, let's quickly do this pack filler break and then we'll Come back and see you get into the break. I've got KPJ Matisse Tybald Siku Dumboya Jordan McLaughlin Kendrick Nun Vigiladipo Cameron Johnson Blake Griffin. We got a little Brandon Clark. Luca Donchich Kobe whites Terence Davis Rui Hachimora Siku Dumboya and a bronze Siku Dumboya All right, there you go guys Now let's switch teams and give away those spots. Good luck. So again top five get in guys roll it Five out of five ten times top five get in one two three four five six seven eight nine and 10th and final time Boom Shaumatic James Martin John and Jay congratulations top Five get in after ten times. So there you go guys another way to win. We post it up soon jazby's case breaks comm


Hello everyone and welcome to or welcome back to Norris Cove. I'm Yoshida. If you are new here I'm a self-employed hairstylist and I like to get my life together by planning minimally and functionally and also Getting my life together Planning my budget. So today we will be doing a budget video a paycheck to paycheck I do not receive a paycheck, but this is how I pay myself. This is how I pay my bills again Like I said before I'm self-employed And I hope that this video will help someone Honestly, I've already recorded this video, but Because I was rusty I did it all wrong. So I had to start over A second thing is I do apologize for my absence In my first video I showed how I had not planned since probably June and All of this is empty. So I did kind of do my November monthly budget But today for today's sake, we're gonna be doing our weekly Paycheck to paycheck budget and Yeah So let's start over and I can show you I had to scratch so much stuff out. I said, you know what? Let me just start over If you're new here, I designed this bundle. This is our 2023 bundle, but we do have our 2024 bundle, this is what it looks like. This is an oops. So I'm gonna use it for myself and matter of fact This again, this is our old one It is about available for a digital download if you want to use this one matter of fact I'll just do this one. I'll just do a separate video on how we're gonna use These especially since I'm a little rusty now. So let's just start this all over Again, I'm gonna flip to November So that I can see what we have to do and this week will be the 20th through the 26th Okay, and my source is of income right now. It's just here and My business which is Norris Cove and so for here I'm just gonna budget around 800. It is Thanksgiving week, which is normally busy for me But I do have some customers that are traveling. I like to say a thousand But I'm gonna stick with 800 this week for Norris Cove. Um, we are doing a Black Friday sale, but I gotta work on the graphics. I gotta get things up, but I'm just gonna stick with like 150 just to be on the safe side I generally don't count my business income because it generally goes back into my business But we're gonna count it because we kind of came out with a profit this month So our total would be I'm just gonna put total right here $950.  I still did it wrong. Okay Bill's due this week. I'm just gonna use my cheat sheet over here. We have Barclays and they will be coming out on the 23rd I Normally don't do automatic Automation for my credit cards But what I did I got this credit card the interest rate taken down because it was just way too high I was paying too much, but they're pretty much close the account would give me a cheaper Interest rate. So now I just paid $50 a month for another year. Okay Next up we have Amazon There's something I got on Amazon that I owe and that'll be on the 2030s whale and that is a hundred and twenty dollars afterpay Have a afterpay payment that is due on Let me look over here the 23rd as well everything is that coming out on the 23rd and that is $25 Okay, and then next up zip, which is sort of like afterpay That is due on the 24th And that is 3854 Next up we have PayPal I'll pay back credit card that is due on the 25th. Generally. It is like 46 dollars. So We're gonna see Next up we have go daddy and go daddy is what I use for my website and my email Professional email my website is paid up for the year, but the email I paid that monthly I don't know why I didn't choose To do this yearly but who because it's more pain in the mouth Okay, and next up we have booth rent Which I rent a chair in a salon that is due on the 25th and that's $250 And that's what I used to run my business and then what I did was I'm paying a portion of my car note I've never really discussed my car note on here But trust me, this is not the full amount, but I'm paying a portion which will come out one probably Tuesday or Wednesday so But I live and What is Monday's date Monday's the 21st? I'm gonna put it around for like the 21st and that'll be to 25 Okay, so now let's do some calculating so For this week the total of what I owe would be $761 and 95 Okay, and we anticipate making 950. So if we subtract that from 950 That leaves us a hundred and eighty eight dollars left. So I like to put that we put that down here in the Summary section Okay, so we don't we're not doing our single funds this week to my knowledge We're not doing expenses because I really don't have any I have gas gas. It lasts me note that payment that I know of and I think that's it. So that leaves us with a total of I'm just gonna put it here a hundred and eighty eight dollars also, I do not zero base budget because I'm self-employed and I could but Because my income is inconsistent It just doesn't really work for me and I have to do what works for me in my budget So by me having this a hundred and eighty eight dollars left now Here's what I could do with that. Of course I'm gonna put I should put some to my savings, but because I'm self-employed I often say sometimes things just come up between this toilet paper So until I get back to my cash stuff and envelopes right now I'm just going to at the following week. I'll say what happened to this one hundred and eighty eight dollars and five cents So that is the end of up but my budget video for today Next week I will do a what I used to do rather is that come back show it got paid How we paid it what didn't get paid however and how the week went and then we'll go on with the Next week, but however, I will say this if you again off your new here You can follow me on Instagram on Sundays and Wednesday. I do financial lives We do a check-in and if there's something maybe that you need which will help with your budget We do that. There's a lot of people to hop on they give budgeting tips and encouraging words Or what they may have done to help save money. It's really a vibe You should really come over and check us out. Also. I have a Facebook group We can their link should be below Also, if you're interested in any of the products that I use today, you can check out my website Which is also listed below again. Thank you all for stopping by again I apologize for my absence and I'll just see you guys in my next video because we're back on track Okay, talk to y'all guys later. Bye