Am I on? On? Oh yes. Hi. Welcome. I know it's Friday after lunch. I'm trying to stay awake myself I apologize if my voice is a little bit going out to a karaoke bar the evening before you give a talk is not a good idea so Thank you for having me so my name is Mikey and I am Having trouble with my clicker So I'm a technical writer for Red Hat I've been a technical writer for almost seven years now. I document OpenStack before that I documented JBoss I've also been involved with Feed Henry. I am a scrum master Don't hold it against me. There are advantages in that in my ever-decreasing spare time I run the European chapter I guess of Write the Docs, which is a documentation community I talk about docs in developer conferences like this one and I also organize Django girls workshops like we did here in the beginning of the week I also coach Developers and open source projects on documentation. So we actually had a help desk with a couple of my esteemed colleagues On Wednesday where we into we had people coming in and getting some advice on their open source project documentation And yeah, so I don't sleep very much I'm based in Burno check Republic. So it kind of makes it easier to get around So why am I here? Why did they put me in this gigantic room? and Brought me all the way over here to your Python because apparently some people think that documentation is important And it's important to me. Obviously. It's my job. Otherwise, you know, if I didn't care I wouldn't be doing this for a living But it also if you don't do this for a living, you know, our users are the ones who have to use your software, right? so They care about it because it helps them get a better experience it, you know, the people who create the software It also helps them because they get to Be able to showcase what the software can do and for the organizations for the communities so It used to be and it still is to varying degrees, right? So like Documentation has kind of been a thing that happens to other people Or it just kind of happens magically But thankfully This thing is a bit finicky So thankfully there's been a shift over the last years last few years where people understand that Your content that accompanies your software is basically a part of the whole package, right? So you have your software you create it you test it you support you document it and then you deliver it to your users So how do we help the success of a software project, right? First of all, how many people here write documentation for a living or as a you know in a project or something like that on a regular basis? Hey, it's not bad cool. I was wondering where everybody was So There's that's kind of there's a lot of different ways of breaking down How things can help how documentation to help you, but mainly it's you know, you want to improve the user experience So, you know content any kind of content could be your user guide could be a read me It could be UI strings or an error message, right? All of these things are Pros that accompanies your code, right? So the so not only that but you want to create A portable and adoptable workflow for how to actually create and use your product, right? So if you have internal processes in your in your project or in your company You want to be able to train people that you've never met in person, right? So it's you know the easiest thing to do is to sit down with someone and be like, okay This is how you use this, you know the software or this library or whatever it is, right? But you want to be able to create something scalable and to create something scalable in today's world You got to be able to give people some text, right? You mean giving a presentation, you know going to events like, you know doing some I don't know consulting in a company or something like that though. Those are great But like you want to be able to reach the people that you can't do in person So join the Docs Club, how do we get there? I've broken this thing down to the three sort of Themes that from my experience Make it like you can do a lot with not a whole lot of initial investment Like you can do this effectively, right? You don't have to just you know, if you're a developer You don't have to you know retrain as a technical writer and you know spend tons and tons of time learning So there's a lot of things that you can do pretty effectively So the first thing that I'm going to talk about is content strategy and content strategy is actually like a marketing web development term that's being slowly applied to the field of technical documentation and It's basically about asking the right questions before You document something, right? So I'm gonna not be original here I'm just gonna use the 5w's because that's what everybody knows, you know It's a very sort of global way of grouping it So the first thing I want to know is who are my readers, right? So, you know, if we're talking about things like personas, do I I'm not I'm referring to end-users developers administrators Business analysts, whatever, right? You can also divide the users according to skill level So is this project is the software going to be used by absolute beginners? Is this something that?  Writing this content to right. So this is also an indication of who your software users are right. So You can also do you can also break down the users according to geo You know some, you know, you talk you talk comparing like the Americas versus Europe versus Asia-Pacific, you know different people need different things And so the next question is what do they want to know, right? So for example if I'm writing Django girls tutorial, right? I Don't really need to give them the entire history of Python and Django and like just get them into deep dive, right? You want to get them the information just enough information that they need, right? So if they want to get started learning about About Django via the Django girls tutorial what sort of information do they need? So I will create a tutorial with a very very slimmed down version To be able to be digested more easily, right? So if I'm documenting let's say a very complicated deployment like of You know service-based architecture or something like OpenStack or you know So there's a different level of information that they need So and then the next question is when do they need it, right? So when I say when it's not necessarily like What time of day or you know, whatever, but it's in the if you look at the Lifecycle of the usage of your of your software, right? So if we're talking about Django girls as an example I'm an absolute beginner. I've never used this thing before, right? Or if let's say we had somebody in the help desk that came in and had a documentation structured At cross purposes, right? So you want to if people come into your project for the first time you want to give them a bit of background About what this project is for what they can use it. Why would they want to use it, right? So this is the beginning and then when they could start when they get started and then they start using The software then you can give them more common tasks Let's say like if I want to do some administration some configuration, you know And then later on if they get into trouble, right? Like what sort of when do they get to your content? When are they going to need this? And then the next question is of course where so when I was talking about things like error messages, right error messages are basically just another form of content, right and a well phrased and informative error message is Better than a 10 or 100 page troubleshooting guide, right? because if I can give the information right when the problem occurs then I've saved the user a lot of frustration and I've made their user experience better, right?  So this is aware And also, you know people naturally after they've tried everything, right? They'll naturally review to Google, right? So how do I make? My content available and accessible online for example or or do I want to do it in a PDF for some reason? But I mean PDFs are still important so These are the I'm just kind of throwing a lot of questions because I'm not actually going to answer all of them because there's so many different ways of looking at it so And then the last question is why right like why do I care? Why are you showing this content to me? How is it going to fix my problem? I was having this discussion a couple of days ago With someone who said that bad documentation is just as bad as no documentation and I actually think this is of course my opinion that Bad documentation is worse Then no documentation because if I'm a user and I got into a problem I need to find something in the documentation. There is no documentation, right?  So Why am I writing this like what am I solving here? Right? I mean why so for example if we're writing What was it an installation guide you want to get your all of your prerequisites? You want to find out the information and then if you deploy it Then you need to know where you can go next as well, right? So This is the kind of question that actually puts all the previous questions To a test and sometimes it uncovers a different problem, right? So if I have to write a big big document that for troubleshooting and for FAQ and it turns out that I'm just really Documenting bugs Maybe we want to consider fixing the bugs so that we don't have to just stick it in the release notes Right, so this is a tricky one, but it's very very important. So now I'm gonna give a couple of examples I wish I could give more examples, but there's just like so many and I could just sit and talk about this all day So the first example I want to talk about is user or role-based Breakdown of content and this is the GNOME help. You'll know it And what I love about it is the first thing that you see when you go into the GNOME help help that know project org Other than the fact that you see a bug or I see a bug. Can anybody see this bug? I wonder if you can see this bug Thank you very much. So, I don't know. I just I was looking for it and I'm like, hey, wait a minute. There's a problem So you have users administrators and theoretically you're supposed to have developers here, right? So I need to file an issue for that So the first thing that you see is GNOME asks you who are you? I should put a Alice in Wonderland Caterpillar meme here. So who are you, right? And then if I'm a user I click on users and then I go to a browsable sort of categorized Library okay, and According to what the thing what type of activities I'm doing in the desktop, right? So it gives me the information that I am most likely to look for as as a user And if I'm an administrator then these are basically the administrator only or the administrator specific Documents that I need so I don't need to worry about how to you know configure my email or install a new Software through the software collections or something like that like this is the thing that a will confuse users And if I throw all that other stuff in there the administrators would be like just just give me what I need Right and then you have the developers. We have the development center You have the APIs you have the platform demos So this is a really nice example of how to use persona based or role-based Information delivery So the arch Linux wiki. I'm assuming most people here know what it is What I like about showing it as an example is that everybody raves about this wiki And I've been hearing about this since I started going to events And at first glance it looks like a mess right and I'm thinking to myself Why right because I mean I don't use arch Linux and you know, I'm still like Try I'm in the Linux user in training, but So I'm looking at this thing I'm going why does everybody love this so much and then I realize the only thing they care about is this Right because and then I realized this by the time that I get as an arch Linux user by the time I get to this wiki I've already tried everything I could possibly think of myself right and I've tried Google whatever so I go to this thing already knowing what I want more or less or at least have a few keywords in mind and a wiki doesn't have to be Browseable right a wiki base is not meant to be hierarchically structured, right? So it's pretty flat And anyone who you know tries to manage their documentation for a more broad Open source project like I know fedora kitty, you know those kind of things It's tricky right when you're trying to address a more broad audience, but I only care about this I want to find what I want and I want to find it fast Yeah, so now I'm going to give an example of Structure and conciseness So one of the things that we're working on this is this I love red hat because we always have a very kind of humoristic self-reflection attitude So in open stack all our documentation is available publicly on the customer portal So if you see here, it starts off like okay I have like every you know every link here is a different guide And then you have the release notes, but then you know You're starting to get a little bit more complicated a little bit messy and you go like I don't know One two three four five like seven upgrading guides, and then the getting started section is so long I couldn't screen capture it And I'm like where where do I go right? So this is actually something that we're working on So we are at the moment as we speak, you know Reviewing everything we have right so it doesn't really matter if you're just starting with your project with your software project Or if you've been doing this for a very long time, right? There's always something to improve and there's always there's it's never too late to also look back and Improve what you have and we're actually to fix this We don't have to change any of the content of the guides, right? all we have to do is look at What these guides are talking about how do we break them down and just sort of dump everything in one pot and Reorganize it so we're working on it, and if you want to follow it you can see when the next version comes out at some point so the second thing I want to talk about and is I Wanted to use doc ops, but somebody trademarked it so this be it so DevOps for docs is a concept that We've been kind of kicking around the documentation community for a little while and some of the things are Some of these practices have been around for a very long time Some of them are just starting to sort of come to light, but the basic concept of it is that we're borrowing Terms and practices methodologies from the engineering world and applying them to documentation, right? so if like beef, you know Long gone are the days of a word processor to a printed PDF, right? Like we don't do that anymore if we can help it because it's a lot. It's very restricting, right? So The first thing I want to talk about is the unified tool chain So for example, we've had a lot of people come up to us and they helped us and go like, you know Which tools or which markup language is which publication tools should I use and the first thing I ask is What's your language? What's your technology, right? And like so if it's Python if it's Ruby if it's whatever right so like in order to make the most out of the documentation tooling we turn to the engineers we turn to the developers and we see what do you use? You know, how do we integrate the documentation authoring and publication into? The development cycle right so it makes it easier it makes it easier because you can just add a documentation string in The code and then you can auto dock it right or you can Java dock it or whatever it is you want There's so many tools out there that can just hook into your code and extract some documentation, you know and not just that I mean you have like GitHub uses GitHub to document GitHub like there's there's a there's a talk about it and write the docs Portland So to be able to kind of dog food your own Engineering tools, so also things like issue tracking, you know to be able to get a documentation type issue in your bugzilla Right or or JIRA or whatever it is just using the same platform to track Documentation tasks Saves a lot, you know because I mean it's otherwise people will just like I'll send them an email I'll see if you can review it or whatever so what we do at hat we have a lot of Every product has whatever Tracking platform for issues and we have our own documentation projects for some of them And so our engineers or our users they can open issues for us, right? So I mean for open source projects is a lot easier because most of the time It's all in the same place, but I mean in the enterprise world. It's a really big deal so And then we have things like continuous integration so every time you you know make a commit and Rebuild the library it checks for you know, you can check for broken links. You can check for you know sanity all these different things And iterative authoring like I said used to be a scrum master I'm probably never going to stop being a scrum master entirely So it's always going to kind of accompany me wherever it is I go and I just I hate looking at a giant pile of tasks I'd rather break things down into more manageable chunks and this is also another thing is if you have iterations in your Coding then integrate your documentation into that. So like I mean if whether you're working like Sprint plus one or or making a documentation of a feature actually a requirement to deliver this feature, right? I mean, I know that I've been hearing more and more about projects that Really do implement peer review For doc for the content as well as the code not that many yet But hopefully I will talk about this in a little bit if you can increase the engagement of the community in the project That things like that can actually help right? So this is I'm talking more of like more infrastructure and the tooling that they can be involved in there So content curation or as we call you some call it sharpening your axe so When I went to I did a sorry I did a documentation sprint with Nick out next OS And I went into their documentation library, which basically they had like four guides each guide was like one giant file XML and Like with it was just it was it was scary for me and I've been writing and authoring an XML for like, you know six years So I can't imagine like if somebody wants to contribute something to it Then they'll just you know, they'll just drop the computer and run away screaming So like things like so what we did is I broke down this gigantic XML file into topics and files And I just organize it in a hierarchical way and so if people want to contribute then the source files were curated in a way That's more modular right? So if you go to the next OS documentation on github then you can see the four main guides Have that kind of structure so you can move things around if you add new features if you want to break it down It's a lot more manageable And you have automation which I love Because I'm lazy So laziness is the mother of automation And when I say automation in a documentation context, I don't just mean like things like continuous deployment Which is more critical for the bigger sort of projects You know, if you just have a wiki base or get hub read me then you have continuous deployment. Congratulations But things like automated testing for documentation and not just for code examples Because code examples can be tested with whatever it is that tests your code, right? So it's the same thing but you have tools like Hemingway and Emender and also a Sublime plug-in From what I hear about more and more tools like that They won't fix your grammar for you, but they'll tell you how what you need to fix, right? So because we deal with pros and not with code There isn't it isn't as straightforward as you know success fail built right so if I write a paragraph and it's really clumsy and long and has a lot of like it's in concise and ambiguous Then you have all sorts of tools And I'm gonna post with the slides. I'm gonna post a bunch of links Because just I want to get through a lot of things So you have a lot of tools that can report things like you view, you know, this sentence has a passive voice or If I write the phrase in order to You know some tools will tell you you don't have to use three words to say something you say with one word Which is good because a you're not wearing your readers out by making them You know, it's it's it's not a novel right like you don't want to you know The point is to it's a functional it's functional English right like so it needs to serve a purpose and The subtitle of this talk is keep it simple present and present simple is the sort of golden standard of technical documentation So you can do this, you know this window opens, you know, it's all very very simple And the reason for that is that your what you're talking about is more important than You know impressive writing Expressions right so it's not an expressive language So these kind of tools I would love to see more collaboration and more innovation around it So if you can just Google The tools are follow the links that I will post. I think they're really cool And they could be integrated into a lot of different existing infrastructures Okay, so and so the third thing that I want to talk about is basically the community engagement and the contribution engagement and how do we make how do we make how do we help the documentation improve by Engaging the people that we work with to care right so in this context We have seen that a lot of many times, you know, the people who Work on these open source projects. You're like, yeah, you know, I wrote this code, but I don't have time to write documentation, but you know, how do I so what one of the things that I do and Some of my contemporaries do as well is you know, we go and we try to Show that a it doesn't have to be such a tedious time investment So even just a little bit of forethought Things like asking the right questions or just thinking a little bit about the infrastructure and how you're integrating into the development cycle Right, so all these different things Outreach efforts Is one of the things that we do that we can do So I'm just gonna give a few examples of the type of activities that you can do in order to Increase the engagement from a community or from a project from your contributors. Of course, this is not Conclusive and there is lots and lots of things that you can do, but these are kind of the things that I've Personally and from talking to people I've seen That had a good impact. So Of course You're welcome to experiment and explore So the contribution guidelines is things like when you want Somebody to contribute to documentation. How do they do it, right? So just like when you have How to contribute to the code of a project just if you invest a little bit of time in figuring out an Optimal contribution workflow or some sort of effective contribution workflow for your project. It's gonna be very helpful down the line So just as an example We wrote this and like No, I think it took us less than half a day like maybe like a few hours at most And it's like a one wiki page on how to contribute to the documentation. It has like, you know What do I need to do? Right? So here are the steps that I need to take in order to contribute to the documentation They didn't have this and now they do and I hope it helps, you know, I mean, I it does I mean, I've seen I've been talking to them a little bit over the last few months but So this type of investment that can be just a few hours and you don't even have to collaborate on it, right? Like if you just figured out how to Contribute or change something in the documentation of a project write it down You know and then it'll help others and then you won't have to keep doing it yourself, right? So this is kind of this is kind of a Preemptive delegation, I guess or in scalability. So another good trick is to use templates and the template is worth a thousand words I've seen here one of the examples that I love that's used a lot is the read-a-docs read-me template And I keep hearing about it's like, oh, this is a really like I would literally go This is a nice me read me. Where'd you get the template? It'd be like here, you know So even if you don't necessarily have a template if you could just point out a topic or a file for One of your pieces of documentation that you think looks good and that the project agrees like so last year if I thought we were working on a Plone read me and They basically are using that as a template for all of their other read-me's So all we needed to do is to get something once looking right and then you can use it You can reuse it and use it as a basis later So things like collaboration and training, you know all these engagement So these are things that are obviously easier to do when you are in person So what we do things like Sprints and hack fests for documentation So this is from last year's Europe. I thought we did a Django girls doc sprint and at This is dev conf they did a workshop about dev assistant and Jenkins for docs So these are all activities and that's from flock to fedora So these are all activities that are done in developer conferences, right? so going into the sort of more broad general open-source tech community and really Helping to educate and coach and train and mentor it it helps. I mean, I've I don't know We had a help desk for it was supposed to be three hours and ended up being four hours because we had so many people come in and you know I love the fact that that the open-source community is so open to receive these things, but you know if if if the writers and developers we can all get together and Cross-train and share the knowledge. So these are good examples of how to do it. So even if you are not a writer We you have Sort of the newer generation of documentation conferences So I mean some people probably might remember the Society of Technical Communication the SDC Which is kind of like your grandfather's conference? and But you have conferences like write the docs like open help and you get sort of pop-up or ad hoc documentation conferences as a part of a bigger conference So open up and write the docs are like the two most popular Documentation communities so open help is more focused on sprints and write the docs is more about we have conferences we have meet-ups as well and The people who come to these events are not just writers. In fact, we probably have Like maybe a third of our attendees that write the docs are writers and then the rest is you know split up between Split up between, you know developers to sediments community managers project managers. We got you know marketing people like you have everybody coming into the same space and talking about content, right, so We have a conference coming up next month in Prague open help has the next conference in September. It's in Cincinnati and so these are exactly the kind of places that I would feel at home as a writer and You know Anybody can enjoy because the developers can learn about how a writer thinks, you know and these You know the the the project managers can learn how to integrate between the different roles and everybody wants to improve the documentation in order to help the success and the adoption of the project, right? because I mean everything is so we have such a Huge amount of information nowadays and there are so many project Projects so many technologies. How are you gonna make it stand out, right?  Thank you and things We've got like seven minutes for questions. So if anyone wants to ask, please keep your hand, right? I'm always I'm also gonna be hanging out afterwards So, hi, thank you very much for this great talk Given that you're a scrum master I was wondering if you have like iteration on your documentation as well So if you bring for example the PO to your to you basically and make them Prove or just prove your documentation Okay, so what you're asking is do we develop documentation and use the same stages as software development? Yeah, in a sense. So if you if you do sprints on documentation, so will your product owner? Be at the review meeting and say well I don't really like this kind of documentation on the specific feature and you go to another iteration Okay, so that's that's a good question. I didn't actually focus on that so much because It's more I think Applicable to the the enterprise world rather than the the sort of small project world But for example at Red Hat, we have content strategists Who basically act as product owners for the documentation and just like you have In a release meeting or release planning you have the you know the engineering lead the QA lead the support Design productization etc. So now you have someone from documentation also in this mix, right? And when we plan the content strategy for the next release we collaborate with all of those people and we come up with a plan And then the content strategist will pass it on to a Documentation program manager who's kind of like a tech lead, right? So it'd be like the engineering team lead and they would distribute the work and break it down into iterations or tasks now specifically for iterations So what we'll do is because the doc the requirements the tasks come up to us already pretty much thought out So we have a basis however Many times we are faced with oh you need to document this feature and then by the time we get to document it Throughout the development of the feature it changed pretty drastically So we have to do a lot of research So before I actually go to document something I will normally either contact the engineers who developed it or the QA Engineers who tested it to see I look at test plans. I look at specs. I look at blog posts So I just had to document something and I'm like, oh, how am I gonna do this? And then the engineers like I wrote a blog post about it and I'm like, thank you You know so these kind of things help write blog posts and then send them to your writers because we love that And then what we'll do is we have So this is I'm talking for most of the companies that I've worked for so far I've used a similar process. So we'll draft it draft the content send it out for What we call a tech review or an SME review and then we'll send it out to a peer review with other writers So you kind of have like a two-step Authentication on your docs before they get published So I hope that answers your question anyone else Do you do for public-facing documentation? Well, do we what for for general documentation? Do you do stuff like a B testing to see if one way of doing it works better with the Clients or people use the API or something than the other Okay, or even like any kind of analytics on the document sort of a Okay, so a lot of these practices are being implemented To improve processes that didn't really work so well or that we can improve right? So if we have like for a company like red hat or a lot of the bigger companies that have different Products and a lot of that, you know stuff came in from acquisitions and some of it is upstream or whatever So you can kind of test out Saying like if I show you this document You can do that but what we'll do specifically now is we've implemented something called a closed loop program Where we actually reach out to customers and we say hey give us some feedback on our documentation like what do you like? What do you not like do you like the way that we construct these tutorials or you know? Do you want to see some architecture guide? You know do you want to see more coded more deployment examples? You know so we do communicate With our users and also with the communities because you know it's all kind of linked together, right? So for an open source project your users are your contributors, right? So and most of the time from what I can see they can be pretty vocal about what they like or not like right? So you normally don't have to seek out feedback From your users because they will they will tell you you know, but yeah It is it is something that we try to implement as well. I was just wondering. Thank you for talk. Of course. It was very nice The where is within I guess in multiple organizations that you've done this have you seen the organizational position of documentation and documentation writers change because for example right now when I go and Look at the documentation for Google or any other bigger company that want to promote the product It's more in the marketing area of things rather than for the people Like you know right so it also depends. So thank you. So it also depends On who your audience is right? So if I write for developer products, then I wouldn't necessarily Have it under the marketing organization So for most of my experience the technical writers have always been under the engineering organization, but About a year and a half ago or something like that at Red Hat We actually got moved to the customer experience and engagement organization So we are in the same that so this is the first time that the technical writing department where the organization is in the same place as people who deal all the people who deal with the customer so support and account managers and so We've been moved from like hiding on you know behind behind the engineers, you know like to actually being a more of a first-class citizen And I know that It depends on the organization. I can't really speak for things like Google or Or other companies because I don't really know what their work structure is But but yeah, it's it's tricky.  Yeah, okay, so this is the last points then Hey, I like it when the programmers write as much documentation as possible because it actually makes their code better They they think about it and they maybe change the code, but when is the time to move and hire a professional writer? That's a really tricky question. So the first of all I Perfectly agree that developers can write documentation for the Components or the software that they code to a certain point, right? So if you have a smaller project It's that doesn't have you know, so as long as okay, I Can't answer that because you have to see for yourself like it's a case-by-case basis But once you start having more than a few components that have to integrate In order to create a solution, right? So once you move from just a piece of software to something more of a solution or a collection of services or components Then you start running into problems because most of the developers were focused on one component or two components Oh, not a whole lot of integration coding Normally happens, right? I mean, I don't know obviously I'm sure there's people who in places who do that But I haven't seen this personally and one of the things that have an advantage of getting a professional Writer or someone who's even take one of the developers who's more Has a broader view So if you're if you live inside this component is gonna be very hard for you to think like a user, right? And as a developer, you're not being paid to think like a user.  So like when we look at the whole scheme of things, you know You don't have to worry about that because now you have a writer that can help you sort of group everything together So I guess that's the closest thing that I can say to a recommendation You know, it'll be nice if you have one writer for every 10 or 15 developers most of the time It's more like 20 but but yeah, I mean this it mean that used to be the sort of guideline But I sorry if I couldn't answer your question more, you know, I don't have a magic formula So but thank you Please thank my key for the dog and the amazing questions


