This study examined the relationship between structural stigma and access to gender affirming care, gender identity disclosure in healthcare, and experiences of discrimination in healthcare among transgender people in Europe. It found that structural stigma was negatively associated with experiences of seeking gender affirming care and positively associated with concealing one's transgender identity to healthcare providers. Additionally, it showed that identity concealment was associated with a lower likelihood of experiencing discrimination in the healthcare setting across all countries, regardless of their level of structural stigma. This suggests that structural stigma may be a barrier to accessing gender affirming care and that efforts to reduce structural stigma could improve access to such care. Furthermore, the study also revealed that the most common reasons for not seeking gender affirming care were fear, which were shared between low and high structural stigma countries. These findings suggest that measures to reduce structural stigma should focus on decreasing fear and increasing access to gender affirming care. This article was authored by Felicitos Fork and Richard Brandstrom. We are article.tv, links in the description below.


Research and Development for Tomorrow's Weapons This is the mission of the Naval Ordinance Laboratory. In this task, scientific photography is an important tool of analysis. Its techniques are the product of more than 90 years of development. They go back to faded photographs like these. For here, on a California racetrack in 1872, sequence photography was born. It started with my brain. Discovery begins with observation. The scientist studies forms, movement, patterns, the commonplace with the unusual. With the invention of photography, investigators saw means of recording data from the fleeting world of events to isolate segments of time or study and analysis. It was Edward Mybridge, photographer extraordinary who made the basic essential contribution. Using wet plates and the cumbersome equipment of his day, Mybridge undertook studies of animal motion. At a racetrack near Palo Alto, he set 24 cameras in a row and devised an effective tripping mechanism. The result, these sequence photographs of a moving horse and rider. The science of photographic motion analysis was off to a galloping start. Mybridge's studies of human and animal motion were classics. They were soon followed by others. Thomas Edison's time-lapse photographs of 1904 use the technique in reverse. Hours were compressed into seconds to reveal the unfolding of a blossom. The growth of crystals received Edison's attention in another time-lapse sequence photographed in 1914. Today, scientists use the same technique to show the slow growth of flame crystals. The elaborate equipment of today, adapted to a variety of special purposes, finds many uses outside scientific research. From measuring the velocity of a golf swing to advertising how well a certain article of clothing will stay with the wear. But in the design and testing of modern weapons, as in other tasks of science and engineering, photography remains of crucial importance. This test range operated by the Naval Ordnance Laboratory at Fort Moderdale is lined with camera stations. The method invented by Mybridge is applied to another kind of subject. Photography of missiles, plunging at supersonic speeds. The pictures that result offer specific information on the missile's speed and acceleration, position and attitude during each movement of the flight. They are the evidence on which the test is evaluated. These airdrop tests are also tracked with the Shoulder Mom camera constructed at the laboratory. The camera follows the missile from drop to impact, revealing every detail in the sequence. These shoulder mounts developed over a period of 20 years, illustrate one of NOL's contributions to progress in scientific photography. Photographic services at the laboratory have dimensions that Mybridge could not have foreseen. But amid the preparations for this underwater test, the purpose of one piece of equipment would be familiar. The sequence programmer is a direct descendant of the electromagnetic exposing motor that Mybridge built for his experiments. Both machines serve to synchronize the camera to the event. The high-speed cameras expose their 100-foot magazines within one second. The programmer times their operation to catch the missile model's brief flight. At 7,000 frames per second, multiple cameras register the model's passage in slow motion. Every frame offers significant data on the test. In the analysis of test photographs, the timing marks that strike the edge of the film are essential. Using them, the analyst can measure velocity and acceleration because he knows the precise time difference between any frames on the roll. A pulse generator is used to mark the film while it is running through the camera. Up to 10,000 pulses per second and even higher rates can be supplied to meet any test requirements. The generator pulses this bulb to expose timing marks directly onto the film. Because NOL needs portable, rugged units, the laboratory's photographic staff has designed and constructed special timing components. They reduce the units required from an unwieldy collection of equipment to this lightweight outfit. At the NOL Open Ballistic Range, Edward Mybridge would recognize the line of camera stations. Their placement follows the technique he developed. But the photograph ballistic projectiles in flight, spark gaps are used. Blashing at 1,000,000th of a second, their shadow graph pictures record the projectiles position and show shock waves and turbulence throughout the flight. At the laboratory's hyperballistic range, an 8-inch gun breach block is used to fire projectiles down this thousand-foot tunnel past these camera stations at speeds of 15,000 feet per second. An intricate system of mirrors and spark gaps is used to produce shadow graph pictures. In the dark room, the developed plate shows a clear image of this nose cone configuration caught at an exposure of 1,000,000th of a second. Schlieren photography, another technique, reveals minute differences in atmospheric density. This system complements the shadow graph by uncovering different aspects of the same phenomenon. Its sensitivity is due to this complex optical system, employing delicate knife edges. The smallest atmospheric disturbance in the subject field is registered as a pattern of refraction on the photographic plate. At the laboratory, much research is devoted to explosive detonations. To make scientific measurements of these phenomena, another type of camera is needed. This camera incorporates a rotating mirror to achieve a rapid framing rate and exposures as brief as one fourth of a millionth of a second. It produces valuable information on what happens at each stage of the detonation. In another type of camera, the rotating mirror is used to spread the image of the detonation along the length of the film. For this reason, it is called a streak camera. The pictures it produces look like this, but to the trained interpreter, they offer a complete record of the detonation. Recently, research workers at the laboratory succeeded in combining the advantages of the framed image with those of the streak camera by constructing a third type, a high-speed focal plane shutter framing camera. This complex instrument offers complete coverage of the event through six focal plane shutters, together with greater optical efficiency and shorter exposures, as brief as one fiftieth of a millionth of a second. Now, let's see how some of these photographic techniques serve the investigator. This project tested the safety limits of a nuclear reactor. The scientist will have to rely on photography to chart the movement of this weighted plug. The laboratory's photographic engineers study the test specifications to outline methods of coverage and their equipment needs. They calibrate the lenses to be used for focal length and optical center. They have surveyed into position the camera stations and the stadia tower that serves as a reference point for measurements. In all, seven cameras will observe the ejection of the plug. On a 50-foot tower are two 35-millimeter cameras. High-speed 16-millimeter cameras are fixed on this 30-foot tower. The sequence programmer links all of this photographic equipment to the control room. Here, as the test begins, one button sets in motion a complex series of events. The RAM that carries the explosive charge begins its journey upward. Within a few seconds, it trips a switch that turns on high-intensity lights and starts the 35-millimeter cameras. Next, the RAM locks itself, starting the 16-millimeter cameras and detonating the explosive. The test is over, but the movement of the plug has been recorded by seven cameras at speeds ranging from 24 to 6,000 frames per second. Meanwhile, the oscilloscope cameras have recorded the pressure time curve inside the test vessel. In this one experiment, a battery of modern photographic techniques has served the cause of investigation. Photography has become a versatile and potent instrument, aiding the scientists' powers of observation, removing the barriers of distance, controlling the swift passage of time, penetrating invisible currents of air. As for Edward Mybridge, who made the first practical application of photographic motion analysis, he did indeed prove what he set out to prove, that all four feet of a running horse are off the ground once during each drive. This has been a boon to artists, horse traders, and veterinarians. And photography has been solving tough problems ever since.


