Okay. Hello and welcome. It's Tuesday, the 18th of May. And last night we had 13 F filings, which is always a really interesting point in the year where we get to see a little bit under the bonnet of some of the positional changes that major players in the market, i.e. hedge funds are making. And there was one big headline, the new big short, which is Tesla and Michael Barry. And I've got a head of Amplify me, Eddie Donmez is joining me, and he's going to talk us through exactly what that finding showed, why this bet's been taken as a rationale behind it. So Eddie, how's it going? Yes, good. Another big short. And it's Tesla this time. So there's Michael Barry, obviously very famous investor from the film on Netflix. And I'm sure you've seen it everywhere, the big short. He called the subprime mortgage crisis of 2008 2009. But he's out again with Tesla. And he's long 8,000 puts against 800,000 Tesla shares. So this is a notional amount that he's short of around 500 million or half a billion. And this is a sizable sum 40% of his total portfolio. So first let's dive into what is a put. Okay, so when would they benefit? It's essentially a derivative and these securities will benefit when the underlying shares, obviously being Tesla to crease past the strike price. So in this 30 net filing, it's not actually disclosed what the expiry of these puts are or the strike price. So we don't actually know if it's in profit yet. However, looking at Barry's track record, it's probably in the green slightly as especially as Tesla's down something like 35% as well. There was a post that you did and we were talking about how this disposition is different to say GameStop because he wants to protect himself against kind of a big breakout against his position. So can you explain that for us? Yeah, definitely. So last year and a bit of this year as well with obviously GameStop and AMC and the Reddit fueled rallies and all of that good type of stuff. It's very important to notice that he's not short calls, which slightly different kind of play. But given the short squeezes that we have seen some of those names and the gamma squeezes we saw even with soft bank with Tesla shares, if you remember last year and especially more recently, it's a much smarter way of actually playing this short without the threat of basically blowing up because being short the calls, if we've all seen the explosive rallies that names like Tesla and Reddit fueled kind of stocks can have, this is just a much smarter way of kind of, okay, a bit more initial capital up front, but protecting yourself from an explosive move for whatever reason. In the kind of market we're in, you know, high speculative excess. We've seen it with things like Dogecoin and Musk has a huge kind of following, which I guess slightly has been vented by the whole Bitcoin argument that he's been going after, but he's very much got to try behind him. But let's take a look at kind of why Burry's short. Yeah, talk me through the rationale. Yeah, so he well, he's long the purse, but he's effectively short. So he's, he has tweeted and then deleted. He's very kind of, he's very wary of the regulatory energy credits that Tesla have been kind of making a lot of money selling to different automakers. And it's kind of widely recognized that Tesla do share those energy credits. I mean, in Tesla's favor, or the argument for Tesla is why wouldn't you sell them if you were unable to? And the argument for the long term kind of ball case for Tesla is similar to that of Amazon, right? Why would you not sell those regulatory credits to then invest via Capex, new factories, you know, giga factories all over the world for to then lower your long term costs to then produce, you know, Model S's, etc. Model threes lower cost base, which is like $30,000 electric car that Musk has talked about quite frequently. Why wouldn't you do that and invest in the future if Amazon's a perfect example? And now they're the massive company that they are. So that's kind of the kind of case. However, let's take a look at Tesla and why it's been crashing more recently. It's down something like 15% last week, 35% over the last three months. The sales in the key market of China have dropped 26,000 in April. That's from 35,000 in the prior month of March. They've paused their plans to expand in Shanghai due to the regulatory kind of tensions coming from the administration. So Biden and a good kind of point that speaks to Murray's play as well, higher rates and the threat of inflation that everyone is talking about right now is hitting those highly speculative names across the board. Tesla is still trading at 97, pretty much 100 forward price to earnings ratio, which is still rich on a traditional basis. So speaking to Murray's play, he's basically aggressively positioning for inflation and higher yields. So he's got large cool positions on things like TLT, sorry, the ultra short ETF, 20 year ultra short, he's got to put on the TLT 20 year. So yes, he's betting on Tesla, the negative price action, but he's also got a more of a macro inflationary bet on as well. So of course, if you're looking at what's happened recently, inflation up yields up, lower discounted cash flows going out into the future for the high speculative names, tech stocks, high speculative names getting hit. Okay, so let's pivot back and let's talk about the other big proponent of this, which is Elon Musk. And he's gone from the SNL appearance. It's all gone a little bit slippery for him recently over the last week or so. Any thoughts on Elon? And one of the things just to lead you into this that I just wanted to share was I asked one of the guys to go back through and put together for me a study about the behavior of Elon on Twitter. And you and I were discussing this the other day, we were like, Christ, he's like the new Trump goes, someone's got to fill that position as like the dominant force on Twitter. And Elon Musk certainly isn't shy of putting forward his opinion as we've seen. And so what I wanted to do was look here today, but also do a slightly bigger study as well, which I'm still collating informational, but this is here today. So Musk has done about 1000, well, to be precise, he's done 109 tweets so far here today. So he's averaging around seven a day. But this is the profile of timings around when he tweets. What's quite interesting is if you were to factor in the opening hours of Wall Street, that's the lowest time of day of which then he tweets, whether or not there's any sensitivity to he's aware that the stock price is tradable at that point, whether he's actually doing some work and not on Twitter. But there's a really distinct pattern of where he tends to be most active post market close, if you're looking after the closing bell on Wall Street up until midnight. You can just imagine Elon sat there after a really, you know, a genius like him, I'm sure he's just got so much going on in his head. It all comes out. And so if you were looking at the session ahead, what I'm anticipating here is I'm sure Elon's going to bite. He seems like the character that actually enjoys confrontation. It's almost like a challenge to him. What do you reckon?  I think he's so intellectually strong that he does love a challenge and he loves to pick apart arguments. And he almost doesn't care about the stock price. I think that's worth noting in the sense of he doesn't really seem to care if it goes up. Hence why he's been tweeting this stock price is too high before he doesn't really care if he gets hit in the short term. He's now got enough capital for that to be not an issue. So yes, I do believe that he will 100% have something to say about this. Like he's picked the fight with the Bitcoin mob. I definitely think he'll address this in some probably maybe not directly, but obscurely via some some tweets or or something like that. But who knows, we might get another movie out of it. That's like the big shot, which I'm hoping for. Well, just to finish is I was looking at the share price and downside I'd just like to mark out 542, which was that low that we printed back on the second of deck and the low on the fifth of March. Now yesterday we closed it around 576. But what I'm quite interested in is that we know Tesla is a very popular name amongst the retail crowd. And just by association of the big short, I wonder if that and to what degree behaviorally that has an impact, even though we're talking about one of the world's largest companies. So I definitely would have that on my radar. I think a breakdown, whether that happens today or not, I think a break of 542 we got a 500 ASAP, which would be that previous all time high that we were seeing back in in September of 2020. But let's see a few hours to go yet to the open. Yeah, let's I'm looking forward to seeing I think after that kind of run up last year. They were up 740 percent or something like last year with the inclusion of of them in the S&P because of those regulatory credits driving some of that. And I think they're sitting on their 200 day average or some moving out something like just 200. Yeah, exactly. So if that breaks down, then look out below. I do think it's a bit of mean reversion as well and this macro inflation hitting these names more generally. But yeah, let's see. Let's see if Musk responds. Cool. On that, thanks everybody. Have a good day. Thanks a lot.


