rmance which we'll go over shortly but you could just use this just as a guide even if you're not using conformance so let's go through a couple of these guidelines and it looks like my notes are a bit out of whack but let's let's try something here so we have perceivable and I'm just going to skip forward to the first slide the next slide just for a second oh no it's all good don't worry so perceivable perceivable sets the stands about the way the website is viewed how does it look on a mobile phone versus a desktop? we're going back to mobile first but this is an important thing because if you design the reason why we did mobile first is because if we just designed for the desktop and not on mobile it would look really pat on mobile so we designed for the mobile first that's part of accessibility so when we're doing that is it still readable on a mobile phone is the website easy to use and understand next one is operable operable looks at whether the user can access the website and find the information easily is the website a document able to be accessed by just the mouse or the keyboard can it be navigable by other things than the mouse so keyboard accessibility enough time to get things done being aware of seizures and physical reactions things like that so this is operable then we have understandable let me go back one can user get around the website or document user hang on we've got the right slide we're out of the way understandable relates to the information and the operation of the user interface which must be understandable is the information readable predictable and provide assistance if inputting information errors must be identified when inputting data and displayed on the screen in such a way ensures that it can be accessed so that's understandable one of the big things here and we're going to come back to this later because predictable is one of the big things about this and when I first learnt this predictable didn't make much sense to me you think why is predictable important in excess welding and when we're doing things we're used to things working in a certain way and if they don't work in a certain way if they're not predictable it might not work for you a good example of this was I was filling out a form there was a home show in Australia that we'd be my wife were going to go to I want to get two tickets or three tickets just have to fill out some information on the website I went through and said how many ticks do you want? Two. Cool fill out this information name, age all this stuff for marketing research that we're used to and then hit submit button hit submit, the form reset no tickets try it again, no tickets try it again, no tickets I couldn't figure out what was going on so if you're like me when you fill out a form and you hit submit and the form resets you think I'm done give me my tickets what was happening was because I'd asked for two tickets when I hit submit it cleared the form and at the very top it changed a little line of text which said person two and if you didn't scroll up you wouldn't see it all you saw was the form resetting so my predictable brain was saying I've submitted this form is reset it's done what they were saying is please give us more information for person two I wasn't predicting that and they weren't making it clear and so I didn't get my tickets I did eventually figure it out and get the tickets but I didn't understand how that can be a problem and then we have robust let me just go to robust relates to compatibility the website or document must be robust enough that it can be interpreted by a wide variety of user agents including excessive technologies that is when a page is viewed on different user agents such as mobile phones, Braille readers screen readers, text-to-speech everything can be interpreted and we do this as coders I remember having mobile phones and different browsers open and checking a website to make sure it all works on that we're used to doing that so making sure that it's robust enough that it works with screen readers and we're doing it making sure it works on mobile phones making sure it works on big desktop that's what robust is making sure that no matter what somebody sees the site on they can understand it it works so if you do have to get some kind of accreditation you would need to go through conformance now with conformance we go back conformance is there's three levels level A if you need to get level A you need to get all level A criteria ticked off if you need level AA you have to get all A and all AA and then guess what if it's AAA all of the above you have to get AA and AAA so getting AAA obviously the highest level and if you need to do that you can use the WCAG or web content accessibility guidelines to go through that process so there's all the boring stuff out of the way this is all the guidelines this is all what you need to do let's actually get on to the practical tips so design use high contrasting colours everybody knows that don't we I notice from a personal experience one of the first websites ever designed I thought it looked amazing everybody told me it looked amazing and then one day somebody called up and said I can't see any words on the screen and I thought they were crazy I'm looking at the website I can see the words and this person said no I can't see any words on the screen there's no it turns out they were colour blind and I'm not the best colour person in the world and I was using dark blue on black which looked great to my eyes and to people with good eyesight but with somebody of colour blindness it was just a black screen so that was my first lesson in accessibility I then changed all of the text to white problem solved contrast use adequate line spacing 0.5 so when you're spacing out try not to get it too close together especially for people just somebody like me with bad eyesight texts all running together can blur, make it very hard to read something simple like that is really good this is one of my favourite ones use text not pictures of text what do I mean by that sometimes it's a good example is just earlier I had the video that said disclaimer now if you did that on a website let's say I had that video to say disclaimer and I didn't put any alt text or anything around it a screen reader won't read it SEO won't read it I actually had a customer once who I had to rebuild her site because she had a sister-in-law build the original site for her and they weren't coders but she was an amazing graphic artist so she created the websites in paint shop or Photoshop and created these beautiful pages beautiful text, butterflies really amazing save them as jpeg put it on the site so the whole site was a jpeg and then she came to me and said I can't get any SEO, Google does not see my site and I went yeah that's because the whole site is pictures and the pictures were image 10476 that's all that Google saw no content so when you're putting content on a website if you use a jpeg or an image to relay that text and nothing else SEO can't see it screen readers can't see it people can see it but some people so that's what if you do have to use a picture for text make sure you've got alt tags descriptions, that kind of thing another important one don't use color alone to convey information so what do I mean by that think about traffic lights traffic lights red, orange green, red stop orange go really fast to get through the lights green go anyway think about somebody with color blindness what are they going to see really severe color blindness they're going to see free lights so using those colors to display information for them is useless I found out that color blindness people actually the traffic lights are universally in a set order might be different different countries but in that country I think it's universally like across the globe they're in a certain order so when the light comes on somebody with color blindness does the top it's stop it's in the middle it's yellow at the bottom it's green so if we do that for websites and somebody's got color blindness they don't have the advantage of knowing the sequence or knowing the code to do that so if you're using color alone to say stop or some kind of a message with color you've got to remember that some people aren't going to see that as that so I'm going to skip a little bit ahead because I'm going to talk about forms later but forms once again when we're doing forms color sometimes we use red to say change the text to red to say that that's gone that's not right somebody with color blindness won't see that so using color alone can be a problem alt text in images alt text is there in case the image doesn't load that's the original reason we had alt text if the image didn't load there was a description of course we use it nowadays for screen readers also SEO SEO picks up on that so it's very important to use alt text we use WordPress well I hope we all did but we're all here for WordCamp WordPress makes it very easy to add alt text so we need to use it if you're not sure when to use alt text and when not to because you don't always have to use alt text if you go to W3org there's a really good alt text decision maker it takes you through the process of what is this image, is it decorative or is it actually relying information that needs to be told about so you can use this tree or this decision maker to understand when to put in alt text and when to maybe mark this as decorative and let a screen reader bypass it form best practice we talked a little bit about the colours so making it predictable I talked earlier about that form I filled out and it wasn't working because it wasn't predictable with screen readers making sure that the labels in front of the text box or anything that needs to be interactive with if you put it behind it might look really cool to design one putting the text underneath but a screen reader is going to see an empty box first and then the description second and it's going to confuse people with a screen reader so make sure you use form best practice I did see an article the other day that pretty much all the wordpress plugins form plugins have accessibility built in so that's good but you still need to have manual intervention make sure that you're setting them up correctly there's also the new web accessibility initiative accessible rich information informed internet applications this is really good for putting in information metadata around things being able to show the screen readers and show SEO and all that different things about the website in a code level so familiarising yourself with this is really important to code things in and show screen readers and accessibility devices how to interpret the website correctly this is one I was told to make people very much aware of beware of accessibility overlays I don't know if you've seen an accessibility overlay there's plugins you can get for wordpress and it says this isn't an accessibility overlay which will help with your accessibility a lot of people think that adding this plugin or this system instantly makes your website accessible but it does not they do help in some ways they can put in buttons to make the text bigger add contrast and things like that but they're not going to fix a lot of the problems we've already been talking about fixing your forms making everything accessible from the ground up and we're seeing a lot of people using these overlays and thinking that their site is successful when it's not and even I've seen companies or groups that are helping people with disabilities and they're not accessible because they think they're accessible because of these so be very careful not saying don't use them I'm saying don't rely on them to do everything and if you do all of that you will if you go searching for it you'll see what I'm talking about now I'm at times up so I'm going to have to go for it really quickly don't let them start by themselves if you can help especially if it's got sound make sure you've got controls to start and stop make sure that you've got captions if you can all those things main thing is don't just let videos start with full blast of music that really annoys people especially people with screen readers because they're trying to listen to the screen reader and it's interfering don't test this yourself when you're doing a project you always get people to check your work don't check your own work for accessibility get somebody outside of the project if you've got a lot of people working on the project get somebody outside the project even better still go to a consultancy there's a lot of accessibility consultancies out there who can check your website for you also train you on accessibility and do all those things which brings me to this slide a massive thank you to Narell Gaddy Narell did a accessibility webinar from my company and that got me interested back into accessibility I did a course with her on accessibility to learn a lot of this stuff but she I wish she was up here doing the talk because she's very passionate she has a visual impairment and her company helps other people put accessibility into the website so when you are doing websites and if it is really important to use a consultancy if you can or somebody who maybe have a disability vision impairment and hearing impairments mobility impairments anything like that to test out the website in a way that you may not be able to and may not be aware of how the problems are so quickly in summary we learnt why why should we be doing this for lots of reasons not just because of disabilities but because we want everybody to enjoy our websites when get in from the very beginning don't wait till the end because you are going to have all this technical debt and all these problems and it's going to be too hard and you won't do it and how there's all these ways to do it we've got the WCAG guidelines but also just use common sense like how do I access a website what really paves me off when I view a website and I can't see any information think about how you interact with websites and how you can make it better and just quickly before I wrap up in October I believe it is 9th and 10th of October there's the WordPress accessibility dates a 24 hour online webinar conference I've actually been invited to be one of the organisers this year which I'm very proud of so if you want to learn more about accessibility and hear some great talks about that in October it's a long way away but please remember it and that's it thank you very much for listening to my ramblings my name is Ricky Blacker and I wish you all a very good word camp and hope to see you all around at the place thank you, thank you now the stage is open for questions and answers we have a few minutes for the Q&A yes we talk about accessibility we typically talk about people with disabilities but I've also noticed that older people tend to have difficulty in using websites so does accessibility consider that that's what I think that was the point I was trying to make we focus on people with disabilities and rightly so we should be accessible for everybody but we tend to focus just on people with visual impairments and mobility issues and hopefully we are but we then neglect just general how to access the website just for normal people those examples I gave were of me trying to access information on the website and I've got no disabilities well I probably have all of my hobbies is probably a disability but that's all my time and I wear glasses and if I take my glasses or if I lose my glasses I struggle to see websites but even just normal normally accessing websites on a day to day basis we've got to make sure that they're accessible to everybody we've got to focus on how easy is it to navigate can they get to all the information quickly and easily and can they get the full experience without being hindered and sometimes when we're designing like I said you're in the project and you know how it works because you designed it and it makes sense to you but if you go outside of that and you get somebody who doesn't know the project doesn't know the website to test it they might find the chinks in the armor that you didn't see that's why we have user testing because it allows us to get somebody else to see outside of the box outside of what we're seeing so yeah we have to look at all the aspects of accessibility Hello Ricky very good talk, thank you I have a question in regards to sometimes when it comes to the needs of say a business to design a website and maybe even especially small businesses they have an opinion on how they want to present their brand and they have an opinion on how to you know say they have already a brand book or they have a logo or something like that how do you approach the conversation of we do need to design accessibility first when they may have an opinion on what they want the website design to look like or interact or be interactive like like they have an idea and that is the big thing I think that's where we're seeing a lot of the issues it comes back to like when do you bring in the accessibility and also how far do you go I think if you have a particular brand and you've got a certain way you want to show your website but it's not accessible is it really doing you any good because there are I mean conversations with people with disabilities and they've had trouble accessing certain sites and people here's the thing as website owners or designers we assume everything's okay because people are viewing our site how many times when you get a website and it doesn't work for you do you go to the person who owns that website or to the company and say hey I couldn't access your website we don't we just go to the next one because there's hundreds of websites out there and a lot of them are doing the same thing so whenever we come up against a barrier we don't say to somebody hey can you fix this we just go look for something else so where a lot of these brands might have their look and their feel and that's the way I want to be but if they're losing customers because of it they'd rather have that over accessibility they may not know that they're actually losing customers and that's I think that's the point we don't know how many people when people are walking past a store are they walking past because they don't want to shop there or because they can't shop there Hi Ricky That was a really good talk Thank you I felt like it was very accessible how to make it as accessible as possible Yeah One of the biggest questions I have and it's very important I hope you can answer it very honestly how did you find a wife that bought you a drone I'm trying to get my wife to buy me a drone she doesn't want to have anything to do with it I don't think that's very an accessible partnership So how would you deal with that Well, it wasn't very smart on her part because she was already complaining that I had too many hobbies and she bought me another one So do I need more hobbies You need more hobbies Excellent, thank you No worries I have a question for you Ricky So when we talk about accessibility when you do the compliance at the end the companies can put one line in their budget including accessibility, compliance or accessibility audit and so they can say $150 $200 or $300 But when we go through the whole thing about building with accessibility right from the start then we are talking about one extra person on the team or extra time and that increases the budget how do we convince businesses to spend a little more time for accessibility The budget impact I probably should have elaborated that more on the economics side when we talk about what's the economic thing there is also a negative obviously if you're spending more time working on accessibility if you need to bring more people in more consultants, if it's going to take you longer there could be a negative impact on it but then what is the positive anything we do there's a positive and negative and okay, yes we might spend more time on accessibility like I said, if you start from the very beginning it's probably going to cost a lot less than waiting until the end and trying to retrofit accessibility into a website that's already not accessible if we're starting at the very beginning and working towards the goal of accessibility it's going to be a lot cheaper and it's going to be a lot better also once again, like I said you've got all these people that you may not even know aren't viewing your website because they can't and so you're losing for a brand they're losing customers without even knowing it and also it's good in this day and age we want to be accessible so it's good if a brand can say we have gone to the trouble or a company has said I've gone to the trouble of making this website accessible and please let me know if it's not because I want you to access my website so it's a positive image as well so I think the impact the positives even though it might cost you a little bit to start with I think the positives way outweigh that cost Any more questions? Any questions? So I thank you Ricky now we can see Ricky is really good looking, handsome man but when we hear him talk we hear his passion about this topic and he's very knowledgeable so thank you very much and no wonder they call him Mr. WordPress in Australia Is that what they call him? Yes, Mr. WordPress from Australia Thank you very much Oh thank you very much Thank you Yogesh I'll give you the money for saying how good looking I am Thank you Thank you very much everybody Now we have a short break It's 5 o'clock for the next session Good evening good people Our next session begins in 5 minutes Good evening everyone Okay, so here we are with our next session So we all know that the world it rests upon a giant turtle, right? But do you know what what does that turtle rest upon? Is turtles all the way down there? Okay, so just like WordPress He blocks all the way down there, right? Or maybe Or maybe not, is it? But Tammy is here to tell us that you know, blocks is one part but the blocks can make patterns and patterns can make I don't know, pages and different things But how do the blocks and patterns and everything stick together?  But Tammy is here to argue that, you know we have the Roman concrete Roman cement of designs and other things which puts all these things together and make WordPress a beautiful place that we know occupies 43% plus of the internet, okay? So Tammy here is a product creator focusing on WordPress and creates products along, helping those and helps other people who are creating products. So she is a product expert but she is from a hybrid background, so this is like very interesting personality, like you know, you look at Tammy and say, oh, this is a product person, but you see there are many facets to Tammy she is a product design and psychology and development that makes it very very interesting. She contributes to WordPress and is passionate about open source, community and tea. Now this makes very interesting person talking about convincing us that WordPress is or maybe not blocks all the way down there. Tammy So thank you very much. So first of all hello. So when someone talks about interacting with WordPress, they are typically talking about the front of the site the elements. We might think of it as a post editor but often it's the site itself and this has evolved and in this talk I'm going to go through what are those elements. How did we get here and maybe where are we going and how do we create things and I'm going to look at some possible future considerations and some hopes at the end and these are going to be for some very personal hopes as well. A lot of this talk is going to focus on themes and extensibility due to these elements being front themselves. And at the end I'm going to share a link with some resources that I'm hoping to grow and encourage checking them out. So the WordPress way is something said a lot and it's something said often with a positive mindset, often accepting that something just works because it's always has in WordPress and we say it's a great path to follow and this has been the case for many things over the phases of the editing experience, from easier editing to customization that has been easy but not taken advantage of because it's been presumed that things maybe worked a particular way because that was the WordPress way that things worked. Processes are also built to work around the WordPress way to accommodate those edges and hitches and when you think everything is always going to be the hard path you are constantly braced and this can have an interesting mind flip when something is actually easier. You don't trust it, you find it a little bit suspicious that something could be that easy but it turns out it actually can be. So changing a theme should be as simple as changing clothes and you should be able to slip in and out of them not losing any content or any great changes and this is quite a generalization but the reality for so long has actually been it's more like changing clothes and kind of removing your head rather than doing anything else. To add to this that themes and often plugins have been an eraser to the bottom of options. You can call it a framework, a builder you can call it whatever you want but even the lightest of intent was burdened by having to support 101 options. All of these with varying interfaces to those interacting had to learn countless colour pickers, endless background settings, the list of interfaces they stacked up to dizzying combinations and heights and plugins often have key interactions like styling for example primary bed ends be different from the rest of the experience because they don't know and then it breaks it so someone doesn't know what they're doing at all. So far the elements I'm going to kind of talk about are kind of simple but there's a hidden design system as well and what does that really mean? Well all too often when creating with WordPress what can or can't be extended and the opportunities are often isn't known. This makes the seed and ever flourishing WordPress design system itself feel to many hidden. The system makes the blocks makes the interface everything you see in the editors and beyond that is the system. There is a design system in WordPress it just feels more hidden than sometimes it should be. This isn't a design system talk though that would have a really different title but due to that close nature and the fact that the elements use this I'm also including that point. So in the fact it kind of felt simpler but that was because it was a known path that we were on. You'd have a theme. You'd add plugins to that theme and likely some custom code as you needed it because some CSS was a normality and to many experiences snippets were shared far and wide that you'd grab and then you'd put them in or you'd have your kind of repo of snippets that you'd always use on every site. Themes however got larger and larger and larger with the boundaries around the plugin and the theme blurring. Plugins were also getting more and more complicated. Pulling in libraries and grabbing in frameworks to accommodate and stack up on these interfaces. The product stack has become unwieldy for many experiences. On phase one of the work that's been done recently saw the foundations laid so the elements could take advantage. It wasn't really until the customization phase where this flourished though. A system was forming and the language around was growing component by component. It's also worth saying that with projects like this there's a term for iceberg projects which is what you see is not maybe what you're kind of experiencing. There's a lot of this foundation work that needs doing first and that led to a vast amount of work that needed to be done and there's still a lot of work that needs to be done so there today feels like a new energy around creation and I don't think it's just me that feels this. That's great, but I've got this far without me kind of explaining what are the elements and I want to do that. What are those elements and how do you even start to create them? If site editing is a sliding scale where do you work and how do you do that depending on what you're creating for and how can you start taking advantage of these? So I'm going to take a look at each of these elements and they are blocks, patterns template parts templates and styles and how they all add up to create a site. So blocks are often what we focus on. Maybe wrongly or too much and I'm kind of going to explore that a little bit. A block is the smallest amount as it's kind of that it says here it's that abstract term to describe units of markup. Quite a statement that. When added together though they form the content, the layout of the page. They're often what we think of after all everything is a block is said frequently so they're what we think of. So block literally make the block editor not just by name they are foundational. Design tools are block based and focus on interfaces that hook into specific blocks powering them to combine styling. Blocks are powerful but they are the foundational element and they are where it starts not where it ends. Patterns are often what people get and understand. So if you close your eyes or someone else does and you start to think of a site you're not seen in blocks you're generally seen in patterns that's why patterns are so powerful. These are a collection of blocks often arranged together with intention because you have to actually put them together and often opinionated with the styling attached to them. Patterns have unlocked and empowered so many people and again it's what we understand when we see sites. The pattern directory has brought some incredible visual freedom and opportunities. It has also brought a range of options to those creating themes and experiences to extend and include. You can even make art and there's a museum of block art using design tools so you can even kind of start to explore and create. There's a styleable and they even now come sinking. It's kind of a great marketing sign but they do. Patterns are a pivotal element but that's just one of them. A template part is a smaller section of content that can be included often across a site but in one or more templates. And I will add that to more common use cases are more than one for this. So when you think of a template part often you'll think of a head or footer but you can think of more things like this like post-meda or you can also think of a sidebar as well. Template parts also within the site editor they zoom in. That's a really great feature because you can go into it as well which is really great experience to know as you're working on. So templates often considered to be the top level if you see styling as the wrapper around it. Templates are often in this quote considered to be one of the most important texts of themes. I'll let everyone debate that. They are the files where everything comes together and we all know about the template hierarchy after all. They are tried tested and known. So templates now have a new lease of life and be able to create more easily than ever in the site editor. Along with that unique ones can be spun up and exported into your theme. And styling well that's this really really simple word but in simple terms it connects something like the theme JSON or I often think of it as a recipe file of your site. It unlocks styling opportunities previously you had to know code to achieve. If that kind of styling recipe then creates these interfaces and says I'm going to use this bit and I'm going to use this bit. So there are styling variations that mean a lot of the time you might have thought you need something like a child theme. You now don't have to do that because you can just do styling changes. Design tools provide consistent unified interfaces for a range of styling functionality and it opens up a whole world of potential combinations for many more. So that's the elements. How do you actually use them? I'm going to take a look at that. Take a look at what's possible within current WordPress and it might be a product or it might be a theme that you want to ship that adapts to any use case. So I'm going to look at two particular things. I'm going to look at with and for. So with is any possible current WordPress feature being able to be used. It might be a product it might be a theme that you want to ship that adapts to any of those use cases. It works with all the features on. So for is going to be crafted to do a job of a particular state. This might of course be a plugin or a site. I'm going to kind of explain that a little bit as I dig into those. So if we're looking at this when creating for everything on or for as many features as possible you are not typically aware of the boundaries of the setup that the site is going to work on. Anything could happen. Any site this could be put on. Typically you would be using as much native around the site editor. The same goes with the block editor. It's worth noting the distinction between the two editors that I'm using here because I think there's two distinct experiences as you go between them currently. Templates, you'd have all the defaults and often a front. Template parts, you probably set up a range of those including header, footer and often meta as well. Style variations often these are going to be used and all core blocks are going to be styled and typically there would be quite a few as well for patterns. Custom blocks probably aren't going to be used if you're doing this but you're probably you could support optional external blocks when you do this. Creating with is creating general and widely using as many features. Looking at default themes is a really good example if you're trying to learn how to do this for example. This is very much as everything on as possible with the unknown implementation of what you are creating as the system. For any plugins or blocks that you are creating with, they're actually going to have minimal styling when you do this as well. So, four depends on the product or if implementing. For example, if a site or a client or depending on the scale would be different to creating a custom product or for a single use. You typically start with the design system when you're doing this. If you're creating a simple site focusing on a simple job to be done, this is pretty easy. It's a pretty simple task that you have. But that starts to get more complicated as you scale and you start to really have to focus on the task paths that are going to be used. Templates and template parts and patterns are very much going to be use case based. What are the jobs to be done? What are people trying to do and what do you need in this case? It's typically going to be the branding provided by the client. You might use a style book to be used to display it. Custom blocks probably are going to be used in this case. If you're an agency, maybe you have a bank of those that you're going to use in a companion plugin, for example. The editor or specifically often the site editor is as much as part of this custom experience. You're going to be looking to scale depending on the extent and go beyond. This is going to be quite a custom experience when you're doing this. There are still a range of options for themes. When considering what to pick, all are valid depending on what you want. Framework, page builder, classic block, all have a place depending on your workflow. That's again looking at all your options and deciding what you want to use for your needs and the needs of what you're creating. Often for those interacting with themes, the most effective are those that get the job done. And that's a really important thing to think about. This idea that you can just go to one place and just be able to do everything with everything, that is actually flawed if you actually ever see someone try and do everything with everything. Themes, however, are today being allowed for the most part to get back to actually what they're curiously good at, which is being themes. They're actually really good at focusing on not trying to be a plugin. There's a strength in themes when they do that, a weakness when they try to do everything. If you create using the site editor, a site, lay down a foundation perhaps, maybe using a theme JSON or the create block plugin, a create block theme plugin, apologize. It can truly feel like using Dreamweaver. Realize I'm dating myself a little bit with that term, but that's okay. This is incredible way to work and I would encourage anyone to try to do it. You're working straight with the real things and it's actually quite freeing. You get to use the elements to create with and it's really work as you're sketching and creating tool. In this flow, you would export at the end of it, so you kind of use it as a prototype and sketch and I do this quite a lot and this is how I create my themes when I'm working with them and I'm trying to prototype. I finally use this way more than a design tool now and it's really effective. So there is a misconception that everything should be a block when creating or everything should be a block in general. As mentioned before, when people think of a site, they're often thinking of a pattern, not of a block. The same goes for creating. Often, it actually just needs to be a pattern. It doesn't need to be a new block either. It's actually probably already a block that exists. There are missing blocks so there is a project in core and the idea is to have repeated blocks that can be supported and that's going to be amazing because if you think, the example I always go back to is the accordion block of how many different agencies probably have their own accordion block and how many different freelancers have their own accordion block if they could have one accordion block they could use, that's quite a sentence. It would be amazing for them to be able to come back and even have variations. But even some of the suggested blocks for that some of them are palants, they're not blocks as well. So being able to consider whether something actually and critically looked should be a block or not is really important. Some themes are going to need functionality and that's where considering letting the thing get back to just being a theme and putting the functionality in a plugin comes in mind.  Unfortunately, we're in a place where a lot of plugins are really hooked into those themes and classic themes have kind of made us into that habit of doing that. Themes and plugins do serve distinct purposes and the hitches and the problems come when they get twisted and merged into each other. Creating is great using just the elements but what is even more incredible is going beyond extending those elements and pushing them into each other. This is where you start to make decisions on how far to go and what to adapt and not even to adapt based on knowing the system. So I already shared about the design system the components and styling and the interface patterns in WordPress. So knowing these allows you to choose what you can bring in or what you don't want to. One aspect of this relating to themes are design tools. Design tools terms the interface to theme JSON. They allow unified tools for spacing, colors and much, much more. This is not only incredible empowerment for creating those interfaces but it allows those that make themes be able to rely on those as well. You can depend on them, you can use them and know that they are getting refined and improved in core as well. Once you know what can be done with the design system and can be extended to what not to use or what to use really it's about knowing those boundaries and then utilizing them in your system and don't presume that it's not available it just kind of it might be being worked on as well it's about that kind of knowledge as well know the elements know when you can use them in your site and this works both for kind of information if you find that there's something that you might want raise that information to the people that are creating it because that might be able to put it on the roadmap as well that might be useful. The scales is the complexity of what has been built happens though for example enterprise sites but it also applies to someone wanting to create a product knowing what can or can be extended in the experience is vital as far as core goes being able to iterate and extend and have that extensibility and improve based on that feedback is key as I said if knowing something isn't known then it's not going to be so there actually is on GitHub kind of some project boards and a tag for extensibility issues and things like that are really important to know what people are creating and know what the barriers that they're hitting and know how that they are creating with in order to do that people need to start creating with them so it's kind of cycle as well often it's hard to see the importance of the foundational features like things like the interactivity API but these provide the grounding that they're being built upon remember I said about the iceberg you sometimes don't know the importance of the things that are foundational a good example is mega menus the example that it recently showed how important all this work is to be able to retrieve things like that these are the stress cases I call them stress because they cause people stress when you don't have them rather than use cases that enable more people to be able to use block themes more people to use these things it's easy to focus just on the visual front thing when creating a site I would encourage thinking of the entire experience what do the styles look like what flows are the editors going to use and the different experiences might you need for different roles what patterns are even going to be visible or not if you are making blocks think of placeholders and primary and secondary and placing of options don't all just put it in the sidebar I also think to craft the experience that the job needs to be done also one WordPress doesn't suit all and it really shouldn't extension and adapting of the experience can and should be done by those working with the elements it's also something to consider in anything that you create not just set and forget so I've looked at the elements the now but what about the future how do you take everything about that and beyond and what does even that mean I hope so it's already started with the maturing of concepts probably one of the foundation things that's happened and benefited so far is this this has helped and continues to make things clear helps is implementing but it also builds trust if you can understand something you can trust it initiatives like the WordPress developer blog have helped along with hallway hangouts and triage focuses because they've helped with understanding clarity and to find things actually having a definition for something was really really useful and using the same word for something is also really useful defining terms that said it's a path to maturity not one that is complete if anything it's a path that underneath again it's not always visibly seen initiatives around its sensibility and interactivity all these improvements give more to literally extend and build with a lot of the missing pieces previously that had to be worked around that WordPress way there's a lot of course around those gaps in classical older bases but that comes from conversations from saying what you're building what the hitches are and then surfacing those hitches because they might not be aware the work going on beyond just the editing experience is important this takes all the learnings and thinking of the system into more areas it literally gives more to the ego pieces to play with which is so amazing it also brings iterations and improvements to the pieces that maybe felt that they were needing kind of that extra iteration you can go back to them as well it also provides the opportunity to explore to know to give feedback and understand how maybe this component needs to adapt and have these kind of improvements brought to it having unified primary buttons makes sense for someone who uses the admin interface of WordPress but giving that information and knowing that and then being able to take care if you use headless and not using it again maybe it's not so important for you but you want to be able to attach those styling so giving that information and being able to use those components in the way that you can use them is really important as well so knowing when a component needs to be free of styling or when styling can be attached to it is also really important learning about those flows and also from a creator's perspective learning when you can use native components when you shouldn't use native components all of this and the ego pieces it also is benefit from existing patterns and you can request that maybe these patterns you use repeatedly and could these be in core as well so this is where I'm going to start to dream a little bit of a future and hold a big invisible sign above my head saying thoughts my own blocks are amazing and projects to create more core supported blocks are incredible because they will help unify blocks and create things over and over again like my example of accordion but it's a really important one that I've seen so many created of however there are features that need to mature for those that creating sites and themes for those who are working with the elements currently finding some path for older things from things like short codes to many is really really important it's just a start and what that path is probably isn't clear and we need to have conversations about what that is as well my hope is for things like pattern variations and other things to be explored and for us to start having conversations about what could be great is also something that people are wanting to do there's a need for that and looking at how people could be able to be doing that with an interface as well the more we have defaults for things in theme jason the better the theme starts are always going to be for those that are creating themes as well and we have a lot of that already so we have that boost before you start so I have many hopes which is probably not a surprise but I want to start with a hope for growing the elements in the WordPress system when there is a kit and there's boundaries and styles defined in core or in a theme for implementing the elements this benefits the end experience core can offer solid defaults custom experiences that always be needed and there can be creativity can flourish the less considerations you have around which color picker to choose or which range control to use or to implement actually the more creative freedom you have it's known when you learn art that the more boundaries you set up actually the better art you can create and that's actually a lesson that we really need to learn trust can be built and grown with an experience when an experience is dependable and a primary action is the same throughout so someone can know what they're doing this is when you're using the system effectively it also means the standard of things and usability can raise up because we can have that quality control over them disparate interfaces are hard to learn hard to know and can you really trust that snippet that you got from a random site possibly you can takes a lot to trust and end user fully so some thinking has to be done how much you open the experience and that relies on the job to be done and that's a challenge to many in this space set up those safe boundaries and allow some play because safe playing and styling really is empowering to end users if you actually think there's a game quite an old game now one of the original Tomb Raider games and the start of the onboarding of that is you literally end up starting to you learn by playing and it's a really great example of onboarding so if you think about taking that into your experiences and it's how humans naturally learn allow that safe playing allow that learning through doing when I look back over the past few years and I see how those elements have come how much possibilities are now as exciting it's thrilling even it's also not done yet and we've reached a great point of documentation and solidifying of concepts it's a great time to dive in and it's a great time to explore those elements yourself A cautious hope is a hope for more opinionated experiences for less options at the start but that experiences and themes to really focus on jobs to be done and not think that all the jobs had to be done or all the time and not showing everything by default because honestly that just overwhelms this countless psychology experiments that prove that my hope is as you get to explore that you're going to share those insights because that's what we do in the community really well we explore those insights and we explore and we experiment we blog it we add a pattern to the directory or the museum of block art we push what can be done and report that bug we engage in feedback in discussion each exploration and question each conversation in the hallway track leads us to more understanding and conversations to better tools and more actionable pieces and elements for us to play with so to that point, thank you and this is my link I'm hoping to grow these collection of links as well and I'd love to continue any discussions that I might have sparked with anyone so please come and talk to me thank you wonderful session Tammy, on that note let the discussions begin now we have a few minutes for Q&A 5.45 we have to be out of here so before that let's ask as many questions to Tammy thank you so much for the presentation find it very interesting and very great to explore the element of WordPress I actually have one question regarding of my current work actually I'm working on maintenance WordPress website which has been built in 2013 I would say so it has been going through transition currently WordPress has moved into blogs and things but was stuck in the past so I was wondering how we can manage and think about what should be a way to go to a modern way because we know that the website that we're going to maintain going to go further into more years and if we still keep using the old technology I would say that it won't be very long lasting so I'm very interested in the point that you say that we need to consider which path we got to go for whether we should be using the element or the full one or other options so how would be the good start to see where we should go into making a website that it's been a long time ago into a modern version so that's a big question thank you first of all planning is just to take is it a site or a theme that you have but it's a whole site that you have we actually build a custom theme but it's like a child theme actually so you have a classic system is it a network as well so to take your whole network and just be like YOLO gonna convert it, that's a lot so you need a plan first of all plan first of all decide how much are you gonna do of site editing if you're not gonna do site editing so the minimum I would say is look at are your child themes do they need to be child themes could they just be style of variations if they are just doing styling then you could bring them back to be style of variations that's one example but again it's planning and first of all that comes with who in your group has that education just start by making a block theme start by learning and knowing how those pieces work look at the default theme as well because if you just jump straight in it's gonna be a lot for you to just jump straight in so look at 2024 I love that theme because it's such a good thing to learn from and learn how those pieces go together and then think how you're gonna do it for your case you're probably talking about a minimal conversion over there's a lot we could be like about an hour going through a roadmap but a companion plugin probably because you probably got a lot in your functions.php files you probably got several in your functions.php of your child files all of those kind of things so you need to look at companion plugins taking that functionality out of your themes as well and just looking at that kind of balance there's a lot there's no small answer to you but everything is possible for you to do and I would encourage you to start slow Theme Jason is a good place for you to start because you're just taking the styling out and just thinking about like what are your colours what are your fonts what are your little pieces that you want you don't have to have everyone in the editor moving everything around or if you don't want that for your editors you can turn on what you want and what you don't want as well thank you so much going back to your fantastic metaphor about how the constraints of what WordPress has become and the block editor can breed creativity and sort of thinking about the way that at least personally in my opinion Gutenberg does do a good job of gradually and carefully introducing new features so that we can test them before they become defaults in WordPress are there any pieces of this toolkit that WordPress has become that you do think have that continue to stifle creativity in some way or that we still need to rethink so the big one I think is we need more defaults currently in the Theme Jason defaults in Theme Jason I would love more the thing that I hear constantly is the worry of like opening things up in the editor and how do we control that how do we lock that down so easier control of flows in the editor role based controls as well like more and more and more I'm hearing that like we got locking yay but yeah pattern by pattern locking is very like it's a weird I'm visual so I just see a door with like masses of locks that's all you can think of and that doesn't really work when you're saying to someone to do it and there's so many like little backdoors that you could easily like fall trip into I don't know I found that there was just one that you could just trip into even if you thought you had it locked off and it may be a bug to do that but user controls, more defaults the tools that create block theme plugin I always forget the theme bit in that are amazing but if those have defaults I think that you spin up and you can say like types that would help there is still this feeling that a theme has to do everything still and it can't be ephemeral I think if we get back to the fact that themes can just be very light and just change and almost that themes are the style variations which is quite radical kind of thinking that's okay because there's so much in patterns and template parts the theme is the package that's like the thing that we're just putting it in the box and sending it off if we're moving it around but we add a lot of weight to it so there's a lot of words but the locking and the flows is a big one Starbuck as well that needs some work I think as well for people I have one question about elements you said the foundation is built by Brock right? so can I use this concept to extend for example a lot of multimedia for example movies or EP3 for different blocks and user can have the slider or effect to change so you could have a block for that yeah is that the question you're asking 100% you can have a block for that so one of the elements is a block yes but you could also have a slider within a pattern if you wanted as well so yeah I want to achieve that kind of design I have to combine with another plugin or I have to develop my own maybe JavaScript there are countless slider plugins so I wouldn't reinvent the wheel there there are countless slider blocks as well so you've actually raised a really good question always search first before reinventing it so I see time and time again people are like making a new block or making you this or making you that there are so many good plugins and blocks out there find them first of all on theme directory then the plugin directory have a look and search because they might be there for you and they're right in your dashboard that you can search for and there might be the ideal one for you there and also have a look depending on your theme that you are using and also have a look if you wanted just a pattern so there are default blocks you're talking about MP3 there are default media blocks that you would be able to use as well you kind of went into slider I don't know what functionality you want because that could be quite a lot but for default you also have like media blocks that are default as well in there in your system I don't know if I helped you I hope I helped you if I did not help you find me after so I'm sure many of you have a few more questions for Tammy find her in the hallways today tomorrow onwards mainly I think 545 everybody goes out so Tammy thank you very much there was a fantastic session it was a very technical talk but there's a lot for non-technical folks to take away from that and because really you explained the whole concept of elements the blocks and the patterns and the templates and how does the styling step in and where to put the boundaries and how does that influence the customer experience and gives creative freedom to the developers, the designers thank you very much wonderful talk and we have a small thank you