Thank you Thank you. It's awesome to be here and since I've only got ten minutes. Well, that's rock I'm unique and I'm here to talk about information architecture Yes, this works And well, what is it? That's the big question We all love WordPress don't we and I don't have to ask you why It's a great CMS and we're all great website builders, aren't we? But when I say I built websites Do I know what I'm building? Actually, do you? What's going on? This talk will be too short to tell you what information architecture is all about but I'm on a mission a mission towards a better structured web and I need you I need you to convince your clients that information architecture is part of that That will be hard because information architecture is the underdog It's not very sexy and it isn't visible But that doesn't mean it isn't important If you take a look at these skeletons Apparently, they're the same they have the same components But once you want to go riding on which animal would you do it? This book on information architecture, which I strongly recommend has got this story Which made me realize that often I'm not too aware on what I'm building and neither is my client It goes like this There's this minister who walks past the construction site And when he walks past he see two guys laying bricks and he asked the first guy Hey, man, what are you doing? The guy looks at him bit disturbed. So like well, can't you see I'm laying bricks It's going like oh, yeah, obvious and he asked the second guy the same questions. They're like What are you doing? And the second guy's ask answers Well, I'm building something great. I'm building a cathedral and Clearly impressed with the answer of the second guy the minister goes home and he can't sleep and he's thinking about it And he decides to go back the next day to ask this guy some more questions because he really inspired him But when he gets to the construction site only the first guy is there And he goes like oh Where where's your partner? Where did he go because I want to ask him some more questions And the guy looks at him while he's laying rakes and he said that's fool He thought we were building a cathedral, but actually we're building a garage So when you're building a website ask yourself the following question Are you building a garage or are you building a cathedral? Or are you just laying bricks? And when you do so do you use the iter method? I think this is right Or do you use some form of research or testing? Because remember you are not your user WordPress helps us with the basic of installing a CMS But it doesn't and cannot help you with organized and good content and And that content needs to be findable and understandable for its users So if we move on to the definition of information architecture I'll go for the very short one because what you need to know is that it makes information findable and understandable and To do so we need some basic concepts of information architecture Which are information of course that needs structure It needs to be organized and it needs to be labeled You probably all agree that Findability is a critical success factor and John made a set it earlier on if a website can't be found well, there's no use putting stuff on it and System will fail if the users can't find what they need But when you design don't design it just for users use it for the organizations and the people managing the content as well So why is it important? we suffer from major information overload and However, this is not new But you can't imagine the growth of information has really sped up with the introduction of personal computers and the internet and The findability techniques that were Developed 15 years ago are not very effective today And when we look at information environments like websites There are not lifeless static constructs Rather, there's a dynamic organic nature to them in both where information systems and the broader context exist And when you look at these three circles of context Users and content you can use these in information architecture to Find the balance and help them ask us the questions you need to develop a good information architecture And when we talk about context We talk about business or organizational context and this is unique to each organization and the websites you build well, the information architecture reflects this unique context and You don't want that to look like the context of your competitor. Do you? Next talking content That's when we look at the ownership who owns the content in what format does it exist? How do we structure it? Is there any metadata in what volume? Does it exist and do we need more volume in the future and how dynamic is it? Will it grow all very quickly and Finally, what I think is most important are the users And when we talk about users Remember, we talk about real people like you and me. It's not an abstract term and These people have different information needs. I'd like to emphasize this remember you are not your user And what you think is right? Well, your user might think different So the final part of this talk is about how to do good information architecture and I'm sorry. I Don't have an answer to that But when you look into your latest WordPress projects be critical and Not only if it's a large-scale project But only also with smaller projects and don't be tempted by your clients to get into a rush and do concessions Because most of your clients think information architecture is abstract and they want to jump to the visual part of graphical design too quick And when time and money are on a tight budget Where you have to make choices of what to include? And again, these three circles will help you do so Good research means asking the right questions and it helps your user answer for questions. They have themselves When they go to a website, they have a question like am I in the right place? Does it has what I'm looking for and if not is there anything better or anything else and After that they ask, what do I do now and it needs to be clear user research is very important Because in the end the users are the ultimate judges of your website and You can do some uses analysis by checking on content performance Visitor information and search analysis and I think the relevancy plug-in is a good way to find out what people are searching for on your website and Always be testing even if you only do one test on a friend of your website That's better than not testing at all and you could use for instance this free card sorting method Which is online but on optimal sort or do a navigation stress test that you can find on that instance websites You have to overcome resistance as well Because people don't really want to spend time on information architecture and common arguments are like We don't have time or money or we already know what you want But if you dig into the information system really good, they will have a website that actually work and it will save them time in the end And finally, I think development and information architecture strategy is important because it can help expose gaps in business strategies and content Collection and it will force people to make choices. They've thus far managed to avoid So nearly there I've collected some resources for you and you can always check WordPress TV check on information architecture to learn more And my website has collected some resources as well and I'd like to invite you to follow me on Twitter Because this is way too short and I'd like to keep the conversation alive. So I've created this hashtag WPIA and Yeah, hook me up and to connect offline I brought this swag the WAPU game that you can play all together and discuss the benefits of WordPress We'll have so thank you for your attention You


So, in this power world video, I bring you a guide on how to breathe the best combat Anubis this game can offer. This Anubis alone is capable of crazy things, and well in my opinion is one everyone should have in their life. We all know Anubis can be one of the best base power workers in the game, but with this setup of passives, I will guide you to getting, he is also a monster in that combat too. I actually went into the creation of this video, into the creation of this power thinking about PVP and the future, especially in that combat arena, that power combat arena. This Anubis were absolutely slay, and with this intention, I decided to create what in my opinion is one of the best combat Anubis's this game can offer. How's it going guys, my name is DPJ and before we go any further, I am giving away a couple of copies of this game, or any game of your choice. To be in with a chance of winning, simply drop a like on this video, leave a comment down below and make sure you are subbed with those notifications turned on, winners will be picked and announced at the end of the week, so good luck everybody. So this combat Anubis I've been trying to breed for a while now, many many cakes and many hours later I've been in the best way in my opinion to get this variant of Anubis, one that will absolutely be deadly in that PVP when it eventually does come in. The stand with PVP is team based, and the better team will win for sure, but having powers with the ultimate passives for the ultimate DPS in said teams will be a massive benefit, especially within that PAL PVP arena.  So these are the four passives we will ultimately end up with on our Anubis today. So where do we start? So there are a few different ways to actually achieve this but after catching and breeding and doing all this stuff for days now, I will give you what in my opinion is definitely the quickest route in achieving this. So firstly we need to catch ourselves PALs which can end up with the two passives which will then push forward and breed with a legendary power to guarantee us that Anubis baby, those two passives we need are muscle head as well as ferocious. Now these ain't exclusive passives to any individual PAL but in regards to breeding up to get to that Anubis the quickest way possible, if I were you I'd recommend you definitely going out looking for a breeding pair of dire halves. With these two you need two passives to look out for, you need one with that muscle head and one with that ferocious on it. These are the two main passives we are after here. Now you can be extremely lucky and catch a single dire halve who may have both of these on it. I mean if luck is on your side that is for me it wasn't that straightforward. I actually took the longer route as I was wasting cakes just breeding random passive rolled dire halves wasting time. Now dire halves can be found around numerous parts of the map and a average spawn around a level 14 and below. But yes get yourself two dire halves, a male and female. Again guys between these breeding pair of dire halves we need the two passives of muscle head and ferocious. Preferably without any other passives answered dire halves too. If they both come with one passive each that is absolutely perfect. But I mean if they do have something else random on them I mean it isn't that bad because when it comes to passives passing down they ain't singled out and with the countless times I have bred myself it's just a good chance you end up with just the two you want or even two random passives at the same time. But you have one parent with one passive and the other parent with the other passive. This in my opinion troubled the best way I've gone about this. I actually bred a dire halve which had ferocious on it. I had another dire halve which had muscle head on it but it had two other passives. One of the first five dire halve babies I got from breeding these two had the perfect two passives I needed of ferocious and muscle head on it. So like I said as long as the parents have both the muscle head and ferocious between them I'll just breed these two until you get what you need. But either or guys result we want here is a single dire halve which has only two passives that we want on it and those are again muscle head and ferocious. We don't want any other passives unsaid final dire halve. Then guys you want to breed this dire halve with jet wagon. Jet wagon being a legendary power has that legend passive on it we want. So jet wagon is obviously a level 50 world boss who isn't the easiest of catches but you can here guys use Palladius or Necromus too. These are other level 50 legendary world bosses breeding either jet wagon, Palladius or Necromus with dire halve will give you the same results of an Anubis baby. So whichever world boss you find easy to catch do what you gotta do there. Now there are other routes you can take to breed other powers which we'll talk about in a quick minute but yeah right now you want to breed that dire halve with that legendary Palladius. I'm using here jet wagon. So breeding dire halve and jet wagon guarantees me an Anubis baby and what we are looking for here guys is one Anubis baby with three of the passives we want and they are legend, muscle head and ferocious. These are the only three passives you want on that Anubis baby and yes this could take you a few attempts just because jet wagon normally has a couple of other passes on him too. So yeah keep going guys until you get just these three unsaid Anubis. You want ferocious muscle head and legend that is the end goal. Okay so once you have this guys there's only one more thing required and that is you go out and catch the world boss Alpha Anubis who spawns in at level 47. This is the only way I as far as I'm aware that you can get the earth emperor passive skill. You need to go out and catch this alpha boss Anubis again at level 47. So once you have this alpha Anubis you then guys to simply breed it with the Anubis we made earlier from jet wagon and the dire halve and your end goal is guys that you want obviously an Anubis baby which has the muscle head the ferocious the legend and the earth emperor as it's four passives. That is the end goal that is what you want and that is what we strive to achieve here and that is guys as simple as it. Yeah it's now alternatively if you have no luck with dire halves or jet wagon you can get two gubbins with muscle head and ferocious as a mating pair and then go ahead and breed these with necromus the legendary pal this will also guarantee you an Anubis baby the same route obviously can be used here alternatively if you struggle jet wagon or don't have him dire halve can also be bred with paladius and necromus as I said earlier this will still guarantee you an Anubis baby now the other legendary alpha world pass is throstallion now you can resort in an Anubis baby from throstallion but it requires you to breed said throstallion with either robin krill and goriot or gal claw this would mean you'd obviously need a breeding pair of said pals with both muscle head and ferocious on them before you start the breeding with throstallion but once that's achieved on your mating pair guys go ahead and breed with throstallion this guarantees you an anubis baby and from here guys you go ahead and breed that anubis baby with said alpha world boss anubis and eventually guys the outcome will be the same of you having the perfect anubis with that muscle head ferocious legend as well as the earth emperor that is what we want here so all in all guys you will end up one of the best anubises in the game especially for that combat but it actually doesn't end there in regards to damage output with anubis here you can buff it even further you can get even more damage by stacking new mods in your pie too these will increase damage to that ground type powers perfect for anubis now obviously you want to be leveling up your anubis vd condensation machine too and using the statue of power once you have that perfect power that perfect anubis i don't feel like i need to be telling people this but yes this definitely should be the case you're making as powerful as possible now we also realize people will mention ivs which i understand but in my opinion these can be sold damn random i just went to achieve the perfect anubis or even power that you're chasing then try and breed the opposite sex with the exact same passes i mean because yeah and then just breed away from there on pc ivs can be calculated easy with mods you can even put mods in again that show you them in game unconsult that is not the case plus in my opinion the difference between high ivs and low ones are pretty minor though so they ain't really worth too much of your time worrying about right now let's get that perfect power first and again like i said try and breed the opposite sex with the exact same passive role but there we have it guys a complete guide on how you get the best combat anubis in this game guys if you enjoyed the video leave a like really helps out if you like what you see want to see more be sure to subscribe and hopefully guys i will see you on that next one