India also faced, you know, invasions and colonization, but here it's still alive. It has not been written enough in the history books, but very brutal invasions. One of them had a real discussion with the people and said, how do we just burn out this Hindu way of life? But still it didn't die.  Namaskaram Satgavam, if you look around the world, all the countries had their own indigenous practices, like Egypt, America, Iran, all had their own practices. But after the invasion that happened, everything is completely wiped out. India also faced, you know, invasions and colonization, but here it's still alive. More actively it's still alive. So how did it manage to survive here? Like, what's the one thing that… See, because you're still wearing a sari. That's how it's survived. Thank you so much. What's the thing that kept this culture alive for thousands of years? Thank you, thank you so much. See, innovation is just a simple word, but when you experience it, the brutality of it is another thing. What happens in those times are unspeakable stuff, especially to women. Men get killed, they're fortunate. In many ways, they get tortured sometimes. That's a little unfortunate, but generally women get to live and they'll be tortured for the rest of their life, usually. So, innovation is not just a simple word. There are two ways of taking people and property or the world itself. One is by invasion, another is by inclusion. If you take something by inclusion, it becomes beautiful, isn't it? If you take something by invasion, it is the ugliest, unspeakable thing that you can think of, whether it's on the level of an individual or a nation or a culture or a civilization. So, what is it that made this culture survive through nearly a thousand years of brutal invasions, brutal? It has not been written enough in the history books, but very brutal invasions. So, what is it? One thing was the people who invaded, power by the force of their religion or by their economic interests. One thing was the culture and the civilization was so complex and profound, they could not figure it out. See, I forget the name of this particular invader. Sometime, no, no, I'm thinking of a particular name. I'm not good at these names, anyway. So, one of them had a real discussion with the people and said, how do we just burn out this Hindu way of life, Hindu thing? Because they thought it's another religion. Just like they believe in one religion, somebody else believes in another religion. That's because I belong to one religion, so you must belong to another religion. How else? Because you do something different, but that's what they never figured out.  That's the idea. So they said, no, there are hundreds of them.  It was never an organized approach. It's every individual seeking their own thing. And everybody accepting that, that was the only organization we had. You're, you're worshipping the tree. I'm okay with that. She's worshipping the rock. I'm okay with that. I'm not a tree worshiper, I'm not a rock worshiper, but I got no problem. I am a sky worshiper. Somebody else worship, doesn't worship anything, but we are okay with him also. So they never figured this because they always believed you must belong to some entity. Here people did not belong to any entity, so there was no leadership. As many people as you want, you kill, but still it is on. In every home, in in human hearts, what is on, you can't kill it, all right? It did not need leadership. It did not need a book. It did not need an ideology. It did not need a God. That's the most important thing. So they went about demolishing temples systematically all across northern India. Southern India, you come and see glorious temples are still here because they didn't come this far down. So you will see phenomenal temples here, you don't see that in the north because they were all largely destroyed.    What do you do with these people? So because this is the most important thing you need to understand. India is Bharat as you know or you do not know is an organized kiosk. People don't understand this. So if you look at India, it looks like it's going nowhere because we are not like an arrow. Arrows will fly for some time and go down. We are like a swarm of bees. Every bee seems to be going in a different direction, but in the end all of them go in the same direction. It's happening very effectively and they also produce honey, you know.