The Islander Cup hockey tournament started today at the Sanford Center. It's the third time the tournament has been played here in Bemidji. It goes on today through Sunday and features 12 teams with four teams in each age bracket. Each team will play four games. The championship and third place games will take place on Sunday. The kids competing this weekend are ages nine through 14 and are grouped based on their birth year. There are numerous tournaments like this throughout the state of Minnesota We try to showcase the division one hockey rink. There's also a big tournament in Ralph Engelsted and Grand Forks. There's one over in Duluth at the Amsoil. And what our goal was is a lot of these kids are traveling through Bemidji on their way to the Twin Cities on a various weekend. So we said hey why not have a tournament here and kind of see if we can get some interest and it's taken off. If you enjoyed this segment of Lakeland News please consider making a tax-deductible contribution to Lakeland PBS.


Hello guys, welcome back to another stream. Hope you guys are doing great Pretty surprising yesterday Pretty much just do all expectations out the window. I mean from Bitcoin Spy and yes did exactly what we wanted yesterday. I mean did nothing in terms of surprising us but Bitcoin well completely came out of left field and just I just go Walls deep I guess just just full send the best Best way to describe it So let's just go yes. I mean yesterday. We only really looked at this and on normally and just said, you know what? Looks pretty suspicious You probably want to be on the long side. That's the only that's what we really care about And we can see the set up from when we left off. I mean Into the setup So we came in we saw this wall. We're like, oh, yeah, cool. This wall probably will hit then we're like, oh, no They ended up removing the wall at the end of the day So when they ended up pushing down deeper, but again, it still came in the right time around sort of thus was This was what 945 Oh 945 then 10 o'clock came in here 10 then you're like, okay, cool. They dig deep they sold into this but they were just fishing for sort of trades They could just grab out of this sort of bag here. That's pretty much we could what you could call it They're from there. It was just a matter of lining this up with spy. So spy was sort of In its source and it sort of throw away.  Nothing's gonna end up happening Too bad. I mean if you're going to future you can see same thing here. She's like, okay It's just not many sort of long. There's not many other locations, but same time It came in came in. We sort of saw that okay It's coming here, but still it would be a nice sort of opportunity to sort of sell here and just like missed entirety of this which is Kind of just like off It is what it is and they I mean So you just wait for it. There's your one. There's your two that you three So you sold early now. You're just like trying your best not to give back Any money that you made and that's the whole plan like if that's like if you're early like you came in here You sold here because that's where the market closed Now it's just a waiting game to come back in so you go one two three you count that now it's like okay now you have A chance to come back in not a perfect chance, but you have a chance So After that now we're coming into the current sort of market conditions here There you go. We've got sort of a barrier here where we created a nice little sort of ceiling for ourselves That ceiling being sort of this area here where you got these sort of long sort of popping out and this is where sort of price shifted long So now you got to see this as your resistance. Of course it being 30k So again, of course, that's where most people either come in or sell Uh, do you see that sort of nice even numbers like oh, yeah 30k. I want to I want to buy I want to see that continue So you got to look at it from the sense that okay if you just look at the breaking the Current section here There you go again a lot of sort of shorts coming in here a lot of sort of selling But that's sort of at this point here. You can see how they got cut here. They got cut here Then they got sort of liquidated sort of here So you got a lot of sort of liquidations already coming in taking effect. But again, you see that sort of selling here or shorts Tending on who you ask So we're still seeing a lot of selling so we might sort of drive itself a bit higher again, we already have it set up to go at least to 30 500 at the worst case best case depending on who you ask but generally you can see that You do have this induced selling So we have Some sort of sentence if we need to shake it off Try and Shake it off here Grab out the stops that are placed here At this sort of level if we need if need be If you go and look at sort of where everything sort of end up spawning I was chart wise. You can see Monday came in. We already sort of smashed it with Tuesday Already sort of working the highs and retested that range here Now it's sort of coming back and you can see how we're sort of completing things very sort of Very sort of evenly you can see that I just came in touch this up here But we also came in and sort of closed Closed around here. You can see this is where the keeping volume shot very tight Around that came up. You can see this or we already know that that's the start of this sort of Large shelf that we thought the source or ceiling Describe where you have your lungs sort of coming in here And this just tapers off as we're sort of going higher But generally if you're looking for price to come down you're sort of wanting price to go higher and I know It does seem quantitative to most but again if you're not familiar Around these parts Pretty much what we do every day In terms of news again Tuesday is a pretty quiet day. I got Speakers coming at four o'clock. That's just more close pretty much Uh, but other than you don't have too much coming in So it's going to be another sort of pure Little price action day. I mean say it was meant to be purely price action, but ended up getting in monkey's business. I mean If we compare it to what spines are doing and what we wanted from spy just Just easy like this this was so there was no no sort of difficulty here came in Opened opened here gap down Came in here continued high closed off this Then just went for the last reach around here And probably going up Already looking to gap up into sort of just slightly higher so you can see This is what we're looking for bitcoin, but instead we just got Well monkey's business really Where if we line up going to together and see where we'd want to sell and what about There we go Let's sort of line this This you can see how it came in we opened. There's your open nice little 10 of 9 30 coming in here 10 o'clock coming in here Then we sort of started just moving higher Then there's your retest from spy. You can see that Came in big deep into this part or change back to that 50% of that bar There was your nice little entry if you miss If you didn't want to come into this mess here, I wouldn't blame you And now you know that's your entry for this you can see that came in retested the top of this here Then off it goes On its merry way if you start into a lot of sell and again it sort of tapered off you see how As this was sort of encroaching a bit higher and higher this was consolidating then pre-market came in Still decided to go a bit higher then market closed Then you just see Bitcoin take it the rest of the way and continue much higher, but You can see how we sort of matched things even though that it didn't sort of meet the expectations of just coming in taking out stops finishing itself here It was in the direction that we wanted We just got adjusted to that in terms of What we ended up getting So you just end up adjusting where you end up selling rather than selling much sooner. You're like, okay, let me sell Instead of selling 25 percent here. Let me sell 10 percent Let me sell 25 percent here or however much you end up selling like oh you end up waiting Then you like oh keep carrying on and you just slowly slowly sell out until you sort of hit that market there In terms of getting out. Yeah triple tap on the top. That's a nice point to get out. It's just like Sure, if you end up continue going up higher You do end up missing out on quite a bit, but at the end of the day, it's Should have made a decent feeling off here to here that you shouldn't really care about if price goes higher That's that's a big if And again, the most likely scenario is price going to Go down for the most part. It's just how it ends up doing it We know that UK is a big barrier Barrier for entry. So a lot of people Are going to try and play here and get sort of killed So We're just waiting for them to do that We already know that there's a lot of sort of offset of loans coming in here and you'll sort of see that On the future market again, there we go that Rise sort of end up being supported here. I can see they Push price higher added a wall for us I think people buy Again, it's not so working too great in the favor So we're looking for them To try and liquidate and again this trying to get rid of these shorts and that's the main Main sort of thing about going higher especially right now is if people go into short shorts this early and ignore sort of the blatant sort of Well the blatant attempt at trying to fish for a fish make make them sort of Fish and just catch them out Then price will end up going higher Try and get rid of these Shorts until they go longer. They'll probably go long around here. They say oh, yeah breakout whatever however, they describe it then Maybe that will be the driving factor for us to push us down It'll be interesting to see what we end up doing today. Remember Monday and Tuesday should just build our Wednesday picture And again, this is just looking like a pristine short for Wednesday if anything Uh, if we end up hanging around on the sort of high side Draw the developing Developing range as well We can sort of draw the developing low is I mean existing and the developing range. Yes Yes, uh, shorted pre-market then went long perfect day I didn't short the pre-market. I mean You can probably get too much. I mean, yeah, if you did it you did it, uh, but Uh, it was again just sort of coming in for spy Uh, didn't again like I say most things you don't need to get the uh, number right You just need to get a direction right Uh It just simplifies trading Thinks so much like uh, I don't care where what number it hits Am I do I get the direction right? Yeah, okay.  I just don't know how much it's going to go up by And then today doesn't matter Uh, so this is 50% of Monday's range. Uh, sort of pay attention to that that is what Uh, basically 2900, uh I'm just pretty hot Then we sort of draw out the developing Uh Developing weekly, which is the Monday and Tuesday. So that's this a little one here. We should make it a little less, uh, visible So we're already coming in we're already sort of building then Developing high and low A lot of things people forget about This will end up being our weekly sort of range and again, we're pretty pretty much pushing it high Uh, but kind of for Tuesday is trade where I've already retested the uh Monday's high. So it's it's sort of Decent to say we can probably push this a bit further higher Uh, we're sort of looking I mean, we already know we've got shorts here We've got a lot more shorts than we do have longs a lot of people are selling So now we need to get those sellers back into being buyers to try and make them trapped and the only way to do that is push market up higher we've got We've got pretty free reign to push up higher as Sure, we have a nice little long shelf here, but it's not Nearly as much as the amount of sort of longs that we've entered in But that's not really too much to say today. Uh, what's the likelihood of price continuing and repping and tearing I would say middling to very low Uh, if it does continue again, it just starts building a cause for, uh The Call for Wednesday again, we have Very much stacked Wednesday if we go into Wednesday, we can see we've got the core inflation and everything's going to be waiting for that We are the forecasted. So if that increases drastically, we're gonna Look pretty scary. Uh We also have the Fed minutes again, uh Coming in at two Then on Thursday, we have a further follow-up which PPI everyone's going to be waiting on this as well So we do have a very sort of stack Uh, two days coming tomorrow and Thursday. So those are what really matter And those those Numbers will affect, uh, where we end up trading and if we already look at where spy is trading it's already sort of gacking There's not too much. It's just going from from here to here essentially doing nothing. So We're gonna we have to see this open. We see if they drag it a bit further and then they pull it back down If they start pulling back down, they just move back into range just that it just becomes very sort of Okay Up in the arms are like coming back here. They sort of move from one to the other then push down Could could But if they start pushing up higher grabbing up these highs here taking out these stops uh slots placed here again, you'll sort of Drag Wednesdays, uh and make it a lot more enticing Because we do have a lot of sort of points to come in and stop at stop at or Be very large drop If we end up planning that Then we've already sort of come in and shown a sort of strength here. You can see the volume on the uh tops being very relatively weak considering And whereas these shorts coming in at these tops here again People say but they buy retest, but are they really buying if they're selling here? Uh Maybe we can even put it out There we go. You can see the increase in shorts coming in As the retest and the double bottom comes up. Uh, so You can see very much Very much always a lie You can see when patterns work. They only work when people do uh talk full The majority of the traders don't follow the patterns They work when they do When they don't work, which is the majority of the time is when everyone believes them to work Uh, so again, we might expect price to continue up a bit higher See if it meets up here or just for the stops here Then from there see if it comes back down If it wants to come back down on the day, I'll probably come back down into here Don't think it pushes itself too much again. We're trying to plan for a short Wednesday Uh, and we'll only get that if uh, sort of hanging around Above here without really going too too down Uh, I mean if we did end up pushing today very aggressively it would need, uh, the appropriate sort of retracement back Before Wednesday could set up for a short Uh, because again, it's uh It's all about trapping uh As much as volume as you possibly humanly can Uh before a major news event So if we are looking like we're trapping longs and we See on bookmark that we're trapping longs Then it's building up for a bigger drop Just in case you don't make it to tomorrow's stream. It's just uh In the uh, yeah Give me note this. Yeah, it's uh, the registered shorts There we go Short volume, you know, because everything has to be registered. Uh, there we go Here's that Connection shields requires brooks the uncertainty advice also horrible stops Before and executing a short sale and entry There you go. You see everything because it's a stock market I remember everything is on the up and up and unless you got back doors It would just show you a retail trader's drawing and that's what we really care about because you don't care about anything else Those retail traders are other people that feed us Keep breaking things How do I keep breaking? Just don't understand. I don't care anymore. You know, also look at options as well Uh, there you go. You know, also look at expiry I would not do that far ahead. We're doing till Uh, we do a lot closer Jan We can see what's going to expire because he got a bunch of sort of uh Uh expiry, uh halls 11th of april Seriously, oh that's today. Uh, no Hey, here's this day. Oh hell, yeah uh That ends up nicely. Uh tomorrow and today you got a lot of sort of loans. So you want to be below here to ideally uh Yeah solo Yeah, that guy's just just laughing at the bank at this moment So you basically got in here. We're not coming back here. So he's not going to be underwater Uh, now it's just about keeping these guys underwater, which is that 407 So we want to be below here. Uh before the execute on the jump Uh, so again, sort of builds up a nice picture Uh, that's where sort of put them quite maximum pain is again We just want to be underwater and these ones you've got these Uh, you've got to expire And they need to sort of if you want to be underwater Go be one way or the other Large large calls expiry on me Very interesting Basically came in today. It's like a lot of That's gonna be So that's that looks like that's June and july are going to be just pump pump central these guys are gonna Actually That's Jesus. That's crazy. No I doubt they're going to come into Interprobation this 410, but that's watching options every night again But it's something you don't need to pay attention to Again a fun day restriction Coming back to the actual charts, uh, you can see it's just the walling out. You got you got your bias guy on these points here The conditions for you to get higher, but these cells are right down up there most of the volume comes straight here Got a lot of cells. We want to get rid of those cells. How do we do that? We go higher Uh, we've got expiries coming out today. We need to get rid of those. How do we do that? We go lower We ideally want to be lower Day to try and make those Uh, it's higher. I mean unless those were being bed Uh Cash, so we need to go higher so but Either all your calls and reactions and those will sort of sell back to the market. So we're going down anyway It's just how far will And when will we go down? Again, looking at the bills up here. You're looking for a price to come down at least like this for most of us Getting strike it up a bit higher get rid of all the shorts If we can't if we sort of start stagnating like this, it'll sort of rub a bound Like we always talk about that. It's just like if sort of pulling and Teething ourselves Down it just always looks bad for us Or the uh with the other side that we're looking at If you look at all coins, I mean, I don't think they had too much success Coming in here You can look at Ethereum again just didn't really move too much Much safer sort of trading. So you just came in there's just a while long This way end up pushing off off spring boarding And there's just sort of high and just comes back to this sort Area here and adds a volume to it Look at that on the hour Go you can see where it starts add volume But generally doesn't move as much as a bit coin is where You would look at the retest that we had bitcoin Other than that Where would it go now? I mean it is looking pretty high, but you can see it's just quite these sort of bell bottoms As it is as it is with bitcoin Just these areas here You want to see price like try and Take these guys out at some point if it looks uh Strong slash weak depending on who you ask then You want to push it down We'll look at a lot, but we'll coin see if they're matching up and lining up to sentiment You can see Adam's always one two sort of print out sort of dumb numbers Like doing this sort of chart just sort of a straight and narrow up You can see that straight narrow up. It's just a nice little channel I can see that a lot of people will look for this to sort of fall out and shortly here, but If it does Again has a bit more Sort of range sort of push up So we've got price added So like with bitcoin and ethereum, it also has a secondary sort of Area that you can push up to if need be to try and catch out a lot of people But generally this just looks like uh, they're just squeezing out shorts Every chance they get try to make people go along and at some point they'll end up reversing this So it does sort of bode well for us Same thing was a vex just very large sort of flush liquidity. So if you've got Wouldn't expect anyone to be in here.  So if you came in here, you're happy.  Oh, no, what happened? It happened Uh, but up they go up they go. Uh, it's already sort of targeted these guys here It's it's got sort of room. I mean you got your triple top. So he's got room sort of consolidate a bit before it actually commits to anything So, yeah, it's another sort of weird one So I mean in the grand scheme of things again, it's another triple top within the short term. It's a triple top So you can definitely sort of call it a bit If sort of pushes higher, there's your two levels that he has a bit higher. I think it was Target no longer These sort of areas here where we'd get breakout traders Uh, so that's where breakout traders why do you like to come back into the market at sort of 18.5? Like they like even numbers. They like keeping things simple They can't count past a certain point So look at dot now. Let's see if it sort of lines up again sort Coming to it it has uh, it's already created a nice area for it to say this is nice little short area But it has the secondary area here like with Ethereum and Bitcoin So you can see that it has that potentially build up higher if it need if need be before pushing down Already at this sort of weekly high here. So if we come down could uh, sort Push down very aggressively See where we're looking So we're coming out again Coming from pretty low Uh Look what it is ourselves. Now. We're just sort of hitting into this shelf here and then If we can't freak it we go down Let me sort of look though to either holds here holds here Then that might be our saving grace Go up higher if you don't have our saving grace Again, you can see how most of that move, uh, yesterday was just Bitcoin nothing sort of, uh, too Major coming out from the alt coins. It was most of the money just went into Bitcoin nothing So alt coins too far away from their origin Solana, I mean It never really did recover but I mean it's slowly making its way back down back up I say I mean But When all the way seven, I mean if you go to seven you're laughing But it's sort of holding itself here. You can see again It's a lot more bearish than everything else. I mean it ideally would like to come down and think that'll be Sort of where you're looking for it Uh, unless it decides to push itself, uh Like the highest ends of the earth, uh, I don't I don't think it was Or higher Again, all your troubles is coming. Uh, it's uh, how we're sort of Preparating the sort of uh Remarket, you can see how we're coming in very sort of setting. So you probably might have that springboard a bit And if it's springboards and takes out a high That could be good for us, but if it ends up pre-test Re-testing lower like it did here, I could then just continue up high and just create a lot more issues Let me catch a half Ten make streams come true. Yeah It does it does make some things easier. I mean Yeah, if we sort of look out where Yes, it's coming in again, you can see it already felt cleared out some bats up top as well We could look decent. I mean you can see how these clothes are nice matched But again, we sort of came in so closed off that gap just never what we really want to want Uh out of a long picture So we could definitely see this open and just hammer fist everything into the earth Uh spy already is looking To come down and it's not it's already Not looking like it wants to gap up anymore. So Again, we're sort of coming in we're sort of pushing itself down. It does look like down down. It's where we're motioning Uh now it comes to the point where how far Do we go down today? Do we just come in kiss this sort of area here and just sort of touch this First area point here and from there we sort of push Because again this area is starting to become very sort of heavy short. So we need to factor it out Uh, if we're looking for a long Long, I mean a short wednesday And again, I don't know why my bias is short for wednesday. Uh, it just is Therefore dead traditional Uh, we'll see what needs to take Ha ha ha Oh no Oh no, it's almost like Elon Musk is not a great Business owner Who would have knew? Oh no Okay, let's see. Let's see Choose a stock set up looking wobbly ahead of a mega consumer price data that could firm up or lose growing consensus for a fed break height next month Yeah, like I said tomorrow's a very important day We already know that an additional interest rate arrives may serve server to entice More investors into the money market bugs Invest invest that may Investments that may have or otherwise gone to bonds or stocks. We don't want it to go to bonds. No, don't do that Uh, that brings us to the call of the day The L's assets. I don't care what you say Because then just beat down the once public investment strategy I'll always beat down Good reason, uh, blah blah blah 2% analyze 40% bonds. Okay You guys can look at the 60 40 in your own time It looks very mixed. I wouldn't trust it Yeah, I wouldn't trust it. I mean I wouldn't trust anything people Get on the news because again, you can you can just pay them like How do you think all the crypto bros got verified during the crypto craze? They just paid market watch they paid journalists for news endorsements and like Look at me. Look at me. Uh, so anything you see, uh on news outlets is paid for so Just do just do the opposite Uh, we're coming back up. It looks like we're going up high which is good Which is what we want to remember. We want we don't want the pre-market to be long We don't want the pre-market to be short if we want to be bearish today It makes the most logical sense if we retrace some and at least From that retracement then push up higher Because again the more the more high we go higher we go without going down The more more like brittle glass we get Actually quiet Yeah, let's just go. I mean the higher we go the better because then we just collapse And collapse are great because they create mass panic But if you're looking at it from the sense of just perseverance in terms of having a good chart, uh We want to go lower today, uh, but Before we can go lower before we can achieve that We want to clear out the shorts that ended up coming in out on these sort of bottoms because If we don't clear them out when we go down these become profitable. That's not what we want If we end up stacking too much in the way of shorts here, uh, it end up just going up higher Just grab these tops Once grab them then we can sort of make cases for that down as push Hmm I don't know. I think I can be honest today. I don't think anything will surprise me Yet And we'll change anything in terms of uh Terms of where I want it. Let's see. I mean gold contracts down Look at gold then before we close off has been a while Last sort of sentiment was price going higher and it did end up going higher Uh, it did end up pushing up unnaturally. I mean we wanted it come down. We want it to go down long term Still within it's still within sort of territory is coming, but it's just been playing Ever since sort of the markets just been looking wonky uh So I'm in coming in here. I can see that double bottom from there. She's like, uh Of the pedal we've got that short from there. We're happy if you want to grab long you go grab long again mist trades mist trades I was just waiting for a reentry back into a short In it's still within error margin of error in terms of coming in from this sort of large structure You can see sort of this push This sort of bigger push here Coming in from this point here, we can sort of collect this into a large little m here Uh, I'm gonna even connect it through here There we go Why not this larger one like this again nice little m but complete it as your w end up completing which ends up Searching for an m we need that m to come into fruition either the short for m here Or the bigger longer one here So again, that's sort of where we can making cases like downwards. So maybe we see Everything be fine and dandy come June when we have that large little cool Other than that Not really too much As your weekly for spy you can see how we're just within within three large weeklies Uh coming in Still see that we're in Two months. These those are I mean weekly is those are monthly here Got your dark dark full volume too much mind, but in here you can see Within this weekly we're inside this That's This is your dailies that were arranged we're in And we're sort of already sort of capping in here. So again This is a spread of a range we're sort of looking at. There's a high there's a low If as long as it sort of holds these areas, but it's sort of fine within these sort of parameters 50% would have lied Round here. So we're already sort of looking Target Just a bit higher So it does make sense to try and pull ourselves a bit further down if we want to come in this would be our bottom essentially We hold this bottom then then look up But yeah, I don't know it's up going around circles and saying what I've already said a million times. I think Uh, everything that I wanted to say has been said Uh Should be an interesting day to follow up yesterday. Uh, if anything Oh If you're unsure just best advice is don't trade today. Just wait for tomorrow Uh, I know I know that sounds like oh, you're missing out on something, but yeah, you'll always find something tomorrow Tomorrow's a large uh much larger day Uh tomorrow, uh today will just set up for that and you don't need to push and uh sort of Stress yourself out for today. Just to get a few extra percent Other than that, I'll catch you guys tomorrow. Hopefully you have a lovely day and make sure to trade safe Peace


One of my key priorities is funding for education. We need to have an education system that is accessible and relevant. Our ancestors understood this. I mean, public education came to this commonwealth in the early 19th century, the early 1800s. And we need to remember why our ancestors committed to public education. They wanted a strong society. They wanted a strong economy. They wanted a healthy democracy. And education was central to that. It remained central. We're a limited government democracy. We believe in the free market. And one of the few things that government ought to do well is education. We ought to educate our fellow citizens. We need to do that with wise investments, but we need to invest in education. We can't keep taking money out of schools and hope to get to a good place. So I'm committed to wise and major investment in education, which is why I've worked so hard for the framework that we have in place.