Hi, welcome to theCUBE. I'm Lisa Martin on the ground at the Computer History Museum with the Association for Corporate Coast Silicon Valley. Tonight is their 13th annual Grow Awards and we're very excited to be with one of their big sponsors, Deloitte. Christy Simons from Deloitte, welcome. Thank you. Great to have you here.  You've been in the tech industry for over 25 years. You've probably seen incredible transformation. Tell us about what you're doing with Deloitte and the advisory services that you offer. Okay, so we offer a number of services, so advisory, audit, tax, and obviously consulting, to in Silicon Valley, to a lot of these emerging growth companies. And so it's been very exciting in my career to see the evolution of Silicon Valley and what I call old technology, right? Where we've kind of got the traditional software, semiconductor, box companies to what is now the digital economy or what I call the new technology and what is propelling the economy and the growth that we're seeing, not only in Silicon Valley, but in the natural economy. Exactly, so right now you are working, leading growth and development of Deloitte's technology practice up in San Francisco. You're working with clients and you mentioned digital and cloud and internet media sectors. Tell us about that, especially as you mentioned new technology. So a lot of them are startup companies which is really the sweet spot of ACG and it's why we're so involved with ACG. But a lot of these new technology companies that you mentioned, cloud, software as a service, internet media, data security, those types of companies is really propelling the digital economy. And so we see a lot of growth in that sector, primarily in San Francisco, but also in the broader Bay Area of Silicon Valley. Being a tech veteran as you are, you mentioned kind of what's going on domestically but also internationally. How do you see the influence of Silicon Valley, both here in Silicon Valley, as well as across the globe? You know, there's a lot of factors. We serve companies all over the globe and so primarily Silicon Valley is propelling a lot of those and to the extent that companies here are international. Most of them, a lot of them are multinational companies and do you sell their products globally? They're developed here, but their products are actually sold globally. Are you seeing kind of the inverse where companies maybe headquartered in Europe or Asia are influencing and bringing technology over to the Silicon Valley that's being led us here? Yeah, some of that, especially as we think about the engineers and the aspects and some of that development that happens there, obviously sourcing that from around the globe. I'm curious from an industry perspective, in 2017, it's like every company is a tech company. We look at Tesla down the street, we look at Walmart Labs and what they're doing there. How are you seeing some of the clients that you advise for? What are some of the industries that you're seeing are now technology industries? Yeah, so there's definitely a convergence, as you mentioned, to many industries, actually all industries. And so when we think about financial services, FinTech, when you think about life sciences, health tech, when you think about retail, right? You've got internet. So we're definitely seeing convergence and technology is impacting our daily lives and almost everything that we do and in almost every product and service that we buy, there's some form or element of technology involved. Exactly, it's really remarkable. And speaking of remarkable, tonight we're here with ACG to recognize two fantastic companies, Twilio, who's the emerging birth winner of 2017. And NVIDIA, the Outstanding Growth Award winner. If you look at NVIDIA, for example, Inventor of the GPU, which is really catalyzed, a tremendous amount of technology across industries as we were just talking about. You look at their market, what do you see them over the next couple of years? What are some of the market drivers that you think are going to impact NVIDIA? Yeah, so you mentioned NVIDIA, right? At Graphics, which NVIDIA is. We historically have been known for games and films and virtual reality kind of things. Well, now they're actually moving more into artificial intelligence. Artificial intelligence, AI, the new buzzword, right? So there's probably a lot of opportunities there for NVIDIA as that technology evolves and develops over the next several years. And same question for Twilio, who's winning the emerging birth award tonight. What do you see for them? So they're a cloud platform company for software developers. And so if you think part of the new technology is the cloud and a cloud platform. And so providing an opportunity for engineers to develop software and software is involved in almost everything that we do as well in our daily lives. So that convergence of all the industries that's happening, a lot of that is a result of software and the developers who are creating that software, Twilio is providing a platform for that communication. So again, tremendous opportunity for both of those companies in this new technology world. Well, Christy, thank you so much for joining us on theCUBE and sharing your insight with us. Have a great evening tonight. Yes, it's a great turnout. Isn't it a lot of fun? It is. We want to thank you for watching theCUBE. We are on the ground at the Computer History Museum with ACGSB. I'm Lisa Martin. Thanks for watching.