Hello everyone and welcome to my talk today. I really appreciate you all taking the time to be here with me And I just wanted to start this talk by thanking all the organizers of this conference And especially for one thing and for that's for encouraging first-time speakers This is my first ever conference talk, and it's also my first ever conference talk proposal that I did send in But it's also actually my first ever tech conference that I attend So I can tell you that I am really really excited to be here with all of you today and The goal here for me is really to talk about how we have been unlocking the potential of Engineers collective knowledge and how you can do the same within your organizations My name is Emma. My pronouns is she her hers You can find me under Twitter and on Twitter github or other platforms as well under Emma Indahl I'm based in Gothenburg, Sweden, and I am a web engineer for Spotify And I've been there for around two years now, and I work specifically in a team who are focused on technical documentation But also discoverability in a on backstage and so when I'm not working on that I'm also super super passionate about teaching kids to code So I'm a volunteer imagine mentor for a startup called a magic labs But let's dive into Spotify's engineering organization a little bit. We are around 1,600 engineers distributed in autonomous cross-functional teams We have around 14,000 plus software components and we have around 1,400 microservices in production and These numbers are great But you know the more these numbers are growing and the more the need for to unlock the potential of engineers Collective knowledge are growing as well And When I say collective knowledge, what do I really mean by that and so Well, I I presented in the previous slide some numbers around that we are 1,600 Engineers internally and we have around for 1,400 microservices Services in production And so as you might have been able to figure out already all of these engineers are not working on the same microservices all the time so That means really that different engineers and every individual working for Spotify knows A little bit about a very small part But together we know a lot So if we can avoid siloed knowledge and instead One person can contribute with what she knows about a service or Another person about what he knows about a website And a third person about what they know about their data pipelines You know, we're starting to build up this space of collective knowledge and So why is this so important then? um The simple answer is really speed Because if we can speed up our engineers and make sure that they go from stuck to unstuck faster They can focus on their products and their end users instead of like issues. They're running into daily And we're now starting to see a more distributed workspace as well So we will continue to do after the pandemic as well And this means that you're not able to like just run by your team members desk and ask them a question that you have on top of your of your head So the the need for collective knowledge is growing there as well But to be able to capture this collective knowledge we need to remove the friction for the producers and with producers here, I mean the people who are writing the content and It's really about so that the engineering knowledge can get shared within organizations And i'm gonna tell you how we did that Uh internally at Spotify And how we are now making it possible for you to do the same in your organizations And first thing first, I wanted to guide you through a story Um, it's it's not really a story. It's more about me talking about myself in third person But it's really about so that we all can get on the same picture and understand and dive into the problems and friction and That comes up when when trying to contribute to collective knowledge And this is specifically in the format of technical documentation So Emma has a new feature she has built and she goes through her everyday workflow Looks something like this. She has been writing her code Committing her changes creating a new pull request and the already configured continuous integration environment gets triggered Tests hopefully passes and she's emerging the the branch into a master and her code gets deployed into production She feels super confident in shipping changes and new features this way because there are not much friction for her to do so But she also feels that she cares about this new service and this new feature She's built and she wants to contribute to this collective knowledge by sharing what she knows because she's she is the expert Right. She have been working for this for a long time and she wants to contribute back So and she also knows that um someone else in her team might work on this in the upcoming weeks or months And if she can get that person up to speed faster, uh, it's going to be worth it, right? And so she's starting to think a little bit about how can I produce this documentation for this new service and Where can I start like what tool should I use? And she gets to a point where she feel like Like no matter what path I take I need to Move out from my everyday workflow to do this So she starts writing the documentation in a new workflow, of course. She have been she have left her Everyday workflow into a new one and she starts writing the documentation some tool that she took a decision around She stored somewhere maybe in the confluence if if she decided to use that or maybe in google drive If that was what she she decided to write the documentation in And then she wanted to just share the the documentation with some team members And so she just copied the link to the Documentation and and then just share it with them And then six months later when you know the documentation has been around around for a while Emma's team members gets back to her and asking where where she did put the documentation that she wrote And if she can share it again And Emma first needs to think about where did I actually put the documentation because she didn't really remember herself maybe and You know she needs to go and find it and then she can get the link again and you know share it to to our team members again for the second time and This time around Emma did actually produce documentation Even though she had to switch context go take a lot of decisions about tools to use where to put it where to store it In the meanwhile and leave her everyday workflow to actually produce the documentation But you know all these extra steps that she had to take will probably stop her from doing it next time And especially since like her team members couldn't even find the documentation without asking her a second time where she did put it So she spent time on time writing documentation that no one could find And the end result of this is that the knowledge Emma sits on will not get shared within the organization And if we take take just one second and think about cncf You know cncf technologies Let organizations and individuals develop software more effectively And removing friction of writing documentation contributes to this too So what if we can just merge these two different workflows into one By tightly coupling the process of writing documentation With the developer workflow So that it becomes as frictionless and natural as shipping new features So let's go back to the first workflow because this was the workflow that Emma felt confident in There were not much friction for her to ship changes this way. So let's go back to that But this time Emma can actually write Documentation in markdown files at the same time. She's writing her code So she can commit her documentation changes at the same time. She's committing her code changes And when the already configured continuous integration environment gets triggered The new documentation is generated using from markdown to html using some static site generator As well as published to some storage in the cloud And the only thing Emma needs to focus on here is to stay in her everyday workflow And all other additional steps are abstracted away for her And then one month later, sorry six months later when the documentation has been around for a while Emma's fellow team members doesn't even Need to go back to her asking where the documentation can be found Because it's so well known within the organization that all internal technical documentation Lives in one single place and can be discoverable there And that place is something we call tech docs and we will go into that a little bit later in the talk And the end result of this then Amazing work in tech docs. It was so easy to set up. I will give you a kitten spotify engineer We did not get a real kitten or we haven't got it yet at least But we did end up with a happy spotify engineer who did contribute to this collective knowledge Because it was so easy to set up and get started And some of you have maybe already heard of this as something called docs like code That was something that we adopted and built out within spotify But it's really just one half of solving the problem It did remove the friction To produce and share knowledge in the format of technical documentation In the same workflow as you were shipping new features But backstage solves the other half making it collective and discoverable in one place But what is backstage then? If you have never heard about backstage before it spotifies internal developer portal A developer portal that enables engineers to create manage and explore software components And the idea is really to centralize and simplify end-to-end software development with an abstraction layer on top And that's it's on top of all your infrastructure and developer tooling And so backstage comes with specifically three core features Of which plays an super important role into solving this problem So i'm just going to dive into the details of these three core features a little bit more And what role each of them have in this experience So the first core feature out is the scaffolder And the scaffolder lets you create new software components based on standard templates And these standard templates can be configurable with tech talks already from before So that your engineers who are creating a new software component out of these templates gets a documentation site up and running Automatically instead of having to configure it all themselves And so who are responsible for putting these templates together Some of them you see here in the picture are actually available for you, but you're of course Free to contribute with what you your organizations What what your organization need? With your own templates really And so let's say that we want to create a standalone documentation component because maybe it's not necessary Doesn't need to be attached to a specific service. Maybe it's meant to be onboarding guide or a Or documentation that spans over multiple services So you just start with filling out some information Such as name description owner of the software of this documentation component As well as where to live what location meaning that where the repository should live really And this process just creates a new Repository for you with all configuration needed as well as some default documentation in the docs folder And So now we have the content we have some default documentation already Because we created a documentation only component through the scaffolder but Where can I actually read the documentation then? Well, the second core feature is tech docs And I've mentioned it briefly briefly before but tech docs is really the place in backstage Where documentation can be discoverable and consumed It's really one place for all internal technical documentation So for example here, we can see a collection of all tech docs sites within the organization And right there we can find the documentation component that we just created in a preview step And by navigating into it we can start reading the documentation that has already been generated for us And last but not least another important core feature of backstage when it comes to unlocking the potential of engineers collective knowledge Is the software catalog And the software catalog in backstage is a way for you to discover All services within the organization that either you own or another team owns Of course also the documentation that is attached to it So let's take a look at what that looks like as let's select the service for example We can just navigate to the docs tab And right there close to the service that we own or another team own We can quickly just start reading the documentation to it and so We didn't just want to unlock the potential of engineers collective knowledge within spotify But we also wanted to unlock this for other organizations as well Therefore we started to open source tech docs as one of these three core features of backstage But you know, we quickly realized that just because we use a specific set of infrastructure behind tech docs It doesn't really mean that other Engineering organizations are using the same So we came to the conclusion after some discussions in the team, but also with the community That we wanted to focus on making tech docs for all So that no matter what technologies you are using from the cloud native landscape Tech docs should be configurable to your needs and solve this problem for you And let's take a look at a few example of that For example with less than 10 lines of configuration in yaml You as an app integrator of backstage can configure the tech docs plugin to publish generated documentation To the cloud storage of your choice And here are three examples such as google cloud storage amazon web services s3 and ashore blob storage Another example of that is that you as an app integrator can set up templates available through the scaffolder that i showed before and You know that core feature where engineers can create a software component out of already existing templates If you pre configure your templates with the source code provider of your choice You are abstracting that configuration away from the engineer. So that again, they can focus on Contributing contributing to this collective knowledge instead of the configuration behind And this slide is just something that I wanted to show you to list all our Currently supported source code hosting providers as well as file storage providers And if your underlying infrastructure and tools are not listed here We are more than happy to collaborate with you to get it on the list And so if we just take a step back and look at this picture again that I showed in the beginning of the talk We can see that this light bulb in the middle can be replaced with backstage Backstage makes it possible to have one centralized place for collective knowledge And again, if we think about tech tech talks, which is the key part into producing and consuming internal technical documentation Knowledge is more than just documentation Maybe in the format of shorter questions and answers Maybe you have a stucco willful instance put together internally That you're collecting questions and answers within the organization So therefore we develop features on top of tech talks for example to the left here You can see the stucco full widget neck that you have next to your documentation so that you can get exposed to Questions and answers connected to the documentation you are reading And remember, you know collective knowledge only happens when more than one person contributes Therefore we have developed We have focused on like closing the feedback loop so that the consumer of the documentation Quickly can just highlight a piece of text and open a new issue and contribute with what they know And keep the documentation up to date And these are by the way features that we have not open source yet, but are definitely on our roadmap And maybe now you all sit here and think collective knowledge is not possible without great discoverability And I told you before about ms team members who were not able to find ms documentation Just and just because we have one place for this collective knowledge It doesn't mean it It doesn't mean it is easy to find Especially not when you're about to browse around 4 000 tech doc sites that we currently have internally So I agree something is really missing here So we have not been unlocking the potential of engineers collective knowledge without leveraging a good search So that's why we are currently open sourcing and building out the search plugins So that one for example from the tech docs plugin can Can index the documentation and make all documentation discoverable through backstage search And with that added on top of these three core features Of backstage we have been unlocking the potential of engineers collective knowledge Both by removing the friction of contributing to collective knowledge As well as making it collective and discoverable through one single place And you know you can do the same because it's all open source or in the progress of open sourcing at least So thank you all for listening to my talk today And if you are interested in the project head over to backstage.io Where you can hopefully find all information you need to get started And you know don't hesitate to contact me if you want to you would like to hear more about this Or maybe you want to tell me about your stories But before we end this session, I wanted to give you a Some time for any questions that are on top of your mind And hope that I can answer as many of them as possible Thank you all


