The premise of Dave's talk: "Good monitoring changes people." Through his evolving experience with monitoring, Dave Josephsen realized he had been “carrying a misapprehension about what monitoring was and who it was for.” His prior experiences with monitoring were much like those of folks he nowadays meets at conferences: monitoring is terrible, alerts are flooding from everything, and the world is probably burning right now. Through observing all teams - ops, data engineering, design - interact at Librato, he realized that the purpose of monitoring isn’t creating alerts but asking questions. There is no “owner” of monitoring, as everyone has the ability to measure things and ask their own questions.
This lecture discusses loops and looping constructs in Java programming. The instructor begins by clarifying the proper use of casts when converting between data types. They then discuss the "loop and a half" pattern, where code is executed at least once before entering the loop. They demonstrate using a while(true) loop with a break statement to avoid duplicating code. Finally, the instructor shows how to draw a checkerboard using nested for loops, constants for the board size, and graphics rectangles. The key topics covered are casts, indefinite loops, the loop and a half pattern, and applying loops to a graphics example.
Time management for marketers: Don't get whacked out poo brainIan Lurie
This document provides time management tips and strategies for staying organized and productive. It discusses structuring work into projects, milestones, and tasks. Milestones represent deliverables with due dates, while tasks should each take less than 45 minutes and be planned daily. The document emphasizes measuring time spent on tasks for improvement, and using tools like Toggl to help automate routines and free up brainspace. It also recommends learning skills like Excel scripting to work more efficiently.
Time Management for Marketers - The MozinarIan Lurie
I did a mozinar today covering time management. These slides cover the tools, structure and tricks I use, as well as Adventure Time, nerdy games and various animals.
Design principles for building useful graph displays and visualisations for monitoring data. What goes into designing graphs, creating a good user experience and what other types of visualisations are appropriate for which situations?
This document discusses FreeSWITCH monitoring and provides an overview of monitoring basics, metrics, logs, alerting, and traditional and emerging monitoring solutions like SNMP, CACTI, Graphite, Prometheus, Sensu, and Grafana. It also introduces a new FreeSWITCH monitoring module called mod_prometheus that exposes FreeSWITCH metrics for Prometheus.
Next generation alerting and fault detection, SRECon Europe 2016Dieter Plaetinck
There is a common belief that in order to solve more [advanced] alerting cases and get more complete coverage, we need complex, often math-heavy solutions based on machine learning or stream processing.
This talk sets context and pro's/cons for such approaches, and provides anecdotal examples from the industry, nuancing the applicability of these methods.
We then explore how we can get dramatically better alerting, as well as make our lives a lot easier by optimizing workflow and machine-human interaction through an alerting IDE (exemplified by bosun), basic logic, basic math and metric metadata, even for solving complicated alerting problems such as detecting faults in seasonal timeseries data.
https://www.usenix.org/conference/srecon16europe/program/presentation/plaetinck
Brian Brazil is an engineer passionate about reliable software operations. He worked at Google SRE for 7 years and is the founder of Prometheus, an open source time series database designed for monitoring system and service metrics. Prometheus supports metric labeling, unified alerting and graphing, and is efficient, decentralized, reliable, and opinionated in how it encourages good monitoring practices.
This lecture discusses loops and looping constructs in Java programming. The instructor begins by clarifying the proper use of casts when converting between data types. They then discuss the "loop and a half" pattern, where code is executed at least once before entering the loop. They demonstrate using a while(true) loop with a break statement to avoid duplicating code. Finally, the instructor shows how to draw a checkerboard using nested for loops, constants for the board size, and graphics rectangles. The key topics covered are casts, indefinite loops, the loop and a half pattern, and applying loops to a graphics example.
Time management for marketers: Don't get whacked out poo brainIan Lurie
This document provides time management tips and strategies for staying organized and productive. It discusses structuring work into projects, milestones, and tasks. Milestones represent deliverables with due dates, while tasks should each take less than 45 minutes and be planned daily. The document emphasizes measuring time spent on tasks for improvement, and using tools like Toggl to help automate routines and free up brainspace. It also recommends learning skills like Excel scripting to work more efficiently.
Time Management for Marketers - The MozinarIan Lurie
I did a mozinar today covering time management. These slides cover the tools, structure and tricks I use, as well as Adventure Time, nerdy games and various animals.
Design principles for building useful graph displays and visualisations for monitoring data. What goes into designing graphs, creating a good user experience and what other types of visualisations are appropriate for which situations?
This document discusses FreeSWITCH monitoring and provides an overview of monitoring basics, metrics, logs, alerting, and traditional and emerging monitoring solutions like SNMP, CACTI, Graphite, Prometheus, Sensu, and Grafana. It also introduces a new FreeSWITCH monitoring module called mod_prometheus that exposes FreeSWITCH metrics for Prometheus.
Next generation alerting and fault detection, SRECon Europe 2016Dieter Plaetinck
There is a common belief that in order to solve more [advanced] alerting cases and get more complete coverage, we need complex, often math-heavy solutions based on machine learning or stream processing.
This talk sets context and pro's/cons for such approaches, and provides anecdotal examples from the industry, nuancing the applicability of these methods.
We then explore how we can get dramatically better alerting, as well as make our lives a lot easier by optimizing workflow and machine-human interaction through an alerting IDE (exemplified by bosun), basic logic, basic math and metric metadata, even for solving complicated alerting problems such as detecting faults in seasonal timeseries data.
https://www.usenix.org/conference/srecon16europe/program/presentation/plaetinck
Brian Brazil is an engineer passionate about reliable software operations. He worked at Google SRE for 7 years and is the founder of Prometheus, an open source time series database designed for monitoring system and service metrics. Prometheus supports metric labeling, unified alerting and graphing, and is efficient, decentralized, reliable, and opinionated in how it encourages good monitoring practices.
10 IMPOSSIBLE THINGS TO DO BEFORE BREAKFAST.DOCclive rosen
1) Marvin discusses how developing quality software is impossible because requirements cannot be fully defined or frozen given an unpredictable universe.
2) Key challenges include not knowing what users want, not understanding one's own mind or process, and not being able to predict all future factors that could impact a system.
3) Traditional software development processes and quality measures are also problematic since the actual process is unpredictable and quality cannot be defined or measured without knowing objectives.
How To Be A Real Developer In Two Easy Stepsnorthofnormal
Have some imposter syndrome? Worried that you aren't a *real* developer? You're in luck! There's an easy, anybody-can-do-it two-step process you can follow to conquer your fears and become a Real Developer. What are those two steps? Well...that's where it gets complicated. Come with Anne as she recounts her path into the world of software development, overcomes her fears, questions the nature of reality, and shows off a super cool Ruby script.
The document describes the creator's experience of getting fired and struggling to find a new job through traditional methods like resumes and networking. This led them to create JibberJobber, a career management tool designed to help users track networking connections, applications, and follow-ups in order to better manage their job searches and careers over time. JibberJobber launched in 2006 and has received positive feedback from career centers and coaches.
Steve analyzes Ari's DISC profile results from a questionnaire. Steve determines that Ari's adaptive style, or work style, is that of a task-oriented project manager focused on getting things done efficiently. Ari's top traits are high dominance (73), low influence (38), low steadiness (41), and high compliance (70). This creative pattern means Ari is driven, logical, flexible, and perfectionist about quality. Ari prefers focusing on tasks over people and can become impatient if others don't work as efficiently. The analysis provides insights that accurately reflect Ari's personality and preferences.
- Stephen Sisler is the founder of Behavioral Research Group and developed the DISC profiling system to analyze people's behavioral patterns based on four dimensions: dominance, influence, steadiness, and compliance.
- DISC profiling can provide insights into how people will behave in personal and professional relationships and leadership styles based on their underlying emotions and tendencies.
- Ari's DISC profile showed high scores in dominance and compliance, indicating a task-focused, results-oriented, and quality-conscious working style where he prioritizes productivity and control over interpersonal elements of a job.
This document discusses how people live their lives according to "scripts" formed from pressures during childhood that are often reinforced unconsciously. It provides examples of common parental scripts and scripts in marriage. The author explains that these scripts can be identified and changed. The document recommends identifying injunctions and attributions from one's past, writing down current scripts, rewriting desired scripts, and committing to living according to the new scripts rather than past patterns. The overall message is that people can recognize and stop unhelpful scripts to gain more control over how they live.
This document summarizes Adam Keys' presentation on "People Hacks" at OSCON 2007. It discusses how interacting with people is an important part of software development as it is a collaborative process. It provides tips for advocating ideas by getting people to smile and be in a good mood. It advises against negativity and criticism unless you know the person well. It also discusses dealing with "jerks" by having a zero tolerance policy for abusive behavior and removing toxic people from projects and communities.
- The instructor introduces the students' final assignment for the class, Assignment No. 7, which involves building a social networking application called "face pamphlet".
- For this assignment, students will create profiles for users that include attributes like a name, status, profile photo, and a list of friends. Profiles will be connected through reciprocal friend relationships.
- The instructor reviews some key aspects of social networks and how they will be modeled in this assignment, such as unique user names, updating profile attributes, and ensuring friendships are always mutual.
RubyConf 2022 - From beginner to expert, and back againmtoppa
"In the beginner's mind there are many possibilities, in the expert's mind there are few."
- Shunryu Suzuki, from "Zen Mind, Beginner's Mind"
The Japanese Zen term shoshin translates as “beginner’s mind” and refers to a paradox: the more you know about a subject, the more likely you are to close your mind to further learning. In contrast, the beginner’s state of mind is judgment free. It’s open, curious, available, and present. We’ll draw on examples of these mindsets from fields as varied as aviation and geology, and discover lessons we can apply to the world of software development.
This document describes a new algebra learning system called Algebra Warrior that is claimed to help students get better grades and achieve their dreams. It promises to be simple, fun, and effective where other programs have failed. The creator says they developed it after volunteering at a children's home and seeing students struggle with algebra. Algebra Warrior is portrayed as a breakthrough that will provide students an unfair advantage over their peers. However, a donation is requested to access the system and get ongoing support from the creator.
This document summarizes a lecture on programming methodology. The instructor begins by announcing that the first assignment is due and handing out the next assignment. They then do a "pain poll" where students indicate how long it took them to complete the first assignment, with most students taking between 2-10 hours. The instructor discusses the variability in time taken and importance of understanding concepts rather than just getting the right output. They then cover various programming concepts like input/output functions, arithmetic operators, order of operations, and type casting. An example program to average two numbers is discussed to illustrate some of these concepts.
Russ Unger’s new book Designing the Conversation: Techniques for Successful Facilitation (Voices That Matter) was discussed in the recent Business901 Podcast, Voices Matter: Are you helping the situation?. This is a transcription of the podcast.
This document summarizes Adam Keys' OSCON 2007 talk on "People Hacks". It discusses how People Hacks are about advocacy, persuasion and improving interpersonal skills rather than manipulation. It provides tips for interacting with others in open source projects, including giving criticism constructively, avoiding negativity, understanding other perspectives before advocating change, and moving minds gradually rather than pushing maximalist positions. The document emphasizes the importance of collaboration and interpersonal skills in software development.
The document discusses how principles from the book "All I Really Need to Know I Learned in Kindergarten" can apply to software testing. It provides examples of testers not sharing knowledge, reporting the same defects multiple times, and publicly criticizing others' work. The document advocates for testers to share information, play fair by not padding metrics, and give constructive feedback privately instead of public criticism. It also emphasizes the importance of collaboration, taking breaks, and finding wonder in one's work.
The production schedule outlines Andrew's plan to create characters, stories, settings and other elements for his creative project over six weeks. However, he anticipates potential problems like difficulty finishing stories, drawing characters, thinking of side characters, laziness and poor understanding of story writing. To address these, he may need to spend more time on tasks or combat laziness. Keeping a log of his process will help document any issues and solutions.
This document lists the most annoying office habits according to a poll. It details habits like not bathing before work, having an untidy desk, incessantly flirting, being sexist, talking loudly on the phone, refusing to flush public toilets, playing loud music, borrowing items and not returning them, overusing CC in emails, interrupting conversations, being on social media constantly, being late often, digging one's nose, eavesdropping on calls, giving unwanted advice, gossiping, getting drunk at office parties, taking excessive breaks, insisting on doing all tasks a certain way, and asking too many personal questions. The list aims to highlight behaviors that irritate coworkers.
Any good business relies on a couple of core processes. They are the anchor for daily operations, and help everyone understand what to expect of each other. Especially in the chaos of startup land, it's of utmost importance to build and protect your processes.
That doesn't mean that they cannot change. Any good process is scrutinized often to make it even better. What worked yesterday may not work tomorrow. Situations change, people change, tools change.
These are 5 of the core processes in our startup. They are not all our core processes, nor will they forever remain the same. We'd love it if you can help us improve our processes, and at the same take another critical look at your own processes.
You can always find us on Twitter: @FloownHQ
This document provides a summary of a talk about public speaking. The speaker discusses several key points about preparing for and delivering public talks, including:
1. Choosing a topic by selecting something you recently learned, doing a deep dive on a concept, or sharing a case study from your work.
2. Writing an abstract that is relevant, readable, engaging and clearly outlines what will be discussed.
3. Creating an outline to organize content and help write the talk, noting sections and bullet points under headings.
4. Additional tips covered include getting over the fear of public speaking by starting small and working up to bigger presentations, and how writing a talk helps sharpen storytelling skills.
The instructor is providing an overview of the student's next programming assignment to implement the game Breakout. They discuss handing out assignment details and code examples. The instructor also checks in on how long it took students to complete the previous assignment, with most students reporting under 10 hours. Then the instructor reviews key concepts around classes from the previous lecture like private/public variables and using getters/setters to access private data.
10 IMPOSSIBLE THINGS TO DO BEFORE BREAKFAST.DOCclive rosen
1) Marvin discusses how developing quality software is impossible because requirements cannot be fully defined or frozen given an unpredictable universe.
2) Key challenges include not knowing what users want, not understanding one's own mind or process, and not being able to predict all future factors that could impact a system.
3) Traditional software development processes and quality measures are also problematic since the actual process is unpredictable and quality cannot be defined or measured without knowing objectives.
How To Be A Real Developer In Two Easy Stepsnorthofnormal
Have some imposter syndrome? Worried that you aren't a *real* developer? You're in luck! There's an easy, anybody-can-do-it two-step process you can follow to conquer your fears and become a Real Developer. What are those two steps? Well...that's where it gets complicated. Come with Anne as she recounts her path into the world of software development, overcomes her fears, questions the nature of reality, and shows off a super cool Ruby script.
The document describes the creator's experience of getting fired and struggling to find a new job through traditional methods like resumes and networking. This led them to create JibberJobber, a career management tool designed to help users track networking connections, applications, and follow-ups in order to better manage their job searches and careers over time. JibberJobber launched in 2006 and has received positive feedback from career centers and coaches.
Steve analyzes Ari's DISC profile results from a questionnaire. Steve determines that Ari's adaptive style, or work style, is that of a task-oriented project manager focused on getting things done efficiently. Ari's top traits are high dominance (73), low influence (38), low steadiness (41), and high compliance (70). This creative pattern means Ari is driven, logical, flexible, and perfectionist about quality. Ari prefers focusing on tasks over people and can become impatient if others don't work as efficiently. The analysis provides insights that accurately reflect Ari's personality and preferences.
- Stephen Sisler is the founder of Behavioral Research Group and developed the DISC profiling system to analyze people's behavioral patterns based on four dimensions: dominance, influence, steadiness, and compliance.
- DISC profiling can provide insights into how people will behave in personal and professional relationships and leadership styles based on their underlying emotions and tendencies.
- Ari's DISC profile showed high scores in dominance and compliance, indicating a task-focused, results-oriented, and quality-conscious working style where he prioritizes productivity and control over interpersonal elements of a job.
This document discusses how people live their lives according to "scripts" formed from pressures during childhood that are often reinforced unconsciously. It provides examples of common parental scripts and scripts in marriage. The author explains that these scripts can be identified and changed. The document recommends identifying injunctions and attributions from one's past, writing down current scripts, rewriting desired scripts, and committing to living according to the new scripts rather than past patterns. The overall message is that people can recognize and stop unhelpful scripts to gain more control over how they live.
This document summarizes Adam Keys' presentation on "People Hacks" at OSCON 2007. It discusses how interacting with people is an important part of software development as it is a collaborative process. It provides tips for advocating ideas by getting people to smile and be in a good mood. It advises against negativity and criticism unless you know the person well. It also discusses dealing with "jerks" by having a zero tolerance policy for abusive behavior and removing toxic people from projects and communities.
- The instructor introduces the students' final assignment for the class, Assignment No. 7, which involves building a social networking application called "face pamphlet".
- For this assignment, students will create profiles for users that include attributes like a name, status, profile photo, and a list of friends. Profiles will be connected through reciprocal friend relationships.
- The instructor reviews some key aspects of social networks and how they will be modeled in this assignment, such as unique user names, updating profile attributes, and ensuring friendships are always mutual.
RubyConf 2022 - From beginner to expert, and back againmtoppa
"In the beginner's mind there are many possibilities, in the expert's mind there are few."
- Shunryu Suzuki, from "Zen Mind, Beginner's Mind"
The Japanese Zen term shoshin translates as “beginner’s mind” and refers to a paradox: the more you know about a subject, the more likely you are to close your mind to further learning. In contrast, the beginner’s state of mind is judgment free. It’s open, curious, available, and present. We’ll draw on examples of these mindsets from fields as varied as aviation and geology, and discover lessons we can apply to the world of software development.
This document describes a new algebra learning system called Algebra Warrior that is claimed to help students get better grades and achieve their dreams. It promises to be simple, fun, and effective where other programs have failed. The creator says they developed it after volunteering at a children's home and seeing students struggle with algebra. Algebra Warrior is portrayed as a breakthrough that will provide students an unfair advantage over their peers. However, a donation is requested to access the system and get ongoing support from the creator.
This document summarizes a lecture on programming methodology. The instructor begins by announcing that the first assignment is due and handing out the next assignment. They then do a "pain poll" where students indicate how long it took them to complete the first assignment, with most students taking between 2-10 hours. The instructor discusses the variability in time taken and importance of understanding concepts rather than just getting the right output. They then cover various programming concepts like input/output functions, arithmetic operators, order of operations, and type casting. An example program to average two numbers is discussed to illustrate some of these concepts.
Russ Unger’s new book Designing the Conversation: Techniques for Successful Facilitation (Voices That Matter) was discussed in the recent Business901 Podcast, Voices Matter: Are you helping the situation?. This is a transcription of the podcast.
This document summarizes Adam Keys' OSCON 2007 talk on "People Hacks". It discusses how People Hacks are about advocacy, persuasion and improving interpersonal skills rather than manipulation. It provides tips for interacting with others in open source projects, including giving criticism constructively, avoiding negativity, understanding other perspectives before advocating change, and moving minds gradually rather than pushing maximalist positions. The document emphasizes the importance of collaboration and interpersonal skills in software development.
The document discusses how principles from the book "All I Really Need to Know I Learned in Kindergarten" can apply to software testing. It provides examples of testers not sharing knowledge, reporting the same defects multiple times, and publicly criticizing others' work. The document advocates for testers to share information, play fair by not padding metrics, and give constructive feedback privately instead of public criticism. It also emphasizes the importance of collaboration, taking breaks, and finding wonder in one's work.
The production schedule outlines Andrew's plan to create characters, stories, settings and other elements for his creative project over six weeks. However, he anticipates potential problems like difficulty finishing stories, drawing characters, thinking of side characters, laziness and poor understanding of story writing. To address these, he may need to spend more time on tasks or combat laziness. Keeping a log of his process will help document any issues and solutions.
This document lists the most annoying office habits according to a poll. It details habits like not bathing before work, having an untidy desk, incessantly flirting, being sexist, talking loudly on the phone, refusing to flush public toilets, playing loud music, borrowing items and not returning them, overusing CC in emails, interrupting conversations, being on social media constantly, being late often, digging one's nose, eavesdropping on calls, giving unwanted advice, gossiping, getting drunk at office parties, taking excessive breaks, insisting on doing all tasks a certain way, and asking too many personal questions. The list aims to highlight behaviors that irritate coworkers.
Any good business relies on a couple of core processes. They are the anchor for daily operations, and help everyone understand what to expect of each other. Especially in the chaos of startup land, it's of utmost importance to build and protect your processes.
That doesn't mean that they cannot change. Any good process is scrutinized often to make it even better. What worked yesterday may not work tomorrow. Situations change, people change, tools change.
These are 5 of the core processes in our startup. They are not all our core processes, nor will they forever remain the same. We'd love it if you can help us improve our processes, and at the same take another critical look at your own processes.
You can always find us on Twitter: @FloownHQ
This document provides a summary of a talk about public speaking. The speaker discusses several key points about preparing for and delivering public talks, including:
1. Choosing a topic by selecting something you recently learned, doing a deep dive on a concept, or sharing a case study from your work.
2. Writing an abstract that is relevant, readable, engaging and clearly outlines what will be discussed.
3. Creating an outline to organize content and help write the talk, noting sections and bullet points under headings.
4. Additional tips covered include getting over the fear of public speaking by starting small and working up to bigger presentations, and how writing a talk helps sharpen storytelling skills.
The instructor is providing an overview of the student's next programming assignment to implement the game Breakout. They discuss handing out assignment details and code examples. The instructor also checks in on how long it took students to complete the previous assignment, with most students reporting under 10 hours. Then the instructor reviews key concepts around classes from the previous lecture like private/public variables and using getters/setters to access private data.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...Zilliz
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
20 Comprehensive Checklist of Designing and Developing a WebsitePixlogix Infotech
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
2. I’m dave
dave@librato.com
@davejosephsen
github: djosephsen
I’m Dave and I work on the Ops team at Librato. In fact you’ve caught me in a bit of a transitional period because
I’ve recently decided to move back to ops after spending two years as Librato’s developer evangelist, which has
been a fascinating role that’s given me the opportunity to really branch out learn many new things.
3. Thought Leader Power Moves
For example Here’s a shot of me doing an all male panel, which is just one of the many thought-leader power
moves I’ve perfected over the last couple years in my former role as developer evangelist.
4. Thought Leader Power Moves
I can also do that faux-earnest, touching my fingers together while wearing a blazer and pontificating at you thing.
That’s totally in my repertoire so if you’re ever in doubt of the validity of my argument I can touch my fingers
together and become super reasonable looking
5. • “Resource”:
•Human-being who works here
!
• “Lead”:
•Human-being who doesn’t work here
!
• “Content Marketing:
•Annoying people on twitter
!
• “Engagement”
•Tricking people into talking to you
I’ve penetrated the marketing team’s vernacular, so yeah.. that took two years, but I can definitely sit in those
meetings now and.. I mean I pretty much know mostly what’s going on I think.
6. Thought Leader Power Moves
git push -f origin master!
I can force-push master from a vendor booth. That was a huge achievement get in this role. By the way I’ve heard if
you force push master from an all male panel they have to make you CTO. Pro tip. But yeah the vender booth is like
a second home to me now. I’ve done quite a bit of venderboothing over the last few years
7. Graphing Na
Venderboothing
Here we are at twilio signal a few months ago. And something happened at signal I want to tell you about, because
it happens a lot in the course of my venderboothing endeavors where
8. Venderboothing
I’ll be there in the booth, you know, my fingernails lightly resting against one another. And I’ll be engaging with
leads, and filling our funnel top with branding, and this neckbeardy dude
9. will kind of slide up, and lurk. He’ll just stand there glaring at me as I do my booth dance, impossible to ignore, like
He’s like, heavy. I mean not literally heavy I’m not body-shaming him, I just mean he’s like… laden with discontent
you know?
10. Graphing Na
BLARG ANOMOLY DETECTION!!!
and after listening for a while he’ll just spontaneously interrupt by blurting out something like “WHAT ABOUT
ANOMOLY DETECTION!”. And by the way in every case this has been what my wife calls a “catestrophic
digression”,
11. Graphing Na
like this interruption will be so awkward and so rude that it will send people scurrying away from the booth out of
either embarrassment or genuine fear for their own safety. And I’ll want to run away too but not running away from
incredulous neck beards is another skill I’ve developed so instead
12. Graphing Na
I’ll don my thought leader cap and be like “what an informed and thought provoking question, Let me ask you,
what kind of monitoring tools are you using today?”
13. and inevitably, he’ll launch into this apocalyptic tale of woe, wherein he will describe the faustian hell in which he is
currently trapped. Like his companies product
21. Graphing NaTHOUSANDS OF
MAPI EMAILZ!!!
And of course they’re sending 5000 emails per day because unexpected state is basically always happening and of
course nobody is paying any attention to the emails.
22. Graphing NaTHOUSANDS OF
MAPI EMAILZ!!!
and usually by this point he feels awful and I feel awful so I’ll say something “like wow, that sounds awful it must be
a really frustrating and stressful environment for you, like I’m sorry to hear it. And he’ll be all”
23. Graphing Na
it’s fine…. and I’ll be like. Man. You sure? because that sounds really bad, like I sincerely want to just hug you right
now. Would you like a hug?
24. Graphing Na
And he’ll be like no really it’s fine, I don’t need a AAAHHH oh my god hug me. And we’ll hug it out and he’ll cry a
little bit, and then I’ll be like. You know what you should do? You should vi that .qmail-root file mister neckbeard.
You know?
25. Graphing Na
| cat > /dev/null && echo ‘emailz,1,g’ | /usr/bin/statsd
Throw something like this in there. Just dev null those messages and count them instead. I’m not saying that’s your
permanent solution or anything
26. Graphing Na
but i mean you don’t even know what that signal LOOKS like. You might be able to alert on simple message
volume, or the derivative, or maybe just seeing that line will TEACH you something about the behavior or rhythm of
your system.
28. Graphing Na
DO EEET!
And I’ll be like heck yeah mister neckbeard. Go giterdone, and he’ll leave happy and with a lighter heart. It’s a funny
story. But it’s also a true story. I’ve had this conversation at least 20 times. And today surrounded by all of you and
my librato teamies it’s easy to forget, but if I’m being honest?
29. This was me one job ago
I was this neckbeard. This was me. Not a long time ago either but like one job ago, I was him. And I more or less
knew everything about monitoring that I know now, and yet I couldn’t .
30. Graphing Na
#1
draw this line, any more than he could. And I can hear you like Really dave emails per second? I mean yes, of course
I could draw a line of emails per second, but then so can he. What neither of us could do is make that cognitive
leap of applying monitoring tools as a means of understanding system behavior independent of alerting. So this is
line number one I couldn’t draw.
31. Graphing NaSpoiler alert:
There will be 4 more
And I come across these pretty commonly these days where I’ll see some data that we’re using internally and be
like man.. I never could have drawn one job ago and I just kind of thought it’d be interesting to explore the reasons
why. Live on stage in front of a room full of visionaries.
32. I was carrying a misapprehension
about what monitoring was and
whom it was for
Because in every case the problem wasn’t a lack of technical aptitude, it was wrapped up in my beliefs and
expectations. In this particular case, the problem . The thing that’s causing our cognitive dissonance is that these
perl scripts are sending alerts already. So to us— to mr neck beard and I, it seemed like monitoring was already in
place. Box checked. Monitoring done.
33. Because to us monitoring the thing that made alerts happen. We had no means of describing an undertaking called
monitoring that was meaningfully discreet from alerting. That’s why monitoring is an ops thing. It’s about uptime. So
obviously ops owns it. So as an ops person the pattern was that we would install or inherit this thing
34. this, guard-dog-like entity. I would tell it where to sit, and it would bark whenever it felt like something wasn’t right.
35. And it was great at barking. It’d bark all day and night bark bark bark bark bark. And that sucked. so I thought,
maybe I should train it. So I’d put in a ticket to train it
36. Squirrel!
ZOMG SQUIRREL!!!
It’s RIGHT THERE!
YOUGUISE? SQUIRRELL!
but I’d never work the ticket because it was literally nobody’s priority but mine. I’d feel guilty if I worked on it
because it seemd self indulgent or I’d feel guilty if I didn’t because dogs sitting over there barking at squirrels all
night and it’s just embarrassing
37. But what about
squirrels?
and maybe eventually I’d get some time to take it aside and be like listen. Thread contention? Bark. Ice cream
trucks? NO BARK. But no matter what I told it, was never something that could help me out with stuff like these
perl emails because
38. Oh sure. Blame
the puppies Dave
ultimately our relationship was Prescriptive in the wrong direction. The dog was always telling me what I was
interested in, so the best we could ever hope to achieve was this on going negotiation about what to bark at how
much barking was enough barking, it always became about the barking
39. Monitoring is not FOR alerting
Here are two important things I no longer believe. These are the things that I think makes me different from mister
neckbeard. First, I don’t believe monitoring is for alerting. It’s not about uptime.
40. Nobody OWNS monitoring
Next, monitoring is neither my responsibility nor is it my burden. It’s not mine. not my pet. It’s a tape measure. It’s a
tape measure that I get to share with every engineer I work with.
41. Ops owns
Monitoring
Everyone
owns
Monitoring
I think if you’ve been listening to the real speakers, basically all the ones who aren’t me, you’ll find that this is the
probably most important underlying belief that differentiates them from mister neckbeard. People who run
effective monitoring infrastructure
42. believe we all get to ask questions. We all get to measure things. Not just ops, not just dev, not just DBA,
everybody who cares, gets to measure, and we all get to use the same tape measure, and it’s perfectly reasonable
to expect to get accurate, timely answers to our questions, and that’s what MONITORING is for.
43. Monitoring is FOR asking questions
It’s the infrastructure that makes it possible for everyone to understand system behavior. That’s what monitoring is
for me now, today. That’s how it works. Not because I installed or bought some particular collection of tools or
learned about percentiles, but exactly because my expectations have changed. Does that make sense?
44. You might be fascinated
with anomaly detection
because your input
signal sucks?
What If I Told You:
And mark was right when he said tools matter, but the tools are there today and yet many still suffer. Like you can
build the metrics infrastructure you need right now, that’s hard, and expensive but possible. Or you can buy it, and
that’s easier and expensive but possible. But to make either of those actually work, you still need to change the
people. That’s a lot harder. No combination of bleeding edge tools, no amount of fancy anomaly detection is going
to save mister neck beard until he understands that monitoring is not for alerting, and that measuring things is
everyone’s job.
45. Complexity Isolates
And Mr Neckbeard has another problem too. He’s embracing complexity. See? To him, those emails are his burden
to bear, his lot in life. They are the hand grenade upon which he will jump to save us all. And that belief isolates
him. It mires him in complexity, and he believes that’s fine. Let me show you what I mean..
46. #2
Here’s line number two that I couldn’t draw. And I can hear you saying Dave, that isn’t even a line. Like, you
literally had one job dude and the first line was disappointing and this isn’t even a line. But the line you aren’t
seeing here is actually a REALLY important … lack of a line.
47. because what you aren’t seeing here is the number of people currently using the Librato API who are being
throttled. So slight digression for context this is a pretty common problem when new users are wiring us up for the
first time and what things do they send?
48. All the things! Cheslock knows all about that you can ask him.. So rather than surprise people with a million dollar
bill, We catch unlikely new ingest throttling and we’ll shoot an email or whatever that’s like hey um, maybe dial that
back unless you actually want to pay us the GDP of uraguy every month.
49. and a whole bunch of metrics like this are physically mounted to the wall next to our support team, because they’re
the ones who are going to be there to help the user understand why they’re suddenly getting http500’s but the
interesting part is that these weren’t created for support. These metrics in fact, were originally put in place by the
engineer who implemented throttling to understand what that signal looked like
50. And this made me wonder like, how did this happen. How did first level support begin repurposing API metrics?
51. With whom shall I share
my bounty of hard-won
metric data?
Was there some cuddly API engineer who, in a spontaneous bout of altruism went to go
52. devops unicorn cuddle with the support team and make rainbow metrics babies of team spirit? That’s amazing, I
want to meet these api engineers, so I went to go talk to them and
53. they seemed like typical software engineers who exhibit the typical demeanor and mannerisms that one expects
software engineers to manifest. So yeah long story short I think what’s happening here
55. and if you’re not familiar, cynefin is a framework that helps us make sense of complexity
56. The idea is that you categorize the complexity you’re dealing with, and then you attempt to move from whatever
category you’re in, to the next less complex category until you hit
58. Things you need to move:
• Control
•Understanding
•Standardization
but my time at Librato has convinced me that cynefin can be an emergent property of effective monitoring systems.
By which I mean effective monitoring just sort of organically provides you a lot of the stuff you need to move
toward obvious
59. And I can hear you like really dave? emergent cynefin properties? You should have stuck with unicorn babies of
team spirit. Like do you even know what you sound like when you say shit like that? which, yes, I hear myself
60. Cynefin
(no, for reals tho)
I mean the processes line up pretty well. What you need to climb the cynefin ladder is pretty much what you give a
decent telemetry system to people who understand that their job is to measure things.
61. And this is a perfect example. Our support team was able to move from a very opaque and chaotic form of
complexity straight to obvious by repurposing monitoring data from another team, and today my friend Nik on the
support team can look up at that very real, very physical wall and say
62. “Behold. Throttled users!”, and go talk to them about it. That’s a first-level support team that organically
understands the concept of http return codes, and services oriented architecture, and API backpressure. Nobody
wrote them a manual for that. That’s Cynefin at work.
63. I could never draw lines like this… not-line. And the reason I couldn’t draw this not-line was because like mister
neck beard I thought that embracing complex things 5000 janky perl emails was my job. I thought complexity was
my lot in life,
64. Me dissecting somebody’s
javascript circa 2003
I was totally the guy who would sit down with that incomprehensible bowl of spagetti code that some mean-
spirited consultant wrote in 1997 and I’d be like I hate not understanding this. “I’m not leaving until this is
understood. I’m not going to a meeting, I’m not going to lunch, I’m not going home”. And managers would come
looking for me like did dave show up today. and my teamies would have to be like
65. don’t bug him he’s dissecting some janky code. This is a real picture, this is my boss steve at IBM global services
bringing me a sandwich. So For the millenials in the audience, this is actually what team spirit looked like in
corporate america in the late 90’s. But then once I had it figured it out I’d become the owner of that janky perl
forever. The only person who ever understood it and then people would be like
66. yo dave, that janky perl thing is broke again. Right? They’d dump it on me when it broke and that’s perfectly
rational, because why should they crawl down there with me? Why should I want them to?
67. Graphing NaEXPERIENCE
5000 JANKY EMAILS
pain hurts y'all. It’s painful, so embracing it just isolates you, even from other engineers, because there’s only so
much pain each of us can endure, we just can’t really go around willy-nilly embracing each others pain. It’s just not a
tenable scaling model.
68. But simplicity feels fantastic. Simplicity wants to be shared and celebrated. I should have always been working to
reduce complexity instead of just accepting it, but I never realized that my monitoring tools could help simplify
things.
69. I used to think this was about as simple as simple got. I used to make things like this when I understood something.
Well I still do I’ll draw a really complicated picture of the really complicated thing. I was so close, but I just never
took that next step. the one that was like lets
70. #3
Simplify that into something that isn’t painful to understand. This is line 3, and now you’re like dave that’s also not a
line, so not only are you 1 for three on following through with the click bait listicle title you sold us, line one was
super boring, and you sir, are a lying deceitful faud.
71. #3
so OK captain pedantic, here’s the line. I couldn’t have drawn it because I never had an amazing dashboard like this
beneath the lines I would draw
73. This diagram. the curator of those metrics, took this diagram and made it obvious making one row
74. Row Per SLB
for every SLB in that architecture diagram, which, if you think about it is an interesting way to simplify your
understanding of service ingress because what does every service have in common? a load balancer.
75. Latency
Availability Traffic
so for each load balancer lets break down a few golden signals and these are like, if any blocking outage happens
inside any of these services, you’re going to see it in one of these signals, it’s guaranteed. If you don’t see it in one
of these signals, then it’s by definition not a blocking problem.
76. #3
And I want to stress that again, the person who curated this view was not the person who wrote the instrumentation
to get this data. Different people, different concerns, and the monitoring system is enabling them to work together
to reduce complexity, and aid comprehension.
77. I never could have drawn that line over this amazing dashboard, I never realized I could use monitoring tools to
build bridges to help other people understand the pain I was experiencing.
78. Everybody gets to measure things
Nobody OWNS monitoring
And then one day I hire into this shop where everybody can measure things, and nobody owns monitoring
79. and all these people are building all this stuff, and they’re taking measurements as they go
80. And then other people get a hold of those signals and refine them, and cynefin happens
81. And bam, suddenly first-level support understands API backpressure. And I’m trippin out like three weeks ago I was
trapped in a perpetual
82. Srsly tho; squirrels.
Bark or don’t bark?
tire-fire with this clueless watch-dog and NOBODY cared. Like nobody even KNEW. I was alone with my bij despite
being surrounded by other engineers
83. #4
I’m sorry it’s just a stark contrast. Like, check out line number four here. This measures the storage latency
introduced by our API matching metric names to UIDs. Point being, this is subtle latency metric. Like I can’t
describe it to you in less than 15 words. But check this out,
84. <redacted>
An Ops guy named Benjo, is working with it. That’s pretty crazy right? I mean where I come from, in the tire-fire it’s
atypical for ops people to work with latency data that describes job execution inside the database. I mean in the
tire fire this is what we referred to as somebody else’s problem. But OK Maybe Ben’s just a really savvy guy.
85. <redacted>
But, wait benjo the ops person is not only wise to this intricate db latency issue but he’s correlating it back to
system metrics. Ok huh, that seems extraordinarily astute to me, I mean even if you have the domain knowledge
86. <redacted>
Wait hold on a sec, he is actually talking to Data Engineering about this? Ok, savvy, astute and brave. Or maybe he
just doesn’t know that data engineers are mean
87. <redacted>
<redacted>
woah, what? they’re actually responding and working together with him? And evidently so is the Front-End Team?
Like What in the actual HELL is happening here? How does Ben the ops guy have all this Data Engineering domain
knowledge? And why isn’t anyone being mean to him? Where are the passive-aggressive insults? The hostility and
mistrust I’ve come to expect from engineers working in other teams? I mean this is dev and ops, this is
88. This is DOGS AND CATS. LIVING TOGETHER. I’m SHOCKED. It’s Shocking!
89. #4
I’ve certainly never been able to draw lines like that. I never knew enough about what was going on around me to
even work with data like this. I mean this is a Line that literally bridge disciplines.
90. #4
Look, if you squint, you can almost see the bridge that this line creates, between
91. #4
Data Engineering and Operations. And again I can’t help but wonder how this happened. Is it possible that
effective monitoring can bring about cultural change?
92. #4
Because it looks to me like that’s what’s happened here. It looks like the combination of an effective telemetry
infrastructure, combined with people who understand that measuring things is their job, has ultimately changed
how people interact with each other in this shop. Good monitoring changes people. That’s kind of mindblowing.
93. #5
So speaking of culture how much time do I have, ok good, because this is the good part, Line number 5. So this is
a funny story about Bryan one of our integrations engineers, and this happened a few months ago now, and for the
record I publicly apologize in advance to Brian I’m sorry dude, if you’re watching for shaming you like this on the
internet, but in my defense.. it was pretty funny though
94. so what happened was, Bryan was working on making our UI faster. And up top he rolls out a change, and that
change? Makes the UI faster. So mission accomplished, good jorb Bryan you done it. And to be clear he’s graphed
the performance data. I mean job done, homework done, he HAS a graph showing the stuff becoming faster.. but
what he’s pasted in here
95. is not that graph. It’s the mouse over of the tooltip. like he drew the graph, moused over it, took a screenshot of
the tooltip of the individual datapoints, for a single polling interval, and then pasted THAT in channel. And for
context, not only does Brian work for a startup whose singular purpose is the drawing linegraphs depicting time
series data, but his Boss at the time is literally
96. Line graphs FTW
the inventor of graphite AND this conference. Basically he works at line-graph-co for the godfather of linegraphs.
And he’s basically just walked up to the godfather of line graphs like “Behold my assortment of individual
datapoints!” but wait.. it gets better..
97. And then he says… ignore the zeros! omg so amazing.
98. I mean look.. if we ignore the zero’s literally we have two values. Like Bryan, sit down, I think it’s time we had the
data-to-ink ratio talk bro. Once upon a time there was a man named Tufte…
99. And I also want to point out the time stamps here, because it’s only a matter of seconds before his team begins
expressing their confusion, like wait.. what?
100. Is me messing with me RN?
Like I can almost see Dixon at home, head tilted to the side, unsure if this is some kind of elaborate troll, he’s like
maybe everybody got together and agreed to not paste any line graphs in channel for the whole week. Which
actually is kind of a brilliant troll and also something we’d totally do, but no, this was all bryan
102. And I never could have drawn this line, because I’ve never had a team around me that actually cared this much
about what I was working on. If I came to someone with some amazing data that I was super proud of they’d look at
it like
104. but look at the love here, these people want to geek out on the data with you. They want to celebrate your win.
Not just in the fortune 500 goals and gift cards way, but by actually quantifying the y-axis of your success. They
want to comprehend your win so bad they are confused when they lack sufficient data to comprehend your win,
which I find astounding.
105. and at the risk of sounding campy I guess I just wanted to say I love mah teamies at Librato and I love all of you as
well, and I wanted to thank you for working to make effective monitoring happen in your shops, and building tools
to make it happen for other people. So, Sincerely, thank you, you make me want to come to work every day.
106. Questions?
@davejosephsen
And at this point the conference organizers have insisted that I allow you to ask questions but I have read the code
of conduct which has literally nothing to say on the subject of speakers shouting smoke bomb and running off stage
if they are confronted with a hostile question. SO that is a right I reserve.