This study found that shift work combined with a pro-inflammatory diet was associated with the highest risk of death from all causes. This suggests that a healthier diet may help reduce the negative effects of shift work on mortality. This article was authored by Yu Kun Li, Xiaodong Peng, Xu Sihuang, and others.


All right welcome everybody. Thank you for coming to the session Designing Drupal experiences with Figma Before I get started. I had a few questions for the group Raise your hand if you went to the pantheon event last night All right, well congrats on making you here this early. I'm really impressed I didn't go because I was nervous about this so Who here is a designer? Okay nice developers Okay, a lot of developers great. Well, I think really everyone's going to get something out of this We're keeping it with really high level about what Figma is and how we can hand it off how designers hand things off to developers So first a little bit about me. Hello. I'm Matt Curtin. I'm the director of design here at phase two This is my third Drupal con, but first time actually speaking so Yeah, we'll see how it goes This clicker is also not working very well, so it is what it is So I'm sure you've seen this slide before or heard about phase two at some point If not, I'm very concerned. You need to go to booth 333 immediately after this There are huge glowing trees. You can't miss it and talk to some of our team and and learn more about us But we're a digital product agency. We're passionate about the customer experience granted and data insights And we've been around for over two decades Here are some stats really illustrating our commitment to Drupal over 85 developers on staff and over a thousand Drupal developers or Drupal projects that have been built So a lot of commitment to Drupal I wanted to start off the session talking about the old days of design handoffs I wanted to tell a brief story the design and creative team has worked really hard with the client to Establish design compositions for their next Drupal build Everyone's excited. We've been through rounds of revisions. We have a Final design approved by the client. We're ready to start building right We pass off the design files to the developers and here come the questions How do I inspect the designs in this case? We were using Adobe Illustrator to create the designs We had these beautiful colors in CMYK and you know, everything was looking great the clients excited Developers get the files they get a PDF. I can't inspect these designs. How do I grab assets? How do I look at things like padding font size things like that? next question What is the what which file is the main source of truth? We tip we've all seen a folder of files like this We're going back and forth with the client. There's a lot of hands in the pot designers helping out with the files You know the developers see this this folder and they're like, what am I looking at here? I'm sure we've all seen a file named final final final before Can you I elements be standardized while every composition might look beautiful and consistent developers start digging in and they find Really subtle differences with things like buttons and card treatments and you know, some things have borders some don't Sometimes the icons on the left or right. How do we standardize some of these components that we're building to do things faster? So the designers left kind of figuring out how to consolidate all of these treatments Where can I find images icons and other assets? We use a lot of images that were on brand a lot of icons back on graphics things like that All these are kind of locked into the design file and the developers have to keep coming to the designer to ask for different assets Really the designers spending a lot of time doing that What are the various in the active interactive states? So we might have designs that show the active menu drop-downs and other states on primary components But other subtle animations and interactions like a button hover or a focus state aren't really documented anywhere So the developers are left kind of assuming what those treatments might actually be How does a responsive grid impact component padding and sizing we create several desktop tablet mobile compositions, but again There's a lot of edge cases with devices and how do these? components scale and expand based on the device that they're rendering on again leaving the designer to do yet more Compositions and to show that breakdown So at the end of the day The designer was excited to move on to either the next project or continuing to create compositions that might be added in post-launch Instead they're spending a lot of time working with the developers to actually hand off everything everyone's frustrated How can we improve this process? in the recent years The industry has been flooded with several design and prototyping tools to make both the designers lives easier and developers Tools like sketch Adobe XD and framer just to name a few From the developer handoff things like avacoad zeppelin and vision design system manager All allow you to upload design files to share with your development team The creative team at phase two has really adopted figma as our main creative tool For everything that we do on the creative side and also development handoff So what features make this such a powerful tool and why did we want to adopt that? Before I get into that I have some starter definitions just so we're make sure we're speaking the same language as we go through these slides We'll start with a component So a component components are elements that you can reuse across your designs They help create and manage consistent designs across all of your projects So again, they're just reusable objects that you can use throughout all of your design compositions They allow you to work faster because you're just reusing the same components and edging content within them And they introduce consistency and rules to follow for both designers and developers as we're working on both sides of either the web project or the compositions Here is a giant button an example of a base component Here we can see you know keeping things very simple with this component We have a border radius background and a base color and font Defined there and text is centered within the button. So just defining those base properties Next is a variant variants provide a way to organize and combine similar components into one overarching components set So with variants we can introduce Subtle changes to a component like the size the content the mode or the state so hover or focus state for example It really helps keep all of our complex components organized when we pass things off to the front and devs So here's an example of that same button, but now we've added some variants to that So we've added some support for potentially adding an icon to the button Maybe a hover or focus state and even introducing a secondary button treatment for a background and changing the text color of that button Then the final definition is the design system So design system is a complete set of standards intended to manage design at scale using reusing usable components and patterns So we think about a design system think about the client that's coming to us They've spent a lot of time and effort establishing their brand and And you know that a lot of time and money doing that so as a web designer and developer I want to make sure that I protect that brand as much as possible as we take that and move it to the digital space When we're working in design systems, it allows us to to expand and grow the system over time and Work more efficiently as a team So why are we recommending Figma for all of this? First it's fast and platform agnostic Meaning anyone with any device can open up a Figma file and and start digging in whether using Apple machine windows or even Linux Allow us a real-time design collaboration. So many designers can be working in the same design the design file at the same time We can even click someone's avatar at the top of the page and observe that design are working We often do that internally a lot when we're collaborating on either a design review or just even a quick sync Like Drupal it has a lot of community support There's thousands of plugins available that allow you to install quickly and use it whether it's for designing faster Or you know checkings for accessibility things like that. There's a lot of plugins available Next level components will talk a lot about this today, but really building interactive components and defining states all in one place Client feedback and commenting so not just exclusive to clients, but really anyone can jump into a file Identify an item that they want to have a comment to or have a question about and there can be some real-time collaboration and discussion about that that element and how it can change Built-in developer handoff so Even as we're designing before designs are approved We can get developers in there and they can start inspecting elements that we're introducing into the design system and really check things like font size spacing Everything color all the things that we're introducing into the design right there And we'll go through that this inspect tab that we see here as well Before I do that I want to talk a little bit to designers in the room about some of the more design features here Global styles so Figma allows designers to establish reusable properties as I'm starting to create my design system in my compositions Things like color typography effects and layout grids can all be saved As I'm working in my style library And I can and by doing this and taking this approach by defining all my color sets and things like that I can quickly change These properties globally across all my compositions Content components so again, we've talked about what a component is we can establish these base components as we're working and creating these Compositions so no longer are we copy and pasting group layers and and just reusing them and iterating them on compositions We're changing them globally across all of the compositions we create taking more of an atomic design approach here So again starting simple with a component like the button we saw and then introducing those that's something like that into a more complex Nested or slotted component that we can continue to iterate a pattern library So I'll give a quick demo of what this looks like but all the components and base styles are all organized in a library And they're available to the entire design team as they're working and collaborating on a design project There's also multiple library support for larger organizations that have a much bigger brand or sub-brands So in this example we can see the library is on the left side I then click that and I can see all of the colors typography and things like that that I've already defined in my Design system as I'm working in these compositions. I can then grab and use some of these components from this library Let's say I want to close that and jump into an individual button I want to change the hover state on my primary button I want to darken that just to make it a little bit more prominent than I'm hovering over it I can then see I've changed something in the library I can then look at that that change I can see that I've not only impacted the button component, but also some of the more complex components that use it I can add a note about what I'm changing. So I'm changing that button style I can update that and publish that to the library once I publish that In this case the library is local to this figma file But if I have that library shared to other files All of those will will grab that change and designers working that file can see what I changed and pull that in Auto layout great feature for designers to really align and things faster You can apply auto layout to not just individual components to have consistent spacing between layers for example But you can also group components. So in this case, I have a grid of cards I can make sure that the spacing on the top on the between them on and below them are consistent throughout in this example have applied auto layout to the Entire frame for the final location page and what this is doing is making sure that As I add and remove sections of content the entire frame will grow and collapse I'm also applying auto layout to the overall location card grid Just to make sure all of the rows of cards are Consistently spaced. Let's say the client wants to add more T location teasers to the the first page of the listing I can continue to add these rows and my design Expands as I continue to add them Interactive prototyping so oftentimes Looking at flat design files isn't really enough We need to to add some prototyping so that both the client and the developer understands how how the end user will interact with something Smart anime is a tool in figma that introduces smooth transitions Between components just so it really mimics the animated experience that we're going to have as the end user on the the built-out app It allows us also to define flows that the user would take for a conversion Like making a purchase or finding care information It also provides a comprehensive list of triggers. So whether I'm touching something on click hover All of those triggers are all very easy to use here in the prototyping tool In this example, you can see I have a lot of app screens With various goals and providing information to a particular patient who's looking for care or looking for a location In this case, I've actually done some prototyping in the individual component itself for the menu So I can click here go to the prototyping tab and I can see all of the various prototyping that I've already done I can go to the main menu hamburger and see that you know That's being prototyped to open up here. I can also do a lot of prototyping to mimic a drill down menu as well. So And Once I'm done with that I can also even do some some prototyping in the artboards themselves so that The client when they're they're demoing this or the developer when they're looking at this They can see that these things are prototyped and clickable to various other pages and they can really see the flow there That's defined once I'm done with all my prototyping. I can hit play and I can actually prototype this directly on a device to really give that feel and I can start driving around So if this is shared with a client or developer, I can really understand how I can go and see my care options I can click some of these accordions and see all informations organized there And I can just drive around and scroll to maybe the home page Clicking the logo going back and seeing all the various sections and controls Some of these are prototyped and some of these are not just to kind of demonstrate like the fixed menu at the top and things like that I can then click the menu We can see all that prototyping work that I've done in that interactive component to drill down into various pages Let's say I want to go to campus maps and see all the various location options if I have an appointment somewhere I can quickly also click one of these locations. Let's say I have an appointment at the main medical center campus I can get walking directions go to the campus map things like that And I just allows me to drive around and really experience how the design was was really intended I Can also, you know, just go further drilling down into wellness services and access, you know, healthy eating fitness recommendations and resources and performance training Stakeholder presentations. We just saw kind of a quick demo of something like that but figma allows us to break out of the the art boards and the frames and Present in a more polished way to clients and then also follow that up with some share links as well And we also allow comp it's allows commenting and feedback directly in figma So we keep all of that feedback in one place In this example, you can see we're presenting a table of contents to the client So they can see all of the various pages that we've created for the various content types in Drupal I can click on any of those and immediately start interacting with something like the home page I can see how the main menu works see how the search can work when I open that up And then I can just start driving around and exploring the home page And we can really see how some of these interactive components come to life as I drive around Again similar to the app. We saw before I can drill down into sub pages We didn't list all of the services, but we can really see how I can go through and scroll and jump back up We even prototyped something like the live chat at the bottom Just to really see how that's fixed the bottom of the screen and how that experience will work We can go to other landing pages Like getting information about my chart And really just driving around and you can see how we use this for actual client presentations We drive around and show them how it works And then we just share a quick figment link. They have the table of contents And they can experience it for themselves offline If things aren't prototyped they can use the left and right arrows just to quickly go through some of these other pages And and see the other compositions that were created and If there's a change that they want they can quickly hit the C key and put a comment anywhere So let's say I want to change the treatment of the clear filters building. I don't necessarily like the red That comment goes right to me. I can then respond directly to that or simply make the change Accessibility is a really important aspect to everything that we do at phase two And figma really helps us there with some accessibility plugins The things that I really care about as I'm working is the proper color contrast Touch targets so the 48 by 48 pixels on on a mobile device is really important And then text in line height making things making sure text is really legible and readable on all devices There's several plugins that are available that make sure allow us to test things for WCAG double a and triple a We always have a double a standard, but triple a is like the goal to strive to So things like able contrast and stark are three plugins. We really recommend for that. You can see here I'm using able to test the color contrast on the menu that we just saw And I'm passing with double a and triple a on all different font sizes I have the proper contest contrast ratio and I can even get a preview of how someone with color blindness would would be digesting that And I can toggle on different types of color blindness as well Now let's get into some of the developer features as well for our handoffs First I'm going to do a tour of the inspect tab Really quick. We can see at the top. I've shared a link with the developer. They immediately start jumping in I inspect the button. I can see at the top of the screen that it's using that primary button component I can click that at the top and jump right into that main component and check it out more and see the variance I can see that that button is part of the hero banner component as well And I can see what variant that is Next is the properties the main properties we care about here are really the padding and you know Potentially if I could dig deeper I can inspect things like font size and other and things like that You'll also notice that as I'm digging deeper. I'm seeing Some guides up here that show me spacing between elements no more redlining for designers. I don't have to Put guides on the page and help developers see what the spacing between elements everything's really done in the app as they're inspecting things And I completely skip what this is showing but I can inspect something like the button and see that I'm using the white color I can see have the naming convention that and how I'm organizing that color and depending on how I'm developing I can grab the hex color RGB values and various other options Typography is another thing again. I can see how I'm organizing all my headings I'm currently using the the large h2 here and again. We can see that spacing between the image and the text group Things like shadows as well If an element has a shadow you can see I'm using a consistent card shadow throughout So if I make a change to that core shadow every element using it will have that change as well and finally Tigma does allow CSS to print So this would not be something you would copy and paste and actually use but it does have some suggested properties and Things that at least get development started and Finally, most importantly a lot of the assets can be clicked and exported directly in this case We're exporting SVG directly out of figma The responsive grid we talked about that before just defining all of our our different grid styles It'll make sure that we're aligning things properly in the designs and the developers have a good idea of consistent spacing throughout for grids and other layouts One one big question that we get from the development team all the time is you've accounted for really small devices and how things Get smaller, but what about the ultra wide break points? It's that's something we also define is How does the theme expand to those large monitors those TV screens that people commonly use now? Design system documentation so along with the Compositions and the component library we take it one step further and actually put together some component sheets Just showing all the various states and variants that a component might have this also allows us to put Design notes and guidelines to developers when we're passing things off to them So here's an example of that again. We can see we're using that table of contents format format So I can dive into my core components like looking at colors all the brand colors and documentation there My typography so all of the headings that I'm using you'll see they're just notes throughout I'm really defining those sizes in pixels and rems And then I can also see things like links and paragraph content along with hover states defining those Active and hover states on elements as well things like form elements things like that alert banners and And The buttons really just putting all of those out in the open and defining that all of the focus states And edge cases that a developer would need to account for when they're building these things I can also jump back to the table of contents at any time and go into some things like the WYSIWYG content seeing how we intend columns to work if we want to have image aligned with a call to action and things like that along with our Reference cards now keep in mind that these names also go exact Pair directly with how the developers are naming them in their design system on the front end Just so the client knows when we refer to an account component what we're talking about And then the developers everybody's on the same page if we if we say full video teaser We know exactly What I'm talking about there and and we're all speaking the same language about components there So It's at a certain point when the designs are getting close to approved or even when we have that round one design presented We're already starting to transition the design source of truth from Figma to Outline and to our web components that we're building on the front end So in this graphic and kind of see how things are talking to each other We have the design system working in Figma We have our our outline system, which is our web components that our team uses internally And then we have everything kind of documented in storybook and pulled together there So designers and developers can really work together and see how things come to life So here we see one example. We have a component in Figma And it's time to transition this to Drupal and to storybook And so we can see I've pulled that component into storybook as a designer I'm jumping in here and testing things out making sure everything's consistent Image size is consistent the sizing and everything that I had to find in Figma We can also see that things are being used as slots or variants Here as well so I can I can change this control to change the color directly to the green primary and so the blue I Can also change settings like the alignment of the text and image Right here in storybook and see that come to life I can also toggle on the code view so I can see how that code would translate to Drupal None of this is pulling an actual Drupal variable variables or any actual Drupal type code. It's all just plain old HTML that we're going to be using to to plug into Drupal and build that component So here's a preview of storybook So as a designer I'm jumping in here and I can really see everything's housed in here So all my various button styles I can interact with those elements I can view the code of those elements and then I can jump into some more complex components as well And really dig deeper into the storybook instance Just so as I'm digging as I'm looking at the interactivity I can you know collaborate with the developer and make subtle changes to make sure things are consistent from what we're seeing in Figma Really we want to account for all of the edge cases here So if we added a bunch of buttons so I might like talk about some of the padding between those buttons there And then when I jump into Drupal on the staging site, I can there's no surprises I know exactly what I'm getting when we when we start adding some of the real content in Drupal We're all on the same page with with how these components look So to talk a little bit more about outline Outlines a set of tools and best practices for developing a design system with platform agnostic web components So really at the end of the day, it's simply JavaScript HTML and CSS I'm not going to go too far in depth with with outline But Jake strong our senior software architect gave a great talk on Tuesday about outline And I definitely encourage you to go to our booth 3 3 3 and check him out at 2 p.m He's going to be giving it a demo about outline. So any designer developer anyone. It's a it's a great demo So what outline provides again talked about platform agnostic web components Things that we can reuse a from project to project from a design perspective I can see all of those base components and I have a good idea when I'm designing You know, what is one of my doing that's going to maybe introduce either a new component that we have to talk about adding to outline Or is there something that we can do to maybe extend it, but really I have my baseline for for all the components There's probably about 80 components that I can choose from And again, we we can you know build that internally over time as we run into more edge cases for for the needs of New components once we add one we can use it and extend it across any project. So we can develop faster and quicker And another good thing is it's it's available on github. So you can jump into that link github phase 2 slash outline and really just see the code base and see the base components that we're already working with So what's next? And we've already done a lot with figma And it's really ingrained in our in our processes, but what what it where we want to go next with it Um figma branching. So when we talk about branching, this is the same exact concept for developers as we would do with with github We would make a feature branch off of our develop would say It's and we can make changes code changes that and then we can test it and we can merge it right back in To our main code base. You can do the same thing with figma Several designers can be working on a complex design system. Let's say I want to make a change to a button I feature that off. I Make a merge request. I can check and see if there's any conflicts with another design that's working in the system And then I can commit that to the main master design system We want to introduce more animation and movement Prototyping and smart animation really only gets us so far But there's tools like principle and after effects that allow you to upload your designs to them and really create more Engaging videos and animations and transitions as I scroll through a design It's really where we want to go for mainly for client presentations to to really show them how that design is going to come to life on the front end Design tokens so we've talked a little bit about design tokens in a past presentation for outline. It's really where we want to go design tokens is not really a new concept, but We're really limited in these design tools as what type of tokens we have access to They're really everything that we everything that we do in the design system can be turned into a design token So like we're talking outline. It's a platform agnostic way for design to communicate directly with development through JSON Each of these variables contains an individual design decision So spacing color typography shadows and blurs all can be documented in an individual token The goal is to define properties in an atomic way There can be options for there can be either option tokens or alias tokens option tokens define the value For example that hex color while alias tokens define the purpose. So a CTA background or a button So we can see here in this example. We have blue 400 which is used to define that hex color for the blue But in a traditional way, I'd be applying that blue 400 to my headings my buttons Everything. So let's say I wanted to make a change to just the CTA background color I can't just change that blue because that would change everything. So I would change that individual token to target Just that element. So it's it's just a faster way to work and a smarter way to define our properties Figma tokens is the most popular Figma plugin for design tokens They help designers generate That those base tokens and that JSON output They can then sync that JSON Through JSON bin or github, which is what we use and push that JSON up to the actual web design system So we can see here we have our our base tokens defined we can see the color set and then we can see that translated to the tokens The craters craters of Figma tokens recently released released a base theme that is super charged with design tokens The theme is relatively inexpensive and really allows you to to dig in and see how Figma tokens can be used sometimes. It's a little bit difficult to get started And this is a great way to see how it's being used actively This is just a really cool example Of I'm actually in cabana right now And I can see you know here. We're looking at several car components One cool thing they're introducing is both a light and dark theme, which I think is a really interesting Perspective there. We're seeing more and more browsers and devices switching to light mode or dark mode So maybe when we're designing something we should account for that as well We can see here. I can jump into the Figma tokens plug-in I can toggle on my dark theme as I do that all of my components my Compositions all change to that dark mode and we can see takes a little bit because all the tokens are Firing but we can see as I click maybe a sub theme of dark how all of those components pick up those tokens I can see what that sub theme looks like for my accent colors backgrounds And then I can toggle on the JSON and see what that output would look like when I send that to my development team So here's my second to last slide or my pen ultimate slide So we just pulled together some plugins of choice We've seen a few of these already Figma tokens able Things like that a few others. I wanted to point out as the downsized module plug-in Sometimes we're working with a huge design system a lot of compositions. We have a lot of imagery icons being used This downside plug-in allows us to globally downsize all the images we're using to really Make that file much smaller and faster perform it Export comments is another one that I've run into that I use a lot While we want to keep all the feedback and comments in Figma This plug-ins a great tool if the client wants to have all the comments exported into like a spreadsheet or something like that It's one click you generate an Excel document. You can use it as a Google spreadsheet, whatever and keep everything there as well All right Thank you. How are we doing on time? Pretty good. I would like to open up for questions for the most part there are some that are They allow some features when you install it But then you know if you want like the upgraded features, they're like, hey, give us five bucks or something so like they're pretty inexpensive, but Some of them do have a cost for them Yep So in terms of like the larger and smaller artboards We're just using pixels But what we do is we're defining all of those breakpoints So like I'll have my headings folder and then I'll have my various device folders as well for all those different sizes So they'll be like an H2 Maybe they might be like a jumbo H1 Then there's like a standard H1 and then we we size all of those down so on those individual devices I'm just using those those mobile specific ones Exactly. Yeah I would say with those different rounds of revisions typically what I'd recommend if you if you want to keep working in the same file Sometimes it might make sense when you share a bunch of design compositions Maybe you globally like detaching the instance of those components that way if you like change something You can always keep that share link and that will just be the share link forever And then you can keep like having more rounds where you're working with live components So I would just like duplicate all of them say round to Keep those components live because you're iterating those and then like keep the round one locked in that way Someone can see oh, where were we before what these designs look like before if you change the live component You're change that design to that's a common problem that we run into too So I just recommend like detaching those instances that we lock those artboards in and you and each round You just share a different link and often times clients like to keep it like a living link and we keep iterating They don't even maybe we export all that all of them as flat PDFs just to like keep it timestamp on those We just keep iterating the same file over and over Mm-hmm We organize them in like pages and sections So like we'll have a section dedicated to those that doesn't those design documentation sheets that you saw And those evolve over time. We don't we don't make rounds of those And then the individual pages where we lock in so we clearly label those so like if I jump in I can say like look at this This is the final approved compositions. So it's really all about communicating within the app and the labeling you're doing Yep in the back To edit like the boot. So you basically installed I couldn't hear you that well, but you installed like a bootstrap 5 base theme in Figma Which gives you like a library components you can then use right? And you're asking How you work with that? Mm-hmm. I would say the benefits to that is bootstrap is a web framework So your development team is gonna like if they know you're using that kit They they install bootstrap on there and they start working with those core components And then you're modifying like the treatments of those components and the code the output of the code doesn't change It's just really just CSS and how you're manipulating the actual components So there is value to that in our case We're using outline as that framework but of web components, but you could use bootstrap or foundation or something like that We're moving a storybook is essentially our pattern lab a few years I would say it's taken a while and it's it's still evolving honestly like What I showed today could be slightly different tomorrow We're constantly improving it based it based on our need for project to project So I might find that I need to add more documentation on particular components But the the cool part is is once I do that I can replicate that on other projects moving forward So it's evolving, but I would say it's taken a few years to kind of evolve. It's at this point Yeah, so the value of outline it's platform agnostic So again, I'm looking at storybook, and I'm just seeing the HTML and CSS output no twig at all. So I Can translate that to a react app. I can translate that to Drupal. It doesn't matter what I'm building at the end of the day What I'm seeing in storybook is just the web component that I would then be injecting What I need for react or Drupal into it So it wouldn't be like pattern lab, which is entirely twig based And it would only work with Drupal or a twig based system It would it can be applied anywhere, and we've already done that on several projects. Any other questions? Yes Yeah, that's that's very true. I Keep things very basic. I would say I wanted I wanted to find my my core interactions. So You know those like button interactions Maybe the image zooms a little bit when I hover over something. So really subtle things like that And if I decide to do like a video background or a transition, I might pull that into principle and do that I guess I'm one off That way I can say here's more of a drastic animation But let's look at the design file and interact with it But more like prototyping menus and things that I'd have to like click or hover on to activate as opposed to a lot Of flashy things in the background and figma Yes Okay into figma directly I would I Definitely encourage you to go to the booth and talk to Jake. I'm gonna completely defer that question to Jake and he can he can illustrate that process as it from the design standpoint I get shared a Staging link or a storybook instance link and I look at a component and test it there and compare it to what I built in Sigma in terms of how that's done I I would venture to say that we have our outline components. We do our base install of that We start modifying that and pulling the code into Storybook it basically storybooks a way that we communicate back and forth from figment to outline Eventually with figma tokens, we'd love that to be automated. Yes That's kind of where we want to go and by using the JSON output We could communicate and say oh this border radius changed or this color change subtly No need to the developer even be involved. It's just done Yep Yes, and no, I would say like For sure from a standpoint of like I know all of the components they're working on I know their methodologies and like what questions they're gonna ask me I actually was coming from a place where I would design and have to build myself So I was using a lot of the things like bootstrap Myself to to build out those components So I'm less involved in the actual like coding of things But hat knowing like how those components are structured out of the gate in outline I know like kind of what I can do and and not do or what I can do and then say hey developer I know I'm extending this component functionality, but here's how I think we could modify it or add a new component For example, so it does make it easier in that regard It's not like a guessing game of like how are we gonna build this thing? How is it gonna be coded? It's we kind of have an idea already So Zeppelin you could upload a Figma file and then I don't use it too much But I know that you could upload Figma and that allows developers to kind of define the tokens that way so technically yes because we could Like mold Zeppelin to work with our web components Outline would be really beneficial for headless. Yes, because again, it's platform agnostic So it's really just JS with HTML and CSS output. No Would it be hard to implement? We're getting out of my element here. Any other questions? I will be at the booth After this if you want to come in and chat And then again Jake will be talking outline. So any technical questions like he can really answer those I'd just be answering the best I could and maybe give you the wrong answer