That was perfect dude, I'll put it in the video. I'll like make sure to zoom in on you, too. Cool. Okay. What is up guys, Karma Medic here and welcome back to another dose, I'm joined again by Kenji in this video. We're going to be covering the second question from our MMI series and this video we want to cover why did you choose this medical school or why are you coming to this university. Okay, so there's a lot of points to go through for this question, but one of the important things that I think you should know is the teaching style of the university. So in the UK, if you don't know, medical schools are basically split into two different camps. One is the traditional style of learning, which is where you either do one or two years of lectures and then you go on to do your clinical years where you're in the hospital or GP for more and more time as the years progress. The other type of learning is PBL or CBL, which stands for problem-based learning or case-based learning and it's where students mostly have to do independent learning. They go by themselves and do a lot of research and then come back to the classroom and disseminate that information. So you definitely want to know which one your university does and it's very important to get that right. It's like the minimum you can do to know how it is you're going to be learning over the next five years and you want to make sure that that teaching style is relevant for you. Yeah. Right? So you definitely mentioned like why do you like this particular type of style? So why do you like problem-based learning? Why do you like lecture-based learning? So for problem-based learning you could say like I like the way you can kind of specify your learning into something, you know, if you find something really, really interesting, you can go into a bit more depth, you know, with that as well. Yeah. You could say that I'll enjoy teaching. I like discussing my, you know, my friends. I like teaching them as well and that's something you could definitely include as well. Yeah. I knew that I definitely would not like case-based learning and so I talked about all the pros of traditional learning or didactic learning and yeah, I basically talked about how I really liked being taught to, taking that information by myself and then re-explaining it in my own words, making more notes and things like that. Yeah. So yeah. And like it's one of the problems with case-based learning as well as that, you all have different information whereas in lectures you're all given the exact same information and you're all at the same level. Yeah. So that's what you could say as well. Yeah. One thing you could also say is about the university being involved in research. So for example, at King's, it's a Ross group university and one of the massive things that King's does is produce really high quality research. Yeah. So the preparation for the interview actually memorised like one or two things that the university has really done. So for King's, I think he was like being involved in the discovery of DNA. Yeah. So it would be really cool just to show them that actually you do know what's going on in the university. You do know what type of research is being undertaken in the university. Yeah. And that could definitely buy you a few brownie funds. Mm-hmm. Actually, I did something similar. I memorised the name of a couple of researchers that I was interested in, what they were doing research on and I brought that up in this question saying that this is something similar to the research I've done in the past and I would love to continue that research at your university. Yeah. And also like notable alumni, any alumni you thought were really, really interesting, any work that they did that you could follow up on. I think Joseph Lister, was he from here? Uh, was he? Maybe, maybe not. I'll Google for the course of medicine, as you know, you're going to be on placement for a lot of your years and that's actually where you're going to spend the majority of your time over the course. So you want to know a decent amount about those placements. For example, in Bristol, they would assign you to, I believe it was seven different hospitals across the whole of England. So you were really going to get exposed to a wide range of different types of hospitals, ethnic diversities, populations, things like that. So that was going to be very useful there. For Kings, both me and Kenji talked about how it's an extremely cultural and multi-cultural, what was the first word I said? Cultural. Diversity, the first thing I want to say. Cut. So both me and Kenji talked about how Kings was in central London and so all of the hospitals were going to be very diverse and have a multi-cultural set of patients in them. They're also very, very large. There's going to be lots of patients to see and learn from. Different diseases as well. Loads of different diseases coming around from around the world. Yeah. Different-page demographic, really. Yeah, yeah. So that's something really important to know. Know your placements. Know what the hospitals are that are affiliated with your university and why you like them, why they're a good fit for you. But one of the things that is really important to know is the different types of support systems. So you talk about having like personal shooters and why you think that's really beneficial. Any kind of welfare support. So like financial welfare support, mental welfare support. I think really is important to know when you do come to university how you will be supported if you do need it. Because everyone does sometimes need the bit of support. Everyone needs help at some point. Yeah, definitely. And yeah, having a personal shooter, I think, for me personally, has been amazing. Yeah, that's definitely something you want to mention. Yeah, Kings, for example, in recent years has made a strong push towards improving mental health. So I remember at the beginning of last year they gave us a huge talk about how much support there is for mental health issues. And if you're struggling financially, emotionally, mentally, anything like that, you can go talk to someone. There are those infrastructures in place. So everyone's going to need that at some point in their university career. So it's good to know that that's around. Definitely. And even when you do come a doctor, you want to know what support is available in the hospital. So it always really does apply. So mentioning that was one of the massive points as well. So something that was really important for me when I was applying to medical schools was that I would be able to do the dissections myself. So I know some medical schools do pro-sections. Some other medical schools have holograms and software-based dissection, which I thought was not cool for me. I didn't want that I wanted to have a cadaver that I would be able to cut into that I would be able to learn from. And that was something that I was really, really looking for. One of my friends is at Plymouth and he does dissection through holographic learning. They have a really high-tech facility where you have a holographic image of a body that you can open and cut into and everything. But I just don't think it's the same. And even he tells me that he doesn't learn as well through that and he learns most of his anatomy through books. But I consider being able to cut into a cadaver one of the biggest privileges of attending King's. There's something very important for me. Me too. I think also one of the points you could mention is just to show a bit of your personality and say, I want to go to London because I support Arsenal, Tottenham, you know, web team support and say something like that is around the local area that you're really looking forward to enjoying. Just to add a bit of your personality, something different and say why you actually want to live in that city and see what they say. Yeah, that's a good point. And like, especially for international students as well, like I was coming from Canada. So I also wanted to justify why I was coming to the UK. I could go study in one of many cities. Basically London was a really good fit for me because I enjoyed big cities. I enjoyed all the diversity and culture and everything like that. And talk about how it matches your personality. So I'm a very social person. I love meeting different people. I love meeting people from different backgrounds, different cultures. And that's why London is so amazing for me or whatever reason that you have. Speaking about London and meeting people, one of the things that I really hit hard on for Kings was that it's such a huge medical school. It's I think the biggest medical school size in Europe. So that was very important for me because like you said, we're very social people. I love meeting people. I love going out there and experiencing new things. So having a big university, a big class size was very important to me. I didn't want to go somewhere like Cambridge or Oxford where there's like a smaller class size, smaller tutorials, even one-on-one teaching. I wanted to be surrounded by as many people as possible. Yeah, that's a good point actually. And also just having five different campuses as well. I love how you can walk in between campuses. You can see the cities. And you can meet people from across different campuses. We meet people from Strand and Waterloo. So you meet people from everywhere. And aside from your academics, you can also mention that you love sports, you love societies. So in Birmingham, we had something called the Med Sock, which is like the medical society. In Kings, we have MSA, which is the Medical Students Association.  GKT people are hardcore. Yeah, for sports. So you guys mentioned, yeah, I want to play sport and I'd love to, you know, to be part of the team.  Whatever it is. And yeah, because I guess being part of society is a huge part of university lifestyle.  Definitely, yeah. Or if there isn't a society available, you can always mention that I'd love to start a society. Because all my friends in my last uni started societies. You can always say that you want to start this society even though you don't want to. I mean, you guys can exaggerate the truth a little bit. Just a tiny bit. Just a tiny bit, yeah. Okay, so long story short, basically you want to say as many unique things about that university as possible.  And if you talk about your past, your experiences, your extracurriculars, how those fit in with the university, how much is your personality, it's going to be something that's really important and it's going to hit home with them. So that's it for this video, guys. Thank you so much for watching. I hope you guys found these tips useful. If you want to check out Kenji's channel, don't forget to visit him on YouTube. Kenji, Tamita, Vlogs. Come check me out. Follow us on social media, Instagram, Snapchat, Facebook, everything. ABC, BBC, iPod, MySpace, don't forget. I just have MySpace. You do? I don't know. I don't know. I don't know. I don't know. Do you know what you have? Beaver or something.