Okay, I'd like to welcome Michael Bokop, who's giving us talk about continuous delivery of Debian packages. So give him a big applause, please. Thank you. I'd like to start with clarifying the terminology. Everyone of you might know continuous integration coming from software development. Continuous deployment is what we understand with as soon as the QA criteria is fine, we ship or deploy it. We don't wait for any further feedback. Continuous delivery, this is what we are talking about now, is you release whenever you decide it's useful to release. So it's kind of a business decision. Does it make sense to release right now because some customers are paying us for this or users are waiting for a new release and it makes sense to release it right now? So in terms of, we can call it continuous integration in a further extended way. Why are we talking about all of this? It's like, what are the benefits we get from continuous delivery in terms of Debian project or in terms of what we are talking about here? Is the cost of a bug fix are getting bigger and bigger in terms of when we are in the pipeline. If we are in the beginning where we have requirements designed, it's quite cheap to change things and define things. What should it look like? And it's getting much more expensive later on, codes, development, accounting, operations. Once we deploy it, all the system, all the changes are getting much more expensive. So what we would like to have is some kind of independence. We don't want to rely on this specific laptop or on this specific machine. Like nobody knows how to rebuild it from scratch or how to change anything. What if we just take it out of operations? Will anything break? We want to be able to kind of scale, not just in terms of one build to many builds. Of course, this is nice, but we would like to be able to also start small and just grow as needed in terms of people. Maybe it's a small team packaging team, like we have five people. What happens if we grow to like 500 people? Reproducible, we would like to have a way of making sure the package we built, we can also rebuild like two years later on. That even reproducible project might be well known. And what's also important is that we have it predictable. Like we really want to have metrics to estimate build times, times to fix. So if we change anything in our software and the build time increases, it would be nice to identify what was responsible. Is it infrastructure change? Is it a packaging change? Is it like upstream change? Do we have any further build dependencies? So what we would like to know is, assuming we would have to fix this and that package, how long would it take us to deliver it to our end user or customer? I'd like to talk about a few problems. We had at a company where I'm working for. There was a kind of mess with golden images to ship custom software stack to customers. It was a long build time. As soon as it changed something, you had to rebuild all the image. You had to upload the image to the customer for one single small change. We also had like builds non-reproducible. It was unmanaged infrastructure so nobody knew on which machine was it built. Developers could even build their own package and upload it or maybe even a binary and just include it in the image. Also, the release process was holding back the ongoing development. As soon as we were heading for a new release, the code was frozen in the version control. Nobody could do any further work in master branches. And all the release process was holding back actual ongoing work. Getting more and more customers meant that we even had to build even more images and diverting from each other, like customers have specific needs or nothing to share, maybe even. We tried like Debian source package uploads to a custom build service, not so sophisticated as the Debian one, but in times of we don't even upload any binaries. We just rebuilt the package from scratch, but the developers still needed to manually build or release packages themselves. This means they need some tools from Debian or what you wouldn't do. They might have problems with actually releasing stuff. What should go in the change log? What version number do I have to use? So this was kind of a big problem. It solved some smallish problems in the first part, but not the overall vision we had. So what actually do we want to have? If we look at the continuous delivery book, the famous one, this is what a continuous deployment pipeline looks like. We have a delivery team, which has version control checks in some stuff. We have built and unit tests, and if they fail, we just go back in the cycle and start again. Once they pass, we can get to the next step, which is like automated acceptance test. If they still fail, we'll go back in the queue. Check in, trigger, trigger. Now we have user acceptance test, and if they pass, we can get to the release. So we transferred this into some kind of workflow for us. What would we like to have? The developer should just have something like git commit and git review. Just push it to the code review system. That's it. Nothing further. You shouldn't touch the event change log at all. Shouldn't care about what release are we actually facing. If we want to just go for ongoing development, just push to master. Jenkins, one continuous integration server, then verifies what we actually built. It relies on the event builds we automatically get. Once you do the git review, we get custom PPAs, which can be used for development and testing, like I want to test is what I'm doing actually working like. The developer might not know what the event package looked like in the end result. So he just pushes it, get a event package and can just install it on the environment. If Jenkins says, no, I'm not good, we are just going back in the queue and say, well, just fix it, git review again. And once you have the plus one, like I'm good, you can integrate the code reviewers like other people, just look at the event packaging stuff or possibly just the software itself and say, does this make sense? Can we push this? Yes, no. Once we're good, we just submit it to a master branch or whatever maintenance branch, we will look at that later. And we have some kind of different needs. The internal tooling, like we run our own infrastructure, we don't need a release dashboard, we can just push it and apply it on our infrastructure once we're happy with it. But we also have the product cycle, which is like a divan release, a new divan release. And we then decided to go for a release dashboard where we have all the projects and just say, we want to release a new version. I don't care about what's in the divan change log, we will automate this handling. We create the according branches, we create the according text, we create the according change log entries and apply the final build. And then all the release workflow, like automated testing, acceptance testing, the QA team can decide whether we are fit for release or not, just continuous. And then we ship it to customers like divan packages. It's really just app get update, app get upgrade. That's it. So that's what we actually want to have. Now, how did we get there? We decided on some principles. We just rely on divan packages and divan repositories for everything, no exceptions, whatever, really nothing. Only what's under version control matters. You don't have any chance to pipe us anything into the final product, into the final system without having it under version control. Otherwise it can't even end up there. And automate all the infrastructure handling. Like we don't want to touch any systems manually. All the configuration management systems, et cetera, should take place. We are using Puppet and Ansible. Automation, we have automated divan change log handling to simplify the releasing of new package versions. Like you don't want to think about what version number do we actually need. We know this is a new build or this is a hot fix or this is a minor change. We can all decide on that. So developers don't need divan or ubuntu at all. They of course are encouraged to do so. But sometimes you have developers working in very specific components of software and they aren't using divan or don't want to use divan for whatever reason. We have automated release branch handling. So whenever we have a new release, the according new release branches gets created the same for a new hot fix. Everything is created automatically. So once you want to fix an existing release, you know you can go at every single project, just go into the according branch and everything is there as released. We have VMs for testing and development. We are using vagrant, so whenever you have a problem and someone says there's this bug report, the steps to reproduce, all you have to do is like vagrant up, take the project, the product in the according name and choose the according version and everything else is set up automatically. So we have automated box builds at least once per day so that these so-called base boxes for vagrant are automatically there for the according releases. And important, but we have PPAs for development. So no version control freezes at all. You can always push to master. Masters should always be good, always good to release but what is actually released is in separate branches. So we just have fast forward approach. You always have to rebase. There's no option for merge and you don't know what you will get. It's just fast forward and the according release branches. Some improvements that we made in this process is usage of TempFS and Eatme data for just building faster or Ccash. So we try to get our builds as fast as possible. Once the user or developer just pushes a git review, the deep end package should come out as soon as possible. We use dashboards for extractions. So people can focus on their actual tasks. They don't have to look at Jenkins. Is this now blue or yellow or red? Where's the error? Whatever. Which build parameters do we actually need to use to end up in the according release? The dashboard takes care of this. It knows which project should go into a release. Which branches do we have? Which tags do we have? So the release manager as well as the according developers have according front ends for their actual needs. And very important is the code review system. The code review system improves of course code quality, but it's also nice for sharing knowledge amongst people. Like you are not yet working in some projects, but there needs to be someone reviewing the code. So you tend to ask, is this useful? What we are doing there? Could you maybe be more robust in the commit message to explain the actual situation you're trying to fix? And it helps, of course, introducing new people because new developers can just start hacking and they get good feedback from people used to work with this project. So you can actually see the progress in a bug fix, see what other people are fixing, what's the workflow there. So code review isn't just about the quality of code, it's also about the quality of a team. And what's under our system is the so-called Jenkins-Diebenglue. Many of you might notice the nice thing about standards is that there are so many of them to choose from, which is kind of like why I asked in the beginning, do you use COW Builder or S-Build? Then we have COW Dancer and P-Builder. We have D-Build, we have D-Backage, Build-Backage, D-Backage, Build-Backage. We have tons of wrappers or existing tools and they're like different flavors and this is good there and that's bad and whatever. So one of the main issues important for me was I don't want to build another tool, I just want to glue existing tools together to just be able to replace one component by the other if for whatever reason I'm unhappy with something. It's building on top of Jenkins. Jenkins was called Hudson before in 2011, it was renamed to Jenkins. They have weekly releases where you can just follow current development. They have LDS versions which is recommended if you run it in production or for actual usage. It's MIT licensed and nowadays there are more than 1,000 plugins available for good and bad purposes. Like you need to identify which plugins are actually useful and which ones actually help and provide something for you. There are more than 120,000 registered installations as of July and just as a disclaimer it's written in Java but it's absolutely not restricted to it at all. You can run whatever kind of project with it. It's like grown on steroids. It's really just a way of scheduling jobs of managing artifacts and such stuff. So why Jenkins deep and glue? We started to formalize the existing knowledge we know about even packaging, provide a framework we can work with, provide a common ground to base further work on if we decide to integrate new stuff. It should be built on top of it. We wanted to gather feedback from other users. What might they need and what's definitely useful and already happened is like you get contributions for further improving your internal system. So it was also a kind of community building so we can talk to each other what problems do other companies, what do other development developers have and don't create new tools or standards. Really we are just relying on what's available in the Debian ecosystem. And it should be easy to use also for non-Debian folks. Like there are people developing upstream software and they would like to provide Debian packages as soon as they have some kind of working in Debian directory. It's quite easy to get according builds with Jenkins deep and glue. So what's behind Jenkins deep and glue? It's open source project. Also MIT licensed started in 2011. We have more than 25 contributors to it so far. It's written mainly in shell, easy to adjust and extend. And mainly through hooks and according configuration variables, environment variables.  So technically it would be possible to just switch Jenkins to something else. But it's the easiest option and open source CI server available. It uses CalBuilder PBuilder as a build environment. Has out of the box support for Git and subversion. I know that there are users of Bazaar and Mercurial and whatever. But out of the box we support Git and subversion with ready to go scripts. It has repository management included with repripro, which everyone of you should know. And the so-called Fright, which is a very simple tool but seems to be useful for some specific purposes. And with plenty of QA tools included are in terms of support like view parts, LinkedIn, auto package test, tab age, per critic, shell check and check position. So who is using Jenkins, even glue? We have in the grimoire project, we also host the package, five in a drama first tools. Also all the grimoire projects or the grimoire packages. Postgres has a pretty sophisticated and big setup building for all the supported Postgres versions for all the all kinds of distributions. LLVM, Camelio, Wikimedia. So there are plenty of users and we get quite interesting feedback in terms of what they actually need. If you want to test it after the talk, there's the manual approach where you can just set up anything manually. But there's an automated setup where it just gets some script. Easy to review, it's trivial. It's just a puppet resype or module which sets up Jenkins, Jenkins, Steven Glue and three jobs for playing around. So you get everything what you need. It's set up in like five minutes on faster machines. It just depends on your system. It's set up in some few minutes. And this is what you will get. You get a Jenkins setup with three Jenkins jobs, Jenkins, Steven Glue source, Jenkins, Steven Glue binaries and Jenkins, Steven Glue cupboards. But this is what we will talk about now. The so-called whatever project you're working on source is generating the Steven source package for you. It's relying on the version control system. So it expects that everything is there in version control. Everything what's on the version control matters. It generates the upstream source, the event changes if applies the control file. It's actually executing a so-called script generate git or generate SVN sepshot. This also automates the change log handling. So you don't have to manually write anything to the change log. It's looking at your history. Thanks for git dch, Guido. Very useful. Important, it needs to be run only once per project, except if you're building for multiple distributions, something different. But out of the box, you just need it to build once as usual for Debian packaging. In the binaries job, then we do the actual Debian binary package build. We have a script called build and provide package. It automates the P builder or call builder actually set up. So usually, if you don't have any special needs, it does everything for you automatically. So you don't even have to set up call builder or whatever, everything will be set up for you. And you build once per architecture or distribution, whatever you are targeting, except for architecture all packages, of course. The Puperts job is useful to get automated install, upgrade and removal tests. It's optional. You don't have to use it, of course, but it's useful since you might forget about it. You don't have the according Puperts set up available if you're working on a package. Jenkins DB Glue automates this and you don't have to take care of this manually as well. We have the repository handling. It's automatically handling all the repositories without any manual interaction. So you don't have to call any repo command lines or yourself the configuration set up for you. By default, it's included in this so-called binaries Jenkins job just to make it easy. Once you scale out or have specific needs, you might want to just separate it into a specific Jenkins job. We by default assume that it's the so-called project repos job. And you can control it then to just build only in the binaries job and provide only then in the repos job. So you can be very specific what you need. You might even want to use the input or whatever other tool to just upload to a repository. Then you can just split off the binaries part and the repository part. It's just for having it configurable as needed. Then we apply further QA testing. LinkedIn is automatically executed in the source and in the binaries job. Auto package test is also executed automatically. So once you have a deep end tests directory in your package, it automatically invokes auto package test. It looks at the according code policies of Perl, Shell code, and Python. And all the results are available as tap and J unit tests in for Jenkins usage. Like you see in this line of code, we have a problem. Jenkins then can just provide according feedback. Do I fail the build or should we continue? It's fine for me if just shell check is unhappy. So all the results are available as according reports then. So an example of a build pipeline we use is like you push it to review, run some unit tests available in your Python project for example, then if this succeeds, you continue to building the source package. You run all the binary builds, run the puparts checks, make sure that the package itself is fine, include according result in the repo and then be able to just app get installed a package from the repos you're interested in. Now, managing many Jenkins jobs without driving nuts. Once you start for every single project to have like five or maybe even 10 Jenkins jobs and you have a product with 50 to 100 event packages, this is quite difficult to manage manually and you might want to change the behavior of all the binary jobs or all the source jobs. So what to do, the OpenStack project has a very nice tool called Jenkins Job Builder and it relies on YAML fires for configuration. You just have plain text fires describing how your project should look like and we have on GitHub, from the SIP-wise company, there's a Camellia depth Jenkins project which has an example of how this could look like. There are plenty of others available as well and it's very nice to use that way because you don't have to click anything in Jenkins web interface at all for handling the jobs. You have the possibility to just use it under version control. So you have your repos with all that your Jenkins configs in there and if you apply a change, you just commit it with the according message and of course you can include it in the code review system again. Like, does this change make actually sense for our infrastructure? Will the result look good? Included in testing environments, et cetera. Now, during this process, I mean, this is like, I was talking now for 25 minutes but this took us more than a few years to actually be there where we are and we had quite some lessons on the way. Developer needs might be quite different from operational distribution needs. They might want to have a specific package which isn't available in the distribution yet or they might need a specific version of a package which isn't available in the according distribution yet. Of course, you should contribute back to the upstream distribution in terms of here, of course, Debian. When reasonable, there might be packages which aren't distributable or whatever for some reason but it makes sense to just push back upstream as possible. Diverse people improve the overall quality. It's interesting to have some common ground of infrastructure for systems but for code quality, it's really interesting to have diverse people and this includes different distributions as well. Like not just think about what Debian provides, outside us might provide interesting input from other distributions. Code review requires good remote working culture. Open source folks are used to remote working so I'm not actually here to promote this because everyone of you might be used to working in this kind of working style but it's something not so much used in corporate environments that aren't driven by remote working culture. External dependencies, like we have failures on GitHub or Sipan is down or Unreachable or PyPy, PyPy, RubyGams, PuppetLabs, Parcona, these are all examples we hit in production usage. So what you definitely want to have is local mirrors of every external dependency you have. It's also good because you get a speedup of your build environment and you have staging options like before going and shipping this to the customer, you decide can I push an update from this specific module or package and only then I will provide it in the production mirror. Configuration management, it's essential to just have the infrastructure as code. If you want to apply any changes to all your Jenkins slaves, this should just go out to the configuration management, whatever you're using, if it's Puppet or Ansible or Chef, doesn't matter, but it's essential that you have some kind of configuration management to ensure consistency. Also consistent time zones, make all the systems in the same time zone, make sure they use some network time protocol so all the systems are, you can compare logs from different systems. Also the catch-22 situation, like we ran into this, the build scripts are broken, but the build infrastructure itself receives the updates for the build infrastructure. So we have some kind of recursion problem. How do you fix a problem with the underlying infrastructure actually applying those changes is broken? Also upgrading from VC to Jesse was everything working, but the deployment of the configuration management depends on unit tests which don't work on Jesse yet. So in terms of this recursion problem, you should definitely have some test infrastructure for setup, for configuration changes, so you don't break production systems, and this doesn't mean just the production system for the customer, it's also the production system of your own infrastructure. A rebuild of a system might look different from currently running one, even with configuration management, because just because you install the package now doesn't mean the same result will be in two years if you rebuild the system from scratch. So you should also have some testing for the configuration management in place. There are plenty of projects like server spec, M-spec data, test server, test kitchen, whatever you prefer, but you should definitely have some tests also for your own infrastructure available. Some tips. Regular rebuilds of all packages are very good and important because you apply recent policies and package build infrastructure changes to the packages. Once you change the underlying build infrastructure, the result might be different from whatever you're building. You might have parallel builds for your even packages, and this is a change in your infrastructure, and you have to rebuild the packages, and this means what we are doing is like for every single release, we rebuild all the packages. We never take the package from the previous release, all the packages are built with all this current infrastructure. If you have to deal with plenty of repositories, no matter if it's Git, Subversion, or whatever, the MR or MyRepos nowadays tool is very useful for dealing with large amounts of repositories. The Perl package group has very good documentation about this on the Devend wiki, and very important integrate your continuous delivery system in your monitoring infrastructure. If there's something broken, it should get the same attention as fixing something in customer production. As soon as you can't build any more packages, all the developers are stuck in development. It's interesting also to gather some metrics independent from whatever you use. If you're pushing data into Jenkins, you get build times and logs and whatever into Jenkins, but once you delete a job, it's gone. Also, there might be infrastructure changes or cleanup for the Jenkins jobs, and then you lose all this kind of data. So it's interesting to just provide the metrics into some independent project or database or whatever. We are using Garage as a code review system, and if you don't like the web interface, many don't know this yet, there's also from the OpenStack community or project itself, the Garty command line tool which provides a command line interface to Garage. So you can just use it on the command line. It has great support for offline, so you can actually go to your airplane, hack on it, review, and once you go back online, you can just push all the strings you did, which is absolutely great for working with it. And also good is some kind of Jenkins verified job, like whatever CI or CD server you might use, but let's call it a verified job to ensure the system actually is working as needed. Are the slaves there I need? Can I trigger a build of some specific job or test job? Does authentication work? Do I have the users look there, but do the nodes actually look good? Because once you get problems in your infrastructure when restarting the CI server, things get out of control. And we identified some anti-patterns for continuous delivery environment. As soon as you start with a manual SSH to some system, you might change the configuration, you might change the underlying system, install additional packages, which change existing behavior, and provide according debugging options is that. This is like keep the call builder environment up and running and provide it to another system or stuff like that, but try to avoid manual SSH. As soon as tests go okay, not okay, okay, not okay, and you don't know why, people will just stop looking at them and take them serious. They won't have any trust and they won't care at all. So once you integrate a new QA tool, make sure that it's working properly before making it mandatory to accept in the pipeline. Like if we want to have all the Puparts jobs to be okay, they should at least be once okay everywhere. Also try to avoid the pulling or crone jobs at the specific times, this is like the de-install run of Debian. You know I have to wait four hours to get my change in. Instead try to trigger immediate actions. Once you push something, immediately start with it. This is like in Jenkins jobs, don't pull for the polling for the version control changes. Instead, once you know that something is going up to the Git server or to the GARID or code review system, whatever, just provide according triggers to trigger the according builds. You want immediate actions and effects. The manual setup of machine configs, I'm not sure if this is an official term, but I just recently read it from Mark Haver, that there's no flake. All they look alike, but they are still different. As soon as you start to run a installer manually and there's one single change in it, the result might be just different. Really it should be all about automation. What was kind of a problem for us, and we have in Jenkins, several wrappers for that purposes, is like you have tools with no standardized output. It makes parsing harder. If you're developing a new tool, make sure that you can rely on the output and parse it appropriately. Checklists are a good way to identify that something is going wrong because you might just miss something from the checklist, the checklist might be out of date. Just use automation instead. If you want to check for something, use a Jenkins job. Hard coding, IP addresses, host names, board numbers, whatever, instead of configurability is bad thing. If you build the same thing in the continuous delivery pipeline once and once again, don't do this. It should be built once and then reused for tests for deploying whatever. If you don't have according notifications, developers start to wait and to pull for something instead of just continuing to work on it. We have some unresolved problems, actually. Dependency management is kind of an unresolved problem, like if you build the pen on package bar and you need another package built before, it's kind of tricky to get this automated, so we are researching on that front. We have built depends and depends, but we have no test depends, so we can't build packages which just have, which say I need this and this package, but just for testing, not for building and not for shipping for the runtime. Once you have high frequency continuous delivery, the deep end repositories cause apt to fail quite often because the mirror is updated and we have hash some mismatches. We are seeing this more and more often and I think we have some kind of ideas how to tackle that, but I'd like to talk to the according maintainers before. Pew parts, we had some like successful runs even if the package couldn't be installed. So the actual solution for Pew parts was remove the package and everything is fine, the actual package you try to test. So just to give you an idea, these are the projects that might be worth a look. Deben, everyone of you hopefully. Jenkins, Jenkins Deben Glue might help you. Vagrant is useful for all this automated testing. As a developer, Garret and Garty for code review is really nice. Jenkins job builder definitely worth a look. Everything under version control, automation is really important. Use dashboards for abstraction to not have users get into the details of Jenkins. Tests, tests, tests really. And built on established workflows and tools like the build package workflow works very well for us. And the only bad thing about this is once you're used to that working, it's really horrible to move outside of such environments. The one of you who are interested in getting deeper into this, we have Jenkins Deben Glue both on the 21st in Room Helsinki, would invite to show you up there. I think time is over. Yeah, are there questions? Hello, yeah. So I'm the Debian OpenStack maintainer. And so I've been exposed to a lot of CIs from OpenStack world. So I've been using Jenkins to build packages for like two years without Jenkins Deben Glue. The thing is I'm very happy to see that this kind of usage of ACI is spreading and that you are using it too. But what I would like to happen is that we use it widely inside Debian. To do that, unfortunately, we have to package Gerrit. Okay, so I started to do that during DebConf. I've packaged one Java library. Invite everyone to join that effort. So I don't know much about Java. Before DebConf I didn't even know how to maintain something with Maven. And so obviously I need help and I don't want to have it done all by myself. I simply won't have the time to do it alone. So first, please join me in doing that effort. I know everybody hates packaging Java in Debian, but we have to do it. That's the first thing. So the final goal would be, we already know that we have Digit, right? So Digit makes the whole of the Debian archive available for everyone to use using Git. What I envision would be using Gerrit on top of Digit. And then the people that are in the uploaders field would be set as core reviewers in Gerrit. And then we'd have this kind of... We were working about building the package, running few parts in Jan and whatnot. And then once it's done, then the people in the uploader fields would be able to say vote plus two, workflow. So that'd be the goal. And I think it's really, really important that we do that and that we have it available on Alioth or another machine. So the DSA already talked to them and they refuse to use Gerrit in Debian and I think they are right to reply this way. So please join me in packaging Gerrit. Do you know about how many dependencies we have left to go to package in Java before it will work? The question was how many packages are left in... Pardon? 60. Gerrit used once upon a time, used end to build. Now we choose this bug. So before we package Gerrit, we need to package bug. It alone is a lot of work. And then once we have package bug, like maybe it's 30 packages, then we have to do it for Gerrit, which is maybe again 30 to 40 packages in Java. I'm not sure. We will discover as we try to build it. Continuous. So just a short question. What are you using for the dashboards? We write our own ones. We started in different languages actually and just continued, but nothing highly sophisticated. It's really just an abstraction to get them. So maybe if I would start nowadays from scratch, it's some mixture of Go and Django, which would be actually preferred in our stack. Just a quick comment about the test dependencies. A quick comment about the test dependencies. So we ran into the same problem, that it's very hard to find out which packages test depend on me. And we discussed this with the package maintainers a while ago and we actually have a plan how to implement this. It's just not done yet, but we have their agreement. We know how it's going to look like. And so that will help us all for figuring out reverse dependency testing properly. Nice. I would like to chat about this later. Just a technical question. So the packages you deliver into production, they are all coming out of the continuous integration environment. So how are they signed then? Because do we have trusted keys on the infrastructure? We have trusted keys on the infrastructure. So designing is essentially anonymously, so to speak. Once you have access to the review system and you get approved packages, they might end up in the product if everything goes straight forward in the pipeline. But no manual signing. If you want to tag something for whatever reason, for example internal tooling or stuff like that, you're encouraged to get tagged with your sign. But no manual signing is needed to bypass. So the personal signing is in the versioning and whatever ready packages you don't rely on on that. Okay, thank you. Any further questions? Okay. How much effort do you think would it take to write a one-bit front, one-bit frontend for it? Like say I'm adding a new distribution stretch comes out and I want to rebuild everything for scratch and the system needs to figure out which packages still missing. I don't want to recompile everything, but just add the missing bits. No idea, but might be worth a try. We might join on that. Sorry for the question, but are you still of the opinion that it's not the right idea to package Jenkins, Debian, Glue and Debian? It's on my to-do list for this week actually. Yay! The main concerns I have is that Debian Pipeline should just, the binary packages should really just fit and so far I basically had the company vision or from different companies what's working for them. So I'm just looking at them, but it's definitely on the to-do list. I have a bug open on GitHub issues. There's time for one more question. No questions? So thank you very much for the talk and good luck.