Okay, Simon asks, I am an objectivist, but I disagree about free will. Could you speak to the idea of free will, not existing, but consciousness existing created by the brain as an emergent phenomena? But then why should I talk about it? If you have no free will, it's a meaningless idea that you can have reason without free will. Reason needs to be activated. Something needs to activate free reason. Reason is not automatic. People are not just reasonable. People are not just rational. It's not just an automatic function. Reason and rationality. They need to be turned on. Effort. Effort needs to be exerted in order to get them going. That's the free will. The free will is exerting the effort necessary to reason. It's exerting the effort necessary to focus rather than drift. So, consciousness exists, but consciousness, human consciousness, is unique because human consciousness has the capacity to, in a sense, turn itself, not turn itself on, but to utilize the reason that we are capable of, that our brain has made possible to us. But that doesn't happen automatically, is the point. That doesn't just happen. You have to, again, turn it on. You have to choose to use it. That's what free will is. So, I can't talk about a consciousness existed created by brain as an emergent phenomena. That's an animal consciousness. That's what every other animal has. They can reason. They can think. They can be rational. They can't change their mind in a deep sense. They can't turn it off either. They can't turn their consciousness off. A cheetah can decide, I'm not going to think today. Well, not think. I'm not going to do the things necessary for my survival today. I'm just going to laze around and if I dive starvation today, so be it. A cheetah can't do that. A dog can't do that. They can't make that choice. There's something very different between human beings and cheetahs, human beings and dogs. Human beings can make that choice. You can actually say to yourself, I'm not going to engage. I'm not going to think. I'm not going to use my means of survival.  And if I die, I die. I don't care. I don't care. That's not consciousness doing that. That's a very specific type of consciousness. And it's a characteristic of consciousness. It's a faculty of consciousness. Which is reason. Reason is a faculty of man. And reason is free will. It's ability to say no. Or yes. I mean, more importantly, yes. Yes, I'm going to focus. Yes, I'm going to think. Yes, I'm going to go by facts and reality alone. Yes, I'm going to apply my reason every way into all things. Yes, I am going to survive. And no, I will not die. No, I will not go out of existence. That's what free will is. And that doesn't require magic. It's just a characteristic of our consciousness. That part of its emergent properties or part of whatever we don't know exactly is this ability to control. To control your decision. To say I and have it mean something. So absolutely free will exists. Absolutely it's not magic. We don't understand what it is scientifically. But so what? We don't understand scientifically. A gazillion things that happen in the universe. And we don't declare therefore that they don't exist. Or that they're just imagination. That we're making them up. Just like we don't declare that they, God. We say, I don't know. It exists. But I don't know. I don't completely understand it. I don't completely get it. To say because we don't understand free will from a physics perspective is to say nothing about its existence or nonexistence. Free will exist because you can perceive it. Free will exist because you can introspect it. It requires no more than that. It is an axiomatic concept in that sense. It is. Every attempt to refute it. Every attempt to deny it refutes itself. Who is denying the free will? How do you know? Who is you? What does it even mean? What does it even mean to say I don't believe? Well, what choice do you have if there's no free will? Why are you even talking to me? How does objectivism differ from the philosophies that many of us have been exposed to in our youths? Philosophies based upon religions, theologians, dogmatists. The very first difference. Objectivism tells you that it is not right. It is not proper to men to take anything on faith. Religion is a matter of faith. You accept a religion emotionally or because you were born to it. You have not chosen it rationally. What objectivism will tell you is that reason. Man's reason is his basic means of survival. That is the most important faculty which he has and he has to guide his life and make his choices by means of his rational faculty. He has to make his own choices but he has to know how to make them. It is immoral for him to act on his emotions, to be guided by the whim of the moment. That objectivism holds as very wrong, very immoral and morality in fact consists of following your reason to the best of your ability. So that rationality is the basic virtue from which all the others proceed.