Good morning, cyber traders. How's everybody doing on this lovely Tuesday of June 19th? How's it going on? Good to see you, Grant. All right. Good to see you, George. Craig, good to see you. Don, Tom, Michael. Look at all these great names coming across. James, Gary, Craig, Lita. All right. So everyone all excited about this morning? What a great morning. You know, I wanna make a comment regarding about this ASTC. Like I jumped in early, I'm right here. Just kind of bringing my account manager. I still own it at $3 and I chased it at $3.68. I'm about 2,500 on that trade. But overall, you could see where it was. I chased it all the way down here when it finally made its pop. But just really quick, I wanna talk about that stock really quick. Guys, this is what pre-market is all about. You know, this stock right here, the ACTTC kind of reminds me of the... No screen, can we see the screen? Oh, hold on one second.  Don't know why that happened. All right, let it come up. All right, as it's coming up and broadcasting, looks like I'm broadcasting on my screen share for the YouTube and Twitter and Facebook, but it's coming up right now. But in the meantime, regarding about this stock right here, I just wanna tell you a little story, which it kind of remind me this morning. Oh, there we go. All right, so let me just bring this back over here so you guys could see it. Yeah, you could see right here, ACTC. I bought it at $3.68, and I still have the IQ trade at $17 up about 25,000 on that trade. Like I told you, that's a swing trade, not more of a day trade. But anyway, regarding about the ACTC, it's wanna kind of like, it remind me going fishing. Now, I don't know if anyone here has ever gone fishing, but I go to Montauk, I'll do some tuna fishing, I'll go out to the canyons, and it really, really stinks. You wake up early, you start at 5 a.m. in the morning, and for some of us, we wake up in the morning, I'm gonna like, you know what? And then it really stinks when you wake up early and you don't catch anything, you know? But you gotta keep doing it, you gotta keep doing it. And then you know what? All of a sudden it's like, bam, you hit the world's record, you got the nicest fish ever, because it's all about putting in your time. And this morning, we only had about maybe, maybe a quarter of you that were here before 8.30. And if you look at the chart right here, guys, and if I break this down to a one-minute chart, if you got in at, just came in just 15 minutes early, 15 minutes, you could have gotten in, maybe at a better price than I did, but you had $3, I owned it, I chased it at 368, I'm like, this something's wrong here. But even if you got in at 8.30 and you logged in at 8.30, you got at 5 and you're probably kicking yourself in the butt and I told you in the chat room, guys, buy one share in the stock. What do you have to lose, okay? If you can't buy one share, you'll live by 1,000. And short of, you guys are killing it, killing it. I always say early bird gets the money. We always say early bird gets the worm, early bird gets the money in the cybergroup room. So this is what I want to kind of make a comment. Don't worry about this stock. I knew you missed it. Unfortunately, we haven't had one like this in about a week. I thought that was pretty funny. Some people have to see this, but look at up 200% just in pre-market alone. Now a lot of you are like, what's the news? What's going on?  But listen, we don't still know how good and great that news is, you know? I've seen stocks that have great new drugs for cancer and stuff like that and they still don't go anywhere. You know, so listen, we're momentum traders. We're not speculators and stuff like that. So anyway, did a great trade on that and a lot of you guys did well and that's awesome. Now let's talk about, there are some new stocks that are moving this morning. We will check them out. But I want to talk about yesterday because yesterday, listen to continue, it started from yesterday. Let's talk about the GEVO trade. The GEVO trade, holy cow.  This stock went from $5 all the way up to over 20.   I don't care what it takes, just tell me where to sign. I want to be part of this room. I want to, and you wonder why we've been in business for 27 years. Where do you find a stock goes from five to 20? Andrea, okay, who thanks me almost every holiday, every time he sends me great cookies. You know, he made $10 on the trade, you know? Just give him a round of applause. From 10, and he chased it. He chased it, okay? So anyway, a lot of people did well on that trade. That was probably the biggest winner who made it. And I know a lot of you guys, I'm like to go, I need to go down the list who did well and whatever. I'd go $10 is pretty impressive in one day's worth of work. Guys, think about it. You buy a thousand shares of that stock, okay? At $10, a $10,000 investment, you sell it at 20. You make $10,000, okay? A day, you times that over the course of 52 weeks, you're talking over millions and millions of dollars. Some people ask me, like, how much you guys make? You know what? Come and join the room and you'll see. And you know what? We just had another one this morning because I told you this yesterday, if you missed a GBO, early burry gets the money. And sure enough, you got it just like in this one, the ASCT. Now, a couple of the big winners that we had yesterday, my God, the IQ, we're killing it. We're killing an IQ.  I still have the swing trade at 1743.  I mean, the stock, look at that chart. We've been trading it all the way down to here. Some of you guys, some of you day trade yesterday, did well, Kathleen actually made a buck on that. Give her a round of applause. So a lot of good stuff going on, man. A lot of good stuff. You know, every day is always a new adventure here at Cybertrain University. All right, so now just to kind of remind everybody, how do we do this? How do we learn? Guys, today is a very important day, okay? Today is the new cycle of the Cybertrain University courses, okay? So phase one is gonna start today. So all you bronze, silver, gold students, you gotta get into that class. Some of you probably know, what's the class? Listen, what we're in this room, you gotta understand something. You could have somebody could teach you how to trade, but if you don't know how to speak the language and trade in the trading room, you'll never do it. You know, you'll never understand.  But to learn and you're in this room right now, cause I know we have a lot of trials in here and they get in the vibe, they get in the itch, they're telling their spouses and their friends, hey, you gotta look what's going on Cybertrain University, look what's going on Fausta, look what's going on with all the great traders in there and all the instructors, what they're doing. You gotta understand how to play the game and it all starts by being in class. So I want all you guys, you gotta make sure, and if you're not in the room, in the class, call your education advisor at Cybertrain University and they'll explain to you, but make sure you're there. It all starts in class, all right? And not only that, but today at 12 o'clock, we're also doing traders talk where we have open discussion, make sure you send in your questions and hopefully be one of the lucky ones, we can answer them. Traders talk, very, very critical, very important. Make sure you're in that room also, all right? Very, very important. All right, now, what are we trading going into this morning? Well, obviously we got the ASTC, that's gonna make the watch list. By the way, the GEVO, GEVO is obviously second biggest percentage gainer again, that's coming back again. We made a lot of money on, look, it's gapping up again, right back to where it started. You thought ASTC might be good news, whatever, look at the GEVO. Same thing, making a nice move. The IQ is back on the watch list. Listen, everyone's sitting there crying, what's going on with the news? The market, President Trump just put $200 million in tariffs, what's wrong with this guy? You know what I mean? Guys, listen, this is great. You know what? Whatever goes up comes down. Let him do what he's doing. It's making great volatility.  At the end of the day, we're here to make money. So, you know what? Lot of stocks to big hits. This, you know what? But when you see a stock like ASTC, doesn't matter. All right, that one, Hoya also is also gonna make the watch list. H-A-Y-Y-A. Oops, I spelled it wrong. H-U-Y-A, another big winner. You can see that trade side by side with IQ. So, those stocks are still on our watch list. All right, there's a couple of the ones that are also popping up over here. This one kind of gapped up. I think it's just a buyout right here, up 28%. Now, you're gonna notice there's gonna be a lot of ETFs moving this morning, all due to the news.  Now, you know we're not a fan of ETFs, but in days like today, this is when ETFs make their moves. So, I don't need to go down the list of what to trade and why not, listen, they're all good, okay? So, it's not going to be a huge list. Ken made 70 cents on GEV already. All right, way to start the morning. Give him a round of applause. So anyway, you got a really good list that's going on regarding about brand names. So, second protocol, if you wanna trade a brand name, go right ahead.  Your ETFs. So, you could trade the market, you know, and I'm telling you right now, personally, the market's still going higher. This is just opportunities to buy, okay? So, when you get a nice little correction, it's healthy for the market, it scares out all the, you know, the amateurs and sure enough, you know, but we're not looking low-term right now. We're looking short-term, short-term is, there's a lot of money to be made. I just wanna remind everybody, you know what, if you did miss the ASTC, it doesn't mean you still can't go higher into the open, okay? And not only that, but most importantly, just make sure you logged in this morning. Now, did I miss anything I did not call out, guys? Anything that I did not put on the list? V-I-V-E, you know what? Vine is pretty good, Vine is pretty, you know, but it's starting to trend down a little bit. I'm not a great fan of that one, but it's okay, Segg. By the way, Segg, you just started, okay? Remember, Segg, forget about being in any position. Remember, we spoke yesterday on the phone, okay?  Just listen, get in the classes, Segg, and don't worry about what's moving. Believe me, we do this every day. And this is not like a one-shot deal, believe me, there's several that we trade over the course of the day, so don't worry about it. G-E-V-O is a target of 21. Well, listen, just remember, can't go broke taking profits, all right? But that G-E-V-O has been a great, great move for us. But remember, you gotta be a level, I would say you gotta be a fourth trader now with the G-E-V-O, so unless you level four, stay away from it, all right? Which you are. I'm here in the five category here at Cybertrain University, so it all goes by your risk to reward. All right, guys, listen, good luck today. We'll see you in class, phase one this morning, right after the market opens, so you guys can make your money. And then, look at that, look at the ASTC. Still going up, baby, look at that, beautiful. I'm up almost three grand already in pre-market. That is beautiful, love it. Early bird gets the money, guys. Like I told you, the market's not even open yet, so you can imagine what that number could probably be when the market opens up. We could probably see another $20 stock, right? Just like the G-E-V-O, who knows? But remember, can't go broke taking profits. And if you didn't get it, what do I always say? Buy one share, okay? What could happen? If you're worried about losing, you're in the wrong business. Good luck everyone, happy trading, enjoy, and see you in class.