Everybody forced here ripping 2022 in case football hobby a box case number 14 Say random divisions break the random results can be found at any time at latent sports cards calm Let's go ahead and get started. Good luck y'all. I think this is the first full case of in case that I've ripped They're almost out of it. All right guys just to stand something NC next there 329 gonna mark down a little bit All right to 25 is a Mari Cooper for the Browns Spiller on the triple jersey rookie for the Chargers to 99 AFC West AFC East on the jumbo patch to 50s the fondigs choice materials Got AFC south on the Damian Pierce auto to 99 scripted signatures Go AFC south And AFC East got a breeze hall rookie auto to 99 encased breeze hall auto 2021 NT and the mixer tonight Sorry for that 2022 NT photo and pumped for that too All right. This is rookie desert ritter Went in some games. He needs to get a little better But went in some games Chiquon brisker rookie triple jersey to 99 for the bears NFC north Zameer right rookie triple patch to 25 AFC west And AFC east got a rookie auto notable signatures of tyquan thorton AFC east All right encased rookie auto to 99 Aden Hutchinson NFC north The hutch starsky and hutch Dude jake's got hair like he's in starsky He's just 21 dude just like playing video games and That's it dude Video games watching baseball and coming to work got jesson herbert I'm going to school.  They have hopes We got an encore collection ladenian thompson patch card for the jets to 25 You go AFC east daniel thompson jets That's Oh, that's very cool to 25 sapphire signatures aj brown NFC east That is sick. We're gonna get that mag. That's a gorgeous card sapphire signatures Of aj brown over to 25 That is so sick. Congrats the NFC east Vicki Oh, big comeback win today sam howl great rookie catpatch autograph to 25 Dude, that is sick too.  That was definitely his best game of his career so far and say that second half was huge for washington Coming back on the road at denver It looks like they're a pretty solid team winning a mile hide never easy either way, so okay. We've got a um And i'm on our st. Brown Future wave can he pick a jersey card to 99 for the afc north Got on core collection elie manning jersey card the 99 for the NFC east winning the super bowl. That's gross, too And george pickings. That's fire. Love it to 25 sapphire signatures rookie for the afc north Beautiful pickings. We'll get that one magged Rookie sapphire six that time Oh, there's the guy right there deon sanders NFC east autograph to 15 legendary signatures Gotta get my sunglasses Gotta get my sunglasses sick deon Just said he was he just said he was he just said this i'm not saying that he just said that he was the best coach called football sick deon Which i think is funny It's hard to say after two games at the current level I guess three games in the current level But hey, that's deon If deon gonna talk we're gonna listen Traylon berks Berkey for the afc south Skymore for the afc west jumbo rookie patch substantial rookie swatches 25 probably had the best game of his career today, too alec pierce quad jersey rookie to 99 afc south On here you go afc south the trail on berks very nice one of 10 a rookie endorsement signatures Nice berks on card to 10 Yeah, they go to eugene I don't know I don't think they win that game but hey especially if hunters out like that's that's huge rookie endorsements Auto to 99 is breeze hall for the afc east again, but hey if your team's gonna get better you gotta play the best You gotta go through adversity All I know is that's a team that I know the most about college football I don't like it that way god rookie damian pierce for the afc south Tyler algear jumbo patch nfc south I don't know I'll send a box wrapper. I'm not sure what's up with the frame on that swatch to 15 It looks it dings, but like it's I think it's just a finish. It's not actually dinged Might be a little lifted. I'll send a box. I'm not sure if they'll replace it But like the right side of the the frame here looks weird And in hutchinson nfc north quad patch to 50. That's a cooling card John meets you the third afc south rookie out into 50. Glad he's playing now Stroud had a good game today And jahan dotson nfc east rookie endorsements auto to 99 j dot Oh pat's got a sack. There we go So they can do something all right pitman base Pierce afc south quad patch to 25 It's got a good game today, too We're shot white rookie triple patch to 50 for the nfc south Super scribe signatures is cameron hayward to 50 for the afc north Cool hayward there clean signature And in case this is jahan dotson again nine of ten rookie Notable signatures Or notable where he signatures might be notable first nfc east doing super super well here. I think it's still just the same slept in nt next No, no personal tonight. Zachariah. We'll be back pretty early But wait, do I have to anymore? I don't know But personal sunday are during the day By the way guys tomorrow purses might be full already. There's some monster orders and already just fyi Oh, yeah, I think it is saints still All right guys, just the saints left Get your link. They're on sale Saints on sale So dolphins Also guys next sunday, uh, just be aware and this will be on the schedule as well But sunday night, there will be no breaks We're all going to the orlando city game messy Succeeding all messy But we will do a sunday daytime pursels next week. I'm guessing the sunday fun day like the football mixer will be I think saturday probably saturday or monday. I'm not sure. I would I would assume it's saturday though some more natural place for it to be Maybe some flawless in the mixer this week since it releases uh davis mills afc west rookie triple jersey asia spiller to 99 And a lockets got the game winning touchdown today one of 25 gamers patch had two touchdowns Actually a huge game NFC west gamers jumbo patch AFC west rookie otto to five as isiah spiller scripted signatures. He really put his heart and soul into that one The signature And afc east again. We got sauce gardener to 50 rookie endorsements auto Let's do a recap Do a recap and then hopefully we can get nt going here Thanks for filling this one up everybody Sorry, it was kind of a lopsided break for Some of these divisions Not normally like that Relics of locket spiller rashad white damien pierce adan hutchinson That's algear alec pierce sky more elie manning kenny pickets lt as a jet trayvon walker zamir white jacquan brisker that's um staphon diggs isiah spiller Autos we had isiah spiller cameron hayward john mitchie the third traylon berks the 10 Uh tyquan thorton and damien pierce encased hits encased autos sauce gardener to 50 dots in the 10 dots in the 99 Reese hall the 99 deon to 15 It's a cool deon. This is sick rookie cat patch on a 25 sam howe That's super cool Hutchinson 99 Reese hall to 99 again Beautiful uh sapphire signatures 25 is a j brown and a sapphire signatures rickety 25 is george pickens Thanks again everybody moving on now to national treasures