The narcissist expects you to sacrifice your life for them. They expect you to give up everything you have because they have nothing. They have no goals or dreams. They have nothing they're working towards. They have nothing to be proud of. They're just getting by. So they're always looking for someone to take care of them. They're looking for someone to support them financially. They are parasites. They live off other people. They live at other people's expense. They go from job to job, person to person. Because they get bored very easily, they're never satisfied with what they have. They always want more but they don't think that they should have to work. They feel entitled to large amounts of money which they don't want to work for.  You may have a good job. You may have plenty of money but you will end up short of money. You will end up needy and wanting if you had dinner with a narcissist. You will end up poor and disadvantaged because the narcissist has all of these needs and desires.  They don't feel that they should have to work. They feel entitled to other people's money. They believe that they are deserving of it even though they've done nothing to earn it and you've only got to look at their past relationships and situations to see that. They've always depended on other people for money and they feel like people have let them down. They feel like people have not given them enough attention and when that happens they will cause drama and chaos and then they will move on. They will find someone else and do the same thing all over again.  They will force you to support them and they will make it very difficult for you to work by them not taking care of the children or other household responsibilities. You may end up having to employ a nanny or caretaker while the narcissist stays at home and does nothing.  Money that you have earned, money that you have worked hard for.  They stay with you because they don't have a home. They don't have anything of their own. They don't have any money that they've earned from a legitimate practice. They will often resort to being involved in illegal activities that earn money or they will leach off their victims but they will have the nerve to make you feel like you're not doing your fair share of the work.  They will compare you to their past victims whom they have exploited while they're not doing anything for you. They will never be satisfied with anything you do for them. They will always expect more. They will feel like they're too good for you. They will feel like you owe them something when they don't have any reason to be owed anything. They're not doing anything for anyone. They're not contributing anything of value to the world. They just have an inflated sense of entitlement. It's all in their head. They're crazy. They're detached from reality and they expect you to participate in their fantasy.  They think everything they have belongs to them and they think everything you have belongs to them. They will never feel the need to share anything they have with you but they believe that everything you have is theirs and they have no interest in you as a person. They don't even care about you. They don't want to listen to you talk about yourself. They don't care about who you are. They don't care about what you might want and need which is why the longer you stay with them the more your health and finances will deteriorate because they want all of your time energy and money but they expect you to be okay with them leaving and doing whatever they want whenever they want and if you're not okay with it they will get angry. They will bring up things that you've done in the past. They will exaggerate it. They will make stuff up to put the focus on you to take the focus off themselves because they don't want to be held accountable for their actions. They feel entitled to do whatever they want. They don't think that they should have to answer to anyone which is why they will never apologize. They will never take responsibility for what they've done. They will never try to make things right because they don't care about what you're going through.  Thank you for watching. I hope this video resonate with you. Please like, comment, share and subscribe. If you would like to donate my PayPal link is in a video description. Coaching inquiries you can email me at coaching at NARC Survivor at the Cudder UK. Thank you for watching and I'll talk to you soon.