marketplace is obviously going to be some potential disruption to getting staff into the office and also the knock on effect for suppliers. What we've been doing is about six months ago we set up a group to look at this and we've asked staff to be flexible in terms,  Beatles . First we want one ask them are they likely to be in the office are they likely to be in the office can they be flexible to in the office particularly canary wharf. Salisbury Squares is obviously less of an issue. We are also working through…well, maybe you could take…we will allow them to take an extra holiday, an extra day holiday during that period. The other issues is for suppliers, we rely on the suppliers to have their own processes in place so that they can get, for instance, a ti'n gallu ei wath oedd yn dweud yn rhaid i'r ffrifurus yn ymdodol, nad oeddwn ni'n dweud y gallwn ni'n rhaid i d wineg. Dyma, i ddysgrifetio eich fflexibillu yn tuio i fynd i fynd i'n rhaid i dd�fynu'n amlwg. Dwi'n rhaid i'r fflexibillu ein cyllid yn ddiogel i'r hunai ddech chi o'i gynhyrchu fan gwybod.


Good morning everybody, now this is Matt's, the one who started that thing. So I happened to create the programming language, and so many people, so many people using my language. I feel like I'm losing my league, but I didn't need a conference, so this is, this sounds great conference. And I believe this, this year's conference will be great. So in February 1993, as a scripted language for units, to the first floor, but now we are living. I just wanted to create my own programming language. I was a language geek for last, I don't know, 30 something years. Then when I was in high school, right after that, I started programming. So that was somehow interesting in programming myself, rather than programming something. So some of my friends are interested in programming and started making games, or using computers as their tools for research or something. Or, or does something to make money. But, exactly, I don't know why, but I find it interesting in programming languages. But then I used the programming language in basic. It was a great programming language, very interactive. But, you know, as a programming language, it's quite weak. So I started learning, I wrote a book about the language in the past, and I studied it. I read through the book, but I didn't have a computer to run my stuff. So then the compiler was so expensive. I don't know, 5,000 dollars or something. It was very expensive. So I could compile my program. So I just read through the book, write down the passcode program. So I considered myself learning the passcode. Interestingly, Pascal taught me many things. That the programming languages can be different, the pro-language languages. And the sound language is very strong in some aspects. The sound language is very weak in some aspects. Every programming language has its design, and its design has its own philosophy upon designing the language. So the language affects the mind, the thought, the way of thinking of programming. So the language design is kind of like programming. So that made me interested in programming languages. So when I was in high school, I decided. I wanted to create my programming languages. But back then, I didn't have any experience. I have no knowledge. I have no internet back then. So I couldn't do that. So I just write down my ideal programming language on the notebook. So it's very sad I lost my data notebook. I don't remember what that language looked like. So I wanted to create my own programming language for years. Then in 1993, I happened to start my programming. That's so fun. So this is the very basic motivation behind Ruby. Recently, a guy came on a web page on Twitter that said, he said, why did you invent Ruby? Where do you have it for? It was redundant. We didn't mention it for you. It was a waste of non-power that is linked to this resource. So many people feel mad at you about your work. Ruby, what do you think? Yeah, we had, there is some truth in it. It just, it was like, you know, we, indeed we have really resource. We only have seven billion people. Very limited. There are few around them called. So it's actually a limited resource. But it's not about like, we have no real resource. Motivation is the most precious resource behind great works. We are not machines. We need driving force to accomplish great things, like making websites. Motivation, like having fun or profit, making money. My motivation is love toward programming languages. So a lot of work. It's just working to love programming languages. Everyone has different motivations. Motivation is very precious to us. And it is the driving force behind great works. Since some people we invented for you, like Ruby after 4, it's redundant. We invented way way. They go ahead if they are even motivated. And when we introduce diversity, diversity is good. It requires a lot of, you know, the redundant works. But it might waste your time. You know, the diversity works. The different works may fail. So you work, but fail. So your time shall be wasted. But I think it's okay. I think it's okay. Just because if you are motivated, you have fun on that place. So you have fun. So it's okay. Just because some of you might like fishing. So fishing takes time. When you finish to get your bike back. But you don't say it's wasted. It's just waiting to have fun. So diversity is motivated diversity. It's a very good thing to have fun. And the world without diversity is unpleasant. What if we force people to focus on pearl in 1993? So we might have a better call. The world, the world. So the young programmer back then, me was forced to work on pearl. Instead of designing my own pet project. It's not present. It's like in the world of 1904, forced them to do something by their big brother. So diversity is kind of a cost of innovation. No one understands about innovation. So no one understands innovation. The people who have succeeded, who made innovation, don't know about innovation in general. The people who succeeded may not make next innovation. And a few people of course don't know about innovation. So no one knows. So each innovation has different phases. So only we can do is try to innovate. Most of them are failed. We try again and again until we make innovation. That's the diversity. That's the spirit of diversity. I think it's a good thing. But we need to create a future to raise the possibility of success. So a few days ago, I read a... So I think most of you don't read the Japanese.  So it says, I.D. survivors will be language designers, deaf interpreters, and high quality needs predictors. Sounds weird? His outline is, it will be fundamental literacy. Like writing and talking. And it can be done by everybody. So professional like us should do hard tasks. But how can we be language designers? That's OK. But you. How can you be language designers, you know? Me? Maybe you don't read all. But you can. I think, I mean, not the language. But more. Of pearl, brass, of ishii, or others. So if you google it, you can find a very interesting website named, Landis Linus, or Silicon. It's a quiz site. When you access it, it gives a bottle, a face ball, of the person who is also you with beard. Some of them are language designers, and the other part of it, Silicon, is quite difficult. Like me, I'm not in there. Not in there. You may not be in the program. How many of you have designed your own program? Raise your hand. But it's much more than I expected. Maybe 10 of them. Out of them. Two people? Seven of them. Ten out of them. You design code, you design API, you design interface, the other ones. We're not here, I guess. Dave Thomas once said, the program is a process designed on DSL. So the process of implementing application is designing and implementing your own DSL upon top of your programming language, like Ruby, then create your application on top of your DSL. So every process of writing application is a process of designing and implementing programming languages. So in that sense, you can be a language planner, but you should be language designers. So to create great programming, great education, so you should be a language planner. Two few people care about design. The world is a group of crafty designs. For example, shoe streets. A few years ago, I had, I bought shoes. This is a nice design shoes. I like that. The pair of shoes, but somehow, those strings loosen every time. So I tied up a game in the game, and I felt like I was wasting my life tying up my shoe strings. This is a bad design. Why on earth in 21st century, we have to tie up my shoes again in the game. So, I had time. So, I still... The shoe strings have this... They are better, should be better designed at the first place. So, the world is fruitful for improvement by starting a new project, a first phase of existing project called Make It Happen. So, I believe most of you here are programmers. Something involving programming in Brooklyn. I think that the reason we gather together here is that we can program. We can code. That is, we can change the world. So, code, make it happen, in good shape, we make it happen. So, make the world better place and be happy. I will. So, who was the last one here? Now we are here. It is dark, it is stormy, it is night, but in 1993, almost 20 years ago, I invented, I started developing Ruby. Actually, I named Ruby on February 24th, 1993. Since the programming language is some kind of virtual existence. So, name is pretty important. So, I decided that date, that date which I named my programming language is the birth date of my programming language. So, since then, it has, almost 20 years has passed. So, I had been happy for the last 20 years. It has always been more than, it has always been more than expected. When I started, I started Ruby, it was my project, it was my hobby. So, I expect Ruby users to be less than 100. Less than 100. Something happened. I don't accept process, something happened. So, everyone got interested in Ruby all over the world. Maybe millions of people right now is Ruby. It's far, far more than I expected. And then, yeah, giving a keynote before several hundred people is far more than expected. So, I will try to make the world better place by providing Ruby. It's not intentional, but you know, but I think Ruby will be better. So, on February 24th, 2013, February next year, it's Ruby's 20th birthday. We were less ritual as we announced before. Previous keynote in Ruby conference. This is the 12th, 11th? Ruby conference? The 12th. The first one in 2001, look back, and the first mention of Ruby 2.0 in 2001. The first Ruby conference. I mentioned Ruby 2.0 in the first keynote, in the first Ruby conference. In 2003, I mentioned Ruby 4.0 again. With the last keynote, I mentioned Ruby 4.0 in these conferences. In 2001, 2006, 2007, 2010, it's kind of like a good boy. This should be true. Of course it's not. Sadly, the guys in Japan is now working on Ruby 4.0, Ruby 4.0, and by compensating they cannot attend. They couldn't afford to attend the Ruby conference, so they had frustrated, so they had something to work on to ignore their stress. So they're working on Ruby 4.0 in this ending one, so I will see it in today or tomorrow. I mean tomorrow. Yeah. We are already in tomorrow. Anyway, the Ruby 2.0 will be faster than Ruby 1.9 that Koichi was working on it, and he is going to give a presentation on how the session and tomorrow I know. I'm not sure that Koichi Sasada will have a session about how to improve the internal version of Ruby 1.9 to reach more. It will be more reliable, it will be more fully tested, so more fun to use, and you will have the keyword for more arguments. So Ruby 1.9 can you can provide keyword arguments at the bottom of the argument list as an inline hash, but you have to decompose it in the call out, call inside by a ticklish hash. It's a kind of keyword. You can see it some way in some Rails methods. But it's so easy, so we automate that kind of decomposition. So you can find keyword for more arguments in the F argument list.   So, and we are going to have a bullet prepend, which provides some kind of method combination in a common list. So it is proposed by the Akuta hats, but we finally implemented as a module prepend. That means that module prepend includes the methods to that existing class of module. But module prepend blocks existing class of module. So the method will come before the four inline prepend module. The method in prepend module wraps the existing method. So you can replace the alias method change by using module prepend. So we will have something named refinement which is kind of like the main space for the monkey pattern. So you can wrap the monkey pattern in some module, some refinement. So you put up where you are using the refinement in space. So the monkey pattern is only available in that scope. So this moving tool feature will be explained in a session named I don't remember the exact name, moving tool in real, on real or something, yeah, today. So if you are interested go there. I believe that there will be extensive explanation. So you can join us the team or effort of making Ruby 2.0 by using trunk and I mean guitar, Ruby, trustworthy or from the solution mainly first week. By reporting bugs, we have bugs on Ruby 2.0 so you can report them. So you may have some kind of validity issues from 19, so we consider basically they are bugs. So we will try to fix. So by fixing bugs you can fix, it's open source. You can fix bugs by yourself if you will. So we will report them. So by setting we are acceptable like this by putting a project in Ruby 2.0 and tell them my project is working Ruby 2.0 now but I need trunk now so it will work on Ruby 2.0 We can make it better. We can make the world better and we can make the world better. Recently I worked on the last year's Ruby. So Ruby is something in the mini Ruby or embedded Ruby. So it's a Ruby of kind of implementation of the subset of the language on to the embedded environment. So we resource like less memory or sticky power or something. So this is very compact it actually runs on very teeny ball computer with few kilobytes of memory comparing to the MRI, 2IS, few mix for the memory. So memory is very very compact. And then we will have some kind of memory, mobility which is the memory extension to be able to write iOS application. So we will have a session on that. So summary model, will you go behind me? Who has invented it? Will you invent wheels? Fix two strings? Bad designs? The improvements have gone past. So make the world better. I believe you can. If you don't, it's okay I don't need to be at the hiking. Thank you.


The Russians are relying on old T-55 tanks. Russia massively removes old T-55 tanks from storage and sends them to the front. Most likely they will be used as an auxiliary weapon on the second line. This was stated in a CNN commentary by a military expert, former US Marine Robert Lee. Some of these tanks will probably initially be used in the rear. So the tanks will not necessarily go forward but rather they will shoot from a long distance, he said. Military historian and weapons expert John Delaney in return suggests that the Russians can use the T-55 as a stationary firing position. You can use this tank to protect the front line from a counter attack, he said. Another reason to send more than 50-year-old tanks to the front is their ease of use, which is especially true when poorly trained mobilized ones begin to form the basis of the Russian army. At the same time military experts state the obvious. Faced with more modern tanks, which Ukraine uses in the counter offensive, the Russians will inevitably suffer very heavy losses. The use of the T-55 in such circumstances experts consider a step of desperation of the occupiers.