Hello everybody! In today's video, we'll be talking about 4K drives to find out what kind of hard disk drive is that, what advantage it has, and how to recover a lot of data from such storage devices. Hello friends! If you need to recover deleted data, view or restore removed browse in history. Hetman software products will help you. Follow the link in the description, download the necessary program for free, install it and analyze the disk. The utility will show you the data you can recover, so you'll be able to view it or get it back. In our channel and blog, you will find solutions to any problem, from installing an operating system or configuring it to fixing possible bugs and errors or optimizing mobile gadgets. Our specialists will answer any questions you ask in your comments under the videos or articles. With the fast development of hard drive industry, the companies producing them started the transition from the traditional sector size of 512 bytes to the larger and more effective 4K sector, holding 4,096 bytes. However, there are plenty of people around who are still using 512 byte drives and haven't seen a 4K drive yet. Talking of data recovery, not all recovery tools are capable of handling this specific drive type. In today's video, we'll try to find out what kind of hard disk drive is that and what advantages it has to offer for an average user. As we know, when data is written to a hard disk drive, it is saved to its sectors. Traditionally, a hard disk drive sector is 512 bytes in size, which is also known as 512n, where n stands for native. The sectors are not really adjacent, but they do have narrow gaps between them. Here is how a disk sector structure looks like. It begins with a gap, the space between the sectors. This is followed by sync mark, which signals the beginning of the sector and allows to synchronize the way a hard disk works. After that, there is an address mark containing data to identify the number and location of the sector. Also, it holds the information about the sector status. It is followed by data field. And the closing element of this sector is ECC, error correction code, which is obviously meant to detect incorrect errors on the fly, if possible. Looking at this picture, you may guess there is plenty of space between the sectors with the conventional 512 bytes size. The more capacity a hard disk drive has, the more sectors it contains, and therefore it has more gaps. Evidently, quite a lot of space seems to be wasted. The main downside about 512 bytes AATDs is that they have to check every 512 bytes for availability of the error correction code. This way, for every 512 bytes, one bit of ECC is created to inform the operating system that the data was written properly. Also, it means that such a disk needs more space for data because every 512 bytes would be followed by a special bit between sectors containing the error correction code bit. Again, it results in heavy fragmentation when very large files are written to the hard disk because they will be scattered in pieces of 512 bytes each all over different cracks of the disk. Actually, 4K drives were developed to tackle this issue. So a 4K hard disk drive is a storage device with sectors 4096 bytes, that is, 4 kilobytes in size. Hard disks with 4 kilobytes sectors have the same physical structure, but instead of wielding data in 512 bytes portions, operating systems will have to read and write by 4 kilobytes in one go. Not only will this save time but also reduce file fragmentation. That is more, hard disk sectors will need error correction code bits only once for every 4 kilobytes. Disk disk structure reduces the gaps between sectors and makes using the disk space way more efficient. You can see the illustration for that on the screen. Compared with conventional hard disks, 4K drives waste less space on having those gaps between the sectors. In the new standard, known as advanced format, the sector size is 4 kilobytes, that is, eight conventional 512 bytes sectors are united into a single sector of 4 kilobytes. Although the new developments increase the disk space usage rate significantly, it's next to impossible to switch to the 4K standard immediately because of Windows compatibility issues. To help solve this problem, emulated disks were introduced, marked as 512e. This is a kind of hard disk having physical sectors of 4,096 bytes, which are divided logically into pieces of 512 bytes each. To make the transition from 512n to 4K allocation easier, most disks use an emulation technology allowing 4K drives to emulate 512n type by providing an emulated sector size of 512 bytes. This approach allows the new disks to be used with operating systems that do not support 4K sectors yet. The new disk format has the same space allocated for gaps, sync mark, and address mark as in conventional HDDs, but the space for error correction code has been increased to 100 bytes. The table you see on the screen compares 512n, 512e, and 4K end disks. The main advantage of 4K sector technology is using the storage device surface more efficiently by combining data. The information that would be written into 8 sectors 512 bytes each is now fitted into one 4 kilobyte sector. The basic elements of a conventional 512 byte sector, the identification and synchronization marks at the beginning, and the ECC area at the end of the sector are still there. Between the sector header and ECC areas, 8 512 byte sectors are combined into one, which eliminates the need for redundant header areas between each individual chunk of 512 byte data. This way, 4K hard disk structure improves greatly the disk space usage rate. In addition, larger sectors strengthen the integration of error correction algorithms, which can help to maintain data integrity at higher storage densities. In 4 kilobyte sectors, the space allocated for error correction code has been expanded from 50 to 100 bytes to provide the longer-waited increase in error correction effectiveness and resilience to surface defects. All in all, the combined profit from a more effective new format and improved error correction makes the transition to 4 kilobyte sectors quite feasible. Now the main task for hard disk manufacturers is to make sure that the transition allows users to gain more performance with as little side effects as possible. Talking of manufacturers, if you are looking for 4K drives to buy, check Seagate and AGST, which by the way stands for Hitachi Global Storage Technologies. In Seagate lineup is the Exos Enterprise series and with Hitachi is UltraStar models. If you are using Windows 10 or Windows 8 and you bought a 4K hard disk from either brand, there is no problem to use it at all. You can even have the 4K disk to be your system drive as both Windows 10 and Windows 8 or 8.1 support booting from 4K hard disks. For Windows 7, though, the operating system will create logical blocks of 512 bytes to let you use 4K drives in your system. Also, it should be noted that some utilities that you may wish to use to create system images are not ready to work with 4K drives yet. That is why it is worth checking if your favorite system image tool is up to the task. And if it's not, but you still want a 4K drive in your PC, find a utility that supports the new disk type. Talking of data recovery, some specialized utilities don't support this disk type yet. However, headman partition recovery is always among the best picks, and it can handle loss data on 4K drives easily. It will scan the hard disk or external storage device, find the loss data and help you recover it in a simple and efficient way. Here is what you do to get your data back. Step 1. Connect the hard disk to a Windows computer. Download, install and run headman partition recovery. Step 2. In the Drive Manager, select the disk, right-click on it and choose Open. Try a fast scan first. It will take less time. If the fast scan can't find the deleted data, then go for Full Analysis. Step 3. The file recovery wizard will scan the selected volume immediately and display the scan results in the right sign of the program's window. Step 4. When the scan is over, all you need is to select the deleted file you want to restore and then click the Recovery button. Specifying where to save the data and click the same button again to start recovery. Also, our program can create a disk image and conduct all recovery operations with this image, which increases your chances to restore the deleted information successfully, because multiple rounds of scanning may result in data overriding, which is not good. You can use this program for data recovery in any of the following cases. To recover files lost after removing or formatting partitions, system errors, virus attacks and other scenarios that involve loss of data. To recover data from internal and external hard disks, USB storage devices, SD memory cards, cameras and other devices used to store information. To recover lost photos, videos, music documents and other file types. Summing up. You know a few essential things about 4K drives and a good tool to recover data from them. And that is all for now. Hopefully, this video was useful. Remember to click the Like button and subscribe to our channel. Push the bell button to receive notifications and never miss new videos. Leave comments to ask questions. Thank you for watching. Good luck.