I will just put the title later. Friends, it is very important that we are all here to talk about many things. So we will talk as usual because the place where we are talking, it is known for the freedom of expression and freedom of speech actually. This is the place JNU is actually branded for that. Many tried many past one year to curtail that, that is impossible. That is impossible if the JNU will be like this and it is going to continue like this. That nobody can stop. Because that is not because of any one person speaking, not speaking, no. Just a week before I met Radhika Vemula. Just a week before. She was just coming and asking me, you just suggest and request. Raja, that is another son. Rohit is the person, next is the Raja. Raja not to enroll in any university of this country. But Raja when he is coming to the same position, he is in an MSC, some geology applied or something that I can't understand. Bhagavad Gita. His score is also very big and that is enough for the enrolled in any university.  So she is coming and begging and saying continuously, what Raja is doing today? Raja is running a auto rickshaw in the Kuntu. It is a shame for the country. You talk about the country so great. You talk about the GDP, you talk about the ADP, BDP. But the student who got the first class in the MSC geology is running the auto because he cannot go to any university because universities have become a gap chambers for the colleagues.  We are unable to enter into your university. Yesterday, Radhika went to the Hyderabad University. She went around the 2 o'clock. There was a meeting in a Sundarai, Viknanakendram. She attended the meeting. Soon after the meeting, she went to the university where she lost the son. The son was killed by the university administration and everybody knows. On the same university, she wants to just enter. What Radhika can do, such a greatest or such a great, what she can do in the university? The whole university and the Telangana police and the administration, they are completely blocked there at the gate. And they have not allowed her inside. And she just wants to enter. And what you are talking about here democracy, what she did, she just want to enter. We are really in such a position today in the country. The crisis of the democracy, the title which you have given, that is an opt for the situation in the country. It is 11 o'clock she called and she said that, I just want to enter and go, but they are not allowing me. And finally they have taken into the jeep and van and they kept the jeep, not taking into the any police station in one ground. After two, three hours, they have taken to the some other place and they just left us. The state is not willing to listen. The state has becoming a more cruel and cruel day by day. The state is taking a kind of a shape of the criminality. There are all senses if you are just to open and listen to the state, their voice. The culture of the criminality is a hard thing. But the problem here is the state has lost the confidence of the citizens. They are not a confident on all of us. They are treating all of us as criminals. Person like me, I feel many times that I am not safe here. People are talking many things and we want to talk many things. When you say something, they are coming and telling us that you are a Deshidroyi. You talk anything with the sense, with the knowledge, with the rational, with the logic. They are branding as a immediately Deshidroyi. This is the thing that is happening. And I talk about this and I would like to talk also because I have an experience with the cow and the beef, how I eat the beef from my childhood. I want to say everywhere wherever I go. Very openly, very proudly, I have to say that that is my culture. But as I have just seen on the newspaper, the cow is not just a kind of a super animal. I had known until today that it is a super animal. A cow is just a super animal. We have to, everybody has to believe that. So, why I oppose that? I have a reason for that. Why I say this? If you make one animal as a super animal, all animals are down to that, which means you are creating a kind of irrational and you are making us to believe that.  See, no, they can do anything.  My dear friends, why I am bringing this? It has an history. The argument has an history. The same people 4,000 years before, they said that there are, somebody is the supreme. Some human beings are the supreme and some are the untouchables. Unfortunately, we everybody believed. That is the reason the Indian society is a unique world society. If it is a knowledge society, which has any belief on the equality, have anything still in the country today. If it is a knowledge society, we are talking about we are very knowledgeable people and we have, in knowledge society there will not be discrimination. You cannot have any differences within the human beings. Now they are bringing the differences between the animals.  They are testing all of us if you believe this.  We are here to prove that. We are not the fools to hear to education minister. You have to talk about and the rational theory is the scientist who has given the life to develop so far. So now you have to come to the rationalistic logic. About the Swachh Bharat, it is a new scheme which he has announced, he is thinking. But it was before also, Clean India. We can translate it into Hindi. If Nayarchi is not necessary, because even before 2014, there was a scheme called the Clean India. Clean India project in the Agra, Jaipur and many visiting places. Foreigners come and see the country. If it is too dirty, they think Indians are dirty. Because the foreigners thinking that we are dirty, they have announced the scheme called the Clean India. Clean India is not a new project. It is a very old. The only thing is the Narendra Modi ji's name Clean India says Swachh Bharat. Clean India has made Swachh. Swachh is coming to the pure and pure conditions. So this is why they have made Swachh. So they don't want freedom. But the problem here is, Safai Karmacharis has not been taken into consideration while he is ending the program or talk. The people who clean this country 4000 years and made today to this level, those people have not taken into consideration. Second is, for them past 30 years, we made a kind of a big movement across the country, not me alone. There are thousands under 6000 volunteers and they made finally that manual scavenging we felt in my childhood. I felt that manual scavenging, we are doing the scavenging because we are illiterates. That is what my neighbors told me. We are doing the scavenging because we are poor. We are doing the manual scavenging because our people are drinks, alcohol and alcoholic addicts. They don't have the strength to do any other hard work. This is the reason we are all doing. That is what all my family members, my community, my neighbors has told us. So I also believed that and I moved like that. In India now, not just the scavengers, everybody we are all cleaning, it is a Swachh Bharat. My dear friends, please understand there is a very clear conspiracy in announcing the scheme. And for that, without the parliament approval, they have given 2 lakh crores immediately. And for the manual scavengers rehabilitation, it is 570 crores 3 years before. This year it is just 10 crores. For the rehabilitation of the scavengers, the amount will come down. And for the construction of the toilets, the amount will go up. Because the corporate companies have come from the many countries. They are constructing the toilets. And for all these toilets, they are constructing the 12 crores toilets in the country by 2019. To construct the 12 crores toilets, they are not mobilizing just 2 lakh crores. They are also taking the... Swachh Bharat says that you know. But to just conclude, the important is when you are constructing 12 crores toilets in the villages, you are also constructing 12 crores septic tanks. Who are going to clean your septic tanks when you don't have any mechanized way of cleaning? Already 1370 people within 2 years died in the septic tank and sewer line. For them the government is supposed to give 10 lakhs compensation to pay that the government of India is not having the money. But for the Swachh Bharat they have the 2 lakhs crores. Please understand the democracy and the priorities of this country how it is moving. That is the reason I just want to inform all of you. Uttar Pradesh, Madhya Pradesh, Bihar, Uttarakhand and Gujarat, these places, still the dry latrines are there. We are giving the notice to them 3 months if they are not hearing again because we have given 87 times in some places, 34 times in some places, memorandums and the pictures. If the collectors are not hearing to us within 3 months, the Sapphai commentary on Durand with all other progressive people in the country, we are going to destroy all those toilets and we are going to take care of India as well.