From time to time I come across distributions that are how shall we say? Unknown to me and that shouldn't surprise anybody because there's like 5,000 different distributions out there Maybe exaggerating a little bit, but there's definitely a lot. There's no way Anybody could know all of them. So every once in a while I go to distro watch our favorite website and I take a gander through the new releases and Every once in a while I'll come across a distro that just makes me ask what is that distro? Why does this exist? What is it? I get very curious So today the distribution that caught my attention is a distribution called slacks now what slacks is is apparently a live ISO Linux distribution meaning that it's meant to be run on a USB key and it has persistent media so that you can actually run and use the USB key as if it was your your hard drive So we're not actually be installing this today at all as far as I'm aware you can't install it now I don't know if that's true or not. We're going to find out But its purpose is to be ran from a live environment. So that's what we're going to do today So first let's go ahead and take a look at the website Now usually when I do these WTF videos The website is not great. A lot of times it's just sourceforge But this is actually a very nice looking website. This looks really well put together And there's a lot of actual documentation on here. There's a lot of different Descriptions on there and there's a list of packages and there's a changelog and it's a really well put together website Now if we go up here to the start slacks We'll actually get an entire page of stuff that will tell you how Slacks is meant to be run all the way from maintaining persistent changes to the boot options that it offers and so on and so forth Now obviously if you're running this from a cd The persistence the persistent changes won't work because you're not using writeable media even if you're using like an rw That's not the way the stuff really is meant to be working But if you're using a usb flash drive you can use this as a persistent media tool And that means you don't install anything you just boot into it. Do your work? Shut it down properly, mind you and it should save all of the changes you made during that session So that's really cool, right? Something like tails or cubes or something like that, which is meant to be used anonymously Now one thing that you don't see on this all that much is actually the use of that Rationale it doesn't say hey, this is an ultra private distribution. It doesn't say anything like that I mean, I'm sure maybe it is I'm not I'm not doubting that it's meant to be private and all that stuff But it's not what it's for instead. It's supposed to be ultra light weight in terms of resources and programs So that you can carry around a full fledged Linux distribution in your pocket. That sounds cool So I could go through and read the stuff, you know on camera, but that sounds boring to me I will leave a link to the website as usual down in the video description Instead, let's go see if we can get this thing to run So let's go ahead and go over divert manager hit begin installation And we'll see if we can get this thing to go full screen and here we go And this is what slacks look like. So we had even we have a start menu now I am not actually sure what desktop environment this is or what it's based on. I have no clue So we're going to have to investigate that we're going to have to look and see what software is here And so on and so forth and as we can see there is actually no way of installing this as far as I can tell Now also this right here looks like all the programs that are installed There's what five there and three there. That's eight One of them is a terminal. So this looks like vlc and that yep. That's vlc So it's actually going to install that so it's not even installed out of the out of the box It's just there Now this is based on debi and 11. Now I should mention that this ISO that I downloaded is a release candidate. So if we see bugs, it's meant there it's meant to be buggy It's a release candidate. So I'm not going to get after it for there being bugs It's just the way it's supposed to meant to be so that was I mean it ran it. It opened it That was pretty cool. A lot of times with these Smaller distros. I expect things to kind of be half-assed That wasn't half-assed. That was really good. So that was that's vlc. I wonder if they're all kind of like that I'm assuming the terminal actually is just a terminal. This is x term. So let's do uname-a. See what kernel we're running We're running 5.10 typical debian 11 fare and then we can go through and see if neofetch is installed It is not so we can the cool thing here is we just do apt install neofetch And now we can run neofetch And we have neofetch now We don't have a custom ascii or and it doesn't actually say that this is slacks. It just says it's debian We have kernel 5.10 as we saw we have 633 packages installed Which if you've ever used debian before you'll know that that number is really low. I mean like really Really low. This is the flux box window manager That's why I didn't recognize it because this is the absolute best i've ever seen flux box look like this is an amazing looking window manager and usually flux box like the mx version of flux box is And i'm sorry mx. I love you, but your flux box themes are Really bad. They're old and they don't look good. So this is flux box with the slacks theme theme This is x term as we said so not a lot here. There's no way to install it as far as I can tell You're not meant to install it. This is just the way it is So unfortunately, I don't know how i'm going to test the persistence because i'm not using this on a usb key I'm using this in a virtual machine And the isos in a virtual machine aren't writable. Usually the writable part is the hard drive. So I'm not sure how I'd go about testing that. I'm sure there's a way This is just pure ignorance on my part So I won't be able to test the persistence part of this Which is actually kind of disappointing because I was actually kind of looking forward to that So I'll have to test that off camera and see if I can go through and Use it on a usb key, but I won't be able to show that on camera So as a browser we get what looks to be chromium and it's going to install it So one of the reasons why that package count was so low is because the stuff that it says it's actually The stuff that says it's actual here is not actually installed. What text editor do they want us to install and stuff? So this is psi te I've never heard of that before like in my entire life. So that's a that's a text editor that I've never heard of before But that's already installed and we do have chromium here installed now. I wish now I wish instead of chromium we had the option for firefox But apparently you can't even install firefox. I tried to install firefox. So sudo apt Install firefox and it just says there's no installation candidate there Probably you could go through and enable all their repositories if you wanted in order to get firefox I wonder actually if firefox esr is here Yeah, firefox esr is here. That's this it's debbie and I always forget that debbie and doesn't have the regular firefox Binary, it's just the esr mode. So now we have firefox installed And that even appears right here in the menu.  I like I said, I haven't been able to test that because I'm on a virtual machine But the idea that is really good. There's not a lot here that we can talk about because there's not a lot here This is a probably the most minimal distribution. I've literally ever tried actually what we can do here is See how much memory we're using 230 yeah using 230 megabytes of ram that's absolutely bonkers Like you're not going to get much lower than that and have an actual, you know, like window environment Now, obviously if you're just running like a tty you can get way lower than that But I'm not just running a tty. There's actual windows being drawn on the screen And I'm pretty sure xorg takes about that much Like if we do let's see if htop here is installed it is installed by default. So yeah The best majority of the memory that we're using here is going is xorg This is I thought So this is has 28 tasks 32 threads. That's just Again, that's bonkers for anything now a lot of that is flux box flux box It's always very minimal in terms of resource usage But debbing usually isn't right even if you install debbing of any flavor Some of that resource usage is that debbing or that you're seeing is always going to be at least some of the things that debbing You know uses and it obviously will balloon even farther than that if you choose some kind of Desktop environment like, you know, or katie or whatever. So the fact that you're seeing 28 tasks and 32 threads is kind of annoyingly minimal So let's just see one thing I haven't seen here is a settings panel Like do you see a settings panel here archiver? I think it's just going to be like yeah, let's get on zip stuff What if we right click on this workspace screenless resolution? So this is how you're going to change your screen resolution I will change that should be 1920 by 1080. There we go It didn't work all that great because the meant the bar went away So you can change your keyboard layout your workspaces and change between workspaces and the icons for the workspaces You can create new workspaces and you can remove the last one And then xn log out. That's literally it. That's all there is no I It's been a long time since I've used flux box I don't remember if flux box has its own settings panel or the one that I vaguely remember Was an mx tool. I'm it's probably an mx tool. I'm guessing seeing so there's literally nothing else here Now again, the resolution change kind of borked this up a little bit as you can see But that's not going to that's either going to be because again This is a release candidate or it's because this is a virtual machine So I'm not going to harp on them too bad about that. So let's go ahead and just wrap this up That is slacks now Out of all of the distributions that I've had in this series the ones that I've looked at This one is the most interesting to me because imagine if you will You wanted to always have Linux around with you and you wanted to ensure That no matter what it would run like no matter what hardware you're on You you'd always have a Linux environment That has all of your applications and whatever With you in your pocket on the size of a usb key like this What distribution you're going to choose now mx has a persistent mode, but it has to be enabled it's not enabled by default and Again as much as I love mx. It's still a full-fledged Distribution it has all the stuff that has that gives you a distribution It has a desktop environment unless you choose the flux box version, which is then a window manager So you're going to have a ton of packages a ton of overhead And when I say a ton, I mean, I'm not saying like mx is bloated or anything I'm just saying that it uses more than 200 megabytes of ram Out of the box now. I'm not sure what the flux box version of mx uses I haven't it's been almost a year since I've looked at it Probably should look at that again But I bet that it uses at least a little bit more than this does and it For sure comes with more applications installed out of the box like damn sure it does It comes with more mx tools Then slacks comes with actual programs because slacks doesn't actually come with too many programs No, we didn't look at the like the file manager if we can open this up. That's called tux commander I'd have never heard of tux commanders before. Let's go ahead and look at about this is tux commander But I would almost guarantee my friends that this is either based off of double commander Or crusader because this has the same Line of buttons along the bottom as crusader does and if this is based on crusader or even double commander They have my heart because I love crusader. It's my favorite Linux application But anyways, it has that and then we open up the terminal or the calculator That was the only other application that was installed and I'm guessing that this is genom calculator This is genom calculator. This looks like the only genom app installed as well. So literally There's not much there, right? And That's impressive to me that the ability to install whatever you want. I mean, it's a devian system So you're gonna have to deal with the fact that devian Doesn't have the largest repositories in the world and it's all going to be outdated but The idea of carrying around an entire Linux system in your pocket I'm one of these and it just being persistent all the time and it will run on whatever hardware you happen to encounter Like that's amazing. That's cool to me. So that is slacks There's not a lot here is if you want to explore more about it I will link the website in the video description There were two package lists there if you wanted to see what packages were installed And there were several boot options that you could use if you wanted to change the way it boots And those boot options will allow you to do several things like Disable the loader of certain sb modules Load with no sound just in case you're loading in a place where you don't want things to you know have sound You can activate the entire fresh copy to ram and so on and so forth. There's a few of them There's also a debug option in case you're having problems. So Usually in this in this series, I Have a hard time liking the distribution that I've chosen to look at And usually I spend about a half an hour looking at it and going through the Various things and while I record time with this is about 20 minutes I will say that I'm highly impressed with this So if you have comments about slacks or slacks or questions, you can leave those in the comment section below You can follow me on twitter at the limits cast you can support me on patreon at patreon.com slash Linux cast I think i'm going to go through and install this on a usb key now and just see how it runs on a usb key I want i'm very curious about it and For that to happen in this series is a milestone of you know in and of itself So uh, that is it for this video before I go. I'd like to take a moment to thank the current patrons Today devon patrick marcus maglen jackson have tool see vey cyber galenix garrick michael art center carbonated jeremy Sean odin martini Merrick camp drash li j dog peter a crucible dark band at six glad a in primus. Thanks everybody for watching. I'll see you next time