How would you describe the way in which these ideas are indeed radical? Well, I think the way to think about it is, Galt talks about, in Atlas Shrugged, about naming the way that people are living in those moments when they are living, naming what people live by. And that's how one of the people he recruits to his cause describes what he did. He just named what I'd always lived by. And it's not true that everybody always lives by what Galt preaches, what I recommend. But it is what people live by to the extent that they're really living, to the extent that they're good, to the extent that they're accomplishing something in life, and to the extent that they have real value, things that they care about and love, and that their life's about those things. So I think in that sense, it's appealing to content that people already have, that people already know is good, that people already evaluate positively, and that the world has been, there's always been some of that in how people lived, otherwise people wouldn't have survived. And there's more and more of it, at least in certain segments of the world.  There are lots of people pursuing their values. There's Silicon Valley and the whole Silicon Valley mindset, there's more and more people feeling empowered and thinking that they should be. So in that sense, there's something in all human beings, and especially in modern American and more broadly Western culture, that we're picking up on, or I'm just picking up on, I think we have to acknowledge that and own that and direct people towards that. On the other hand, those things have not been, and have certainly not been consistently identified as what's morally good. And insofar as there have been explicit codes of what's morally good, they've had little bits of that positive content in them, but the integrating principle for them has always been something that's antithetical to life on Earth, and antithetical to an individual's life on Earth and happiness. So whether it's God, some magic person who's supposed to tell you what to do and who to sacrifice to, or whether it's the society, or whether it's in the more technical realms, Kantian ethics or environmental ethics, it's always about sacrificing yourself to some set of duties of one sort or another. And we're very radical in rejecting that, or Rand was, and I am, and you. And in seeing how deeply that mindset has infected moral thinking, even in cases where it's not obviously about that, and how deeply it's infected the way that people talk about and think about both what's good and what's good for them.