Thank you for coming to my talk. I appreciate it. This is me. I'm Jason. I am a software engineer at Splunk, but I'm not here to sell you anything. The opinions in this talk are mine alone and not necessarily those of my employer. I help out with the Java Instrumentation project. I help out with Android within open telemetry. So that's kind of my background. So this is maybe the dumbest outline of a talk you'll ever see. It's like, what's the problem? Who cares about that problem? And then what are we going to do to make it maybe a little bit better? Hopefully, we'll get through that today in 25 minutes. So maybe some of you have spoken with this guy before. He's like, well, I added this instrumentation to my project because I want to know what the heck is going on. And suddenly, my HTTP response latency went up by a whopping 75% and he is really concerned. Has anybody talked to this person before? Yeah? OK. All right. And then maybe he goes on and he says, well, therefore, I'm very smart here. I conclude that I can never put this into production. It's going to be too costly. It's going to burn through cores and I could never have this in my environment. All right. And then maybe, I don't know what else he does. He goes back to hand-tuning assembly code or something. I don't know. He probably says some other words. And that's fine. I mean, that comes from a good place. But I think it's not super well-grounded. And I want, in this talk, I hope to give you a different way to think about overhead because it's not as simple as most people think. So in order to generate telemetry, the computer has to do some work. And this work consumes CPU cycles. It has a cost associated with it. Instrumentation uses resources and that's what we're calling overhead. So you have an app. It does some work. You add instrumentation. It does the work it did before, plus a little bit more work. All right. As much as we would like it to be free, as much as we would like instrumentation just to be the smallest, most microscopic layer on top of your application, it's not. And I even wrote down here, you know, you think that offloading some work to a collector might solve your problem. You might think that offloading or sneaking in under the application by using EBPF eliminates that problem and it's still not true, right? If you have a collector on the same machine or you have to put data on the wire to get to a collector, that's just a different problem. Sneaking in with EBPF, well, I'm sorry, that code still will execute operations on your central processing unit. So I mentioned compute. Users will almost always, after the introduction of instrumentation, they will notice an increase in CPU utilization. And that is just the way it is. Hopefully, it's not that noticeable. And memory as well. Every single object, like piece of telemetry, every span or metric measurement has to take up something resonant in memory and it's gonna, you're gonna incur some cost, some overhead cost. And then if you have a threaded platform, every thread that your instrumentation uses will also have kind of a built-in natural amount of overhead. Now when your CPU goes up and your memory goes up, guess what happens? Your latency will tend to increase, like overall. And if you have an environment that has dynamic allocations and you incur some garbage collection costs, that use of memory can also use CPU in the form of garbage collections, further increasing latency. Now that's not the only form of overhead, right? It's not just memory and it's not just CPU. There's also startup time. And it's not always the case, right? Some instrumentations require no change in startup time. But like I work in Java a bunch, we have tons of instrumentation that gets applied at runtime. And so when every single class is loaded, there's an instrumentation step and that slows down the boot up process for that, for that app. And like I said, not every app is impacted by this. Some systems have compile time instrumentation or build time instrumentation. You also see an increase in bandwidth. If you have telemetry in hand and you wanna get it somewhere, you gotta put it on the wire, you're gonna see an increase in data usage in almost every case. And usually it's within tolerance, it's okay. And then you're also potentially gonna see an increase in disk space, sometimes from the instrumentation itself, like the collector binary or a jar file or whatever your instrumentation looks like in the case of Android, which I'm gonna be talking about later. We have a mechanism through which we buffer telemetry on disk for a little while, and so there is an increase in disk space potentially. If there's one takeaway from this talk, it's this. I want you to really think about this. Okay, so the person says, my HTTP response latency went up by 75%. Well, I think just right off the bat, that's probably a lie. And I think many of you know why, right? Your service does not have just one latency, you probably have some sort of like distribution curve and some users see one thing, others see others, and that changes constantly for most applications. Okay, fine, really what we're talking about is just like median latency, that's the thing we actually care about. Okay, well, we can talk about that. So let's talk about that, shall we? And let's do so with a common language called math. So let's take an application, no instrumentation. It's latency, it's measured latency that you can measure from the outside of the application. Let's call it MN. That is equal to the latency of the application itself. So let's call those the same thing, and this is ignoring any additional cost for like proxies or load balancers or all of that. We're calling that a fixed unit, we're throwing it out for the purposes of this. Measured latency is the same as the app. Now you've added instrumentation. There's some amount of additional latency that's going to be introduced, we call that LI. So MW, that's the measured latency with instrumentation, is a sum of the application latency plus the latency caused by instrumentation. Okay, so we have two equations so far. The way to compute the percentage change, remember I said percentage changes in latency are lies, this is how you compute the percentage change after you've added latency, after you've added instrumentation.  Welcome to very basic math. Now we're going to substitute those other equations into our percentage equation. Okay, so we start by substituting M sub N with the application latency, then we substitute M sub W. Don't fall asleep on me, stay with me. With the sum of those two, we simplify it and we get an equation that looks very simply like this, straightforward inverse relationship. So the percentage change to your latency is 100 times the instrumentation latency divided by the original application latency. Okay, who cares, right? Why is that interesting? What does that matter? That means for a fixed instrumentation cost, let's say that I really optimize my instrumentation, I get it all the way down to one femtosecond, right? Doesn't matter what the unit is, one microsecond. For changes in LA, as you drive your application latency down, meaning as your application gets faster, the percentage change goes up. Let that sink in if it hasn't already. I know it's simple math, but if you're only talking like median latencies and you have a very fast microservice, which all of us do these days and it performs very well, any instrumentation, if you want to spin that as a change in percentage of latency, will go up significantly with an application with very good performance. How few we got there, okay. Let's take a concrete example. Two apps, app one, app two. App one is very fast, fine-tuned, three millisecond mean latency. App two, a little bit slower, but I think a lot of us run apps that perform at 100 milliseconds, and then we add instrumentation, picked an arbitrary number of two milliseconds. That increases the total latency in app one's case to five milliseconds. In app two, all the way up to 102, and if you look at the percentage change, who's complaining more, right? The person operating app one or the person operating app two, they see very different things. And just visualized as a percentage here on the vertical axis, you can see that red is a huge chunk of app one. It's almost nothing. Person running app two doesn't care about that. All right, how are we doing on time? Workload is independent, sorry, overhead is workload independent, or workload dependent, sorry, and distracted by time up in here, got a lot to go through still. What this means is like your overhead will change as your workload, as your request count, as your throughput, as your concurrency, as your time of day changes. All of those things impact the latency, sorry, it impact your overhead. And user input itself, right? Every service that takes input from a user which almost or an external source, almost all of them do, that's also going to incur changes, or you are subject to that input changing your performance characteristics of your instrumentation, therefore your overhead. All right, other things that cause it, we touched on these real quickly. Data volumes, for example, a service that generates a thousand traces is gonna have probably a higher overhead than a service that only generates maybe a couple of traces. All right, if you think that you have a problem with overhead, at the end of the day, you have to measure it yourself. You just have to. You can't just sample a couple of things or reduce it down to a mean latency and then say, oh, this is my overhead. Actually calculating the overhead for your application is tricky. And here's a couple of quick notes about that. When you test, you gotta make sure that you control your environment. You have to use data that's similar to your production workloads. In an environment that's similar to your production. And when you do that, you wanna be comparing. So before adding instrumentation, after adding instrumentation, you wanna be comparing apples to apples there. And so controlling the environment means trying to isolate your hardware as much as you can, even if that doesn't sometimes look like production. I know that's a contradiction, but, and then purge your database, do a warm up cycle. If you don't, if you have environments that have JIT or anything, they're going to be impacted if you don't do a warm up cycle. And it won't be a fair test. It won't be a fair comparison, rather. All right, and this is really important. This is not, when you're trying to measure your overhead for instrumentation, this is not the time to do a heavy stress test. Like running at max capacity is going to give you wildly varying results and it will be very hard to get repeatable outcomes in most languages. All right, once again, let's say that you do have problems with overhead. What can you do about it? You've measured, you've tested. What's the very first thing you can do? Well, maybe do nothing, right? Like, yeah, it's good enough. Yeah, we could save a few pennies, but maybe it's okay. Maybe the time spent testing, optimizing tuning, maybe it's not worth it. So this is the shortest, easiest path. If you can do this, it's probably the least amount of engineering. All right, now that you've measured, you've tested, you have quantified your overhead. What do you do about it? Okay, step two, remove any signals that are not helpful. If you're primarily looking at tracing to get a better understanding of what your environment looks like and how services talk to one another, maybe you don't need these logs, right? This looks like a lot of log volume. Maybe you can turn that off. Upgrade your instrumentation. If you haven't done so in the last, oh, I don't know, month, six months, year, I know a lot of people have not, they just deploy it once, right? They never upgrade their instrumentation. Well, I can tell you firsthand that open telemetry engineers are working really hard around the clock to make instrumentation more performant. And if you're doing yourself a disservice, if you don't upgrade. All right, sampling is a thing that exists. I'm not gonna go into too much detail here, but it's a way to throw out some of your traces before you have to put them on the wire. There are different forms of sampling. All right, and step five, especially like in like a runtime like Java where we have 100 different instrumentations that could be applied, some of those you may not be interested in the telemetry coming out of them and you can just turn them off. And that will reduce the amount of computational overhead, memory overhead. And then I think finally, just a word of warning about manual instrumentation. I know that not everyone uses auto instrumentation. So what ends up happening sometimes is you have engineers who got paged once and therefore go into the code back on Monday and they just start sprinkling manual instrumentation code like everywhere because they don't wanna get paged again. And if they do, they wanna have like a very detailed record of like all of these things that happened. So they're targeting this anomalous case with like liberal sprinkling of manual instrumentation. And that's fine. I just think it has to be used carefully and you have to remember to pull it back out. So if you're an operator and you're looking at some overhead, you also need to know what your developers might have put in there on themselves, like what kind of instrumentation they have added. So just be wary, know that that's a factor that can play into it. With that, I'm going to end. Thank you for listening. I think we might have a couple of minutes for Q and A. So let's do that if people are into it. Great talk, thanks. Quick question. How do I know the average of my overhead before instrumenting my code? Can you repeat the question? So you showed the math where I have the basis and then I add the instrumentation. Yeah, yeah. How do I know the basis? So like... Yeah, so the basis would be like in the case of like an HTTP service endpoint that you're testing. You wanna know the impact of that. You can measure it from the outside using a performance tool like K6 or LoadRun or any of those like tools that help you to test a service endpoint latency. So you test with no instrumentation first. I'm using a testing tool. Like generate a load and look at how long it takes for that service to handle those. Awesome, thank you. Yeah, yeah. Other questions, don't be shy. We're all friends here. Come on up. Hey, there we go. Okay, so I have one. I'm coming from the serverless community and sometimes the overhead is much bigger than what you showed. You showed two milliseconds, right? But in case of call starts in Lambda, you need to start the collector inside of it. So it's adding much more time to it. I know that there are a couple of new processors like decoupled and this kind of things, but what are your arguments to use in discussion with this kind of serverless folks? Yeah, so the question is what can I do if I'm running a serverless, especially if I have to like spin up a collector? Yeah, sometimes that startup cost can be very expensive.  I'm definitely not an expert in serverless or functions of service styles operational modes, but I would expect to have maybe longer living collector processes if that's where you're really having problems. In general, it's like 1% of the invocations are call starts, but people are overthinking it, I guess that's my opinion, right? But what are your opinion on that? Because I think that we are getting a lot of value, right? By instrumenting our applications, you can improve much further apart from like a hundred percentile in that case, right? But is there anything that is planned by the open telemetry to do? And for example, there's another way that you could do the instrumentation and for example, use just the endpoint for gateway collector and send the telemetry in there. But you have a problem that in case that gateway collector is down because of some reasons, you might get impacted even harder, right? And also in serverless case, you are paying for every second of invocations. So it might pile up quite nicely. Yeah, there's a lot to unpack in what you just said. So I appreciate that. Yeah, if you have 1% cold starts, I think you're doing pretty okay.  And yeah, so the question around is open telemetry doing something like this? I'm not aware of it. I think they probably are. And this might be a good question or a good thing to ask of the serverless community. Good presentation, thanks. Thanks. Is there a way to measure the overhead of each instrumentation library from the Java agent? We don't have that yet. We really want this. Also nice to meet you, by the way. Yeah, no, this has been, this has been brought up a couple of times and I would love for people who, smart people that might have ideas on how to do this, right? Because we have in the Java agent literally like a hundred instrumentations and not all of them get applied, but the ones that do. It's hard to decompose like an attribute like of the overhead for a given call for each instrumentation that was in play. What is the relative weight of their overhead? Yeah, we do not have that. Yeah, good question. You mentioned to Android, what's the open telemetry stands currently on thinking about the difference between like human readability and efficiency of your transfer protocol for things like mobile where that's sort of at a premium? A little bit of a change of subject, but yeah, I think the idea is to keep it small, especially in mobile and like by using things like protobuf, the idea is to not have to incur some expensive marshaling. So yeah, does that answer your question? Okay. All right, if there's no more questions, we'll end it there. Thank you. Thank you, Jason.


Hi everyone, Joe for jaspyscasebrakes.com coming at you with a Brake King Brake. This is 2021 Brake King Premium Edition Multisport One Box Random Letter Brake Number One. At the end of the break with a different dice roll, $3,000 football mixer spot being given away. Pretty good odds too because we only sold 18 spots. So you've got a chance at some of this nice stuff here from Brake King plus you have a chance at that and at some better odds than some of the 32 spot fillers that we have on the site. For the letters we're going to go by the first letter of their first name and there's all the letters right there. So actually that example is not correct so ignore that example but it's first letter first name. So there's all that right there. Big thanks to everybody here for making this happen and there are the letters right there. Go ahead and roll it and randomize it one and five six times for names and letters. Your names first. One, two, three, four, five, and six and final time, good luck. Jimmy down to Adam, let's highlight that again, one and five six times for the letters one, two, three, four, five, and six. We got T down to S. Alright, Jimmy with T, Robert with E, Sean with A, D, B, Derek with P, Sean with C, Nick with F, Colin with W, John with R, Derek with the combo letters, NK, Brian with L, Daniel with J, Colin with M, Daniel with G, Derek with H, and Adam with S. Let's sort by column B, alphabetically by letter and remember we're going by the first letter of their first name. So there you go, first letter of their first name and it's a multi-sport break as well. So I'm going to pause the video, when we come back we're going to see if there's any trades and then we'll have the break. Stick around, BRB. Alright, welcome back. I just unpause the video really quick just because we're going to select the box right here while people are still considering trades. I also lost my mind here. It is first letter of their last name, I don't know what I'm doing, losing my mind. First letter of their last name, so if it's Killian Mbappe it'll go to M, right? If it's Dominic Calvert-Lewin, Calvert-Lewin's his last name, it's C, so on and so forth. However it appears in the card, that's what we're going to do. Alright, let me flip screens just for a second while you're still considering trades. Here's the case right here. We're going to pop that open. There's three boxes in this case. A box, let's try it open here. If it's Kaka, yeah, it's K. If it's Pele, it's P. What are some other weird names? If the card just says Ichiro, it'll be I. If the card gives him his full name, Ichiro Suzuki, it'll be S. We'll cross that bridge when we get there. So here's what I'm going to do. I'm going to select one die, I'm going to select that one, and we'll go 1, 2, 3, 4, 5, 6 on the dice roll. It's just a one box break. And it's 6. 1, 2, 3, 4, 5, 6, so it's the bottom box. Now this we will mark with X's right here. So the next break will be, you'll know it's from the same case. I actually don't think there's any trade, so maybe I'll just roll on the video. Just keep rolling. Right? No trades? All right. So let's officially close the trade window. So TWC trade window. If it's Steph Curry with a K, Derek, yes, it would go to you. The professional bowler, Steph Curry with a K, I don't know if there's a dark darts player, pro darts player, Steph Curry with a K.  So there's three carts per box in here, it'll focus up, right? There it is. All right, reminder to me mostly. First letter, their last name. All right, so once again, thanks everyone for getting in on the action. There's the final printout. I don't have them covered up. So first one out of the gate, oh, also Junior's not his last name, okay? So just a reminder, here's PJ Washington Jr., it's not going to go to J. Washington Jr. is his last name. That's PSA 10, PJ Washington Jr. And that will go to W, Colin with that one. Nice, PSA 10, not bad. PJ Washington's got some nice upside. We've got another graded card. Oh, I've heard of this guy. This is pretty good. PSA 7, Kobe, wow, 1996, Fleer Metal Basketball, Kobe Bryant. That is awesome. Kind of young he looks there, RIP, that is pretty sweet. Letter B, that's going to be for Sean, there you go. And the third and final one, oh, is also graded, wow. Letter B, Joe Burrow, PSA 10, Purple Shock from Donner's Optic, I think those are exclusive to the Blaster Boxes. So another one for Sean M with the letter B, and that was Last Spot Mojo as well. 70% of the time, Last Spot Mojo hits 100% of the time. We'll load up another one of these boxes, so think about it, an opportunity to get the nice cards out of here, and a 1 and 18 chance, great odds there are 1 and 18 chance to get a $3,000 mixer spot. So let's do that. New dice, new list, let's gather everybody here. Let's roll it, let's randomize it, 403 lucky seven, well lucky for one person, but lucky seven times, 403. And Montauk gets it, one, two, three, four, five, six, and seventh and final time. After seven, Colin, there you go, congrats to you Colin, we're going to see you in that 48 box football mixer. Thanks for watching everybody, Jaspy's Case Breaks.com.