Russia would target Selydov after Avdivka. Russia's intentions to attack Selydov after Avdivka are clear, Serhii Hamash, editor-in-chief of the Ukrainian Ostrov publication, said on Radio N.V. If the situation in Avdivka worsens and the front line continues to shift, then it is obvious that the next city that Russia will try to capture will be Selydov, Hamash said. He expressed concern about the changing nature of Russian shelling in the city. If a few days ago I was sure that they were still targeting military objectives, or at least areas where they believe our military is, given the city's front line status, now I have the impression that they have adopted scorched earth tactics. Indeed, there are a lot of hits on non-military targets, Hamash said. Russia launched attacks on civilian infrastructure in Selydov-Denechsk Oblast, including a hospital and a five-storey apartment block on February the 14th. Russia has been spreading fakes about the big losses of the Ukrainian armed forces near Selydov. Tavria operational group commander Oleksandr Tarnovsky said. A training ground near Selydov was supposedly targeted. Russian propagandists claimed resulting in about 1,500 people dying. This turned out to be yet another Russian fake. The fighting in Avdeevka-Denechsk Oblast, where additional units have redeployed as reinforcements, is many times more difficult than previous battles for Bakhmut, the deputy commander of the Third Separate Assault Brigade Major Maxim Zorin said. The Third Brigade is performing combat missions in conditions that even we could hardly imagine. The soldiers are facing not just superior forces of the Russian army, but their numbers are huge and Russian forces are pushing from all sides.