The National Youth Service Corps NYSC has organized a workshop for employers to exchange ideas on operations and enable an efficient working environment for core members. Plus TV Africa Angozika HHC, who monitored the employer's workshop in Lagos, tells us more. The 2021 edition is themed optimizing the NYSC core employer's partnership for national development in the context of new normal. The Lagos State NYSC coordinator, Edwin Megwa, who was represented by Esther Otoyo, drew the attention of the participants to some shortcomings on the path of core employers which need to be tackled. Number one, delay in applying or not applying at all for the services of core members and expecting them to be posted. Two, increasing rejection of core members. Three, aiding core members to stage manage their own rejection. Four, on the utilization of core members. Five, delay in issuance of monthly clearance to deserving core members. Some employers share the challenges they encounter with core members and spoke on their expectations. The challenges we have is that usually they send someone from money sending someone the study business admin or sending someone the study diplomas. And our system is actually digital too. We just do most of digital marketing, not like the physical sales revenue too. So we really usually don't have where to fix the core members too. So we actually have challenges of oh, we don't want to reject, but if you accept here, we don't want you to be redundant. They expect them when they get there, like to meet up with their KPIs. Core members at the workshop explained why their colleagues want some employers to reject their deployment to place of primary assignments. Why some core members like necessitates their rejection? Maybe the company does not have an accommodation due to distance, like from where they stay to the company. Some of them, they feel like the company won't pay enough. Yeah, because if the company is paying them like enough money, I don't think anybody will look at distance. I mean, their transportation will be covered and all of that stuff. It is hoped that critical actions will be taken concerning all the issues raised at this forum. One of the highlights of the event was an award of recognition to the best employer of the year. For Plus TV Africa, Ngoziqa, oh, hi Jessie. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Here in my garage just bought this new Lamborghini here fun to drive up here in the Hollywood Hills But you know what I like a lot more than materialistic things Knowledge in fact, I'm a lot more proud of these seven new bookshelves that I had to get installed to hold 2,000 new books that I bought It's like the billionaire Warren Buffett says the more you learn the more you earn